An incident memo usually gets written under pressure. Something has gone wrong — a fall in the yard, a phishing email that worked, a complaint about a colleague's behaviour — and you need the facts down while they are still fresh. Whatever you write in that first hour will be read later by people who were not there. That is the whole test: would a stranger understand what happened, and could they act on it?
Get the structure right and the memo almost writes itself. Get it wrong and you spend a fortnight answering questions the document should have answered already.
Start with purpose, not blame
An incident report memo has three jobs. It tells the right people what happened, it records the immediate response, and it creates a reliable record for whoever looks at the matter later — a manager, a safety officer, an insurer, an HR adviser. It is not a verdict.
Deciding whether someone was at fault, whether a claim is valid or whether a process failed belongs to a separate investigation. Mixing the two makes the record weaker, because your conclusions end up tangled with your observations. Write the facts as they are known, note what is still unclear, and stop there.
The blocks every incident memo needs
Whatever triggered it, an incident memo is built from the same handful of blocks. Include them all, even when a line feels obvious.
- Reference number. One simple code, so the memo can be found again.
- Incident date, time and location. Down to the room, bay, vehicle registration or webpage, as appropriate.
- Date and time the memo was written. A report written at 16:00 the same day is not the same document as one written three weeks later.
- People involved. Full names, roles, and whether they were injured, present, or simply the person reporting.
- What happened. A plain chronological account, no commentary.
- Immediate action taken. First aid, isolating equipment, locking accounts, calling the emergency services, informing a manager.
- Witnesses and evidence. Names, CCTV camera references, photographs, screenshots, ticket numbers.
- Current status and next steps. What is still open, who is investigating, what decision is awaited.
- Author and distribution. Your name, your role, and who is receiving the memo.
A header that does the boring work
Put a fixed block at the top of every incident memo: reference, incident time, report time, location, author, distribution. A repeating header means nothing gets forgotten when you are writing at ten to six on a Friday. It also makes incidents searchable. Reference numbers are what let somebody find the right record in two years' time.
Describe events as a timeline, not a story
Chronology beats narrative. Keep to roughly one event per sentence, put times on everything you can, and resist the urge to explain as you go. Compare these two:
Weak: "There was some confusion around the loading bay and a pallet ended up coming off the stack."
Stronger: "At 09:42 a forklift reversed out of bay 3. The pallet of tiles standing at the edge of bay 3 tipped forward and landed on the floor. No one was struck. The bay was closed at 09:47 and the area taped off."
The second version gives a reader times, positions and a clean sequence. It also avoids the word "confusion", which tells us nothing.
Separate what you saw from what you were told. "I saw the pallet fall" and "Tomas Reid, agency worker, told me he heard the reversing alarm" are different kinds of evidence, and a reader needs to know which is which. Gaps are fine too. "I do not know whether the alarm sounded" is a useful line. A guess is not.
What to leave out
- Speculation about cause. "The brake was probably worn" is a guess dressed up as a finding. Note it for the investigation, not the memo.
- Blame and character judgements. "Careless", "lazy", "difficult", "should have known better" — these invite dispute and prove nothing.
- Opinions about consequences. Whether someone should be retrained, moved or disciplined is a decision for others.
- Medical detail beyond what you observed. "Taken to hospital by ambulance" is usually enough. Clinical records belong with occupational health or HR.
- Unnecessary personal data. Home phone numbers, dates of birth and health conditions rarely help anyone understand the incident.
- Off-the-record remarks. Anything said "just between us" during the incident should not appear in a document that gets filed.
Tone that survives being read aloud
Write in plain past tense and keep the active voice where it is accurate — "Sara started the machine" is clearer than "the machine was started", as long as it is true. Avoid adjectives that carry judgement. "The fire door was propped open with an extinguisher" is factual; "someone stupidly propped the fire door open" describes the same event and starts an argument.
Skip the humour, even when it relieves tension. The joke lands badly when it is read by someone investigating an injury. Keep sentences short, and if a sentence contains more than one "and", split it. Aim the language at a reader who knows nothing about your department.
UK record-keeping habits worth having
One central register, with reference numbers, is the single most useful habit here. A memo that lives only in your sent items is a memo lost. Store incident records somewhere with restricted access rather than in shared drives, and record who has viewed or amended them.
Retention periods are set by your organisation, but accidents, complaints and suspected data breaches are usually kept longer than a routine near miss, because a claim or a complaint can surface much later. If in doubt, keep it. Many workplaces also keep an accident book for injuries; reference that entry in your memo rather than copying out injury details.
Under UK data protection rules, record personal information only as far as you need it, and remember that people can ask to see records held about them. Factual notes read very differently from opinionated ones.
This is general guidance, not legal advice. If a serious injury, a suspected data breach or a possible claim is involved, speak to your legal or HR adviser before circulating anything widely.
Before you hit send
- Does the first paragraph say what happened, where and when?
- Have the names, times and locations been checked against a second source?
- Have you separated what you saw from what you were told?
- Would you be comfortable reading the whole memo aloud to the people named in it?
- Are the evidence references — CCTV, photographs, ticket numbers — noted or attached?
- Does the distribution list match the sensitivity of the content?
An incident memo that answers those six questions is doing its job. Keep it factual, keep it dated, and file it where the next person can find it.
Photo: Alexas_Fotos / Pixabay
