What the site logbook is: a guide for site engineers in Latin America
Last reviewed: Regulations change: the text is checked against the official source at each review.
The site logbook is the formal instrument where the relevant facts of a project are recorded as it is built: instructions, queries, authorisations, incidents and anything affecting time, cost or scope. It is not the site engineer's personal diary: it is a means of communication between the parties to the contract, with legal effect, and that is why both of them sign it.
That last distinction is the one most often lost. A notebook where the site engineer jots down whatever seems worth noting is an operational record. A site logbook is something else: what is written there binds, and what is not written there, for practical purposes, did not happen.
Five names, one instrument
| Country | Name | Official system on public works |
|---|---|---|
| Mexico | Bitácora de obra | BESOP |
| Peru | Cuaderno de incidencias (formerly cuaderno de obra) | Pladicop |
| Chile | Libro de obras | — |
| Colombia | Bitácora / libro de obra | — |
| Argentina | Libro de obra | — |
The differences are not only in the name. In Mexico and Peru, public works have official electronic systems that are mandatory, with electronic signature. In the other markets the format is set by the contract or by local regulation, and there is considerably more freedom.
On private projects, in every country, the instrument is contractual: it exists and takes the shape the parties agree on. Being contractual does not make it less important — it makes it more so, because nobody is going to impose a format on you that protects you.
What separates it from a notebook
Four attributes. If one is missing, what you have is a record, not a site logbook.
It is bilateral. Both parties write in it and both consult it. The contractor records, the supervision answers. A record only one party writes in is not an instrument of communication.
It is sequential and folioed. Entries run in order, numbered, without gaps. Continuity is part of the proof: an unbroken series is credible, a loose document is not.
It is tamper-resistant. Nothing is erased, torn out or written over. An error is corrected with a new entry that rectifies the previous one, and both remain.
It is signed. Every entry carries the signature of whoever made it and, where applicable, the counterparty’s agreement or objection.
Who may write in it
Broadly, and with variations by country and regime: the site engineer or technical director for the contractor, and the supervisor, inspector or interventor for the client. On public works there is usually a closed list of authorised people, and an entry made by someone outside that list may be invalid.
This creates a practical problem almost nobody solves well: whoever sees what happens on site is normally not the person authorised to record it. The foreman sees the problem at ten in the morning, mentions it to the site engineer at four in the afternoon, and the site engineer records it the next day if he remembers. Every link loses detail.
What it must contain
Regardless of the country, there is a common core:
- Date of each entry
- Weather conditions and working hours
- Personnel and equipment on site
- Work carried out, with its location
- Instructions issued and by whom
- Contractor queries and the answers to them
- Authorisations and approvals
- Incidents, suspensions and their causes
- Quality observations
- Handover and acceptance of work fronts
And the criterion that sums up the rest: if it affects time, cost or scope, it goes in the logbook. If it does not, it probably belongs in the daily report and not here.
The four mistakes that make it useless
Writing too much. A logbook with fifteen daily entries of trivia buries the three entries that matter. Abundance is a form of concealment.
Writing too little. The opposite case, and the more common one. Only milestones get recorded, and when a dispute appears there is nothing to support the facts in between.
Recording only your own side. Many site engineers log their progress and systematically leave out what the client did not do: the front that was not released, the drawing that never arrived, the material that was not delivered. That is exactly what you cannot claim for later.
Recording days later. An entry with a shifted date loses most of its evidentiary value and, under some regimes, may constitute a formal irregularity.
What is at stake there
It is worth saying plainly: the site logbook is the document that decides most construction disputes.
When a project ends in argument —over time, over cost, over quality— the first thing requested is the logbook. And what is written there weighs far more than what the parties remember. A verbal instruction that was never recorded is an instruction that did not exist. A suspension that was not logged is time running on your account.
It is also the document that gets the least attention while the project is going well, which is precisely when it can be built properly.
Frequently asked questions
- Is the site logbook mandatory on private projects?
- Legally, generally not, unless local building regulations require it. Contractually it almost always is, because well-drafted contracts establish it. And in practice it is worth keeping even when nobody demands it, for the same reason you keep receipts.
- Can it be kept in digital form?
- Yes, and that is the trend across the region. On Mexican and Peruvian public works the digital format is the mandatory standard. On private projects what matters is that the four attributes are met: bilaterality, sequential numbering, tamper resistance and signature. An editable file in a shared folder meets none of them.
- What happens if the logbook is lost?
- It is a serious problem. On public works it may constitute an administrative irregularity with liability for those involved. On private projects, losing it leaves both parties without support and usually harms most whoever carried the burden of proof. It is one of the strongest arguments for a digital format with backup.
- How long does it have to be kept?
- For the whole term of contractual and warranty liability, which depending on the country and the type of project can run from five to ten years, and in some cases longer for infrastructure.
- Can the site engineer refuse to sign an entry made by the supervisor?
- Normally you do not refuse to sign: you sign placing your disagreement on record and enter your own version. Refusing to sign tends to be read against you. Recording the discrepancy, by contrast, leaves evidence that there were two positions and which one was yours.
Founder and CEO of Paladio. He has spent more than 15 years building financial products that touch the lives of millions of people. He writes about what he sees on site: how progress is really measured and where the money leaks.
See all their articles →
