What should be written down immediately after a workplace injury?

What happened, where, when, who was involved, who witnessed it, and what was done immediately afterward — in plain, factual language, before memory of the details starts to soften. Reporting deadlines and required forms are set by your regulator and insurer and vary by jurisdiction and severity; this page addresses the record itself, not those specific obligations.

Who typically reads an incident record months later, and what do they need from it?

An insurance adjuster, a regulator, a lawyer, or your own future self trying to understand a pattern across incidents — none of whom were present when it happened. They need the record to be complete on its own terms: specific enough that someone with no memory of the day can reconstruct what occurred without asking anyone to fill in gaps from recollection.

Should an incident record include an opinion about fault or cause?

Separate the two. Record the observable facts — what happened, in what order, who was present — as their own section, and any opinion about cause or fault as a clearly labeled separate section, ideally attributed to whoever is offering it. Blending speculation into the factual account weakens the factual account and makes both harder to trust later.

How does an incident record relate to a training or certification record?

An investigation into an incident often asks whether the person involved had received relevant safety training or held a required certification at the time. If those records are logged against the same named employee, the question can be answered directly. If labor, training, and incidents are tracked in disconnected systems, answering it becomes a reconstruction project.

Injury and Incident Records on the Farm

An incident record is written on the worst day and read, almost always, by someone who was not there. That gap between writer and reader is what makes it a different kind of document from every other record on the farm. A labor log or a spray record is usually read by someone who could, if needed, ask the person who wrote it a follow-up question. An incident record often cannot be followed up on — the moment is gone, the people involved remember less each month, and the record is what stands in for all of it.

It is also written under conditions that work against good record-keeping: adrenaline, urgency, sometimes shock, and often more than one person talking at once about what just happened. The combination — a document that has to be unusually complete, written under unusually poor conditions for completeness — is why incident records fail more often than almost any other kind of farm record, and why they deserve deliberate structure decided in advance, not improvised in the moment.

This page is about building that structure ahead of the day you need it, so the record written in a bad moment still reads clearly to someone much later who was not there.

This is not legal or safety advice. Reporting deadlines, required forms, and notification obligations after a workplace injury are set by your regulator, your insurer, and your jurisdiction, and they vary by severity and by industry. Nothing here tells you what your operation is required to report or by when. What follows is about the shape of the underlying record, not your reporting obligations. For those, consult your regulator, your insurer, and a lawyer.

The record is written by someone who is not thinking clearly, for a reader who was not there

Both halves of that sentence work against the record. The person writing it is often the person closest to the incident, which means they are also the person least likely to be composed enough to write carefully. And the eventual reader — an adjuster, a regulator, a lawyer, or your own future self reviewing a pattern across a season — has none of the context that was obvious to everyone standing in the field that afternoon.

A record that relies on the writer’s composure or the reader’s shared context will fail on both counts. The fix is not to expect calm writing in the moment; it is to have a structure fixed in advance that a rattled person can fill in quickly, and that a stranger can read without needing anything filled in around it.

Facts first, separated cleanly from opinion

The most useful incident records keep two things in clearly separate sections: what was observed, and what anyone believes caused it. What happened, in order, who was present, what was done immediately after — that section should read like a timeline, free of speculation. A separate section can hold opinions about cause or fault, attributed to whoever is offering them, but it should never be blended into the factual account.

Blending the two weakens both. A factual timeline that includes a guess about cause reads, months later, as if the guess were observed rather than inferred. And a genuine opinion about cause, buried inside a factual account, is harder for a later reader to identify and weigh appropriately.

Specificity is what makes the record usable later

“A worker was injured near the barn” is a sentence that feels adequate on the day, because everyone reading it already knows which worker, which barn, and roughly what happened. None of that context survives to the reader who actually needs the record — the one reading it cold, months later, with none of the shared knowledge that made the vague version feel sufficient at the time.

Write it for that reader: the specific person, by name, the specific location, the specific time, the specific sequence of events, and the specific people who witnessed it or responded. It is the same discipline that makes a safety training record defensible — resolving to individuals and specifics rather than a general description that felt complete only because the writer already knew what it meant.

Where the incident record connects to the rest of the labor file

An investigation into an incident routinely asks whether the person involved had received relevant safety training, held a required certification, or had logged hours consistent with the task at the time. If the incident record, the training record, and the labor log all point at the same named employee, that question has a direct answer. If they live in separate systems — a paper incident form here, a training binder there, payroll somewhere else — answering it becomes a reconstruction exercise under the same time pressure that made the incident record itself hard to write well.

The connection runs in both directions. A certification that had lapsed before an incident is a fact an investigator will look for specifically, and it can only be found if the certification record and the incident record resolve to the same person. A farm that tracks expiry dates carefully but cannot connect them to a named incident report has built half of the answer and left the other half undiscoverable.

This is the practical argument for keeping labor records against real named employees in the first place: an incident record is only as useful as the other records it can be checked against, and it can only be checked against them if all the records resolve to the same person.

Building the structure before you need it

The single most effective thing a farm can do for incident recordkeeping is decide the structure — the sections, the questions, the fields — before an incident happens, so the day it is actually needed is not the day the format is invented. A short, fixed template, filled in quickly, beats a blank page that a shaken person has to structure from scratch.

Farm40 lets an incident be logged against a named employee alongside their existing training and certification history, so a later reader can see, in one place, what training that person had received and what certifications they held at the time. The limit: Farm40 stores the record you enter; it does not structure the incident narrative for you beyond a text field, does not determine what must be reported to a regulator or insurer, and does not judge cause or fault. Those calls, and the reporting obligations that follow an incident, remain yours and your regulator’s.

Write it for the reader who was not there. That reader is who the record is actually for.

Frequently asked questions

What should be written down immediately after a workplace injury?: What happened, where, when, who was involved, who witnessed it, and what was done immediately afterward — in plain, factual language, before memory of the details starts to soften. Reporting deadlines and required forms are set by your regulator and insurer and vary by jurisdiction and severity; this page addresses the record itself, not those specific obligations.
Who typically reads an incident record months later, and what do they need from it?: An insurance adjuster, a regulator, a lawyer, or your own future self trying to understand a pattern across incidents — none of whom were present when it happened. They need the record to be complete on its own terms: specific enough that someone with no memory of the day can reconstruct what occurred without asking anyone to fill in gaps from recollection.
Should an incident record include an opinion about fault or cause?: Separate the two. Record the observable facts — what happened, in what order, who was present — as their own section, and any opinion about cause or fault as a clearly labeled separate section, ideally attributed to whoever is offering it. Blending speculation into the factual account weakens the factual account and makes both harder to trust later.
How does an incident record relate to a training or certification record?: An investigation into an incident often asks whether the person involved had received relevant safety training or held a required certification at the time. If those records are logged against the same named employee, the question can be answered directly. If labor, training, and incidents are tracked in disconnected systems, answering it becomes a reconstruction project.