How to Tie Payment Milestones to Your Build Schedule

Why payment disputes almost always start at the milestone

In a construction contract, money moves at milestones — completion of foundations, topping out, waterproofing done, final handover. The problem is that "foundations complete" is a phrase, not a definition. When the contractor says the pour is done and the owner says the backfill is not finished, you have the same words and two different pictures. That gap — not malice, and rarely incompetence — is where most construction payment disputes are born. Closing the gap starts before any money changes hands: each milestone needs a specific, measurable description attached to a named point on the project schedule, agreed in writing before work begins.

What a payment milestone actually is — and what it is not

A milestone is a defined point in the schedule where a meaningful, verifiable stage of work is complete — not a date on the calendar and not a percentage pulled from thin air. "Week six" is a date, not a milestone. "Structural columns cast and cured, all-floor slabs poured, engineer sign-off received" is a milestone. The key test is whether an impartial person could walk onto site, look at the work, and agree that it is done — without either party having to explain. If the answer requires negotiation to reach, rewrite the milestone description before the contract is signed.

How to map payment milestones onto the Gantt from the start

When you build the project plan, place milestone diamonds at each payment trigger in the Gantt planning view — foundation complete, structure closed, MEP rough-in done, plastering complete, handover. Attach the payment amount or percentage to that milestone's description so the link between schedule and money is explicit. The plan now tells two stories at once: when the work is expected to finish, and when money is due. When actual progress catches up with a milestone diamond, the trigger is visible on the same screen where the work lives — not buried in a contract document nobody can find in a hurry.

A worked example: a five-stage house build in Pathum Thani

Consider Khun Preecha, running a 3.2-million-baht two-storey house build in Pathum Thani. His contract splits payment into five stages: 15% on signing, 20% on foundation complete, 20% on structure and roof complete, 25% on MEP rough-in and plastering, 20% on handover. Each stage maps to a named milestone diamond on the Gantt. When the structural frame and roof are closed in week eleven, the foreman logs a 100% update against the Structure Complete milestone in SiteBoard, attaches three photos, and adds a short note describing what is done. Preecha sends the owner a link to the owner-sharing view, which shows the milestone marked complete with the photo record. The 20% draw — 640,000 baht — is released the same day without a site visit argument.

How to document milestone completion so the owner cannot dispute it

A phone call saying "the plastering is done" is not documentation — it is a claim that becomes your word against the owner's six months later. What holds up is a timestamped progress update attached to the milestone task in the project plan, with at least one photo of the completed scope and a short note describing what was done. SiteBoard's on-site progress updates let the foreman capture this directly from site in under a minute: tap the milestone task, slide to 100%, snap a photo, confirm. That entry is stamped with the date and time and lives in the same system as the schedule, so the record cannot be separated from the work it describes.

Timing the payment request to the Gantt, not the calendar

Many contractors ask for milestone payments on a fixed day of the month — the first Friday, the end of every four weeks — regardless of where the work actually stands. This disconnects payment from progress and invites disputes: the owner's site visit on the fifteenth finds the plastering two days short, and now there is an argument about whether to pay in full, hold, or prorate. Tying the request to the Gantt instead is cleaner: when the milestone task hits 100% in the system and the photo record is in, that is the day the invoice goes out. The owner sees the evidence in the owner-sharing view before the invoice arrives — not at the same time as a demand for money.

How does owner sharing help with milestone payments?

The owner-sharing link in SiteBoard shows the project's current progress, the latest site photos, and the overall completion percentage — updated the moment the foreman logs a task. When a milestone is hit, the owner can see it on the shared page without calling anyone. This turns the payment request into a confirmation of something the owner has already witnessed, rather than a claim that surprises them. In Thai construction, where payment delays are common and disputes over completion percentages are frequent, showing verifiable progress before asking for money is one of the simplest ways to get paid faster and more reliably.

What happens when the owner says the milestone is not complete?

With a documented milestone — a 100% task update, a timestamped photo, a note in the system — the conversation has a starting point: here is what was agreed, and here is the record showing it is done. The owner must point to something specific that is missing, not just express a general doubt. If they are right, the task goes back to in-progress and the foreman logs the fix. If the milestone genuinely is complete and the owner is stalling, the timestamped record is the evidence you would present to a mediator or, in the worst case, to a lawyer. Most disputes never reach that stage when the documentation is clear from day one.

Should every task on the Gantt trigger a payment?

No — only tasks that represent a meaningful, verifiable stage of work that an owner can inspect. Day-to-day tasks like "mix concrete for column" or "level render on the north wall" are operational steps, not payment triggers. A payment milestone typically spans a full phase: all foundation work done, all structural work complete, all MEP rough-in done. Group the operational tasks under that phase in the Gantt, and place the milestone diamond at the point where the whole phase is complete and inspectable. The Gantt stays detailed enough for the crew to follow, and the milestones stay clear enough for the owner and the contract to reference.

What to do when a milestone payment arrives late

If the Gantt shows a milestone completed and the payment has not arrived within the agreed window, the first step is a calm, factual message — not a demand, but a reference: the milestone was logged complete on this date, the invoice went out on this date, the payment window closes on this date. Attach a link to the owner-sharing view showing the completed milestone and the photo record. Most late payments resolve at this stage because the documentation removes any ambiguity about whether the work is done. For persistent late payment, that timestamped record becomes the foundation of a formal notice. Projects where milestones are documented rigorously tend to have fewer late-payment incidents overall — everyone involved knows the evidence trail is there from the first day of work.