An inventory alert fires at 9:12pm on a Friday. The ERP has flagged a forming stockout on a fast-moving SKU — six days of cover remaining, a confirmed customer order due to ship in nine. The alert goes to the operations shared inbox. Nobody responds until Monday morning, when the procurement lead sees it, escalates to the VP Operations for an emergency purchase order approval, and the PO is raised by 11am. By that point, the customer's ship window was Monday 8am. The order misses. OTIF takes a hit.
The supply chain worked correctly. The supplier had stock. The lead time was manageable. What failed was the decision path — the gap between a signal that arrived at 9pm Friday and an approval that happened at 11am Monday. Fifty hours. Most of it was not anyone's fault. It was a governance failure: no named owner, no after-hours path, no mechanism to get a decision made until the decision window had already closed.
What OTIF actually measures
On-time-in-full is typically presented as a supply chain health metric. Companies track it by supplier, by SKU, by customer. They build supplier scorecards around it. They run root cause analyses when it dips. The root causes they find are usually supply-side: lead time variability, demand forecasting error, inventory positioning.
This framing misses the governance dimension. A significant fraction of OTIF failures in mid-market manufacturing are not supply-side failures. They are decision-side failures: situations where the material was available, the supplier was reliable, and the demand signal was accurate — but the approval that would have triggered the right action arrived too late to use it.
The 9pm Friday problem is the clearest version of this. But it appears in other patterns too: the quality hold that waited for the quality manager to return from travel. The emergency reorder that needed a spend override that only one person could approve and they were in a customer meeting all day. The production schedule change that required sign-off from two departments who couldn't get on a call until Thursday.
The approval gap in a specific manufacturing scenario
Here is the timeline of a typical OTIF failure driven by decision latency. The material circumstances are not unusual. The governance gap is the problem.
The entire failure was contained in a 50-hour window during which the material existed, the supplier was ready, and the only missing piece was an approved purchase order. The material circumstances were fine. The decision infrastructure was not.
Why after-hours is the test for your governance model
Most governance models work adequately during business hours. During the day, the VP Operations is reachable. The procurement lead can escalate. The relevant people are in the office or on video. The informal coordination layer that substitutes for a formal governance model is available.
After-hours removes that layer. And manufacturing operations do not stop at 5pm. Inventory moves. Demand signals arrive. Quality holds get triggered. Production anomalies surface. The decisions those events require are no different at 9pm Friday than they are at 2pm Tuesday — but the governance capacity to make them is dramatically lower. The gaps that are invisible during business hours become OTIF failures at night and on weekends.
This is why after-hours decision coverage is not a fringe concern in manufacturing operations. It is the test of whether your governance model is real or informal. An informal model — built on the availability of specific individuals — will fail consistently at the worst times.
What a governed after-hours decision path looks like
A governed after-hours decision path has three components. These are operational design decisions, not software features. The technology that enforces them can vary.
This is what decision infrastructure means in practice for a plant manager or COO: not better forecasting, not more alerts — a governed path from signal to approved execution that operates at any hour, without depending on who happens to be available.
What changes for OTIF when governance is in place
When after-hours decision governance is operational, the improvement in OTIF comes from two sources. The first is direct: decisions that previously waited 48 hours for a business-hours approval now close in 2–4 hours. Orders that would have missed ship windows get approved in time to ship. This is the primary effect.
The second is structural: the audit trail created by a governed decision path allows operations teams to identify exactly where decisions are stalling, at what time of day, at what spend threshold, and on which SKUs. The OTIF root cause analysis moves from post-hoc supply chain forensics to real-time governance visibility. You can see the pattern before it becomes a customer impact.
If you are trying to measure the governance dimension of your OTIF problem: count the number of OTIF failures in the last 90 days, then determine how many of them occurred within 72 hours of a signal that received no approved response. That number is the governance-driven portion of your OTIF problem — and it is addressable without changing anything about your supply chain.
OpsGrid: governed decision paths for Business Central manufacturers
OpsGrid — in live beta — is IntelliconnectQ's decision infrastructure layer for Dynamics 365 Business Central. For manufacturing operations on BC, it provides the named decision owner model, the Teams-based mobile approval interface with live BC data context, and the direct connection from approved decision to ERP execution — with full audit trail.
When a BC inventory signal fires at 9pm Friday, OpsGrid routes it to the named owner with the relevant order context and a 2-hour SLA. The owner approves from their phone. The PO is raised in BC. The decision, approver, context, and timestamp are logged. The Monday morning backlog of manual ERP translations does not exist.
If your OTIF problem has a governance component — decisions that miss windows because approvals are delayed, not because material is unavailable — start a conversation with us about what the governed decision path would look like in your operation.