Incident Reporting in Aged Care

Write it while it is fresh

The quality of an incident report is decided in the first twenty minutes, not in the review a week later. Details that matter at review time are the ones that evaporate first: which lights were on, what the resident was doing, who was where, and what was said. If the report is finished at the end of a shift, most of that is already gone.

The practical rule is that the first entry is written by the person who responded, before the shift ends, in whatever form is fastest. Cleaning up the language can wait. Losing the detail cannot.

What to capture

A useful incident record is factual and specific. Six fields cover the ground.

• What happened: a single neutral sentence with no conclusion attached.
• When and where: time, room or zone, and how the area was lit.
• Who was present: staff roles and who found the resident, without speculation about fault.
• The resident's state before and after: mobility, orientation, and anything unusual that day.
• What was done: the immediate response, who was called, and when.
• What happens next: the review date and the named owner of any change.

What to leave out

Two things do not belong in the first write-up. The first is diagnosis: staff should record observed facts and let clinical judgement come from the clinician. The second is blame. A record that reads as an accusation will be written defensively from that point on, and a defensive record is a less useful one.

This is also why the incident record and the resident's risk record should be different documents that reference each other, rather than one document doing both jobs badly. The risk record is described in our note on assessing fall risk.

The 24-hour review

An incident that is filed and never read has cost time and changed nothing. Put a review inside 24 hours, on the calendar, with three questions: what did we already know, what would have made this less likely, and what single change is worth making.

Keep the answers short and name an owner for each change. A review that produces four actions and no owner produces nothing. Where an incident involves a resident's family, the review should also decide what is communicated and by whom, which is a communication problem we cover separately in keeping families informed.

Incidents and near-misses

A near-miss is a fall that did not happen: the resident caught the rail, the staff reached them in time, the chair slipped but nobody went down. Near-misses are the cheapest evidence you will ever get about where your risk actually is, and they are almost always under-reported because nothing went wrong.

Give near-misses a one-line form and a visible count. Homes that track them usually find a pattern in the corridors within a month.

Making the reports add up to something

Individually, incident reports are noise. Aggregated, they are a map. Once a month, strip the reports of names and look at them by zone, by hour and by activity. The pattern is usually not 'this resident falls'; it is 'this corner, at this time, during this routine'.

That pattern is what turns a record-keeping habit into prevention. Technology can help here by producing the timestamp and zone automatically, which is one of the things a zone-based monitoring system does; the sensing side of our own family of products is Steadicore, and the training side is Sanospark.

Think about the three audiences

Every incident record is read by three different people: the clinician deciding what to change, the manager answering for the home, and, eventually, a family member or an inspector who wants to know what happened. Writing for all three at once is what makes a report worth keeping. Our FAQ covers the questions we get asked about how the platform records and reports events.

Who writes, and when

Reports written by one designated person are usually worse than reports written by whoever responded, because detail degrades every time it is retold. The person who was there should own the first entry, even when a manager later edits the wording.

This also settles the awkward case where the responder is the manager on duty. The rule does not change: the nearest person writes first, the review happens later, and a first entry is not quietly smoothed afterwards without a note saying so.

Keep the first entry in the resident's own environment, on the device or the pad that the shift actually uses. A form that has to be fetched from an office will be completed from memory, and memory is at its worst at the end of a night shift.

Two things never to write

Two phrases weaken a report more than any omission. The first is an explanation that begins with because, when the cause has not yet been established. The second is any sentence that reads as an accusation, however gently worded, because it changes how the next report is written.

Neither phrase is dishonest, and that is the point. A report is a record of observation, and cause belongs to the review, where it can be tested against the whole picture rather than guessed at within twenty minutes of an event.