Sponsor and commissioning lead

No. In the demo, selecting a phase only changes the information you view. It does not advance a real project or record sponsor approval. The six workplace phases are Discover, Define, Design, Deliver, Embed and Recalibrate; phases in Deploy remain examples. Read them in their displayed context. A real programme must identify its playbook, version and who may approve a transition. That operational approval is not yet available in the demo.

The complete project workflow is not yet available. The intended sequence is Question → Decision → Update → Action → Evaluation. A question receives an owner, an authorised person makes the required decision, and current guidance reaches the right audience before people act. Evaluation determines whether follow-up is needed. Publishing already has draft, review, approval and publication stages, but Deploy only shows fictional examples without real storage or approval. For actual project work, agree who handles questions, who decides and where follow-up is recorded.

Start with the sponsor guide and presentation on the sponsor role page in Support, available without login in Dutch and English, dated 4 October 2026. Then explore the Programme demo: identify the outcome, next decision, open questions and accountable person. Phases and milestones do not prove readiness or approval; decisions and charts are fictional. For a real programme, request evidence, uncertainties, consequences and a decision deadline in the agreed project record. The sponsor makes an authorised decision and ensures follow-up; viewing the demo records no decision.

• /experience/app/consultant

No, the Deploy demo does not save real decisions or approve anything. A displayed decision or completed worksheet does not replace authorised approval. Use your project's agreed decision record for real work. A future process must preserve the proposal, evidence, decision-maker, reasoning, conditions and effective date, and connect the decision to reviewed information for its audience. Before use, test approval permissions, corrections and publication with separate roles. Keep drafts visibly distinct from approved decisions.

No, the demo pulse is an illustration, not a readiness score or evidence of project results. The example described provides no response counts, coverage or scale definition. A meaningful report needs a clear question, period, population, response count, scale and relevant comparison before you interpret change. Sponsors should receive appropriate project results and protected aggregates, not unrestricted personal responses. Reporting in Deploy is fictional. Ask the measurement owner to explain the actual data and its limits before using it for a decision.