Sample records
Three fictional records that show layout, speaker attribution and numbered references. None uses client material, and none is a certified transcript or official record.
Read the samples
Each record runs to 28 numbered lines; you raise corrections by line number.
Disciplinary appeal hearing
Video meeting (fictional)
14 July 2026
Intelligent-verbatim record
- MC Marian Cole, Appeal chair
- DS David Shah, Presenting manager
- EM Elena Morris, Appellant
- RB Ruth Bell, Companion
(opens the PDF in a new tab)Synthetic test exemplar. All details are fictional. Not a client record, certified transcript or official record.
| Ref. | Initials | Message |
|---|---|---|
| 001 | MC | Good morning. The time is 09:30. This is the appeal hearing concerning the written warning issued on 2 July. I will first confirm who is present. |
| 002 | DS | David Shah, operations manager. I am presenting the management case. |
| 003 | EM | Elena Morris. I am the appellant. |
| 004 | RB | Ruth Bell, attending as Elena’s workplace companion. |
| 005 | MC | Thank you. Elena, have you received the appeal papers and the meeting procedure? |
| 006 | EM | Yes, I received them on Friday. I have read them, although I have one correction to the chronology. |
| 007 | MC | We will take that correction when we reach the chronology. Is there anything you need before we begin? |
| 008 | EM | No, thank you. |
| 009 | MC | David, please summarise the reason for the warning. |
| 010 | DS | The warning followed three late submissions of the weekly control report. The dates were 6 May, 20 May and 3 June. |
| 011 | EM | Sorry - may I clarify that the 20 May report was sent before the deadline? |
| 012 | MC | You will have an opportunity to respond. David, please finish the summary, and then I will come back to that point. |
| 013 | DS | Of course. Management’s position is that the agreed reporting process was not followed on those three dates and that the delays affected the review meeting. |
| 014 | MC | Thank you. Elena, please give your grounds of appeal. |
| 015 | EM | My first ground is that the chronology is inaccurate. On 20 May, I sent the report at 15:42. The deadline in the team email was 16:00. |
| 016 | MC | Which document contains that email? |
| 017 | EM | It is document E3 in my appeal pack. The sent email is immediately behind it. |
| 018 | DS | I accept that the email shown at E3 says 16:00. The local tracker recorded the report at 16:08, which is why it was treated as late. |
| 019 | RB | The appeal point is that the report was sent on time, even if the tracker updated later. |
| 020 | MC | Understood. I will record that as a point requiring verification. David, can the tracker timing be checked after this meeting? |
| 021 | DS | Yes. I can ask the systems team to confirm when the attachment reached the shared folder. |
| 022 | MC | Please do that by 16:00 tomorrow. We will not reach a decision until the check is complete. |
| 023 | EM | Thank you. My second ground concerns the 3 June report. I had notified my manager that I was attending an urgent client call. |
| 024 | MC | Do you rely on a particular document for that notification? |
| 025 | EM | Yes, document E7. It is a message sent at 13:11. |
| 026 | DS | I have E7. Management accepts the message was sent, but the handover arrangements were not clear. |
| 027 | MC | All right. We will distinguish the notification issue from the handover issue. Please continue, Elena. |
| 028 | EM | Those are my main points. I am asking for the warning to be withdrawn or reduced. |
Investigation interview
Remote interview (fictional)
22 July 2026
Intelligent-verbatim record
- PA Priya Anand, Investigator
- TR Thomas Reed, Interviewee
- NW Naomi West, HR adviser
- AG Alex Green, Note taker
(opens the PDF in a new tab)Synthetic test exemplar. All details are fictional. Not a client record, certified transcript or official record.
| Ref. | Initials | Message |
|---|---|---|
| 001 | PA | Please state your name, role and how long you have worked in the service team. |
| 002 | TR | My name is Thomas Reed. I am a senior service coordinator, and I have worked in the team for four years. |
| 003 | PA | Were you working on Monday 13 July? |
| 004 | TR | Yes. I started at 08:00 and was scheduled to finish at 16:00. |
| 005 | PA | What first drew your attention to order RM-418? |
| 006 | TR | At about 10:15, the dashboard showed it as urgent and unassigned. I opened the record to check the notes. |
| 007 | PA | What did the notes say? |
| 008 | TR | They said the customer had called twice about a delivery needed for a site inspection the next morning. |
| 009 | PA | What did you do after reading that? |
| 010 | TR | I messaged the allocations channel and asked whether anyone had contacted the supplier. I also called the supplier’s main number. |
| 011 | PA | Did anyone respond in the allocations channel? |
| 012 | TR | Maya replied at 10:23 and said she had emailed the supplier but had not received an answer. |
| 013 | PA | Do you have a copy of that exchange? |
| 014 | TR | Yes. It is included as attachment TR2. |
| 015 | PA | The call log records an outgoing call at 10:31 lasting 46 seconds. Is that the call you mentioned? |
| 016 | TR | Yes. The call went to voicemail, and I left my name and the order reference. |
| 017 | PA | Why was the order still shown as unassigned at 11:05? |
| 018 | TR | I believed Maya was continuing with it because she had already emailed. I did not change the owner field. |
| 019 | PA | Was that consistent with the team’s escalation procedure? |
| 020 | TR | No. Looking back, I should have assigned it to myself or asked Maya to confirm ownership in the record. |
| 021 | NW | For clarity, which version of the escalation procedure are you referring to? |
| 022 | PA | The version dated 1 April 2026, document I4. |
| 023 | TR | That is the version I had read. |
| 024 | PA | Did workload or staffing affect your decision at the time? |
| 025 | TR | We had two people absent, but I would not say that prevented me from updating the owner field. It was an oversight. |
| 026 | PA | Is there anything else that would help explain the sequence? |
| 027 | TR | Only that I did not intend to leave the order unattended. I thought the channel message had made the handover clear, but I accept the record did not show that. |
| 028 | PA | Thank you. I will send you the draft transcript for factual corrections. Please identify any correction by the three-digit reference number. |
Project governance meeting
Video meeting (fictional)
5 August 2026
Structured meeting record
- AM Aisha Morgan, Chair
- BC Ben Carter, Project lead
- SE Sofia Evans, Finance lead
- DW Daniel Wu, Operations lead
(opens the PDF in a new tab)Synthetic test exemplar. All details are fictional. Not a client record, certified transcript or official record.
| Ref. | Initials | Message |
|---|---|---|
| 001 | AM | The meeting opened at 14:00. Apologies were received from Louise King. The minutes of 15 July were approved without amendment. |
| 002 | AM | Item one is the implementation timetable. Ben, please give the current position. |
| 003 | BC | Configuration is complete in the test environment. User testing starts on Monday and is scheduled for two weeks. |
| 004 | AM | Is the 1 September launch date still achievable? |
| 005 | BC | Yes, provided the data-validation issue is closed by 18 August. That is the main dependency. |
| 006 | DW | Operations can provide two additional testers next week. I will confirm their names by Friday. |
| 007 | AM | Action DW1: Daniel to confirm two operations testers by 7 August. |
| 008 | SE | The approved budget includes testing support, but not additional supplier days. Are any extra days expected? |
| 009 | BC | Not at present. The supplier has used 18 of the 22 days in the statement of work. |
| 010 | SE | Please include the remaining-day count in the weekly report so finance can track the exposure. |
| 011 | AM | Action BC1: Ben to add supplier days used and remaining to the weekly report from 10 August. |
| 012 | AM | Item two is communications. The draft staff notice was circulated yesterday. Has everyone reviewed it? |
| 013 | DW | I have reviewed it. The support contact should be the service desk rather than the project mailbox after launch. |
| 014 | BC | Agreed. I will amend that line and add the opening hours. |
| 015 | SE | The notice should also avoid saying the new process is mandatory until the policy approval is recorded. |
| 016 | AM | Decision: the notice will say the process is planned to take effect on 1 September, subject to final policy approval. |
| 017 | AM | Action BC2: Ben to circulate the amended notice by 12:00 on 6 August. |
| 018 | AM | Item three is risk. The current top risk is incomplete data validation. What mitigation is in place? |
| 019 | BC | A daily exception report is now running. Thirty-two records failed yesterday; eleven remain unresolved this morning. |
| 020 | DW | My team can review the remaining eleven today if the report includes the source-system owner. |
| 021 | BC | It does. I will send the report immediately after the meeting. |
| 022 | AM | Action BC3: Ben to send the exception report to Daniel today. Action DW2: operations to return the reviewed records by 16:00 on 6 August. |
| 023 | SE | If the unresolved count is above five on 14 August, should the launch decision return to this group? |
| 024 | AM | Yes. Decision: more than five unresolved validation exceptions on 14 August triggers an extraordinary governance meeting. |
| 025 | AM | Any other business? |
| 026 | DW | No additional items. |
| 027 | SE | None from finance. |
| 028 | AM | The next scheduled meeting is 19 August at 14:00. The meeting closed at 14:47. |
A sample from your own recording
As a new client, you can ask for a complimentary transcript of up to 15 minutes of an authorised recording, subject to suitability and availability. Custom formats are possible. Keep recordings and sensitive material out of your first message.