Use this as a proposed readiness sprint, not a promise to complete procurement or implementation.
| Timing | Action | Tangible output |
|---|---|---|
| Days 1–2 | Convene sponsor, programme lead, technology, audit and procurement; verify contractual dates | Decision owner, deadline register and initial scope |
| Days 3–4 | Agree the first workflow and alternatives | Approved scope charter and mandatory requirements |
| Days 5–6 | Inspect redacted records, exports and integration dependencies | Readiness findings and unanswered questions |
| Days 7–8 | Prepare common scenarios and a blank three-year cost model | Demo-to-acceptance pack and quote clarification template |
| Days 9–10 | Decide what the team can resolve and what needs specialist investigation | Funded next-stage plan with owners and explicit stop conditions |
Where desk worksheets are available, the relevant specifications are the Minimum Viable GRC Scope Builder, GRC Migration Readiness X-Ray, GRC Integration Reality Check, Three-Year GRC True Cost Comparator and After-the-Consultants GRC Operating Plan. Their names describe useful deliverables; this research has not verified live downloads or service availability.
A concise brief to a prospective adviser is:
We need to decide whether to retain, repair or replace our platform for this first workflow. Assess these redacted records and dependencies, identify what remains unproven, and provide a bounded test plan, cost clarification list and recommended decision. Separate observed facts, assumptions and unresolved questions.
The next commitment should buy evidence for the next decision—not simply a larger implementation.