WEBVTT

00:00:00.100 --> 00:00:05.584
This journey continues the fictional policy case from the complete Product Tour.

00:00:05.534 --> 00:00:12.737
The Data retention policy 2026 has been approved and takes effect on the first of December.

00:00:12.737 --> 00:00:17.362
The policy owner does not begin again with a copied summary.

00:00:17.362 --> 00:00:20.387
Select Load approved handover.

00:00:20.387 --> 00:00:33.627
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.

00:00:33.627 --> 00:00:38.483
The source and the decision stay visible beside the work they created.

00:00:38.483 --> 00:00:44.262
This matters because implementation can take weeks and involve several teams.

00:00:44.262 --> 00:00:51.546
People should still be able to see which approved change they are implementing and why the case was opened.

00:00:51.700 --> 00:01:00.887
The approved policy describes an outcome, but the organisation still has to work out where that outcome changes day-to-day activity.

00:01:00.837 --> 00:01:09.234
The case owner identifies three affected areas: Records operations, Customer service and Technology.

00:01:09.234 --> 00:01:14.700
Each area has an owner and two prepared implementation items.

00:01:14.700 --> 00:01:20.316
Select another area if you want to change the impact map, then confirm it.

00:01:20.316 --> 00:01:25.864
Pūnaha is not interpreting the policy on the organisation's behalf.

00:01:25.864 --> 00:01:33.596
Responsible people decide which teams, processes, systems, documents and controls are affected.

00:01:33.596 --> 00:01:47.853
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.

00:01:48.000 --> 00:01:52.982
Each affected area needs to answer the same practical questions.

00:01:52.932 --> 00:01:55.238
Who owns the change?

00:01:55.238 --> 00:01:57.490
What happens today?

00:01:57.490 --> 00:01:59.714
What must change?

00:01:59.714 --> 00:02:04.394
What evidence will show completion, and when can the team be ready?

00:02:04.394 --> 00:02:07.487
Select Run prepared assessments.

00:02:07.487 --> 00:02:16.698
A mapped BPMN-based workflow coordinates that repeatable sequence and returns each result to the implementation case.

00:02:16.698 --> 00:02:21.662
Records operations and Customer service are ready to continue.

00:02:21.662 --> 00:02:27.265
Technology reports that a legacy archive cannot meet the original date.

00:02:27.265 --> 00:02:35.119
The same assessment route gives the case owner comparable information, while the result remains specific to each team.

00:02:35.119 --> 00:02:42.498
A real workflow could assign human tasks, wait for responses and require supporting evidence.

00:02:42.498 --> 00:02:47.897
This public walkthrough uses prepared fictional results and sends nothing.

00:02:48.050 --> 00:02:53.222
The case now has enough information to choose the configured review route.

00:02:53.172 --> 00:03:00.402
This example uses organisational impact, readiness and time remaining before the effective date.

00:03:00.402 --> 00:03:04.282
Change an answer and watch the result update.

00:03:04.282 --> 00:03:16.476
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.

00:03:16.476 --> 00:03:20.207
The score, rule and reasons stay visible.

00:03:20.207 --> 00:03:24.642
This is not a universal policy or compliance method.

00:03:24.642 --> 00:03:31.086
An organisation would define and approve its own inputs, thresholds and authority.

00:03:31.086 --> 00:03:36.037
The value is that the routing logic is not hidden inside a prompt.

00:03:36.037 --> 00:03:42.616
Reviewers can see which recorded facts selected the route before the implementation moves forward.

00:03:42.770 --> 00:03:47.657
The decision result prepares a published implementation workflow.

00:03:47.607 --> 00:03:50.917
Select Start implementation work.

00:03:50.917 --> 00:04:02.325
Records operations receives the procedure update, Customer service receives the guidance and briefing task, and Technology receives the archive setting change.

00:04:02.325 --> 00:04:07.561
Each task carries its owner, due date and evidence requirement.

00:04:07.561 --> 00:04:13.326
The blocked technology item remains visible instead of being treated as complete.

