The first month should produce decision evidence, not a premature enterprise rollout.
A proposed sequence is:
| Period | Work | Decision artifact |
|---|---|---|
| Days 1–7 | Map hand-offs, responsibilities and current costs | Accepted-File Cost Calculator inputs and operating baseline |
| Days 8–14 | Review returned files and calibrate material defects | Carrier-Ready Acceptance Pack and Rework Mapper |
| Days 15–21 | Compare internal improvement, managed production and targeted automation | In-House vs Managed Production Decision Matrix and Quote Normaliser |
| Days 22–30 | Agree pilot population, controls and procurement requirements | Pilot protocol, Control Audit and Capacity Stress Test |
These are recommended worksheet names and outputs, not claims that downloadable tools are already available.
Use three decision outcomes:
- Proceed to a bounded pilot: scope, economics and controls are sufficiently defined.
- Repair inputs or internal process first: the dominant defect lies outside the proposed supplier’s control.
- Do not proceed yet: material evidence, security, authority or integration questions remain unresolved.
The final buying test is straightforward: Does this operating model produce more usable files at an acceptable total cost, with evidence and accountability intact? If the answer depends on unmeasured reviewer effort, excluded difficult files or unverifiable accuracy claims, the business case is not ready.