Giving your site logbook evidentiary weight: folios, signatures and certain date

This article describes general principles. Concrete evidentiary weight depends on the jurisdiction, the type of proceeding and the contract. Consult a lawyer for your specific case.

Why a notebook is not enough

Think about how a site notebook looks from the outside, in a dispute.

It is an object that was under your exclusive custody. Pages can be torn out. One can write with the same pen three months later. The date on every page was written by you. There is no technical way to tell an entry made on Tuesday the 4th from one made the following Friday.

That does not mean a notebook is useless. It means its strength depends entirely on the credibility of whoever presents it — a fragile position when money is at stake.

The four attributes

1. Tamper-evidence

The record cannot be modified without leaving a trace.

On paper this is solved with folio numbering, indelible ink, an original plus copies distributed between the parties, and the rule that an error is never erased but corrected with a new entry.

Digitally it is solved with append-only architecture — records are written, never edited or deleted — and cryptographic chaining: each entry incorporates the fingerprint of the previous one, so altering one breaks the chain of all subsequent entries, and that is detectable.

What does not meet this attribute: a text document in a shared folder, a spreadsheet, a PDF that gets regenerated. All are editable and none leaves a trace.

2. Sequential continuity

Entries are numbered and in order, with no gaps or jumps.

Its value is less obvious and quite large: a continuous series is credible; an isolated document is not. A record that appears only about the disputed event raises the suspicion of having been fabricated for the occasion. The same fact, as entry number 247 of an uninterrupted daily series that began on day one, is far harder to question.

This is the strongest argument for keeping the record every day even when nothing happens. The value is not in each entry: it is in being able to prove the habit.

3. Certain date

The date of the record can be proven by a means other than your own say-so.

It is the hardest attribute to achieve and the one that weighs the most. There are several routes, from weakest to strongest:

In Mexico there is a specific, inexpensive mechanism for this: the data-message preservation certificate under NOM-151, issued by an authorized certification service provider. It incorporates the document’s digital fingerprint and a digital timestamp, proving existence and integrity from that date. It costs cents per certificate and can be issued automatically over the record’s daily close.

Its limit deserves honest mention: it proves that the content existed on that date and has not been modified since. It does not prove the content is true. That rests on the other attributes and the associated evidence.

4. Acknowledgment by the parties

The counterparty saw the record and had the opportunity to object.

This is what turns a unilateral record into a bilateral instrument, and it is the most neglected attribute on private projects. Three levels, from least to most demanding:

Acknowledgment per entry. The counterparty receives the note and replies with approval or observations. Sufficient for most daily records.

Notified daily close. A summary of the day sent to both parties over a channel with delivery acknowledgment. If the contract provides for it, silence after a set period constitutes tacit acceptance.

Periodic signature. A consolidated document, monthly or per progress billing, signed by both parties with electronic signatures. Nobody signs forty entries a day; one signature a month is sustainable.

The clause that holds it all up

Here is the most important part of this article, and it is not technical.

On private projects, all of the architecture above is worth far more if the contract recognizes it. A clause establishing:

• That the parties designate this instrument as their agreed conventional logbook
• Who is authorized to record entries, for each party
• The channel and form of notification of entries
• The period to object and the effect of silence
• The preservation mechanism and retention period
• That the parties recognize its value as a means of proof

Without that clause, your record is a version of events with good technical architecture. With it, it is the instrument the parties agreed on to communicate — and objecting to it later means contradicting their own contract.

It is the cheapest, highest-yield intervention in this whole subject. Have a lawyer draft it once and use it in every contract.

What can be promised and what cannot

Precision matters here, because commercial exaggeration abounds.

Can be asserted: that the record is verifiable by a third party, that its integrity is technically provable, that it existed on a given date, and that authorship is attributable.

Cannot be asserted: that it constitutes conclusive proof, that it is unobjectionable, or that it guarantees winning a dispute. A well-built electronic record generally carries the weight of a private document, and if challenged it may require forensic IT expert evidence to confirm its integrity.

The difference between the two lists matters. The first is an enormous leap over a notebook. The second is what your lawyer will tell you if you promise more.