> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-4-progressa-end-to-end-the-method-on-one-sector/4.6-phase-4-plan-sequence-the-roadmap-and-cost-it.md). # 4.6 Phase 4, Plan — sequence the roadmap and cost it Plan turns Progressa's decisions into a sequenced, costed roadmap in waves — the deliverable the minister takes to cabinet — signed off with budget committed. {% embed url="" %} EA lifecycle Phase 4: sequence a wave-based roadmap your minister can take to cabinet (\~4 min) {% endembed %} **Watch first (\~4 min).** Then come back for the play. The video's recap slide carries an on-screen practice box — it is not narrated — and this page is where that box points. > **Single message.** Plan turns Progressa's decisions into a sequenced, costed roadmap in waves — the deliverable the minister takes to cabinet — signed off with budget committed. ## The concept Phase four is Plan. Now the decisions become a sequence: how does Progressa get from today to the target, in what order, at what cost? The deliverable is a roadmap in waves with investment estimates. About six to eight weeks. Progressa sequences the work into waves, the way PAERA's recommended roadmap suggests. Wave one is inception — stand up the repository and the Board, and make the Learner Registry the authoritative learner. Wave two is the high-priority use case — the single learner record, by having the Examination Authority and the grant programme consume the Learner Registry and the Identity Authority instead of their own lists. Wave three builds out the shared data-exchange backbone. Wave four takes it to mass scale — every education service running on the backbone. Each wave delivers something the minister can show, not just groundwork. Each wave gets an honest cost. Wave one is mostly people — the initial engagement and the small permanent EA team. Wave two adds the integration work to connect the authorities to the registries. Wave three is the backbone investment. The estimates are directional, not quotations — enough for cabinet to commit a five-year envelope, not an annual line that vanishes. And the sequencing is deliberate: the minister sees the single learner record — the thing they promised — land in wave two, inside the first year, not in year five. The roadmap does a second job: it is the one page the business side and the IT side both point at — the minister reading outcomes and dates, the architects reading the sequence and its dependencies — so the policy goal and the technical sequence line up without translation. Plan ends with the fourth sign-off, the most consequential of the four. The decision-maker and the EA Board approve the roadmap and commit the budget — ideally a multi-year envelope, not an annual line. This is the deliverable the minister takes to cabinet. With it approved, Progressa moves from planning to building. Four sign-offs done, in roughly six months from the first day of Discovery. Now the work shifts to making it live. ## Do this on your own sector — Sequence your roadmap into waves {% hint style="success" %} **✍️ Drafting play · produces A26 Wave roadmap** **Bring:** ranked gaps and the sourcing matrix. From **A25, A3** (see [Your country workbook](/experience-digital-transformation/gea/your-country-workbook.md)). **Get:** a four-wave roadmap with deliverables, dependencies and cost drivers. As text in the chat, not a file or a chart. **Time:** \~20 min · **Assistant:** any; the plays are tool-neutral. **With the kit:** no skill in this release, so the prompt runs bare in any assistant. **Watch for:** Directional estimates are to motivate a real costing, not to quote. {% endhint %} ✍️ **Drafting play.** You give a few facts; the play produces a first draft of a document you will edit. **What it does.** An architect in the Plan phase needs to turn ranked gaps and sourcing decisions into a wave-sequenced roadmap that puts an early visible win first and respects dependencies. {% tabs %} {% tab title="Prompt" %} Copy the prompt, replace the bracketed parts with your own context, and run it in the AI assistant of your choice. Never paste personal data or unpublished documents — see [How to use the plays](/experience-digital-transformation/gea/start-here/how-to-use-the-plays.md). ``` Below are my ranked gaps and sourcing decisions for [country X]'s [sector] sector [paste the ranked gap list and the build/buy/share matrix]. Sequence the work into waves, following the pattern: Wave 1 inception (stand up the repository and Board, make the core registry authoritative); Wave 2 the high-priority use case (the one cross-cutting outcome the minister has promised); Wave 3 build-out (the shared data exchange); Wave 4 mass scale. For each wave give: what it delivers (something visible, not just groundwork), its prerequisites from earlier waves, and a directional cost driver (people / integration / platform). Put the minister's promised outcome in an early wave. Output: a four-wave roadmap with deliverables, dependencies and cost drivers. ``` [Open in Claude](https://claude.ai/new?q=Below%20are%20my%20ranked%20gaps%20and%20sourcing%20decisions%20for%20%5Bcountry%20X%5D%27s%20%5Bsector%5D%20sector%20%5Bpaste%20the%20ranked%20gap%20list%20and%20the%20build%2Fbuy%2Fshare%20matrix%5D.%20Sequence%20the%20work%20into%20waves%2C%20following%20the%20pattern%3A%20Wave%201%20inception%20%28stand%20up%20the%20repository%20and%20Board%2C%20make%20the%20core%20registry%20authoritative%29%3B%20Wave%202%20the%20high-priority%20use%20case%20%28the%20one%20cross-cutting%20outcome%20the%20minister%20has%20promised%29%3B%20Wave%203%20build-out%20%28the%20shared%20data%20exchange%29%3B%20Wave%204%20mass%20scale.%20For%20each%20wave%20give%3A%20what%20it%20delivers%20%28something%20visible%2C%20not%20just%20groundwork%29%2C%20its%20prerequisites%20from%20earlier%20waves%2C%20and%20a%20directional%20cost%20driver%20%28people%20%2F%20integration%20%2F%20platform%29.%20Put%20the%20minister%27s%20promised%20outcome%20in%20an%20early%20wave.%20Output%3A%20a%20four-wave%20roadmap%20with%20deliverables%2C%20dependencies%20and%20cost%20drivers.) *(experimental deep link: pre-fills the prompt in a new claude.ai chat; check the bracketed parts before sending)* *Input, output and the kit skill are in the box above.* {% endtab %} {% tab title="Example on Progressa — coming" %} {% hint style="warning" %} **Worked example pending.** The prompt above is final and runs today. The Progressa worked example, the annotated reading and the what-next notes are added when this module's examples are run (Module 1 shows the shape). {% endhint %} Run the play on [Progressa](/experience-digital-transformation/gea/start-here/progressa-the-demonstration-country.md) yourself in the meantime: paste the sections named in **Bring** above, and read the result against **Watch for**. {% endtab %} {% tab title="What next" %} File the output as **A26** in your country workbook once you have worked it the way **Watch for** asks. A fuller what-next is added with the worked example. **This artefact feeds:** [4.7 Run a gate decision on a real project](/experience-digital-transformation/gea/module-4-progressa-end-to-end-the-method-on-one-sector/4.7-phase-5-execute-and-govern-stand-up-the-living-ea.md), [4.8 Map the Progressa method to your sector](/experience-digital-transformation/gea/module-4-progressa-end-to-end-the-method-on-one-sector/4.8-run-this-on-your-own-sector-the-transferable-recipe.md), [5.3 Sequence your national rollout into waves](/experience-digital-transformation/gea/module-5-evidence-rollout-and-the-case/5.3-roll-it-out-across-sectors-and-why-the-second-is-cheaper.md), [5.4 Draft the one-page ministerial business case](/experience-digital-transformation/gea/module-5-evidence-rollout-and-the-case/5.4-win-the-commitment-the-business-case-that-gets-your-minister-to-yes.md) See the full chain in [Your country workbook](/experience-digital-transformation/gea/your-country-workbook.md). {% endtab %} {% endtabs %} ## Sources * PAERA v1.0 §5.4 (Organisational Assessment & Roadmap) — * PAERA v1.0 §5.7 (Recommended Roadmap) — --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-4-progressa-end-to-end-the-method-on-one-sector/4.6-phase-4-plan-sequence-the-roadmap-and-cost-it.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.