Bulk
Platform / Audit trail by default
Trust, AI & connect

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.

The auditor, eight months later
“Who changed the cure temp on that batch — last March?”
already written — nobody typed it
On the
record
BATCH-4417
RP
Rosa Patel
12 March, 14:02
Changed cure temp
180° 175°
Signed off by J. Mensah · Dortmund
In plain terms

What is Bulk Audit Trail?

Bulk Audit Trail is the by-default record layer of Bulk's manufacturing operations software. Every action across every module writes its own entry as it happens — no forms to fill, no logging to switch on. The record is append-only, so a correction adds a line and nothing is ever erased. Pull any batch, job, or order and read its whole history.

Traceability, not busywork

Pull one record, get its whole history.

Pick any record — a batch, a job, an order — and read its full life as one thread: created, changed, approved, shipped. Every stop carries a name, a time, and the old value beside the new. Not a report you assemble. A thread you pull.

Created
9 Mar · Sana Kaur
Cure temp changed
12 Mar · Rosa Patel
RP BATCH-4417 · quality hold cleared on recheck
180° 175° · reason noted
Approved
12 Mar · Joe Mensah
Shipped
18 Mar · on time
0:07
to trace this batch, start to ship — who, what, when, why
Also lives in Org Activity Logs Per-record Logs tab Around-the-floor feed
The trick

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 fill The action she takes to do her job is the entry — there's no second step.
  • No logging to switch on It isn't a feature that can be left off — every write is captured, by default.
  • No module left out If it happened in Bulk — any module, any site — it's in the record.
Rosa · Line 2
RPJust doing her job
Cure temp175°
Save
The record · same second
RP14:02 · Rosa · 180° → 175°
JM13:45 · Joe · approved the change
SK11:20 · Sana · started the batch
Integrity

Written in ink. Nothing gets erased.

What makes the record evidence instead of notes: it's append-only. A correction adds a new line — the old one stays. Nothing is overwritten, nothing deleted.

Batch-4417
SK11:20 · Sana · started the batch
RP14:02 · Rosa · cure temp 180° → 175° Right-click
RP14:31 · Rosa · reason corrected — NCR-88 ref added
Edit entry
Delete entry
Overwrite value
Append correction

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.

Record controlsrev. final
DELETE
OVERWRITE
PURGE
+ APPEND
Wired to nothing
Where it earns its keep

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.

March2026
14
Audit day

The trail is already complete — hand it over.

Every change already logged
the day the work was done
June2026
02
A part comes back

Trace it to every hand, machine and change.

Old and new values both kept
nothing overwritten
October2026
27
“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
Straight answers

Questions, answered.

01

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.

02

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.

03

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.

04

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.

05

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.

06

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.