Method version & module selector
Confirms which method version and which diagnostic modules apply to this engagement, reconciling the standard configuration against any scope variations agreed at intake.
In / outStandard method config + scope variation notes → locked module set for this engagement
You might say…
“Running a module that was explicitly out of scope wastes time and confuses the client — locking the config before starting prevents that.”
What it does
Confirms which method version and which diagnostic modules apply to this engagement, reconciling the standard configuration against any scope variations agreed at intake. Used once the brief is understood, to lock the exact procedure that will run.
Trigger: Use once the engagement brief is understood; provide the standard method configuration and any scope variation notes.
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