Note
What Goes on a Handover Document an Engineer Will Sign
A signed handover document is the thing that separates a finished job from a closed job. Most contractors understand this now. The question is how you get the customer’s engineer to sign on the day, rather than after a round of phone calls and a second site visit.
The answer is almost always content. An engineer who hesitates is usually not being difficult. They are looking at a document that does not clearly show what was installed, what was tested, and what they are accepting responsibility for. Give them those three things in plain, site-specific language and the conversation is short.
Why does an engineer hesitate to sign?
Not every engineer delays. The ones who do usually have one of three concerns:
- The document uses generic categories that do not match what is on the floor. “Electrical panel” covers a wide range. “Cutler-Hammer 200A distribution board, Zone B, serial 2209-4471” does not leave room for ambiguity.
- There is no record of what was tested. Signing a document that says work is complete is different from signing one that says these specific points were tested and passed. Engineers are often signing something their plant manager or safety officer will review later.
- The scope is not in plain language. If the document is a list of technical line items with no summary of what the contractor was hired to do, the engineer is being asked to confirm something they may not fully understand.
None of that is unreasonable. The document carries their signature and they need to know what they are signing.
Why does the handover need two documents, not one?
A handover is not one document. It is two, even if they are presented as a single packet.
The installation record is a factual account of what was put in place: every piece of equipment, its location, brand and model, serial number, warranty expiry date, and whether commissioning tests were run on it. This is the record the customer keeps for future maintenance and inspection.
The acceptance certificate is the sign-off document: a plain-language description of the scope of work, a reference to the installation record, the key test results in summary form, the date of the final on-site inspection, and the signatures. This is the document someone will file and may need to retrieve in five years.
Both belong in the handover packet. Only the acceptance certificate means the customer has no record of what they received. Only the installation record means there is nothing to sign.
What goes on the installation record?
For a factory solar or LED installation, each item should include:
- Location or zone: specific enough that someone new to the site can find it without asking anyone (Roof Section A, Production Hall 3, MDB Room B2)
- Equipment type: panel, inverter, luminaire, distribution board, combiner box
- Brand and full model string: not a shorthand or internal reference
- Serial number: especially for inverters and panels, which carry manufacturer warranties tied to the serial
- Quantity: number of units at that location, not a running total across the whole job
- Warranty expiry date: a specific date, not a duration. “5-year warranty” is meaningless when the document is retrieved three years later with no installation date on the page
- Commissioning test and result: what was measured, what the reading was, pass or fail
A 40 kW rooftop solar system, for example, has 98 panels at a documented orientation, two inverters with individual serial numbers, a combiner box with its string configuration, and surge protection at two points. All of that belongs in the installation record. “Solar system installation” tells an engineer nothing they can verify on a walkthrough.
What goes on the acceptance certificate?
- A plain-language scope statement: “Installation of a 40 kW grid-connected solar PV system on Building 2 rooftop, including panels, inverters, cabling, and metering, per contract [number] dated [date]”
- A reference to the attached installation record
- Key commissioning results in summary form: system output at test, protection tests passed, metering confirmed
- The date of the final inspection on-site
- A signature line for the contractor’s representative with printed name and role
- A signature line for the customer’s engineer or site representative with printed name and role
That last line should read “Accepted on behalf of [customer company name]” so it is clear that the customer is accepting completed work, not just witnessing a document.
Does a generic template create problems?
A template that was not written for factory electrical work tends to strip out the specifics. The result is a document that looks complete but is not actually verifiable. The customer’s engineer cannot confirm “electrical equipment installed as per scope” against what they can see on a walkthrough. They can confirm “Inverter A: Huawei SUN2000-20KTL, serial 02KM-0034-7811, MDB Room, commissioned 2026-07-14, output at test 19.4 kW against rated 20 kW, pass.”
The specificity that feels like extra work to produce is the same specificity that gets the document signed on the day. These are not two different things. A generic template also has no natural place for warranty expiry dates or zone references, so that information ends up on a sticky note or not recorded at all.
What does this have to do with next year?
The installation record is the foundation of the site register. When the data from handover, including warranty expiry dates and the date for the next inspection, flows directly into the site record, nothing has to be reconstructed later. The warranty clock starts from a known date and someone can see when it ends.
The same document that gets you paid this month is the same document that tells your team which sites to contact next March. That connection only works if the data was captured at handover. If it was not, the maintenance side runs on memory, and memory is not a system.
FAQ
What if the engineer wants to add conditions before signing?
Normal, and not a reason to delay. A condition on a signed document is better than no signature. Common conditions are minor items to follow up within a fixed number of days. Note the condition, both parties sign, and the follow-up becomes a separate job order.
Does the handover document need to be in Thai?
For a customer whose engineer and plant manager work in Thai, a Thai-language version avoids ambiguity later. At minimum, equipment descriptions, serial numbers, test results, and warranty expiry dates should be readable without translation. A document that requires help to read is one a customer will hesitate to file.
How long should the on-site handover take?
If the document is prepared in advance from the job order, the on-site step is a walkthrough and a signature. Thirty minutes is the upper end for a standard solar or LED installation. If it takes longer, the preparation was incomplete, not the conversation.
If structuring your handover documents is part of what you want to put in place during the TRACE 30 install, the program overview is at /program/. If a short conversation first makes more sense, /schedule-a-call/ is there.