How Do You Know Who Changed What on a Warehouse Job?

Only if every change is recorded as it happens — who made it, when, what it was before and what it became — on the job itself. Spreadsheets, whiteboards and edited PDFs keep the latest value and quietly forget the rest.

That is fine until somebody asks. In warehouse labor, somebody always asks, and usually weeks after anybody can remember.

The questions that arrive later

• “Who changed the case count on this job?”
• “The paperwork says five people. Why are only four on the job?”
• “When did this shift get shortened, and by whom?”
• “Why is this invoice line less than the rate card?”
• “Who took the damage photo off the job?”

Each one is either a thirty-second lookup or an afternoon of messages, depending entirely on whether the job kept its history.

What a job's history has to hold

Four things for every change: who, when, before and after, and — for the changes that touch pay or billing — why. Missing any one turns the trail back into a matter of opinion.

In FOREMAN every load carries an Activity Timeline, and each entry names the person who did it. An excerpt:

What FOREMAN records on every job

The timeline filters by Load, Crew, Notes and Files, and covers:

• The job itself. Created, paused, resumed, completed, reopened, closed or cancelled; every edited field shown as before → after; a flow-type change; marked invoiced, or released back to unbilled.
• The crew. Each person assigned, clocked in, clocked out, or removed — with the removal reason.
• Notes. Added, edited (old text → new text) and deleted.
• Files. Uploaded, archived, restored, shared with the customer, and unshared.

The two changes that need a reason

Crew time. Clock-ins and clock-outs take the server's time, so nobody types a start time or backdates a shift. When someone genuinely forgot to clock a person out, the real time is entered as a correction: a reason is required, the original and corrected times are both kept, and the change is written to the job's history. Corrections are refused once that week's payroll is approved, and once the job is closed or invoiced. A correction that would overlap the same person's time on another job is always rejected.

Money. An administrator can override the billing or payout FOREMAN calculated for a completed job, but only with a stated reason. The load shows the override, the reason, who set it and when; FOREMAN keeps its own calculation, so the override can be reset to it. Why that matters for a payroll run is covered in what a payroll mistake costs.

Who sees the history

Supervisors see the same timeline for jobs at their site, with the money taken out: billing and payout amounts, rates and invoice links are stripped before the entries reach them. They can see what happened without seeing what it was worth.

Two honest limits. A timeline entry for a note or a file shows the first few words, not the whole thing — the full note stays on the note. And deleting removes the thing itself: a deleted note leaves only that snippet in the history, and a deleted file is gone. Archiving a file instead is reversible and keeps it on the job.

The point of an audit trail is not to catch people out. It is to make the question “who changed this?” boring.

Keep the history with the job

FOREMAN writes every change to the job it belongs to, so the answer to “who changed what?” is on the same screen as the work. What the customer is allowed to see of it is covered in sharing proof of work with customers.