Judge whether received inputs are fit for the delivery line
Reviews each received input against the method's format and quality requirements — checking file types, data completeness, date ranges, and structural conformance — and flags items that are present but unusable.
In / outReceived inputs + method format/quality requirements → format fitness report (usable / unusable / needs conversion per item) with specific issues flagged
You might say…
“The checklist shows everything as received but the data file they sent is in a format the method can't process — and I only find out when we try to run step one.”
What it does
Single-judgement review of each received item to decide whether its content and format actually satisfy what the delivery line needs — not merely that something was submitted. Used when a checklist item is marked present but its usability is uncertain (wrong format, incomplete data, ambiguous version).
Trigger: Use after the completeness reconciliation confirms all items are received, to verify that what arrived is actually fit for the method to consume.
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