Complex complaint investigation and resolution in Pūnaha Voice: en-NZ-MollyNeural (natural synthetic voice) Prepared Pūnaha walkthrough. The organisation, participants, allegations, evidence, findings and outcomes are fictional. This is not legal or human resources advice. Nothing is submitted, sent or saved. Chapter 1: Open the active investigation This walkthrough begins after a fictional conduct complaint has already been accepted for investigation. There is no service request, contact form or ticket queue. The case contains three allegations about an organisational decision meeting and the actions that followed it. Select Open investigation record. The original allegations, four participant roles, six evidence items and the final decision authority become visible together. This starting point matters because an investigation should not quietly change its own history. The case preserves the scope that was approved at the beginning, even when later evidence changes the work. Everything shown here is prepared demonstration information. No real complaint, participant or customer record is used. Chapter 2: Check independence Before examining the evidence, the organisation checks who can investigate. One candidate worked on the original decision. Another is a member of the panel that will make the final organisational decision. The prepared independent reviewer has no declared connection to the events. Select Confirm investigator. The case now records who will investigate and keeps the governance panel separate. Pūnaha does not decide whether a relationship creates a legal or professional conflict. The organisation defines those rules and an authorised person confirms the assignment. The walkthrough makes the separation visible so the findings and the final decision do not appear to come from the same unchecked role. Chapter 3: Build the evidence map A long bundle of documents does not explain an investigation by itself. Select Build evidence map. The first allegation concerns conduct during the meeting and already has two statements that conflict. The second concerns information that may have been withheld and still has a missing source. The third concerns an action taken after the meeting and has two supporting records. The map connects each ground to the material that supports it, contradicts it or is still missing. It also turns the allegations into clear investigation questions. The investigator can see what work is needed without treating the volume of documents as proof of any conclusion. Chapter 4: Prepare the source-linked chronology The records describe events across one working day. A configured model can help organise that material, but its draft must remain tied to the sources. Select Prepare source-linked chronology. Four events appear with five source references. The briefing pack, meeting start and later approval are supported by the prepared records. The event at ten forty-two remains disputed because the accounts disagree about what information the group received. Pūnaha leaves that conflict visible. The investigator checks the draft and corrects anything that the sources do not support. AI is useful here because it reduces the effort of arranging material. It does not turn an uncertain statement into a fact. Chapter 5: Start the investigation plan The case now has enough structure to begin the investigation work. Select Start investigation plan. Required activities become active for reviewing the meeting records, obtaining participant responses and completing the evidence checkpoint. Specialist advice remains discretionary. The investigator can activate it if the evidence makes that useful, rather than forcing every complaint through the same path. A published workflow can coordinate the repeatable requests and checkpoints, while the adaptive case holds the work that depends on judgement. The evidence checkpoint blocks findings until the required material has been considered. The case plan provides discipline without pretending that the investigation outcome is already known. Chapter 6: Compare conflicting accounts Two participants agree that additional information was discussed during the meeting. They disagree about whether the complete material was available before the decision. Select Compare the accounts. The comparison records one agreed event, one material contradiction and one missing meeting attachment. It does not label either participant as credible or unreliable. That judgement belongs to the investigator and may require more evidence. The missing attachment becomes the next evidence request. Presenting the accounts side by side helps the investigator see the exact point of disagreement while preserving the original statements. The product organises the comparison. It does not decide which person should be believed. Chapter 7: Respond to new evidence A later witness statement introduces conduct that was not part of the approved investigation scope. The statement relates to the action taken after the meeting and identifies another participant. The investigator has three choices: extend this investigation, open a separate linked matter or record the evidence for later review. Keep Extend this investigation selected, then choose Record scope decision. A fourth allegation and its related work are added. The original three allegations, completed work and earlier evidence remain intact. The case also records why the scope changed. This is the central adaptive moment in the walkthrough. New evidence changes the plan without silently rewriting what the investigation was originally authorised to examine. Chapter 8: Record human findings After the evidence work is complete, the investigator records a separate finding for each allegation. Select Record prepared findings. The fictional example records a mixture of supported, partly supported and unable-to-determine results. Each finding would retain its reasons, the evidence relied on and any remaining limitation. No model chooses these values. AI may help prepare a draft summary, but the investigator must check the record and make the professional judgement. Keeping the allegations separate prevents one strong piece of evidence from being treated as proof of every complaint ground. It also gives the later decision-maker a clear view of what was found and where uncertainty remains. Chapter 9: Make the independent decision The investigation findings now go to the governance panel. The decision pack shows four findings, the recorded scope change, two evidence limitations and three proposed organisational actions. Select Approve outcome. The panel note and authorised outcome are recorded separately from the investigator's work. In a real implementation, the organisation decides what authority the panel has, what options it can choose and what further review may be available. Pūnaha keeps the handover visible and can wait for the authorised people to act. It does not recommend disciplinary action or choose a consequence. The distinction between investigation and decision remains clear in the case history. Chapter 10: Track actions and follow-up A complaint is not finished simply because a decision has been recorded. Select Start follow-up work. The approved actions now have owners and dates. One corrects the decision record. Another clarifies what information must be available for future meetings. A later assurance review checks whether the agreed changes were completed. The follow-up remains connected to the complaint, its evidence and the panel decision. If the organisation needs to revisit the matter, the earlier scope, findings and reasons are still available. This closes the fictional walkthrough with accountable work rather than a neat but empty status. The scenario shows how knowledge, workflow, adaptive cases, decisions and human responsibility can operate together.