If it happened here, it's on the record.
A surveillance audit, a customer escape, a part that comes back. Someone asks about a batch from last March. Bulk wrote the answer the day the work was done, and kept it.
“Who changed the cure temp on that batch last March?”
Already written. Nobody typed it.
Pull one record, get its whole history.
Any batch, job or order. Every stop signed and timed, the old value kept beside the new, and the reason in their own words.
- 9 Mar08:14
CreatedSana Kaur
- 12 Mar14:02
Cure temp 180°175°Rosa Patel
“Oven recalibrated after service. 180 was scorching the crust.”
- 13 Mar09:40
Quality hold cleared on recheckJoe Mensah
- 14 Mar16:05
Approved for dispatchJoe Mensah
- 18 Mar07:30
Shippedon time
Nobody keeps this record. It keeps itself.
Traceability programmes fail on discipline: someone forgets to log it. Here there's nothing to forget.
- No forms to fillThe action she takes to do her job is the entry. There's no second step.
- No logging to switch onIt isn't a feature that can be left off. Every write is captured, by default.
- No module left outIf it happened in Bulk (any module, any site) it's in the record.
- RP14:02 · Rosa · 180° → 175°
- JM13:45 · Joe · approved the change
- SK11:20 · Sana · started the batch
Written in ink. Nothing gets erased.
What makes the record evidence instead of notes: it's append-only. A correction adds a new line and the old one stays. Nothing is overwritten, nothing deleted.
There is no eraser. We never built one.
Not a permission you toggle: a capability that doesn't exist. A correction adds a line; the original stays. Names and timestamps are permanent, every module, every site, for years.
- DELETENot built
- OVERWRITENot built
- PURGENot built
- + APPENDThe only control
For the days everything is on the line.
In aerospace, defence and other regulated work, traceability is the whole game. Three days the trail earns its keep.
- March202614
Audit day
The trail is already complete. Hand it over.
Every change already logged, the day the work was done.
- June202602
A part comes back
Trace it to every hand, machine and change.
Old and new values both kept, nothing overwritten.
- October202627
“Who signed off on this?”
Name, time and reason, on the record.
Names & timestamps permanent, retained for years.
Append-only, SOC2-grade: every module, every site, ready before the day comes.
Questions, answered.
What is Bulk Audit Trail?
It records everything by default: every action across every module writes its own entry as it happens, so any batch, job, or order carries a complete history of who did what, when, and why.
Do I have to switch logging on?
No. There's no feature to enable and no form to fill. The action someone takes to do their job is the entry, so every write is captured by default. Nothing to remember, nothing to forget.
Can records be edited or deleted?
No. The record is append-only. A correction adds a new line and the original stays. Delete, overwrite, and purge don't exist. Names and timestamps are permanent.
How fast can I trace a batch?
Pick any record and read its full life as one thread: created, changed, approved, shipped. Each stop carries a name, a time, and the old value beside the new, so who, what, when, and why is one pull, not a report you assemble.
Where does the audit trail show up?
The same history lives in Org Activity Logs, a per-record Logs tab, and the around-the-floor feed. Every module, every site.
Is it suitable for regulated industries?
Yes. It's append-only and SOC2-grade, with names and timestamps retained for years. Built for aerospace, defence, and other regulated work where traceability is the whole game.
Bring your toughest audit question.
Pick any record on our demo floor: who, what, when, why. Time how fast the answer comes back.