Can AI change the facts in your incident report?

Yes, and quietly. Rough field notes go into ChatGPT or Copilot, a clean report comes out, and it reads better than anything written at the end of a long shift. But a report that reads well is not the same as a report that says what you saw.

The short answer

Asked for a clearer or shorter report, general AI tools rewrite all of it, including the facts.
The usual changes: an approximate time becomes exact, “unknown” or “estimated” disappears, a doubt moves to a different fact.
Before you submit, compare the AI version with your notes. The checklist below takes about two minutes.

A real example

A crew's notes on an offshore sheen:

Crew reported a sheen on the water near the platform leg around 1100 hrs. Volume unknown, appears minor. Possibly from the transfer hose but we have not confirmed. Notified USCG at 1215.

Asked to make them “clearer and more concise”, a general-purpose AI assistant returned this (run on 30 September 2026, copied exactly):

At 1100 hrs, the crew spotted a minor, unconfirmed sheen near the platform leg, possibly from the transfer hose. The USCG was notified at 1215.

It is shorter and tidier, and it now reports three things the crew never said:

An exact time. "Around 1100" became "at 1100", a time nobody recorded.
A size. "Volume unknown, appears minor" became "minor". If the release turns out larger, your own report already called it minor.
A different doubt. The crew saw the sheen; what they had not confirmed was its source. The rewrite made the sheen itself "unconfirmed" instead.

None of these is a typo. Each one is the kind of change a language model makes when it is asked to sound clear and confident: qualifiers look like clutter, so they go.

Why it matters

An incident report is rarely read only once. A client, an insurer, an investigator or a regulator may read it weeks later, and they will take its words as the facts as they were known at the time.

Take the sheen above. Under the EPA discharge-of-oil rule, a discharge that causes “a film or sheen upon or discoloration of the surface of the water” is one that may be harmful, and the person in charge must notify the National Response Center immediately. A report that turns an observed sheen into an “unconfirmed” one changes the very fact that decides whether a report was due.

Records matter on the safety side too. Under section 17(g) of the OSH Act, knowingly making a false statement in a required record or report can bring a fine of up to $10,000, up to six months in prison, or both. An AI change you never noticed is not a knowingly false statement. But once you have read a report and signed it, its words are yours, which is the best reason to read it against your notes first.

Before you submit an AI-edited report

1
Put the AI version next to your notes
Read them side by side, or paste both into a compare tool so every change is highlighted. A changed figure is easy to miss in a paragraph that reads well. Our free Text Compare runs in your browser.
2
Check every number and unit
Quantities, pressures, depths, volumes and their units should match your notes exactly. Watch for rounding: "about 2 bbl" is not "2 bbl".
3
Check every time
If the notes say "around" or "approx.", the report must too. An exact time is a claim that someone looked at a clock.
4
Keep every hedge
"Appears", "estimated", "suspected", "not yet confirmed": these words carry the facts as you knew them. Tools asked for a concise report tend to drop them first.
5
Keep cause and observation apart
What was seen and what is suspected to have caused it are different facts. Make sure the doubt stays attached to the right one.
6
Check nothing was added
No new names, quantities, actions or conclusions that are not in your notes, however reasonable they sound.
7
Keep your original notes
Save the rough notes as their own file. If a question comes up later, you can show what was observed and what the tidied report said.

Where ABCcount fits, exactly

ABCcount's Energy mode turns rough field notes into a clean report and then checks the result against what you wrote: times, figures, units, “approx” and “suspected” must come back exactly as they went in, and field abbreviations keep their meaning.

It cannot tell whether your notes are right, so the checklist above still applies. Try it free: 7 days of Pro for one person, or a 14-day pilot for your crew. No card.

Start a free trial See Energy mode

Frequently asked questions

Can AI change the numbers in an incident report?

Yes. Asked to make a report clearer or more concise, general AI tools rewrite all of it, and that can make an approximate time exact, drop "estimated" or "unknown", round a figure, or move a doubt from one fact to another. The result usually reads better, which is why the change gets through.

Is it safe to use ChatGPT or Copilot for incident reports?

For tidying wording, it can save time, but treat the result as a new draft. Compare it against your notes before you submit, using the checklist on this page, and keep the notes.

Why does an "approximate" time matter?

Because the report may be read later by a client, an insurer, an investigator or a regulator. An exact time, a definite size or a confirmed cause that nobody actually established is a statement of fact, and your name is on it.

Does a sheen have to be reported?

Under the EPA discharge-of-oil rule, a discharge that causes a film or sheen on the surface of the water is one that may be harmful, and the person in charge of the vessel or facility must notify the National Response Center immediately. That is why the wording about what was seen, and what is only suspected, matters. Check the rules that apply to your site.

Does ABCcount stop this?

Its Energy mode checks every rewrite against what you wrote: times, figures, units and words like "approx" and "suspected" must come back exactly as they went in, and field abbreviations keep their meaning. It cannot know whether your notes are right, so read the report before you submit it whatever tool you use.

Sources: US EPA, Discharge of Oil Regulation overview (40 CFR part 110); OSHA, OSH Act of 1970, section 17; the AI rewrite is the run published on our incident report template page. Checked 7 November 2026. This page is general information, not legal or regulatory advice.

Also free: an incident report template with a near miss version, and how an AI edit changed checked legal citations.