What this is
What is a witness statement?
What is a witness statement?
A witness statement is a first-person record of what one person saw, heard or did around an event, captured in their own words rather than summarised by the investigator. It attaches to the incident or investigation record as evidence and is not itself an incident report.
How is a witness statement different from an incident report?
An incident report describes what the organisation understands happened, compiled after the fact from multiple sources. A witness statement is one person's uncorrected account, taken close to the event, and its value lies precisely in staying uncorrected — even where it conflicts with other statements.
Who needs to be present when a statement is taken?
The witness and an investigator, at minimum. The investigator's job is to record, not to lead or summarise; a second person taking notes is common where the statement may later be contested.
Scope
When is a witness statement required?
This record captures one witness's account for one event. Using it to build the organisation's version of events, or to record findings, blurs a first-person statement with analysis that belongs elsewhere.
Use this template when
- An event has just occurred and someone saw, heard or was involved in part of it
- An investigator needs an individual, uncorroborated account before comparing it against others
- The statement will support a Root Cause Analysis or a regulatory notification already under way
- A record is needed that survives being read out or disclosed later, with its own signature and timestamp
- A separate statement is needed from each person involved, rather than one combined account
Do not use it for
- Root Cause Analysis, which works out why something happened, not who was where and saw what.
- Corrective and Preventive Action, which records the fix, not the eyewitness account behind it.
- Just Culture Determination, which judges culpability rather than capturing testimony.
- Incident Report, which is the organisation's compiled account, not one person's own words.
- Anything outside General, which belongs in the workspace that owns that process
Compliance mapping
Which Investigation good practice requirements does this satisfy?
The template maps directly to how a defensible statement is actually taken, from identifying the witness to closing the record with two signatures.
| Clause | Requirement | Where it lands |
|---|---|---|
| Statement identity | Every statement carries its own ID and links to the case it supports | Header |
| Timing capture | The date the statement was taken and time elapsed since the event are both recorded | Header |
| Witness position | Where the witness was standing and what they could see from there is recorded, not assumed | Witness |
| Interviewer identification | The person taking the statement is named and accountable for how it was taken | Witness |
| Verbatim account | What the witness saw and heard is recorded without leading or summarising | Statement |
| Supporting evidence | A sketch, photo, audio or video can attach directly to the statement where words alone are ambiguous | Statement |
| Investigation linkage | The statement references the Root Cause Analysis it supports, without duplicating its content | Related records |
| Read-back and sign-off | The witness confirms the statement was read back and is accurate before both parties sign | Confirmation |
What it does not cover
- The statement was taken more than a few days after the event, which gives witnesses time to compare accounts and lets the record drift toward a shared story rather than an individual one.
- The investigator wrote the account and the witness only signed it, which turns testimony into paraphrase and invites the challenge that the words aren't actually the witness's own.
- Position When Event Occurred is left vague, which makes it impossible to establish what the witness could physically have seen from where they stood.
- No read-back confirmation is recorded, which leaves no evidence the witness ever agreed the written account matches what they said.
- The statement carries no interviewer signature, which leaves no one accountable for how the account was taken if the process is later questioned.
Global
Witness Statement requirements by country
How a witness statement holds up depends on where it might end up being read — a regulator's file, an employment tribunal, or a civil claim. The same document needs to survive all three.
Employment Tribunal and HSE investigation practice
A statement taken close to the event, in the witness's own words and countersigned, carries far more weight than one drafted from memory months later.
Treat every statement as if it may be disclosed and cross-examined, and keep the interviewer's process consistent across witnesses.
OSHA recordkeeping and civil discovery practice
Contemporaneous witness statements are treated as business records when taken as part of routine investigation, but lose that status if they read as an after-the-fact reconstruction.
Time-stamp statements at the point of capture and avoid editing them once the witness has signed.
Work Health and Safety Act investigation practice
Regulators and courts weigh witness statements by how soon after the event they were taken and whether the witness's own words were preserved.
Position and timing fields aren't administrative detail — they're what establishes the statement's reliability later.
How to complete it
How to complete a witness statement, step by step
Filling in the fields is mechanical. The judgement calls are about what to do when the witness's account doesn't cooperate.
Some questions are needed to get a witness talking, but every prompt risks becoming a lead. The defensible line is open questions only — what did you see, not did you see the guard rail down — and noting in the record when a specific question was asked.
Conflicting accounts aren't a problem to fix at the point of capture. Record each witness's account as given, flag the conflict for the investigator running the Root Cause Analysis, and resist the urge to reconcile them here.
If a witness says something that's factually wrong — the wrong time, the wrong person's name — it still goes in as said, with a note. Correcting it in the record erases the very inconsistency an investigator needs to see.
A statement taken weeks after the event, once people have talked, still has value but a different kind — treat it as a secondary account and say so, rather than presenting it with the same weight as one taken on the day.
What auditors find
Most common witness statement findings
These are the gaps that show up most often when witness statements are reviewed after the fact, usually once a case is already being scrutinised.
| Finding | Clause | What fixes it |
|---|---|---|
| Statement Date recorded but Time Since Event left blank | Header — Time Since Event | Require the field whenever the event date and the interview date differ, so lag is visible without cross-referencing two records. |
| Position When Event Occurred filled with a generic location rather than a specific vantage point | Witness — Position When Event Occurred | Prompt for what the witness could see from there, not just where they were standing. |
| What They Saw And Heard reads as a third-person summary | Statement — What They Saw And Heard | Reject statements drafted in the investigator's voice; require first-person, verbatim capture. |
| Anything Unusual Beforehand left blank as a default rather than genuinely answered | Statement — Anything Unusual Beforehand | Treat a blank answer as unconfirmed, not as 'nothing unusual', and follow up before closing the record. |
| RCA ID never populated even where an investigation is clearly under way | Related records — RCA ID | Make linking the statement to its investigation part of the RCA intake checklist, not an optional afterthought. |
| Witness Signature captured before Statement Read Back is confirmed | Confirmation — Statement Read Back | Sequence the form so read-back confirmation is required before the signature fields unlock. |
Case in point
Case in point: the statement that couldn't be used
An investigator taking statements after a forklift near-miss wrote up what three witnesses told him in his own summary paragraph, then had each one sign underneath. When the case reached a formal review months later, all three statements read almost identically — because they were, in substance, the investigator's account repeated three times.
None of the individual, sometimes contradictory, details that make a witness statement useful — who was actually looking at the forklift, who only heard the horn — survived the rewrite. The near miss was real, but the evidence built to explain it wasn't usable.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
5 sections
- Reference
- FDN-019
- Archetype
- Record
- Record ID
- WIT-2026-000
- Scoring
- Not scored
- Direction
- n/a
- Singleton
- Yes
- Basis
- Investigation good practice
- Links
- Linked to incidents
- Tags
- Investigation, Evidence
- Sections
- 5
- Fields
- 21
- Follow up fields
- 0
- Repeating sections
- 0
- Links out
- 2
Header
4 fieldsStatement ID*
Format WIT-2026-00000.
The record's own ID. Other templates point at this value.
Case ID*
The event this statement relates to.
Thread key
Statement Date*
Take statements as soon as possible, before people talk to each other.
Time Since Event
Witness
6 fieldsWitness Name*
Person ID
Links to FDN-003 Person ID
Role At Time*
What they were doing when it happened.
Position When Event Occurred*
Where they were, and what they could actually see from there.
Contact Number
Interviewer*
Statement
6 fieldsGuidance
Record what the witness saw and heard, in their own words. Do not lead, do not summarise, and do not correct their account.
What They Saw And Heard*
The witness's own words.
What They Did
Anything Unusual Beforehand
Often the most valuable part of a statement.
Sketch Or Photo
A rough sketch of positions is often clearer than words.
Audio Or Video
Related records
1 fieldRCA ID
The investigation this statement supports.
Links to FDN-013 RCA ID
Confirmation
4 fieldsStatement Read Back*
The witness has heard their statement read back and agrees it is accurate.
Witness Confirms Accurate*
Witness Signature*
Interviewer Signature*
FDN-019 · record IDs look like WIT-2026-000 · Linked to incidents
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form captures the words. Keeping statements consistent across witnesses, chasing the interviewer's signature and linking every statement back to its case is where the process actually breaks down.
Tracks every open witness statement against its incident, flags where a Statement Date is missing or lagging the event, and chases the interviewer for the outstanding read-back and signature.
Rolls witness statements into the wider investigation record, checking that each one links to its Root Cause Analysis rather than sitting unattached.
Watches for statements that may need to be disclosed to a regulator, and confirms the read-back and dual signatures are in place before that happens.
Holds the witness statement library against your registers, routes each record to its owner, and keeps the evidence trail together — never editing a signed statement without your approval.
This template lives in General — control tower. The orchestration layer. Registries and engines every other workspace reads from.
Meet General→Glossary
Witness Statement definitions and key terms
- Verbatim account
- The witness's own words, recorded as given, without paraphrasing or correction by the interviewer.
- Read-back
- The step where the statement is read aloud to the witness so they can confirm, before signing, that it says what they meant.
- Leading question
- A question that suggests its own answer, such as asking whether a guard was down rather than asking what the witness saw.
- Contemporaneous record
- A record made at or close to the time of the event, valued because memory and motive haven't yet had time to shift.
- Corroboration
- Where one witness's account is supported, wholly or partly, by another's — established by comparing statements after they're taken, not while taking them.
FAQ
Frequently asked questions about witness statement
What is the witness statement template based on?+
It follows established investigation good practice rather than a single named standard — take the account as soon as possible, in the witness's own words, with a read-back and signature before it's treated as final.
What sections does the witness statement contain?+
Five: Header, Witness, Statement, Related records and Confirmation, holding 21 fields between them, 12 of which are required.
Does every witness need their own statement?+
Yes. Combining several witnesses into one record collapses individual, sometimes conflicting, accounts into a single narrative and defeats the purpose of taking statements separately.
Can a witness statement be edited after it's signed?+
No. Once read back and signed, the statement stands as taken; a later correction or addition goes in as a new, dated entry rather than an edit to the original.
Does a witness statement replace the incident report?+
No. It supports the incident and investigation record as one piece of evidence; the incident report is the organisation's compiled account, built from statements, physical evidence and other records together.
Who should take the statement — the line manager or an independent investigator?+
Wherever possible, someone without a stake in the outcome. A line manager who was also involved in the event, or who supervises the witness, compromises the statement's independence even if it's accurate.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Incident and Investigation
Root Cause Analysis
Finds out why something happened rather than who was involved
Corrective and Preventive Action
The single action record used everywhere
Finding
Records a single deficiency picked up during an audit, inspection or check
Effectiveness Verification
Checks whether an action actually worked, some time after it was put in place
Just Culture Determination
Separates a system problem from a genuine choice to take a risk, using a consistent set of questions
Extent of Condition Review
Asks two questions after an investigation: where else does this same condition exist, and where else could this same cause bite us
More in Engines
Risk Assessment
The single risk assessment used across the whole business
Root Cause Analysis
Finds out why something happened rather than who was involved
Corrective and Preventive Action
The single action record used everywhere
Finding
Records a single deficiency picked up during an audit, inspection or check
Effectiveness Verification
Checks whether an action actually worked, some time after it was put in place
Just Culture Determination
Separates a system problem from a genuine choice to take a risk, using a consistent set of questions
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 45001:2018 cl.10.2 — Incident, nonconformity and corrective action
- HSE INDG245 — Investigating accidents and incidents (a workbook for employers)
- OSHA 29 CFR 1904 — Recording and reporting occupational injuries and illnesses
- Work Health and Safety Act 2011 (Cth) — incident investigation and evidence gathering
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.