WEBVTT

00:00:00.100 --> 00:00:03.658
This journey starts with a simple request.

00:00:03.608 --> 00:00:11.177
Property Operations needs a supplier for scheduled and urgent maintenance across three Wellington offices.

00:00:11.177 --> 00:00:18.773
The requester enters the supplier name, the service, the business sponsor and the reason for bringing them on board.

00:00:18.773 --> 00:00:22.965
These are fictional details, but the point is practical.

00:00:22.965 --> 00:00:26.817
The same record moves through the rest of the work.

00:00:26.817 --> 00:00:35.702
People do not have to copy the supplier name and purpose into a separate risk sheet, approval email and contract reminder.

00:00:35.860 --> 00:00:39.608
Pūnaha makes the required evidence visible.

00:00:39.558 --> 00:00:45.879
Company details, a security questionnaire and a continuity plan have arrived.

00:00:45.879 --> 00:00:52.010
The insurance certificate is still missing, so the process waits at a known point.

00:00:52.010 --> 00:00:58.928
When the certificate arrives, the coordinator marks it received and the evidence set becomes complete.

00:00:58.928 --> 00:01:05.670
Nothing has been emailed into a forgotten thread, and the workflow has not lost its place.

00:01:05.670 --> 00:01:12.045
The required items and their state remain attached to the supplier record for the next reviewer.

00:01:12.200 --> 00:01:16.233
Now the reviewer answers four example questions.

00:01:16.183 --> 00:01:19.519
What information will the supplier handle?

00:01:19.519 --> 00:01:22.273
How important is the service?

00:01:22.273 --> 00:01:24.755
Is the evidence complete?

00:01:24.755 --> 00:01:27.604
Has continuity been assessed?

00:01:27.604 --> 00:01:33.491
The selected answers are evaluated by a configurable DMN-based decision.

00:01:33.491 --> 00:01:38.863
Here, the result is medium risk and a human review is required.

00:01:38.863 --> 00:01:42.485
Watch what happens when an answer changes.

00:01:42.485 --> 00:01:46.839
The score, matched rule and reasons update together.

00:01:46.839 --> 00:01:50.583
This is not a universal supplier-risk method.

00:01:50.583 --> 00:01:57.040
Your organisation would decide the real questions, thresholds and approval authority.

00:01:57.040 --> 00:02:01.923
The value is that the logic and the reason for the result stay visible.

00:02:02.070 --> 00:02:07.649
The insurance certificate is current, but the name on it is Kōwhai Group Limited.

00:02:07.599 --> 00:02:12.170
The purchase order names Kōwhai Field Services Limited.

00:02:12.170 --> 00:02:20.214
A fixed process can recognise that the evidence does not line up, but it cannot know which company will actually do the work.

00:02:20.214 --> 00:02:24.094
The reviewer opens an adaptive exception case.

00:02:24.094 --> 00:02:29.384
The documents, the question and the available follow-up work stay together.

00:02:29.384 --> 00:02:35.122
They can contact the supplier, check the contract or ask the site manager.

00:02:35.122 --> 00:02:41.972
A person decides what evidence is needed next, then the supplier can return to the normal route.

00:02:42.130 --> 00:02:46.040
The supplier approver receives one review pack.

00:02:45.990 --> 00:02:53.166
It contains the service, the evidence set, the risk result and the finding from the exception case.

00:02:53.166 --> 00:02:56.571
Pūnaha prepares the work and waits.

00:02:56.571 --> 00:03:00.640
It does not turn the recommendation into an approval.

00:03:00.640 --> 00:03:06.636
The reviewer can ask for more evidence, approve, or approve with a condition.

00:03:06.636 --> 00:03:15.006
In this walkthrough, they approve the supplier for twelve months and require the insurance evidence to be checked again at renewal.

00:03:15.006 --> 00:03:19.387
The choice and the review note remain with the supplier record.

00:03:19.550 --> 00:03:24.084
The approved supplier now has an active contract record.

00:03:24.034 --> 00:03:31.794
It begins on the first of July 2027 and expires on the thirtieth of June 2028.

00:03:31.794 --> 00:03:36.880
The owner and the renewal condition are visible beside those dates.

00:03:36.880 --> 00:03:45.399
The review start is calculated as three calendar months before expiry, which is the thirtieth of March 2028.

00:03:45.399 --> 00:03:51.056
In this scenario, a configured scheduled workflow checks the contract date.

00:03:51.056 --> 00:03:59.140
That means the next work can begin from the date in the record instead of relying on someone to remember a diary note.

00:03:59.290 --> 00:04:03.594
It is now the twenty-ninth of March 2028.

00:04:03.544 --> 00:04:08.102
The review task is scheduled, but it is not active yet.

00:04:08.102 --> 00:04:11.506
Move the scenario forward one day.

00:04:11.506 --> 00:04:19.889
On the thirtieth of March, the configured workflow reaches the three-month review point and opens the supplier review task.

00:04:19.889 --> 00:04:23.986
The task is assigned to the Supplier Assurance Lead.

00:04:23.986 --> 00:04:32.125
It includes the contract expiry, the earlier approval, the risk result, the documents and the exception finding.

00:04:32.125 --> 00:04:40.155
The reviewer has three months to do the work, and they do not have to reconstruct the supplier history before they can begin.

00:04:40.310 --> 00:04:48.453
The renewal reviewer checks what has changed, repeats the risk assessment and confirms the earlier insurance condition.

00:04:48.403 --> 00:04:54.425
The task shows each part of the review and keeps the supporting record close by.

00:04:54.425 --> 00:05:02.469
The responsible person can renew the supplier, renew with conditions, escalate the decision or plan an exit.

00:05:02.469 --> 00:05:05.711
Here, they choose a conditional renewal.

00:05:05.711 --> 00:05:14.094
Pūnaha records that outcome in the audit history with the earlier request, approval and review-task activation.

00:05:14.094 --> 00:05:24.065
One supplier record has now carried the work from onboarding to the next accountable decision, without removing the judgement from the people responsible for it.
