The SOP Codex diagnostic scores process documentation on five dimensions: coverage, currency, findability, adoption fidelity, and production capability. It scores each dimension on a 0 to 5 scale. Red scores propose remediation playbooks, and amber scores get 30-day pulse checks.
Why Processes Live in Heads
At a score of 1 for currency, reviews never happen, and most SOPs are older than two quarters. At a score of 1 for findability, documents sit scattered across drives, and finding an SOP is luck. The diagnostic scores process documentation on coverage, currency, findability, adoption, and production as five separate dimensions. A scored view shows which of those five weaknesses applies, and how badly.
The lowest written anchor for coverage describes a related state in plain terms. Coverage sits below 30%, and critical processes live in heads. A red state for SOP Completion Percentage typically starts below 30%, and the published target is 80% within two quarters.
A coverage red also matters outside the documentation work itself. It routes to the Exit and Acquisition Layer module, which flags key-person risk exposure for diligence.
What Stale Process Documentation Looks Like in the Anchors
The lowest anchor for documentation currency describes the stale state directly. Reviews never happen, most SOPs are older than two quarters, and nobody measures the overdue average. At a middle score, the anchor describes a review engine that exists while the overdue average creeps upward.
A rising Average Days Overdue Review turns the process-clarity cell in the Intelligent Foundations module amber or red. Currency reds also route to the KPI Precision Grid, where stale SOPs produce stale KPIs. The overdue average then becomes evidence for the Process Clarity anchor review at the next recalibration.
Adoption fidelity describes a second kind of staleness, where the document and the work drift apart. At a score of 1, the documented process and the actual process diverge widely, and nobody measures deviation. At a score of 3, walkthroughs show drift between reviews.
The standing metric for Process Deviation Incidents carries a clear published rule. It treats high deviation as a wrong SOP, not wrong people. At a score of 5, high-deviation SOPs get revised, and walkthroughs confirm fidelity between the document and the work.
Diagnose Before Writing
A fishbone diagram can help an owner separate the causes behind a recurring process gap. That lens is an outside tool, and an owner can compare its branches with the routing below. Coverage, findability, and production reds route to the Documentation Sprint. Owners who want broader background can read about business process improvement consulting as well.
Currency reds route to Review Engine Restoration, which works on reviews and reminders. Findability reds also route moment-of-need surfacing gaps to the Change Enablement Sprint module. Production reds also trigger a Draft-With-AI governance state check in the AI Deployment Canvas module, which sets manual mode if the AERI score sits below 40.
Adoption reds route to Deviation Response, which looks for one of three causes. The SOP is wrong, the tooling fights it, or the people were never adopted. A wrong SOP gets revised, a tooling conflict escalates to the Integrated Tech Stack module, and an adoption gap routes to the Change Enablement Sprint module.
Consider a hypothetical firm where the onboarding SOP is current and correct but hard to find. Findability then scores low in that firm, while currency scores well on the same review. A red findability score would propose the Documentation Sprint and route surfacing gaps to the Change Enablement Sprint module. The scores only set the routing, and leadership still confirms each proposal.
The SOP Codex Diagnostic as a Framework
The VWCG OS SOP Codex diagnostic scores five dimensions on a 0 to 5 scale. Each scorer works against written anchors, and the published tables describe scores of 1, 3, and 5. The composite score is a weighted sum with equal weights. Each dimension carries a weight of 0.20 in that composite.
Three standing page metrics carry the published targets alongside the scores. SOP Completion Percentage targets 80% within two quarters, and Process Deviation Incidents treat high deviation as a wrong SOP. Average Days Overdue Review is the third standing metric.
The routing rules state that scorer agreement has not yet passed the reliability test. A route from a scored dimension stays a proposal until leadership confirms it in review. Any route that carries evidence feeds the next scoring of the receiving dimension and never sets a score directly.
A theory of constraints lens can help an owner pick a starting point among several weak dimensions. That lens is an outside reading, since the composite itself weights all five dimensions equally. The owner can ask which weak dimension blocks the most downstream work. The routing table then shows where each red would go.
How the Diagnostic Scores Process Documentation
SOP Coverage measures SOP Completion Percentage against the 14-area core-process checklist, with a page target of 80%. At a score of 5, coverage sits at or above 80%. All 14 areas are assessed, and gaps have owners and dates, while a score of 1 means coverage below 30%.
Documentation Currency measures the share of SOPs reviewed within 90 days. It also measures the average days overdue across the library. At a score of 5, every SOP is re-validated inside 90 days. The overdue average sits near zero and is trended over time.
Findability and Taxonomy checks that every SOP carries a taxonomy code. A retrieval test asks a sampled employee to find a needed SOP in under 2 minutes. The dimension also checks whether SOPs surface inside CRM and helpdesk tools. At a score of 1, documents sit scattered across drives, and finding an SOP is luck.
Adoption Fidelity compares documented process to actual process through deviation rates and sampled walkthroughs. SOP Production Capability checks for a named librarian role and an operating interview-to-draft workflow. That workflow runs AI-assisted when the AI Deployment Canvas state permits and manually otherwise. A RACI chart can serve as an outside lens on who owns each SOP and its review date.
Scoring Bands and Monitoring Paths
The composite bands are red, amber, and green, with full coverage and no gaps or overlaps. Red runs from 0.0 up to but not including 2.0, and amber runs from 2.0 to 3.5 inclusive. Green runs above 3.5 up to and including 5.0 on the 0 to 5 weighted score.
A red band proposes the owning remediation playbook, and safety routes act on the first reading. Leadership confirms a proposal at the next monthly governance review or the Core Execution Phase 3 review, whichever comes first. The stated duration of a playbook starts at that confirmation.
Every amber dimension routes to the Codex Monitoring playbook for 30-day pulse checks. That path logs the amber dimension with its evidence snapshot, schedules the pulse check, and scores it again. Persistent amber gets a named owner and a second date. No amber may persist two checks without an escalation decision.
Green dimensions hold and are monitored quarterly through the Core Execution module, and the SOP-revision signal runs on events. A color changes only when a score clears the band edge by a margin, or holds for two consecutive scorings. The margin is 0.25 points on 0 to 5 scales. On the AERI 0 to 100 scale, the margin is 5 points.
Red Playbooks and Their Work
The Documentation Sprint belongs to the COO with an SOP librarian designate, for 6 weeks. It scores the 14-area checklist for documented, current, and followed, and ranks gaps by downstream dependency. It also names the librarian and sets up an interview-to-draft pipeline. A weekly quota sized to hit 80% coverage within two quarters sets the production pace.
Each SOP is published with a taxonomy code, an owner, and a 90-day review date. Owners who want a related discipline can read about project management consulting as outside background. The SOP librarian owns Review Engine Restoration, which runs for 3 weeks. It pulls every SOP past its 90-day review date and computes the standing average-days-overdue metric.
The restoration then triages the overdue list by change status. Changed processes get full re-validation, while unchanged processes get confirm-and-stamp. Reminder automation reaches owners 14 days before expiry, with weekly escalation to the librarian. The outcome requires a backlog cleared or on a dated quota plan, live reminder automation, and a falling overdue average.
Deviation Response belongs to the COO with the SOP librarian, at 3 weeks per targeted cluster. It ranks SOPs by deviation incident count and diagnoses the worst cluster per SOP. Every incident gets a disposition, and deviation is re-measured on the cluster after 30 days. Each owner runs at most three red playbooks at once, so a fourth red queues behind them.
Building a System That Holds
The playbooks share one lifecycle: open, running, met or missed, escalated, closed. An outcome met, with an independent re-score at amber or better, closes the run. Someone other than the owner performs that re-score of the dimension.
An outcome missed at the end of its stated duration escalates to the manager of the owner. It also goes onto the next Core Execution quarter planning agenda.
Routes from other modules can also make this process documentation work mandatory. A process clarity red in the Intelligent Foundations module shifts the SOP Codex from optional to mandatory. Data hygiene in the red band there makes the SOP Codex prioritize data-related SOPs for data entry, validation, and ownership. An AERI score below 40 turns Draft-With-AI off, and SOP drafting falls back to interview-and-write.
Suppose a founder-led firm names a librarian and starts an interview-to-draft workflow. The score of 5 anchor for production describes a librarian-owned pipeline that runs interview-to-publish in days, not weeks. At the other end, the score of 1 anchor describes a firm where nobody owns documentation and new SOPs require a project. The anchors define the target, and the scores show the distance to it.
A balanced scorecard can serve as an outside lens that places these measures beside financial and customer views. Unit economics can offer a second outside lens on the cost of the work. Neither lens forms part of the SOP Codex scoring or routing. The method itself stays with five dimensions, three bands, and four playbooks.
Frequently Asked Questions
- What are the five dimensions scored by the SOP Codex diagnostic?
- The diagnostic scores SOP Coverage, Documentation Currency, Findability and Taxonomy, Adoption Fidelity, and SOP Production Capability. Each dimension carries a weight of 0.20 in the composite score. The composite is a weighted sum of those five dimensions. Written anchors at scores of 1, 3, and 5 guide the scorer.
- What is the scoring range for the composite score?
- The composite score runs on a 0 to 5 weighted score. Red runs from 0.0 up to but not including 2.0, and amber runs from 2.0 to 3.5 inclusive. Green runs above 3.5 up to and including 5.0, and the bands have full coverage with no gaps and no overlaps.
- What triggers a Documentation Sprint playbook?
- A Documentation Sprint triggers when SOP Coverage or SOP Production Capability scores red. It also triggers when a process-clarity red in the Intelligent Foundations module makes the SOP Codex mandatory. A Findability and Taxonomy red also routes to the sprint. The COO owns the sprint with an SOP librarian designate.
- How long does the Review Engine Restoration playbook take?
- Review Engine Restoration has a stated duration of 3 weeks, counted from confirmation. It triggers when Documentation Currency scores red, with reviews overdue and stale SOPs feeding stale KPIs. The playbook pulls every SOP past its 90-day review date and triages the list, and the SOP librarian owns the work.
- What happens when an amber dimension persists two checks without escalation?
- The Codex Monitoring outcome rules that case out, since no amber may persist two checks without an escalation decision. Persistent amber gets a named owner and a second date. A move into red past the hysteresis margin proposes the owning red playbook, and the SOP librarian owns this standing path.
- How does World Consulting Group help an owner take the next step after learning about the SOP Codex diagnostic?
- World Consulting Group delivers the SOP Codex diagnostic as a service within VWCG OS. The first step of the engagement is a scoring pass of the five dimensions against the written anchors. Each red dimension then proposes its owning playbook, and amber dimensions move to 30-day pulse checks under the Codex Monitoring playbook.
