SaleShade Operations · Audit trail

Who did what, and when — on every record

Every record carries its own history — each stage with a name and a minute, images alongside. Not a report you open; a property of the thing itself.

The reconstruction meeting that ends nowhere

Something went wrong — a wrong dispatch, a count that moved, a replacement that vanished — and now four people are in a room reconstructing last Tuesday. Who allotted it?

The problem is not your people. It is that the question who did what, and when has no written answer anywhere — so the only source is recollection, and recollection takes sides.

The old way1

Something went wrong

a wrong dispatch, a count that moved
2

Four people in a room

reconstructing last Tuesday
3

Everyone answers honestly

from memory
4

The memories disagree

and everyone leaves slightly accused

Every record carries its own history

Beside every entry in the system — an order, a receipt, a count, a service visit — sits a small clock icon.

Open it, and the record's full history is there: every stage, the name of the person who performed it, and the time, to the minute.

Trail — SO/26/1184
MappedPriya M.Tue 11:02 AMcrude entry made exact
AllottedHarjit S.Tue 3:12 PM80 of 120 · photo
CheckedRamesh K.Wed 9:05 AMswitched item caught
Invoice finalisedaccountsWed 4:20 PMafter the physical check
PackedSandeep K.Wed 6:20 PM12 boxes
DispatchedHarjit S.Wed 6:52 PMdocket photographed
DeliveredSandeep K.Thu 11:05 AMreceived by Ramesh
Nobody wrote this. Each line is the act of doing the work.
Illustrative view. Times are to the minute, and no line can be edited after the fact.

A clock beside every record

An order, a receipt, a count, a service visit — open the clock and the record's own history is there, every stage with its name and its minute.

A gallery beside the clock

Every image the record collected on the way: the checking photos, the boxes, the docket, the finished work.

Nobody writes this history, and that is the point

The trail is not a register anyone fills.

It generates itself, from the acts: the man who allots creates the allotment line by allotting; the packer creates the packing line by packing. There is nothing to remember, nothing to skip on a busy day, and nothing to embellish afterwards.

A history that writes itself is the only kind that survives contact with a real godown — and the only kind worth trusting in an argument.

A register somebody fillsThe old way
  • Has to be remembered — and gets skipped on the day it would matter most
  • Can be embellished — written afterwards, by whoever writes it
  • Survives a quiet week — and nothing harder
A trail the work writes
  • The man who allots — creates the allotment line by allotting
  • The packer — creates the packing line by packing
  • Nothing to remember — nothing to skip, nothing to embellish afterwards

The record protects the man who did it right

Say it plainly, because every owner will wonder and every team will worry: this is not surveillance.

A trail settles the reconstruction meeting in thirty seconds — and nine times out of ten, it settles it in favour of the man being doubted.

Memory takes sides.

The packer

Who packed it right has proof he packed it right — in his own name, with the minute on it.

The godown executive

Who flagged the shortage on Tuesday has the flag, with Tuesday on it.

Everyone else

Gets thirty seconds instead of a meeting — and nine times out of ten it settles in favour of the man being doubted.

The record does not — which is precisely why honest people end up preferring it.

The history sits with the thing it describes

There is no audit section to visit and no report to compile.

The trail is a property of every record, read where the record lives — which is why every page on this site mentions it in one line and this page alone explains it.

Open any record in the demo and read its biography.

Ask for a demo