Assess whether a missing item is material enough to delay handoff
Evaluates each outstanding intake gap against the method's dependencies to determine whether it is blocking (delivery cannot start), degrading (quality reduced), or tolerable (can proceed with a caveat).
In / outOutstanding intake item + method dependency map → materiality verdict (blocking / degrading / tolerable) with rationale and recommended action
You might say…
“A document is still missing on start day and I don't know whether to hold everything or just flag it and push forward — the answer depends on what that document actually feeds into.”
What it does
Decides, for a still-outstanding item, whether its absence is material enough to block handoff to the delivery line or whether collection can be considered complete-enough to proceed. Used when chasing stalls. Single human-in-loop judgement that gates the engagement.
Trigger: Use when an intake item is still outstanding at or near the delivery start date and you need a principled decision about whether to proceed, hold, or caveat.
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