Note
When the Customer Won't Sign the Handover
The crew has left the site. The punch list is clear. You sent the handover document twice. Two weeks have passed and the customer has not signed. Your invoice sits in the queue, the next project needs some of the same technicians, and nobody is returning calls. This is a stalled handover, and it costs more than most contractors track.
What does a stalled handover actually look like?
A stall is different from an active punch list. When items are still open, the customer has a legitimate reason to hold the signature. A stall happens when the work is genuinely complete, the customer agrees it is done, but the signature still does not come.
Stalls take a few recognisable forms:
- The non-responsive customer. Emails and messages go unanswered. The site engineer says they are checking with management. Nobody schedules the final walkthrough.
- The moving-target customer. New items keep appearing: a label they dislike, a cable routing they would prefer changed, a test result they want in a different format. Each item takes a week to address, and once it is cleared, another appears.
- The scope dispute. The customer raises something they believe was in the original scope that you believe was not. The handover stalls while both sides disagree about what was agreed.
- The timing stall. The customer knows what the signature means. Signing releases the final invoice. Their financial quarter ends in two weeks, and delay is the simplest way to push the payment into the next period without saying so.
These four stalls require different responses. Treating a timing stall as a punch list problem just adds more completed work without resolving anything.
Why do customers delay? The structural reasons behind a slow signature
Most delays in Thailand are not about bad faith. Several structural factors inside factory procurement slow handover signatures independently of whether the customer intends to pay.
Authority layers. The site engineer who managed the installation often cannot sign. The document needs to reach the facility manager, then procurement, sometimes the factory director. Each step adds days.
Internal auditing. Some factories require their own engineering or safety team to inspect before signing any contractor handover. That team works on its own schedule.
Document format. If your handover document does not match what the customer’s engineering department expects, it gets returned for revision rather than signed.
The common pattern: none of these delays explain themselves. You see “not signed.” The customer has a specific internal reason that was never communicated to you.
What the delay costs you
The cost is straightforward to calculate. Take the final invoice amount. The weeks that money sits uninvoiced represent real carrying cost: equipment financing still running, cash the business is short of, and technician time spent chasing documents instead of working.
On a multi-project operation, the cost compounds. A contractor closing eight projects a month with an average three-week stall on each final invoice carries roughly six projects’ worth of finished-but-unbilled work at any given time. That is not a quality number. It is a working-capital number that limits how many new projects you can take on before you run short of operating cash.
What to do in the first week of a stall
The default response to a non-signing customer is to send a reminder. A more useful first step is to diagnose which type of stall you are in.
Ask a specific question instead of sending a general nudge: “Can you tell me who needs to approve this, and what they need from us?” If the answer is an internal inspection not yet scheduled, you can ask when it is expected. If the answer is a format issue, you can fix it in a day. If the answer is silence, you are probably in a timing stall rather than a process one.
Document every contact: every email, every LINE message, every follow-up call. Not for legal purposes yet. For your own clarity about how long the stall has run and what you have already tried.
Then take stock of what you have from the installation:
- Timestamped photos at each stage of the work
- A jointly signed punch list showing zero remaining items
- Any written acknowledgments from the customer during the installation (a message saying the work looks good, a note from a mid-install walkthrough)
That file establishes that the work is done and has been acknowledged as done. It is not a legal threat. It is the factual basis for a direct conversation about what is holding the signature.
Partial acceptance: signing for what is finished
When a dispute over one item or one section holds the entire handover, partial acceptance is sometimes the way forward.
The customer signs for the portions that are complete and uncontested. The disputed item stays open under a separate written agreement with its own timeline and a specific description of what is in dispute.
This only works if your handover document can reflect it. A single-signature document covering the whole scope either gets signed or does not. A document structured in sections, each with its own acknowledgment field, gives both parties a way to move forward while the contested piece is resolved.
Partial acceptance is not a concession. It is a recognition that the bulk of the work is unambiguously finished and should not wait on a single contested item. Whether the customer agrees often depends on whether they face their own deadline: a utility interconnection inspection, a production start date, or a regulatory sign-off that requires the electrical handover.
FAQ
How long should you wait before escalating a stall?
Decide this before a stall happens. Follow up on day five after submission, reach out to a named decision-maker by day ten, send a formal written notice by day fifteen. The notice should state when the work was completed, when the document was first submitted, and the outstanding invoice amount. You do not need a lawyer. You need a record that it was sent.
Does partial acceptance weaken your position on the disputed item?
Not if the partial acceptance is in writing and clearly scoped. You acknowledge sections A and B as complete; section C remains open pending resolution of a named specific issue. That is clearer than “we are still discussing it” because it eliminates ambiguity about what is settled and what is not.
What if the customer claims the work does not match what was agreed?
A signed scope document, a jointly signed punch list, and timestamped photos are the factual record. That record does not resolve a dispute on its own, but it determines who must show that something different from what is documented was actually agreed.
Building the path to a signature into the project from the start is more reliable than recovering it after a stall. The way TRACE 30 structures the closing gate, a job cannot be marked done without a customer-signed handover, so the signature gets scheduled into the project timeline rather than chased after the fact. Visit /program/ to see how it fits into a 30-day install, or schedule a call to walk through your current handover numbers.