Ombudsman investigations depend on impartiality, source control and reasoning that can be followed by both parties. Voice recording can support interviews and analytical notes, but it cannot decide jurisdiction, weigh evidence or approve a final determination. Those functions remain with authorised investigators and decision-makers.
Confirm remit and investigation scope
Before gathering evidence, record the complaint points accepted for investigation, the matters outside jurisdiction, the relevant time period and the remedy or recommendation within the organisation’s powers. If the scope changes, document who authorised the change and notify the parties through the approved process.
Identify the policies, legislation, standards or service commitments relevant to the case, including the version and effective date. Avoid introducing a requirement that did not apply at the time of the events.
Use an authorised interview protocol
Follow the organisation’s procedure for recording interviews. Explain the purpose, access, retention and permitted use of the recording, and obtain the necessary agreement or authorisation. Provide an alternative where required. Confirm the speaker’s role and connection to the events without collecting irrelevant personal details.
Use neutral, open questions before testing specific inconsistencies. Do not use an AI-generated summary as a substitute for the speaker’s actual account. Important statements should be checked against the audio and, where appropriate, confirmed in writing.
Create an allegation-response-evidence matrix
For each complaint point, maintain separate columns for:
- the complainant’s allegation and supporting account;
- the organisation’s response;
- documents, records and independent evidence;
- evidence supporting each position;
- contrary evidence and unresolved gaps;
- the provisional finding and reason.
This prevents a strong narrative from being mistaken for stronger evidence. It also makes it easier to show that both parties’ relevant submissions were considered.
Control chronology and provenance
Build a dated chronology using source-linked entries. Each entry should identify whether the date comes from a contemporaneous document, a system record, an interview recollection or an inference. Where sources conflict, preserve the conflict and investigate it rather than selecting the most convenient date.
For every important document, record the provider, date received, author, version, relevant section and any question about completeness or authenticity. Keep original files unchanged and work from controlled copies where the procedure requires it.
Maintain impartial analysis
Separate process failings from disagreement with an outcome. An organisation may reach an unfavourable decision through a fair process, or reach a reasonable outcome despite weaknesses in its administration. Analyse the relevant complaint test rather than assuming that poor communication proves the substantive decision was wrong.
Actively record evidence that challenges the emerging view. Note alternative explanations and why they were accepted or rejected. Apply the organisation’s stated standard or approach to evidence; do not invent a higher or lower threshold for a particular party.
Draft findings and invite representations
Write a provisional finding for each complaint point using the evidence, applicable standard and reasoning. Identify facts that remain uncertain. Where the process permits, send draft findings or relevant adverse material to the parties and record their representations.
Assess whether new submissions change the evidence matrix, chronology or remedy analysis. A response should not be dismissed simply because it arrives late unless the applicable procedure supports that decision and the reason is documented.
Decision, remedy and human approval
The final decision should state the scope, evidence considered, finding on each point, reasoning and any remedy or recommendation. Link remedies to the identified injustice or service failure. Record who approved the determination and the date of approval.
AI-generated text should never issue or approve a determination. It can help organise material, but the investigator must verify quotations, dates, names, document references and the balance of evidence.
Access, retention and disclosure
Limit recordings and transcripts to the case team and authorised reviewers. Apply redaction and disclosure rules consistently. Retain material according to the approved case schedule and delete unnecessary working copies, duplicate exports and audio after the authorised period.
The NERALVO Halo AI Voice Recorder can support interview capture and structured transcription through the DOWAY app. The resulting notes should be treated as working material until checked against the audio and integrated into the controlled case record.
Defensibility checklist
- Is jurisdiction and scope clearly recorded?
- Were recording permissions and interview procedures followed?
- Can every significant fact be traced to a source?
- Are both parties’ accounts and contrary evidence visible?
- Does each finding identify the standard, evidence and reasoning?
- Were representations considered before final approval?
- Is the remedy linked to the identified failure or injustice?
Ready to capture meetings properly?
View the NERALVO Halo AI voice recorder with 64GB local storage, meeting capture, compatible phone-call recording workflows and one year of DOWAY Max included.
View NERALVO Halo