What records win document disputes?

The question every document dispute reduces to

Defective work, late information, building from a superseded revision — the surface arguments differ, but underneath they are the same question: who had which information, and when did they have it?

That question has exactly one good kind of answer, and it is a contemporaneous one. A record created at the time, in the ordinary course of running the project, carries weight that a reconstruction assembled for the arbitration never will.

Acknowledgment is the artifact that matters

Proof of sending is weak. Proof of receipt is strong. A “delivered” status tells you a server accepted a message; a positive acknowledgment tells you a named person confirmed they had the revision, on a date.

This is why unacknowledged transmittals should be chased as routine work rather than discovered during a dispute. Each one is a hole in the record, and holes in the record are where the other side’s case is built.

And it cuts both ways

A register maintained only when it flatters you is worth nothing when you need it. The same log that proves the subcontractor received Rev C will prove you never issued Rev D — and a tribunal reads a selectively maintained record the way it reads a selectively maintained site diary.

The argument for keeping it honest is not integrity for its own sake. It is that a record you can rely on is the only kind worth keeping.

Terms

• Document Register