Note
The Technical File That Travels with the Site
A signed acceptance certificate is the document that closes the job. The technical file is the document the factory’s engineering team actually uses.
Most contractors understand the first. Far fewer treat the second as a separate deliverable. The result is that the acceptance certificate gets filed and three years later the factory’s maintenance team calls because nobody knows how the Zone C distribution board is configured, or which protection relay controls the solar system’s anti-islanding function. The contractor becomes the first call for questions that a well-assembled technical file would have answered in two minutes.
What is the technical file, and how is it different from the acceptance certificate?
The acceptance certificate is a commercial and legal document. It records what was installed, what was tested, and that both parties agreed the scope was fulfilled. It is addressed to a file, a procurement system, and the customer’s accounts payable team.
The technical file is an operational document. It is addressed to the engineer who will maintain, modify, or troubleshoot the system over the next ten to twenty years. It answers different questions: not “was the work done?” but “what exactly is there, how is it wired, and how should a qualified person work on it safely?”
Both belong in the handover packet. Providing only the acceptance certificate means the customer has no working reference for future electrical work on the installation.
What goes in a complete technical file?
For a factory solar or LED installation, the file covers four areas.
System drawings
- As-built single-line diagram: the actual installed configuration, not the pre-installation design. If conduit was rerouted, a combiner box was relocated, or a string configuration was adjusted to fit the roof, the drawing reflects what is on the wall.
- Cable schedule: each cable run, its origin, destination, cross-section, and its protective device. For solar, this includes DC string cables and AC output cables. For LED, this means circuit-to-zone mapping with fixture count per circuit.
- Protection schedule: each protection device (circuit breaker, fuse, surge protection unit), its rating, and what it protects.
Equipment documentation
- Datasheet or specification sheet for each main piece of equipment: inverters, protection relays, distribution boards, LED drivers, luminaires.
- Serial numbers, if not already on the installation record inside the acceptance certificate.
- Manufacturer warranty documents: the actual warranty certificate, not just the warranty period noted elsewhere.
Test and commissioning records
- Full commissioning measurements: not a summary, but the actual values for each string, each circuit, each measurement point. The commissioning baseline record is the source of these.
- Protection test results, including anti-islanding test confirmation for solar systems connected to PEA or MEA.
- Insulation resistance test results per string or circuit.
- For LED: lux reading sheet with measurement point locations.
Operating and maintenance instructions
- O&M manual for each main piece of equipment, either a printed copy or a clearly identified document reference and revision number.
- A one-page system description written by the contractor: what was installed, how it is controlled, and what the first-level maintenance checks are. This is for the person who was not present on installation day and will not call before doing something to the system.
Why do engineers actually open it?
Three situations make the technical file more useful than the acceptance certificate alone.
Future modifications. Factories add equipment, change layouts, and increase electrical load. An engineer planning to extend a circuit or add new machinery needs the current protection schedule before touching the MDB. Without it, they are guessing or calling the original installer. If you are no longer the contact, the work gets done by someone without the full picture.
Fault diagnosis. When something stops working, the first task is locating the relevant circuit or protection device. An as-built drawing turns a twenty-minute search into a sixty-second reference check.
Audits and inspections. Factory customers subject to periodic safety or insurance audits will be asked for the single-line diagram and test records. If the contractor did not provide them, the factory must request them retrospectively, commission a new survey, or present an incomplete file.
What gets skipped, and what does it cost later?
The most commonly missing items are as-built drawings, O&M manuals, and commissioning certificates.
As-built drawings are the most critical gap. The design drawing is not an as-built. On most factory installations, something changes during the install: conduit is rerouted, a panel is moved, a string configuration is adjusted. If nobody marks those changes before handing over, the drawing is a description of intent, not reality.
O&M manuals get left out because contractors assume the customer will not read them. Many factory maintenance teams do, particularly for inverters and protection relays. The manual tells them which parameters are adjustable, what fault codes mean, and how to reset after a trip.
Commissioning certificates matter most when comparing two states. A claim that performance has degraded means nothing without a reference. The baseline measurements taken on commissioning day provide that reference.
How to assemble the file without extending the closeout
The documents that make up the technical file are produced during the installation. The as-built drawing is marked up as changes happen on site. Serial numbers go into the job order. Test results are recorded in the commissioning form. O&M manuals come in the equipment packaging or from the manufacturer’s website.
Assembly is collecting existing documents into one place. If that happens at job close rather than being reconstructed from scattered sources weeks later, it takes under two hours for a standard solar or LED project.
The practical question is who is responsible for collecting it, where it lives, and whether it transfers from close-out to the site register automatically or depends on someone remembering.
FAQ
Does the technical file replace the acceptance certificate?
No. The acceptance certificate is the commercial close-out: it proves scope was delivered and triggers invoicing. The technical file is the operational reference: it travels with the site for the life of the installation. Both belong in the handover packet.
Who should receive the technical file?
The factory’s engineering or facilities team, not only the project manager. On a larger site that may mean one copy to the project manager and a second to the head of electrical maintenance. The second copy is the one that gets used.
What if no as-built drawing was produced?
If the installation followed the design drawing with no changes, the design drawing can serve as the as-built, marked “installed as designed” with the date and contractor’s signature. If changes were made and not documented, the as-built needs to be produced retrospectively: a site visit to record what is there. That is the argument for marking changes during the install rather than after.
If you want a close-out process that captures both the acceptance certificate and the technical file together, the TRACE 30 program puts that in place. Details at /program/, or book a call at /schedule-a-call/.