Order-Penetration Point Audit¶
Audit — instantiates Push-Pull Decoupling Point Design
Walks the actual flow to measure where customer-order information really starts governing work, versus where policy claims it does.
The Order-Penetration Point Audit is a periodic verification that goes and looks: it walks the real flow, traces a sample of actual orders, and measures the stage where customer-order information actually first governs the work — then compares that observed point against the one the map and policy claim, quantifying the gap with boundary metrics. Its defining idea is that it produces evidence of the real boundary, not a drawing of the intended one. Its output is a findings report — drift, off-policy stocking, false pulls, mismatched service — backed by measurement rather than assertion. It verifies; it does not design the boundary and it does not govern the response to what it finds.
Example¶
A company running an after-sales spare-parts network believes its own policy: fast-moving parts are stocked at regional depots and pushed to forecast, while slow and critical parts are held centrally and shipped only against a repair order. An order-penetration point audit tests that belief against reality. Over a quarter it samples real repair jobs and traces, for each part consumed, the stage where the order first drove action. The finding is uncomfortable: field technicians, distrusting central lead times, had been informally hoarding "pull" parts in their vans, so the true penetration point had drifted downstream of policy — inflating hidden inventory and quietly aging stock nobody was counting. The audit puts numbers to it: fill rate by tier, expedite rate, buffer aging, and a count of off-policy stocking locations. Its conclusion that the real point does not match the stated point is what triggers a redesign; the audit itself moves nothing.
How it works¶
- Sample real orders, not the plan. Trace a representative set of actual jobs through the flow as executed.
- Locate the true penetration point. For each traced order, find the stage where order information first governs work, and compare it to the stated point.
- Instrument the boundary. Compute fill rate, buffer turns and aging, expedite percentage, obsolescence, and false-pull counts to size the gap.
- Report findings, not fixes. Deliver the observed-versus-stated divergence and its cost as evidence for whoever owns the response.
Tuning parameters¶
- Sample size and coverage — how many orders and which product lines the audit traces. Broader coverage catches more drift but costs more effort and delays findings.
- Audit cadence — annual, quarterly, or event-triggered. More frequent audits catch drift sooner but risk becoming a ritual; rarer ones let the point wander further between checks.
- Metric depth — a handful of headline numbers versus a full boundary instrument. Depth reveals subtler drift but raises the data burden and the noise.
- Independence — internal self-check versus an external or cross-functional auditor. More independence surfaces uncomfortable findings but costs access and goodwill.
- Root-cause depth — stopping at "the point has drifted" versus tracing why. Deeper analysis yields actionable findings but slows the audit.
When it helps, and when it misleads¶
The audit's strength is that it catches the silent drift a design diagram cannot: it is the go-and-see (gemba)[n1] check on the boundary, and it is often the only mechanism that will discover the point has migrated because people quietly work around the official flow. Because the archetype's own invariant is that repeated exceptions signal a misplaced point, an instrument that counts those exceptions is close to indispensable.
Its limits are those of any snapshot. Between audits the point can drift back, and a sample can miss the rare-but-costly exception; auditors also gravitate to the metrics that are easy to pull, potentially missing the obsolescence and lost-fit costs that matter most. The classic misuse is treating the audit as governance — auditing on a loop while no accountable owner acts on the findings, so the report becomes a filing exercise. The guarding discipline is to route findings into the standing governance forum and pair periodic audits with a live dashboard owned by someone who can actually move the boundary.
How it implements the components¶
flow_stage_map— the audit reconstructs the actual staged flow as walked, which routinely differs from the drawn one; producing that observed map is the audit's first act.boundary_performance_dashboard— the audit defines and populates the boundary metric set (fill rate, turns, aging, expedite, false-pull count) that reveals where the true point sits.
The audit measures the boundary but does not draw the intended design — positioning the decoupling_buffer on the planned flow is the Customer-Order Decoupling Point Map's — and it does not own the standing response to its findings (boundary_owner_and_exception_path, repositioning_cadence — the Sales and Operations Boundary Review's). Nearest twin is the decoupling-point map, since both locate the order-penetration point on the flow: the map draws where the point should be; the audit measures where it actually is.
Related¶
- Instantiates: Push-Pull Decoupling Point Design — the audit supplies the ground-truth measurement of where the boundary really sits.
- Consumes: Customer-Order Decoupling Point Map — the stated point it checks the real flow against.
- Sibling mechanisms: Configuration Cell or Final Assembly Cell · Demand Segmentation ABC/XYZ Matrix · Kanban or Reorder Replenishment Rule · Lead-Time / Inventory Trade-off Curve · Make-to-Stock / Make-to-Order Split Policy · Postponement Strategy Matrix · Sales and Operations Boundary Review · Semi-Finished Goods Buffer
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Order-Penetration Point Audit operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it walks the actual flow to measure where customer-order information really starts governing work, versus where policy claims it does.
Independent corroboration: The frozen evidence defines Order-Penetration Point Audit as 'Walks the actual flow to measure where customer-order information really starts governing work, versus where policy claims it does', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Logistics & Supply Chain Management
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Specialized
Rationale: Order-Penetration Point Audit is most directly rooted in logistics and supply-chain management's control of flow, queues, capacity, inventory, and fulfillment. The lineage fits its defining practice: Walks the actual flow to measure where customer-order information really starts governing work, versus where policy claims it does.
Related originating lineages:
- Operations Research — Order-Penetration Point Audit also draws materially on operations research's mathematical optimization, simulation, queues, decision analysis, and resource allocation, which shaped this mechanism rather than merely adopting it as an application.
- Organizational & Management Science — Lean process analysis materially shapes the audit of actual versus officially claimed workflow control.
Review resolution: Both independent reviews agree on primary origin logistics_supply_chain; reconciliation resolves alternate_origin_disagreement. Formative alternate lineages retained: operations_research, organizational_management. The broader reach of later applications is kept separate as domain_reach=specialized; origin_mode=cross_disciplinary_synthesis records how the formative lineages relate. Confidence is conservatively reconciled to high, and encyclopedia_synthesis=false preserves the reviewers' boundary judgment.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The audit's most valuable output is usually not the headline metric but the list of exceptions — the specific orders that penetrated earlier or later than policy allows. In this archetype a cluster of exceptions is not noise to be smoothed away; it is the primary evidence that the point is in the wrong place or that the demand segments are misclassified, and it should be read as a redesign trigger rather than a compliance failure.
[n1] Gemba walk — the lean practice of going to the actual place where work happens to observe reality directly, rather than relying on reports or plans. The order-penetration audit is a gemba walk aimed specifically at the push-pull boundary. ↩