Using Your Gantt Record to Defend Against Delay Claims

Why do delay penalty clauses catch Thai contractors by surprise?

Most Thai construction contracts include a penalty clause that charges a fixed sum for every day the build runs past the agreed completion date. In principle this protects the owner; in practice it catches contractors off guard when the delay was caused not by their own crew but by a late drawing revision, a delayed approval, or an instalment payment that arrived weeks after its due date. Without a dated, documented record of what happened and who caused it, the contractor has no way to separate their liability from the owner's — and the penalty clause applies in full. A well-kept Gantt schedule is the foundation of any credible delay defence.

Which delays belong to the contractor and which to the owner?

Construction delays fall into three categories, and the distinction matters legally. Contractor-caused delays — crew shortages, procurement mistakes, poor sequencing — are the contractor's liability, full stop. Owner-caused delays are different: the owner approved material selections three weeks late, a drawing revision arrived after the structural pour was supposed to start, or a progress payment was held far past the contractual due date. These delays should extend the programme, not trigger a penalty. A third category is neutral delay, such as a declared natural disaster or a government shutdown. Knowing which category each delay falls into is the first step; documenting it in the Gantt with the cause and the date is how you prove it later.

What does an owner-caused delay look like on a real Thai project?

Consider a four-unit townhouse in Nakhon Ratchasima, with a structural phase scheduled from the first to the twenty-eighth of March. On the sixteenth, the owner requested a column repositioning to accommodate a new staircase layout. The structural engineer took eleven days to revise the drawing, and the concrete crew could not pour the affected columns until day twenty-seven. The structural phase closed on the tenth of April — twelve days late. Only four of those days were the contractor's: a concrete-truck delay at the very start. The other eight were directly caused by the owner's change request and the drawing revision it triggered. Without a dated Gantt entry noting the request and the wait, the contractor faces a twelve-day penalty across all four units.

How does the Gantt planning view capture a baseline you can defend later?

The baseline is the agreed schedule at contract start — the dates both parties signed off on. In SiteBoard's Gantt planning view, those original bars represent the baseline. Each time a delay occurs, update the affected tasks to their new dates and attach a short task note — even one line: 'owner approved tile selection fourteen days late' — so the reason is dated and sits with the task itself. Phase 2 of SiteBoard will surface formal baseline tracking, letting you compare planned and actual in a single view. Even now, the habit of updating tasks in real time and noting the cause produces a timestamped record far stronger than a memory or a LINE message recalled weeks after the fact.

How does the owner sharing link protect you during a dispute?

When you share the project via SiteBoard's owner sharing link, the owner sees the live schedule — current task dates, percentage complete, and the latest site photos — on the day they open it. If the owner opens the link on the day you update a task to read 'column pour on hold — awaiting revised structural drawing,' that view is timestamped. Both parties have seen the same information at the same moment. This makes it very difficult for an owner to later claim the contractor never flagged the problem or that they were unaware of a developing delay. Used consistently, the owner sharing view doubles as a shared, real-time record: a client communication tool and a protection at once.

What role do on-site progress updates play in documenting a blockage?

Every update made through SiteBoard's on-site progress updates carries a timestamp and a photo. If the concrete crew is standing by because the revised drawing has not arrived, the foreman can log a zero-progress entry on the blocked task with a photo of the unworked slab and a note: 'Awaiting revised column drawing — no pour today.' Done each day the blockage continues, this builds a dated, photo-backed log showing the site was ready and the blockage was a missing document, not a crew failure. Across eleven days of waiting you build eleven independent, timestamped records — the difference between a vague claim and a documented sequence a mediator can follow without ambiguity.

When should you issue a written delay notice to the owner?

Thai contracts increasingly include a notification clause: the contractor must give written notice — often within seven to fourteen days — of any event that entitles them to extra programme time. Miss that window and you may lose the right to claim an extension even if the delay was clearly the owner's fault. A brief LINE message or email on the day you discover the blocking event is sufficient as a first notice: state what happened, the date it started, and that you are flagging it as a programme impact. Back it up immediately with a dated Gantt task update and a foreman progress note so the written notice and the schedule record both point to the same event on the same day.

How do you build the documentation habit before a dispute begins?

The best time to set this up is at the project kickoff, not when a dispute has already started. When you create the project in SiteBoard, spend thirty minutes entering the agreed schedule, mark the contract completion date as a Gantt milestone, and send the owner sharing link on day one. Agree in writing — even by LINE — that the shared schedule is the reference plan. From that point, every change is visible in context: original dates, new dates, and the task note explaining why. Train your foremen to log a daily progress entry on every active task, including zero-progress days with a brief note on the cause. After two or three projects run this way, the habit is automatic and the records are simply there.

FAQ: Does a Gantt export hold up if a dispute goes to mediation?

A Gantt export is supporting evidence, not a standalone legal document. Its strength lies in corroboration: the task note matches the date of your written notice to the owner, the foreman's daily photo log shows the site was ready and the crew was present, and the architect's email confirms when the revised drawing was actually sent. When three or four independent records point to the same event on the same date, a mediator has a clear picture without needing a formal delay register. The concern that a Gantt could be edited retroactively is answered when the owner has been watching the shared schedule in real time throughout the build.

FAQ: What if the owner disputes that their decision caused the delay?

This is exactly where the daily update habit pays off. If the owner claims a drawing revision took three days and you recorded eleven, the on-site progress updates tell the story day by day. If your foreman entered a zero-progress note on each of those eleven days, you have eleven dated records showing the task did not move. The owner must then produce a dated document — an email or LINE message from the architect — proving the drawing arrived earlier than your records show. Your daily Gantt update and the foreman's notes are the anchor; the owner needs a dated document to contradict them. A clear daily record resolves most disputes before formal proceedings begin, because the documented sequence becomes self-evident to both sides.

FAQ: Should I keep delay records even on projects that finish on time?

Yes — especially when on-time completion required absorbing owner-caused delays through weekend shifts or a compressed finishing schedule. If the owner later raises a defect in the accelerated work, the record of why the schedule was compressed is your defence. The defects liability period on a Thai residential build typically runs six months to one year after handover, and during that window delay and acceleration records can be relevant to variation claims, payment disputes, or warranty questions. Run the documentation habit on every project, on time or late, and the records are simply there when needed — silent and invisible on smooth jobs, essential when something goes wrong.