SOPs, runbooks and playbooks
Standard operating procedures, runbooks and playbooks written by operating teams, with version history, owners and the systems each step touches. Labs use them to train agents that follow multi-step procedures and to build tasks grounded in real business processes.
What a record contains
One procedure: title, purpose, steps with decision points, linked forms or systems, the owning role, review dates and earlier versions.
| Field | What it holds |
|---|---|
doc_id, title | Pseudonymous ID and title |
department | Owning team |
steps[] | Instruction, system used, decision points |
owner_role | Role, not a named person |
versions[] | Dates and changes |
{
"doc_id": "SOP-212",
"title": "Claims intake: missing police report",
"department": "claims",
"steps": [
{"n": 1, "instruction": "Check the claim for a report number in field 7.", "system": "claims_core"},
{"n": 2, "instruction": "If missing and loss > $5k, request the report and set status Pending-Docs.",
"decision_point": true}
],
"versions": [{"date": "2023-08-01", "change": "Raised threshold from $2.5k"}]
}How AI labs use it
- Procedure-following agents
- Real steps, decision points and exceptions.
- Grounded task generation
- Turn real procedures into agent tasks with known correct steps.
- Policy question answering
- Questions whose answers depend on the current version.
Typical preparation requirements
Agreed with the supplier before any work begins. Typical requirements include:
- Security-sensitive procedures such as access, keys and incident response reviewed or excluded
- Names replaced with roles
- Third-party vendor manuals excluded
Every dataset has a documented owner and confirmed licensing rights. See data governance on sourcex.si.
What makes a strong package
- Versions over time
- Procedures linked to the tickets or tasks that used them
- Regulated domains such as claims, billing and compliance
Compared with public datasets
Public sets such as TechQA and doc2dial are useful references, but limited as enterprise training data. The documents and knowledge category page compares them with licensed data.
Who typically holds it
- BPOs
- Healthcare administration teams
- Insurers
- Logistics companies
- Field-service companies
Know a company like this?
Introduce the company to SourceX. If its data deal closes, you can earn up to $100,000 in referral fees, paid after the buyer accepts the data and SourceX receives payment.
Refer a companyQuestions
Why do versions matter?
Versions show how procedures changed after mistakes or new rules, which helps agents learn to use the current one.
Need this data for a model?
Describe what you need: domain, volume, history, format and licensing terms. SourceX looks for companies that hold it and can license it.