Quality Checkpoints on Your Gantt: Never Miss an Inspection

What is a quality checkpoint on a construction schedule?

A quality checkpoint is a milestone on your project timeline that marks a point where work must stop, be inspected, and receive formal sign-off before the next phase begins. On a construction Gantt, it sits after the tasks that lead into it and before the tasks that depend on its outcome. Examples include a structural inspection after the foundation pour, a government building inspector visit before wall cladding goes on, a client walk-through at the end of rough-in work, and an MEP sign-off before plaster seals the conduit inside the walls. When these checkpoints are visible on the Gantt planning view, every subcontractor can see what is coming and plan accordingly — instead of being surprised when work grinds to a halt because an inspection was forgotten.

Why do contractors lose time at inspections?

The most common cause of inspection delays is not a failed test — it is an inspection that was never booked. A structural inspection in Thailand requires advance notice to the relevant authority, sometimes three to five working days. If the team pours the foundation slab on a Tuesday expecting inspection on Wednesday, and nobody booked the inspector a week earlier, the project sits idle for four days while the permit office processes the request. The second most common cause is a task that was marked complete in the schedule but was not actually ready for inspection — the gap between what the Gantt says and what the site shows. Both failures are preventable when inspection milestones are wired into the schedule and treated like any other task.

Which inspections belong on the Gantt?

Four categories of inspection consistently affect the critical path of a Thai SME construction project. Government statutory inspections — structural frame, electrical rough-in, plumbing, and final occupancy certificate — are legally required and cannot move without approval. Third-party engineer sign-offs, required by many lenders and design firms, protect the contractor as much as the client. Payment-milestone walk-throughs, where the owner visits the site before releasing the next tranche of funds, affect cash flow directly. And internal quality gates — concrete cube tests, waterproofing flood tests, MEP pressure tests — catch problems before they are buried. All four types belong on the Gantt because all four can stop work if they slip.

How to add inspection checkpoints in SiteBoard

In SiteBoard's Gantt planning view, inspection points are added as milestone markers on the timeline — a single-day event pinned to the date when sign-off must happen. Link the milestone to the tasks that must be complete before it: the foundation pour, the rebar check, the slab cure period. When those tasks update their percentage on the Gantt, the milestone sits visibly downstream, reminding the team what is coming. For a government inspection, set the milestone three to five working days after the expected completion of the preceding work, so there is built-in lead time to book the inspector. The milestone appears on the shared Gantt view, so the whole team sees the hard stop even if they never read the task notes.

How to link inspection milestones to payment milestones

In most Thai residential and commercial construction contracts, the payment schedule is tied to phases of completion: foundation done, structure topped out, roof on, fit-out complete. Those phases almost always end with an inspection or a walk-through by the owner. Placing the payment milestone on the Gantt immediately after the corresponding inspection milestone creates a logical chain: the concrete frame inspection must pass before the structure payment is released. When both milestones appear on the same Gantt, the project manager can see how much float exists between the inspection date and the payment trigger, and plan accordingly. A slipping foundation pour that pushes the inspection by a week automatically shows as a week's delay to the payment milestone — visible to everyone rather than discovered by accident.

A worked example: Khun Somchai's five-storey shophouse

Khun Somchai is building a five-storey shophouse in Chiang Mai for a 6.8-million-baht contract. His Gantt has four inspection milestones: structural frame inspection at week eight, electrical rough-in sign-off at week sixteen, waterproofing flood test at week eighteen, and a final occupancy inspection at week twenty-six. The payment schedule releases 25 percent of the contract — 1.7 million baht — when the structural frame inspection passes. In week seven, the steel subcontractor falls three days behind. Because the inspection milestone is on the Gantt, Khun Somchai sees immediately that if he does not recover those three days, the booked inspection date will slip and the 1.7-million-baht payment will be delayed by nearly two weeks. He calls in a weekend crew, recovers one day, and arrives two days before the inspector. The payment lands on time.

What should you do when a task fails inspection?

A failed inspection does not mean the project is in crisis — it means the checkpoint worked. The right response is immediate: identify exactly which elements failed, assign specific rework tasks with short durations on the Gantt, set a re-inspection milestone as close as the authority allows, and update the affected task percentage to reflect incomplete status. In SiteBoard, this means resetting the task to the correct lower percentage and adding a note in the on-site progress update describing the failure and the fix. The owner sees the updated status via the owner sharing link without needing a phone call. The key discipline is never to leave a failed-inspection task marked at one hundred percent on the schedule — that is how a known problem stays invisible until final handover, when fixing it costs ten times more.

Does every inspection need a separate milestone on the Gantt?

Not every inspection is on the critical path — some are quick internal checks that can be folded into the task notes. The rule is: if a failed or delayed inspection could block the start of the next phase or delay a payment, it belongs on the Gantt as an explicit milestone. If it is a routine quality check that the team can resolve in a few hours without stopping other work, a note in the on-site update is enough. Erring toward more milestones is better than fewer: a Gantt with clear inspection markers is easier to present in a client meeting or a site walk than one where inspection events are buried in notes and only the project manager knows when they fall.

How far in advance should you set inspection milestones?

Government and third-party inspections need the most lead time — book them as soon as the preceding tasks are scheduled, not when they are finished. For statutory inspections in Thailand, booking two weeks before the expected completion of the preceding work is a reasonable buffer. Client walk-throughs require at least three to five days' notice so the owner can arrange their schedule. Internal quality tests — concrete cube tests, waterproofing flood tests — can be set one to two days after task completion. The habit of setting inspection milestones at project-planning time, not scrambling to book them when the work is done, is what separates contractors who consistently make their payment schedule from those who lose a week of cash flow every cycle.

Can the owner see inspection milestones through the owner sharing link?

Yes — when inspection milestones are marked on the Gantt in SiteBoard, they appear on the owner sharing link alongside the task bars. The owner can see exactly when each milestone is scheduled, whether it has been hit, and what is coming next. This visibility replaces anxious phone calls: an owner who sees a government inspection milestone booked for Friday, followed by a payment milestone the following Monday, understands why funds are not yet released without needing to ask. When the inspection passes and the milestone is marked complete, the owner sees it update in real time. Transparent inspection tracking through the shared Gantt is one of the simplest ways a contractor can build credibility with an owner before a single word is spoken.