Separate selection, supplier implementation, buyer readiness and stabilisation. They are different clocks.
For one concrete supplier example, LogicGate publishes approximate implementation durations ranging from 30 days for Lite to 150 days for Elite, with intermediate packages. Its services description states that each implementation option covers one Application. Those are supplier-described package timelines, not evidence that a multi-function enterprise programme can be selected, migrated and adopted in the same period. (logicgate.ai)
What does a usable GRC implementation project plan look like?
The following 42-week planning example assumes a phased deployment, an available internal team and a limited first release. Activities overlap deliberately.
| Stage | Illustrative window | Principal document | Approval before proceeding |
|---|---|---|---|
| 1. Mobilise | Weeks 1–2 | Decision charter and baseline | Sponsor accepts the problem and decision rights |
| 2. Define scope | Weeks 3–6 | Scope charter and applicability register | Process owners approve release-one boundaries |
| 3. Prepare data | Weeks 4–10, continuing as needed | Data inventory, dictionary and remediation backlog | Migration method is credible |
| 4. Requirements and proposals | Weeks 7–12 | RFP and commercial response workbook | Comparable shortlist evidence exists |
| 5. Demonstrations and proof of concept | Weeks 11–16 | Scenario results and decision log | Mandatory requirements are proven or resolved |
| 6. Diligence and contracting | Weeks 13–18 | TCO, contract schedules and delivery scope | Security, finance, legal and sponsor approve |
| 7. Detailed design and foundations | Weeks 19–24 | Design baseline and configuration register | Data and access designs are accepted |
| 8. Build and integrate | Weeks 25–32 | Configurations and interface runbooks | Technical tests pass |
| 9. Rehearse and accept | Weeks 29–36 | Migration reconciliation and UAT results | Business and technical acceptance gates pass |
| 10. Cut over | Weeks 37–38 | Cutover, rollback and communications plans | Named go/no-go authority approves |
| 11. Stabilise | Weeks 39–42 | Support handover and operating backlog | Operating team accepts ownership |
| 12. Renew or exit | Ongoing | Portability tests and renewal calendar | Decision occurs before notice deadlines |
Do not compress this example by deleting testing or migration rehearsal. If a deadline is fixed, reduce the first release and establish an interim control process for excluded work.
Build your actual critical path around five dependencies: approval lead times, data cleansing, source-system access, supplier delivery availability and the earliest safe cutover window. KPMG’s implementation guidance specifically calls for resource allocation, integrated testing, access validation and explicit go/no-go criteria. (kpmg.com)
Sources cited on this page
- logicgate.ai ↗www.logicgate.ai
- kpmg.com ↗kpmg.com