Note
Stage Accepted on Site, No Form Signed
A main contractor’s site engineer walks your work, says “this looks good, move to the next zone,” and keeps walking. No form changes hands. You move on. Three weeks later you submit the billing stage and the main contractor’s accounts team says there is no acceptance on file.
The work was done. The engineer saw it. The stage is real. But the accounts team works from documents, and there are none.
This situation is common enough in Thai subcontracting to have a name: verbal acceptance. It is not unusual or improper. Many experienced engineers treat the site walk as the acceptance event and expect formal paperwork to follow through a separate channel. The problem is not the intent. The problem is the gap between the walk and the form, and what can disappear into it.
Why a Verbal Acceptance Rarely Causes a Problem on the Day
The relationship between a subcontractor and a main contractor’s engineer usually runs on speed and trust. An engineer who stops every acceptance to produce a formal document slows the site down for everyone. A verbal sign-off is a reasonable working shorthand when both sides trust each other and the paperwork is expected to catch up.
Two things break that assumption. First, the engineer transfers to another project. The person who holds the memory of the verbal acceptance is gone, and the incoming engineer has no record of the conversation. Second, the site team and accounts team operate on separate tracks. A verbal acceptance on site creates no entry in the accounts system until someone raises a form. Neither case involves bad faith. Both result in a billing stage that is real but invisible to the team processing the invoice.
What Makes a Verbal Acceptance Hard to Recover Later?
Three things erode it over time.
Time itself. A verbal acceptance from yesterday is easy to confirm. One from six weeks ago requires someone to recall a specific comment during a walkthrough that looked like dozens of others.
Personnel change. If the engineer who gave the acceptance has transferred, the person reviewing the billing dispute was not present. Their only tool is the paper file. An empty file means the starting position in any dispute is that acceptance was not given.
Competing versions. Two people can walk the same site and remember the same conversation differently, especially when the walkthrough covered multiple zones and moved quickly. Without a contemporaneous note, neither version can be verified.
The Three-Line Record That Protects the Stage
The fix does not require the engineer to sign anything on the day. It requires one person on your team to record the moment while the memory is still fresh.
Three elements: who walked the work, what was said in one sentence, and when it happened. That record goes into the communication channel already in use with the main contractor’s team, a project LINE group or a shared chat thread. A message of three lines sent that same evening counts as a contemporaneous record.
The reason to send it into the shared channel is visibility. A message the main contractor’s team received and did not dispute within a reasonable window is much harder to contradict later. You are not asking for confirmation. You are summarising what happened as a normal course-of-business note.
A worked example: a partitioning subcontract covers eight zones. On Tuesday afternoon the engineer walks zones 4 and 5 and says “this looks fine, start zone 6 tomorrow.” That evening the site manager sends a message to the project LINE group: “Summary from today’s walkthrough: zones 4 and 5 completed and signed off by [name], starting zone 6 tomorrow.” No reply arrives.
Three weeks later, when the billing stage for zones 3 to 6 is submitted, that LINE message is the nearest thing to a signed acceptance in the file. It is not a formal form. But it is a dated message in a shared channel the main contractor’s team received and did not challenge. That is a different starting position than no record at all.
How Do You Turn a Site Walkthrough Into a Documented Record?
The same-day message covers future stages. For a project that has already accumulated verbal acceptances without documentation, a one-time catch-up is the next option.
Review the communication history: LINE groups, WhatsApp threads, emails. Find any message referencing work walked or approved. Compile these into a summary listing the scope items, dates, and parties.
Send the summary to the main contractor’s commercial team before the next invoice with a request to confirm acceptance status: “Please confirm that the items below are accepted so the invoice reflects the correct scope.” An affirmative reply confirms what was agreed. A partial confirmation shows which items still need formal documentation.
What to Do When the Billing Stage Is Already Disputed
When the dispute has arrived and there is no contemporaneous record, the options narrow but do not disappear.
Start with the communication history. A LINE message, an email, a note in a shared thread is a document even when it was not created as one. Screenshot everything that references the scope in question.
Then request a meeting with the engineer who walked the work, not with the accounts team. The accounts team disputes from documents they do not have. The engineer is the witness. A meeting that results in the engineer confirming acceptance in writing, even retrospectively, resolves the dispute without escalation. If the engineer has transferred, send a written request to the main contractor’s commercial manager asking for the acceptance position to be confirmed from the project record.
Can I submit a billing stage before a signed acceptance form arrives?
Most subcontracts do not require a signed acceptance form as a precondition for submitting an invoice. They require certified acceptance before payment becomes due. Submitting the invoice starts the clock; if acceptance is confirmed later, the payment timeline runs from the submission date. Waiting for a form to arrive before submitting delays the clock for no reason.
What if the engineer who walked the work has transferred?
The contemporaneous record in the shared channel is more important in this case than in any other. The new engineer has no personal knowledge of the acceptance. The shared message history is the closest available record. A written request to the main contractor’s commercial manager asking for the acceptance position to be confirmed based on the project record carries more weight than a verbal follow-up to someone who was not there.
What does the acceptance form minimally need to contain?
The minimum is a description of the scope accepted, the date, and a name and role from an authorised person on the main contractor’s side. An acceptance form that identifies the billing stage, the specific zones or scope items, and the person accepting is sufficient for billing purposes. It does not need to be a long document. A one-page checklist with a signature line covers the requirement, and is much easier to get signed after a walkthrough than a multi-section form.
If any of your current billing stages rest on verbal acceptance with no documentation, a 45-minute call is a practical starting point. We open the project communication records together and identify what is there.