Policy change implementation in Pūnaha Voice: en-NZ-MollyNeural (natural synthetic voice) Prepared Pūnaha walkthrough. Fictional policy, organisation, people, dates and results. No customer or compliance result is implied. Nothing is sent or saved. Chapter 1: Load the approved handover This journey continues the fictional policy case from the complete Product Tour. The Data retention policy 2026 has been approved and takes effect on the first of December. The policy owner does not begin again with a copied summary. Select Load approved handover. The implementation case receives the approved document identity, the cited passages used in the earlier assessment, the human approval and note, the implementation objective and the effective date. The source and the decision stay visible beside the work they created. This matters because implementation can take weeks and involve several teams. People should still be able to see which approved change they are implementing and why the case was opened. Chapter 2: Map the organisational impact The approved policy describes an outcome, but the organisation still has to work out where that outcome changes day-to-day activity. The case owner identifies three affected areas: Records operations, Customer service and Technology. Each area has an owner and two prepared implementation items. Select another area if you want to change the impact map, then confirm it. Pūnaha is not interpreting the policy on the organisation's behalf. Responsible people decide which teams, processes, systems, documents and controls are affected. The case gives those decisions a shared structure so the implementation register, ownership and later evidence stay connected to the approved source rather than being spread across separate messages and spreadsheets. Chapter 3: Run consistent team assessments Each affected area needs to answer the same practical questions. Who owns the change? What happens today? What must change? What evidence will show completion, and when can the team be ready? Select Run prepared assessments. A mapped BPMN-based workflow coordinates that repeatable sequence and returns each result to the implementation case. Records operations and Customer service are ready to continue. Technology reports that a legacy archive cannot meet the original date. The same assessment route gives the case owner comparable information, while the result remains specific to each team. A real workflow could assign human tasks, wait for responses and require supporting evidence. This public walkthrough uses prepared fictional results and sends nothing. Chapter 4: Explain the rollout route The case now has enough information to choose the configured review route. This example uses organisational impact, readiness and time remaining before the effective date. Change an answer and watch the result update. With several areas affected, one area at risk and twelve days remaining, the matching rule selects a controlled rollout with an exception and requires policy owner approval. The score, rule and reasons stay visible. This is not a universal policy or compliance method. An organisation would define and approve its own inputs, thresholds and authority. The value is that the routing logic is not hidden inside a prompt. Reviewers can see which recorded facts selected the route before the implementation moves forward. Chapter 5: Coordinate implementation work The decision result prepares a published implementation workflow. Select Start implementation work. Records operations receives the procedure update, Customer service receives the guidance and briefing task, and Technology receives the archive setting change. Each task carries its owner, due date and evidence requirement. The blocked technology item remains visible instead of being treated as complete. In a real configuration, the workflow could use human tasks, waits and approved connections to coordinate work in existing systems. Administrators would control the connection and credentials, and the organisation would decide which actions require approval. The public page starts only the browser demonstration. It does not create a real task, call a connection or change an operational system. Chapter 6: Open the exception review The technology assessment adds new evidence. The legacy archive cannot complete the planned setting change before the first of December, although its existing access and deletion controls remain in place. The case makes exception review available without sending every affected team through that work. Select Open exception review. The discretionary task is assigned to the Technology owner with a review date of the fifteenth of January. The reason, compensating control, owner and review date will be available to the readiness decision. The walkthrough does not decide whether this exception is acceptable. That judgement belongs to the organisation and the people with the appropriate authority. Pūnaha keeps the exception and its later review connected to the same case. Chapter 7: Record the evidence checkpoint Before the readiness review, the case shows exactly what evidence is available. The updated records procedure, customer service guidance and technology implementation plan are complete. The legacy archive change is not complete and is covered by the prepared exception. Try selecting or clearing an item and watch the count change. Then record the checkpoint. The snapshot keeps the approved policy, workflow version, rollout decision, completed evidence and controlled exception together. An evidence checkpoint does not prove that a policy has been interpreted correctly or that the organisation is compliant. It records the configured information and state at that point in the workflow so an authorised reviewer can understand what is ready, what is missing and what conditions still require attention. Chapter 8: Keep a person responsible for readiness The policy owner receives one readiness pack. It contains the impact register, team assessments, rollout decision, evidence checkpoint and the remaining archive condition. Pūnaha prepares the pack and waits. It does not turn a recommendation into approval. The owner can defer the effective date, approve with a condition or approve the implementation as ready. Choose Approve with condition. The reviewer note records that the policy can proceed with the temporary exception and that the archive change must be reviewed by the fifteenth of January. The human choice and note remain part of the case. This makes the boundary clear: the system coordinates information and work, while the accountable person decides whether the prepared implementation state is acceptable. Chapter 9: Reach the effective date It is now the thirtieth of November. Move the fictional clock forward one day. The effective-date event reaches the case and records the policy milestone. The case history shows the approved handover, impact assessments, workflow activity, decision reasons, evidence checkpoint, exception and human readiness approval. It also keeps the archive review condition open for the fifteenth of January. Reaching the milestone does not erase unfinished work or make a compliance claim. It records the event and the state that the responsible person approved. The complete journey has taken one policy change from approved source to coordinated implementation without losing the exception, the evidence or the people responsible for the final judgement.