--- title: "SOP Coverage: The Gap Between the Written Procedure and the Process That Actually Runs" description: "SOP coverage is measured not by the number of procedures but by how much of the critical process set is written, owned, measured, and evidenced by records. In the typical company, coverage is densest in low-variability work and thinnest where judgment is required, and this asymmetry reaches valuation through earn-out, escrow, and key-person structures rather than through price." url: https://www.beirek.com/en/blog/sop-scope-operational-due-diligence canonical: https://www.beirek.com/en/blog/sop-scope-operational-due-diligence published: 2026-05-17 modified: 2026-05-17 category: "Operations & Processes" category_url: https://www.beirek.com/en/blog/category/operations-processes language: en-US reading_time_minutes: 8 publisher: BEIREK LLC publisher_url: https://www.beirek.com license: "© BEIREK LLC — citation with attribution and link permitted" keywords: ["SOP coverage","operational due diligence","process documentation","earn-out and escrow structuring","key person dependency","representation and warranty insurance"] topics: ["Investment readiness and valuation review","Operations and process governance","Transaction structuring and post-closing risk allocation"] alternate_language_url: https://www.beirek.com/tr/blog/sop-scope-operational-due-diligence --- # SOP Coverage: The Gap Between the Written Procedure and the Process That Actually Runs > **In short:** SOP coverage is measured not by the number of procedures but by how much of the critical process set is written, owned, measured, and evidenced by records. In the typical company, coverage is densest in low-variability work and thinnest where judgment is required, and this asymmetry reaches valuation through earn-out, escrow, and key-person structures rather than through price. *There is no reliable relationship between the volume of a procedure set and the auditability of an operation. What matters at the review table is not how many procedures were written, but whether the processes that actually determine margin and delivery schedule are documented, owned, and evidenced by a record.* --- In the opening days of an operational review, the request for the procedure set tends to produce a recognizable sequence. The index that arrives is longer than expected, the folder structure is orderly, and the approval boxes on the cover sheets have been filled in. The reviewing party does not read the index end to end. It selects the three or four processes that actually determine margin and delivery schedule — who is authorized to grant a discount above a defined threshold during bid pricing, on what evidence a new supplier enters the approved list, at which point a deviation in the production or service flow is halted and at which point it is signed off and allowed to continue — and looks for their written counterparts. For those three or four, either no counterpart exists, or what exists is a single page drafted three years earlier for a certification audit and untouched since. The distribution of coverage displays a consistent slope wherever it is observed. Procedural density is highest in the work with the least variability and the most predictable output, and it thins out precisely where judgment is required, where exceptions are frequent, and where the cost of an error is greatest. The same asymmetry surfaces the moment ownership is raised. Asked how a particular process runs during a week when the person responsible for it is on leave, the answer is typically a name rather than a document; and where a second name is offered, it usually rests on that individual having handled the same work at some point in the past, not on a defined handover routine with a record behind it. The organizational chart shows a function, the operating reality shows a person, and the two are not interchangeable to a party pricing continuity. The mechanism underneath this distribution is not neglect but an asymmetry of timing. Committing a process to writing costs something today, and it is paid out of the most expensive hours in the organization, namely those of the people who run the process well enough to describe it. The return is collected only when an event occurs: a key individual departs, volume steps up, a customer complaint escalates into a contractual dispute. Since no such event appears on the current quarter calendar, deferring documentation is rational in the short run. The difficulty lies not in the shortcut itself but in its persistence after the conditions that justified it have changed. Tacit knowledge that travels adequately across ten people does not travel across sixty; yet the documentation decision continues to be made with the cost intuition formed during the ten-person period. A second mechanism derives from the nature of expertise itself. The person who knows a process best, when asked to describe it, records the steps and omits the judgment. What gets written is an account of the normal flow, whereas the cost of an operation accumulates not in the normal flow but in the handling of exceptions: which deviation is tolerable, at what threshold work stops, in which circumstances the customer is notified in advance rather than after the fact. The expert assumption that the reader shares the same baseline — the curse of knowledge, the difficulty of reconstructing what it is like not to already know something — turns the omission from an occasional oversight into a systematic one. The result is a body of documents that passes the existence test and collapses under the implementation test: the procedures are present, but they are not what governs the daily decision. A third mechanism concerns how scope comes to be shaped at all. A substantial share of procedures originates from two triggers, an incident that has already occurred and an audit imposed from outside. The first builds coverage around accident history, which leaves risks that are probable but not yet realized entirely unwritten. The second builds coverage around the clause list of a standard, which produces documents answering the auditor question set rather than the internal logic of the work. In both cases the resulting map overlaps only partially with the company actual risk map, and the non-overlapping portion is, with some regularity, exactly the portion examined in a transaction review. Coverage assembled in this manner can be extensive in page count and thin in precisely the places where a buyer allocates its own attention and its own diligence budget. The channel through which this gap reaches valuation is, more often than not, something other than the headline multiple. Where a buyer observes weakness in the ownership and continuity dimensions, the typical response is to restructure rather than to reprice: a larger portion of the consideration is placed into an earn-out, the escrow percentage and its release period are increased, retention and consultancy undertakings are sought from key personnel for the post-closing period, and the transfer of specified processes is added to the conditions precedent. Taken together, these adjustments produce an outcome in which the nominal price is preserved while the seller cash receipt is deferred and the underlying risk remains on the seller side of the table. The institutional cost appears here not as a discount but as a collection schedule and a risk-bearing obligation. The second channel is measurement. Where deviation rates, first-pass yield, rework hours, and the results of compliance checks are not recorded, the effect of volume growth on unit cost cannot be modeled by either party. In that situation the buyer constructs the growth scenario on its own assumptions, and those assumptions are conservative in a predictable way; a claim that the current margin will hold at scale carries little evidentiary weight for as long as the burden of proof sits with the seller. The same absence keeps quality costs invisible. Rework, warranty provisions, returns, and delay penalties, to the extent that they remain dispersed across income statement lines rather than gathered and attributed, cannot be separated into what stems from a repeatable process weakness and what stems from isolated events with no recurrence probability. The third channel is post-closing cost, and it is generally the last to be recognized. Where a business line is carved out of a group and sold, thin procedural coverage translates directly into a longer transitional services arrangement; the monthly service fee the buyer pays, together with the continuing dependency that fee reflects, compresses cash flow through the first year after closing. On the credit side, undertakings relating to operational continuity are, in the absence of a documented structure, balanced by tighter reporting conditions and shorter certification intervals. In representation and warranty insurance, the exclusion of areas with documented weakness from policy coverage is an ordinary underwriting practice, and that exclusion converts the exposure from an insurable item into one carried on the seller balance sheet for the duration of the survival period. The intervention that neutralizes this tendency is not the writing of more procedures but the reordering of coverage, and a structure that works has four separable components. The first is a process inventory ranked neither alphabetically nor by department but by the product of error cost, frequency of recurrence, and dependency on a single individual, with the coverage decision taken against the upper band of that ranking. The second is the attachment of an owner, an effective date, and a review interval to each procedure, with ownership deliberately separated from line management so that deviation approval rests on a defined authority threshold rather than personal discretion. The third is the design of the record a procedure generates as an asset distinct from the procedure text. The fourth is the placement of exception handling in the body of the document rather than in its annex. The BEIREK contribution in this area concerns the construction of a record chain and a review rhythm rather than the production of documents. We extract the process inventory in risk-ranked form, attach a single owner and a defined decision threshold to every process in the upper band, place deviation records on a weekly review cadence, and make the output of that cadence a standing item in management reporting. The document set that enters the data room is then assembled not around procedure texts but around the signed forms, deviation logs, and compliance check results those texts have generated over the preceding twelve months, since what the reviewing party seeks in the implementation dimension is not the existence of the procedure but its trace. Transferability is tested not as an assertion but through observation of a period in which the owner was absent and the process nonetheless ran on the record. The timing of this work largely determines its outcome. Where process documentation is assembled after a transaction calendar has already begun, the resulting documents carry recent effective dates and their verification value remains correspondingly limited; the reviewing party routinely compares the effective date on a procedure with the upload date in the data room, and a narrow gap between the two is read as preparation rather than as practice. Coverage that has operated, been revised, and been measured across at least one full operating cycle gives the identical document a materially different evidentiary weight. Where SOP coverage is built not as a line item in sale preparation but as an investment in the predictability of the business itself, its reflection in valuation follows without having to be argued at the table. The question put by the party conducting the review is not how many procedures a company holds, nor how neatly they are indexed. It is whether the work that determines margin produces the same result without the individual who runs it today, and whether that proposition can be shown rather than merely stated. An answer of that kind is given by the records of a period already concluded, examined against the exceptions that arose within it, and such records exist only where they were kept before anyone thought to ask for them. ## Key Points - Procedural coverage in most companies derives from incident history and from the clause list of a certification audit rather than from the company's own risk map, which leaves the most critical processes unwritten. - The review value of a procedure sits less in its text than in the records it generates; a procedure without deviation logs is treated as unverified in the implementation dimension. - Without a measurement layer, the effect of capacity growth on margin cannot be modeled, and the buyer constructs the growth scenario on its own conservative assumptions. - Where process ownership is not separated from line management, deviation approval rests on personal discretion instead of a defined authority threshold, which entrenches founder dependency. - Documentation weakness can produce exclusions in representation and warranty insurance, which leaves the underlying exposure on the seller's balance sheet through the survival period. ## Questions ### How is SOP coverage assessed during due diligence? The reviewing party looks not at the number of procedures but at whether the processes that determine margin and delivery schedule are documented. The assessment moves across six dimensions: whether the procedure exists, whether it is supported by a current and approved document, whether it actually governs daily work, whether its results are measured, whether a defined owner exists, and whether it is sustainable independently of key individuals. Implementation is verified through the records a procedure generates, not through its text. ### Why can a review find procedures inadequate even when they are written? Written text describes the normal flow, while operating cost accumulates mainly in the handling of exceptions. Where the tolerable deviation and the threshold at which work stops are left unwritten, the procedure does not govern the daily decision. In addition, without traces such as deviation logs, compliance check results, or signed forms, actual application cannot be verified, and the document is treated as having passed only the existence test. ### How does weak process documentation affect company valuation? The effect usually appears in deal structure rather than headline price. Where a buyer sees weakness in ownership and continuity, it enlarges the earn-out portion, raises the escrow percentage and its release period, and seeks retention undertakings from key personnel. Absent measurement data, the growth scenario is built conservatively. Areas with documentation weakness may also be excluded from representation and warranty insurance, which leaves that exposure on the seller side. ### How far ahead of a sale process should SOP coverage be prepared? The verification value of documents depends on their having operated, been revised, and been measured across at least one full operating cycle. Procedures produced after a transaction calendar has begun carry recent effective dates, and the reviewing party routinely checks the distance between the effective date and the data room upload date. A record history exceeding a year gives the same document a distinctly different evidentiary weight. --- Source: https://www.beirek.com/en/blog/sop-scope-operational-due-diligence Publisher: BEIREK LLC — https://www.beirek.com