This guide is for operators and specialist advisors who see procedures up close: quality consultants, ISO and safety auditors, operations and implementation advisors. You often know whether a client's procedures are maintained or merely filed. That knowledge is a reason to ask good questions, not permission to describe someone else's documents.
A revision trail, in plain terms
Each version of a procedure carries, at best, an identifier, an effective date, a description of what changed and why, the name of whoever drafted it, the name of whoever approved it, and a retained copy of the version it replaced. Many companies keep only the latest PDF in a shared drive. Others run a document control system that holds every approved version with its approval record. The difference between those two companies is the difference between a binder and a history.
Some industries keep trails because a rule asks for them. For drug manufacturers, 21 CFR 211.100 says: "These written procedures, including any changes, shall be drafted, reviewed, and approved by the appropriate organizational units and reviewed and approved by the quality control unit." The same section adds: "Any deviation from the written procedures shall be recorded and justified." OSHA's process safety standard, 1910.119, requires (in paraphrase) that operating procedures for covered processes be reviewed as often as needed to reflect current practice, with an annual certification that they are current and accurate, and that changes to procedures go through written management-of-change procedures.
A rule that demands approvals gives a company a reason to keep a tidy trail. That trail still proves nothing about the right to license it or whether anyone wants it, and linked records such as deviation logs can describe batches, incidents or named people that need care before anyone discusses them.
On the buyer's side, SourceX's technical page on SOP revision histories describes a revision history as the chain of approved versions plus the reason for each change: material that can support change-aware instruction grounding and evaluation items, and that cannot show whether the floor ever followed the revised text. That page is for suppliers and AI teams. This one is about the introduction.
Why the history, not the binder, shifts the conversation
Three things change when you ask about history rather than the current procedures.
- You need a different person. Whoever runs operations can describe today's binder. The document control or quality lead knows where superseded versions live, how approvals were recorded and what a migration may have dropped. The CEO still decides whether there is a conversation at all.
- Origins surface. A revision log can show the day a section was replaced with text from a manufacturer's manual, a client's mandated procedure or a franchisor's update. The current version reads as one document and hides those seams.
- Gaps show up. Purged superseded versions, a system migration that carried only current documents, blank change-reason fields: none of these is visible from the binder, and each changes how the company should describe its material.
Each shift alters what goes into the introduction, which is why the interview comes before any description.
The process-history discovery interview
Twelve questions in four rounds, asked of the document owner the CEO names. Every question is answered from memory or from the person's own knowledge of the system; none asks for a file, an export, a screenshot or a login.
| Round | Question | A useful answer sounds like | Stop or flag signal |
|---|---|---|---|
| Scope | 1. Which procedures have revision histories, for which sites or service lines? | About 300 procedures across two plants | Nobody can say where procedures live |
| Scope | 2. How far back do approved versions go, and in which system? | Every approved version since 2015, in the document control system | Only current versions survive |
| Scope | 3. Is the reason for each change written down? | A change description on every revision | Reasons exist only in people's memories |
| Authorship and approval | 4. Who drafts revisions? | Our quality and process engineers | An outside consultant drafted most of them |
| Authorship and approval | 5. Who approves them, and is the approval recorded? | Quality signs each revision inside the system | Approvals went by email nobody kept |
| Authorship and approval | 6. Do change-control, deviation or incident records link to revisions? | Each change cites a change-control number | The linked records describe named individuals |
| Imported content | 7. Do any procedures reproduce an equipment maker's manual or a software vendor's guide? | Two maintenance procedures quote a maker's manual | Most of the corpus is vendor text |
| Imported content | 8. Were any procedures written for clients, or handed over by them? | None; client requirements stay in contracts | Client-mandated procedures form the core |
| Imported content | 9. Does a franchisor, parent or licensor supply a base manual? | No, or yes with our own addenda kept separate | Own text cannot be told apart from the manual |
| Custody and limits | 10. Has the company or this material changed hands? | No ownership change since 2012 | An acquisition or carve-out left the decision-maker unclear |
| Custody and limits | 11. Has any of it been licensed for AI training before? | Never | Yes, or nobody is sure |
| Custody and limits | 12. Does the CEO know about this conversation and want it to continue? | Yes, the CEO asked me to talk to you | Not yet |
A single stop signal ends the round, not the relationship. Write it down with the date, tell the CEO what it was, and pick up again only if the facts change. Question 11 matters more than it looks: SourceX's process page lists, among the things a supplier confirms, that the data has not been licensed for AI training before.
When the interview is done, draft a five-line summary in plain words (scope, span, authorship, imported content, open flags) and send it to the CEO to approve before anyone else sees it.
Method note. The interview applies SourceX's screening page and process page, 21 CFR 211.100 and OSHA 1910.119, all checked on 2026-10-27. It records where a history came from and how it was kept. It does not test the quality of the procedures, whether staff followed them, demand for them or value; SourceX's review assesses relevance, and rights are settled there too.
Three revision trails, three different introductions (Illustrative)
Illustrative. The three firms below are generic, their facts are made up, and no result for any of them is implied.
| Check | Original work | Mixed third-party content | Uncertain ownership |
|---|---|---|---|
| Company | 180-person contract packaging firm | 320-person restaurant franchisee group | 140-person business process outsourcer |
| What the history holds | 240 procedures, every approved version since 2015, a quality approval and change reason on each | 90 kitchen and front-of-house procedures: 60 reproduce the franchisor's manual, 30 are the group's own local addenda | 410 client-specific procedures its staff wrote and revised under client contracts since 2017 |
| Interview flag | Question 7: two maintenance procedures quote a maker's manual | Question 9: a base manual from the franchisor | Question 8: procedures written for clients |
| Route | Introduce, naming the two quoted procedures | Introduce for the addenda only, if the CEO wants; the manual stays out | Hold until the CEO checks what the client contracts say about ownership |
| What review settles | Scope and relevance | Whether the addenda stand on their own | Rights first, then anything else |
Even one procedure can cross origins. One of the packaging firm's maintenance procedures has five approved revisions: A in 2015, B in 2017, D in 2022 and E in 2025 were drafted by its own quality team, while C in 2019 pasted three pages from the filling machine maker's manual. Every revision carries a quality approval. In the introduction it is described as company-written with one revision containing the maker's text, and the review decides what to do with that revision.
The outsourcer's case is the one to slow down on. Procedures written by the company's staff for a client's work may still belong to the client under the contract, and the screening page lists material that belongs to clients as usually not a fit. The client SOP change adoption inventory covers that record type in detail.
Who owns the binder, and who can open the conversation
The CEO decides whether the company discusses licensing and signs for it. The quality head, the document control manager and site managers answer the interview and may sponsor the idea internally; they do not authorize it. Outside rights holders, such as an equipment maker, a franchisor or a client, own their own text and are never contacted by the partner. If the company was acquired, the acquirer's CEO now decides.
SourceX's screening page names SOPs, internal knowledge bases, project histories and QA records among the original documentation it looks for, provided the company created the material and can license it without breaching client confidentiality, employee privacy or third-party contracts. The company also needs a full-time headcount that reached 50 or more at its peak, contractors excluded, and a documented operating history. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.
The SOP and runbook dataset page and the introduction checklist for SOPs and runbooks describe the material from SourceX's side. For an owner preparing procedures ahead of a sale, documenting SOPs before selling a business is the nearer guide, and submittal revision history shows the same versioning logic in construction.
Keeping the interview bounded
The interview is a conversation about documents, never a tour of them. Ask nothing that requires the document owner to open, export or show you a record. Do not ask for deviation or incident details, even in summary. Do not tell SourceX that a company is "compliant" or "audit-ready"; you are not in a position to say so, and it is not what review needs. And do not tell the company its history will be licensed. The honest line is that SourceX looks at it and decides.
Credit is decided from dated records rather than from the work you did. You sign the SourceX Channel Partner Agreement before submitting anything. The earliest valid introduction of a company that is new to SourceX, made inside the 90-day attribution window, earns credit once the company files a verified application. If the company already had an application, a relationship or an earlier valid introduction with SourceX, it goes to duplicate review and is not credited to you. More guides on neighboring records sit in the guides hub.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
Once the CEO has approved a summary of the company's revision history and wants the conversation, register as a partner, recheck the company against who qualifies and read the program terms before submitting the introduction.