Skip to content
Outrich Data

Data type

License your standard operating procedures for AI training

Standard operating procedures your company wrote and owns can usually be licensed for AI training, because they describe work and say little about people. Outrich Data is the direct buyer: it checks authorship, removes names, client references and security-sensitive steps, and pays you for a licensed copy. You approve each package in writing before delivery.

What counts as sops

A standard operating procedure is the written version of how a job gets done at your company. It lists the steps in order, the tools and forms used, the checks at each stage, who may approve an exception and what to do when something goes wrong. Most companies of any size hold hundreds of them: work instructions, runbooks, checklists, quality procedures and onboarding guides.

The useful archive is wider than the current approved version. Superseded revisions, change logs and the reason a step was added after an incident all count. Procedures a consultant or franchisor supplied, industry standards saved alongside your own files, and procedures you maintain for a client under contract are not yours to sell and are excluded.

Why AI labs want it

Procedural knowledge is thin in public text. The web explains what a purchase order is, but not the exact steps one company follows to approve it, or the point at which a second signature is required. AI labs building models that plan and complete tasks need examples of real procedures with ordering, conditions and exception paths.

Revision history adds a second signal. When version four adds a verification step that version three lacked, the pair shows a model how a process is corrected. Procedures that can be matched to the logs or tickets produced by following them are more useful still, because a lab can compare the written rule with what happened.

Removed before licensing

What comes out first.

  • Names, initials and signatures of authors, approvers and process owners
  • Client, supplier and vendor names written into steps
  • Passwords, door codes, system URLs and admin paths included for convenience
  • Security procedures whose disclosure would weaken a live control, such as alarm, vault or fraud-check steps
  • Screenshots that show real customer or employee records
  • Third-party standards, vendor manuals and franchisor material copied into the document
  • Phone extensions, personal mobile numbers and on-call rosters

Data title search

What gets checked.

  • Authorship. Confirm employees wrote the procedures in the course of their work. Consultant-written procedures depend on the engagement terms and may need an assignment.
  • Franchise and licensed methods. Operations manuals from a franchisor, a software vendor or a certification body usually stay that party's property.
  • Client-specific procedures. Playbooks written for one client's account often fall under that client's confidentiality terms, even when your staff drafted them.
  • Standards content. Text quoted from ISO, ASTM or similar standards is copyrighted by the publisher. Your own procedure built to meet the standard is a separate work.
  • Trade secrets. For processes you treat as trade secrets, ask counsel how a license should be structured so that secrecy measures stay in place, or hold those procedures back.

Who signsThe COO or head of operations usually sponsors it, since the procedures describe how the company runs. The general counsel approves the license, and the quality or document control lead runs the export.

Value

What moves the price of sops.

FactorEffect on value
Revision historyProcedures with dated versions and change reasons are generally worth more than a single current copy.
Exception handlingSteps that say what to do when a check fails are scarcer and more instructive than a clean happy path.
Specialist domainProcedures for regulated, technical or physical work are thinner in public data than general office routines.
Link to execution recordsSOPs that can be matched to the tickets, logs or forms produced by following them attract more interest.
In active useEvidence that staff follow the document, such as sign-offs or training records, separates working procedures from shelfware.

Questions

Licensing sops: what companies ask.

Our SOPs are our competitive edge. Does licensing them give that away?
It can if you license the wrong ones, so selection matters. Most companies would hold back the few procedures that carry real trade secrets and offer the routine majority. License terms limit use to training and evaluation. Decide with counsel which processes to exclude before approving a package.
Do outdated procedures have any value?
Yes. Old versions show how a process changed and why, which is useful in its own right. They should be labeled as superseded so a buyer does not treat a retired step as current practice.
A consultant wrote half of our procedures. Can those be included?
Check the consulting agreement. If it assigned the work product to your company, they can usually be assessed with the rest. If it only granted you a right to use the material, the consultant's consent is needed or those documents are left out.
Our SOPs are full of screenshots from live systems. Is that a problem?
Screenshots are reviewed separately from text. Images that show customer or employee records are redacted or dropped, and some vendor agreements restrict sharing images of their software. Text steps usually survive even when the screenshot does not.

Find out if your data qualifies.

Eleven questions, about five minutes, no call required. You get an answer on screen and a written follow-up.

esc