Triage surfaced gaps as resolvable, escalate, or block
Evaluates each outstanding gap from the audit against delivery dependencies and timeline, classifying each as must-resolve-before-start, resolve-in-flight, or waive-with-caveat, and recommending the action for each.
In / outGap register (outstanding items) + delivery dependency map + timeline → gap triage (must-resolve / resolve-in-flight / waive-with-caveat per item) with rationale
You might say…
“Start date is tomorrow, three items are still missing, and I need to decide in the next hour which ones will actually stop us and which ones we can work around.”
What it does
Single-judgement classification of each gap from the completeness audit into fast-resolvable (chase/clarify), escalate-upstream (commercial renegotiation), or hard-block. Used immediately after the audit to decide which gaps belong in this activity versus routing elsewhere.
Trigger: Use at the pre-start readiness gate when gaps remain and time pressure means each gap needs a fast, prioritised decision rather than a blanket hold.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation