Energy Mode · ProMax
It's 7pm and the report still isn't written.
You have the facts — in the order they happened, in shorthand, in a notes app. What you don't have is another hour to turn them into something a regulator will read, and nobody is going to check it before it goes.
A real incident note
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.
Why general writing tools are dangerous here
Every writing assistant is built to make prose better, and “better” almost always means shorter, more confident, less hedged. Those are the right instincts for a marketing email. They are precisely wrong for a report that may be read in a deposition.
Hedges look like weak writing to a tool that has never seen a regulator. So possibly, but not confirmed becomes a clean declarative sentence. Repeated figures look like clutter, so 8,432 ft becomes approximately 8,400. A sequence of observations looks like it wants a conclusion, so the tool supplies one.
Energy mode is built the other way round — around what it is not allowed to touch. It will tighten your sentence. It will not tell your regulator anything you did not.
What it will not round
12,847 ft
measured depth
3,247 psi
casing pressure
13.2 ppg
mud weight
42-317-38291
API number
Exactly as you entered them. Never rounded, never converted to metric, never tidied to three significant figures because the sentence scanned better that way.
What it was built for
- Incident and HSE reports
- No cause added that you did not write.
- Drilling and completion reports
- Depths, pressures, mud weights, formation names — untouched.
- Railroad Commission filings
- Regulator-ready register. API numbers exactly as entered.
- AFEs
- Every cost line survives to the figure.
- Technical memoranda
- Terminology applied where you meant it, never introduced where you did not.
- JOAs and farmouts
- Contract drafting, handled by Legal mode — included.
- The email explaining the delay
- To somebody who is not an engineer, and who will forward it.
Eighteen months later somebody pulls it out of that drawer. Maybe an auditor, maybe a lawyer, maybe a colleague who was not there and is trying to work out what happened.
They were not on site. They did not see the sheen on the water or hear what the crew said. All they have is the sentence you wrote at the end of a fourteen-hour day — and every word in it will be read as though you chose it deliberately.
You did choose it deliberately. That is exactly why nothing should have quietly rewritten possibly, but not confirmed into a statement of fact on the way to the filing cabinet.
Don't take any of this on trust
Paste in a report you have already filed — one with figures in it, and one where the cause was still under investigation. If anything moves that shouldn't have, you will know inside thirty seconds, and you will not have to take our word for any of it.