Derive the required-document checklist from the methodology
Derives the specific document and data checklist for this engagement from the method's standard input requirements, mapped against the client's known situation, naming exactly what is needed and why.
In / outMethod's standard input requirements + client context (sector, scope, known data landscape) → specific named document and data checklist for this engagement
You might say…
“I ask for documents using the same generic list every time and clients send me things I don't need while missing the two files that actually matter.”
What it does
Reads the engagement's methodology and produces the specific list of documents, reports, exports, and data files the delivery line will depend on. Used at the start of collection. Judgement call mapping method steps to concrete input artefacts.
Trigger: Use before requesting documents from the client, when you need a precise, client-legible list rather than the full method input catalogue.
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