00:04:13.326 --> 00:04:23.038
In a real configuration, the workflow could use human tasks, waits and approved connections to coordinate work in existing systems.

00:04:23.038 --> 00:04:31.639
Administrators would control the connection and credentials, and the organisation would decide which actions require approval.

00:04:31.639 --> 00:04:36.074
The public page starts only the browser demonstration.

00:04:36.074 --> 00:04:42.667
It does not create a real task, call a connection or change an operational system.

00:04:42.820 --> 00:04:46.663
The technology assessment adds new evidence.

00:04:46.613 --> 00:04:57.654
The legacy archive cannot complete the planned setting change before the first of December, although its existing access and deletion controls remain in place.

00:04:57.654 --> 00:05:04.071
The case makes exception review available without sending every affected team through that work.

00:05:04.071 --> 00:05:07.055
Select Open exception review.

00:05:07.055 --> 00:05:14.543
The discretionary task is assigned to the Technology owner with a review date of the fifteenth of January.

00:05:14.543 --> 00:05:21.813
The reason, compensating control, owner and review date will be available to the readiness decision.

00:05:21.813 --> 00:05:26.547
The walkthrough does not decide whether this exception is acceptable.

00:05:26.547 --> 00:05:32.692
That judgement belongs to the organisation and the people with the appropriate authority.

00:05:32.692 --> 00:05:38.498
Pūnaha keeps the exception and its later review connected to the same case.

00:05:38.640 --> 00:05:44.599
Before the readiness review, the case shows exactly what evidence is available.

00:05:44.549 --> 00:05:52.566
The updated records procedure, customer service guidance and technology implementation plan are complete.

00:05:52.566 --> 00:05:58.778
The legacy archive change is not complete and is covered by the prepared exception.

00:05:58.778 --> 00:06:03.757
Try selecting or clearing an item and watch the count change.

00:06:03.757 --> 00:06:06.456
Then record the checkpoint.

00:06:06.456 --> 00:06:15.816
The snapshot keeps the approved policy, workflow version, rollout decision, completed evidence and controlled exception together.

00:06:15.816 --> 00:06:24.579
An evidence checkpoint does not prove that a policy has been interpreted correctly or that the organisation is compliant.

00:06:24.579 --> 00:06:37.058
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.

00:06:37.200 --> 00:06:41.043
The policy owner receives one readiness pack.

00:06:40.993 --> 00:06:50.013
It contains the impact register, team assessments, rollout decision, evidence checkpoint and the remaining archive condition.

00:06:50.013 --> 00:06:53.323
Pūnaha prepares the pack and waits.

00:06:53.323 --> 00:06:57.338
It does not turn a recommendation into approval.

00:06:57.338 --> 00:07:04.867
The owner can defer the effective date, approve with a condition or approve the implementation as ready.

00:07:04.867 --> 00:07:07.485
Choose Approve with condition.

00:07:07.485 --> 00:07:17.631
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.

00:07:17.631 --> 00:07:21.755
The human choice and note remain part of the case.

00:07:21.755 --> 00:07:32.892
This makes the boundary clear: the system coordinates information and work, while the accountable person decides whether the prepared implementation state is acceptable.

00:07:33.050 --> 00:07:36.011
It is now the thirtieth of November.

00:07:35.961 --> 00:07:39.461
Move the fictional clock forward one day.

00:07:39.461 --> 00:07:44.887
The effective-date event reaches the case and records the policy milestone.

00:07:44.887 --> 00:07:56.620
The case history shows the approved handover, impact assessments, workflow activity, decision reasons, evidence checkpoint, exception and human readiness approval.

00:07:56.620 --> 00:08:02.358
It also keeps the archive review condition open for the fifteenth of January.

00:08:02.358 --> 00:08:08.340
Reaching the milestone does not erase unfinished work or make a compliance claim.

00:08:08.340 --> 00:08:13.454
It records the event and the state that the responsible person approved.

00:08:13.454 --> 00:08:26.341
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.
