Pack contents: everything the client signs
The handover pack has a fixed spine: the plan as installed, the single-line diagram, the panel schedule with breaker ratings, the cable schedule with routes and cross-sections, the bill of materials, the estimate as executed, and the automatic-check report. Where the panel passport with QR is issued, it joins the pack as the panel's identity card for future maintenance.
Close the pack with two administrative pages: the acceptance record and the snag list. In GorkyCAD the whole set — plan, single-line, panel schedule, specification, cable schedule, estimate — exports as one PDF from a single model, so the pack cannot contain a plan from March and a schedule from May. One model, one revision, one signature.
- Drawings: plan, single-line diagram, panel schedule.
- Registers: cable schedule, bill of materials, estimate.
- Admin: check report, acceptance record, snag list.
Lean on the standards behind the set: IEC 60617 single-line symbols, IEC 60364-based sizing and protection checks, and a deterministic calculation engine rather than a language model. Clients rarely read methodologies, but naming them in the cover note visibly raises the weight of the pack.
As-built vs design: redlines that matter
Almost no installation matches the design millimetre for millimetre: a route shifts around a beam, a device is substituted for an equal, a group splits during commissioning. Each deviation gets a redline on the drawing and a one-line note — what changed, why, who approved it. Unrecorded deviations are the seeds of every future dispute.
Produce the as-built set by updating the model, not by sketching over PDFs: move the route, swap the device, regenerate the schedules and re-export. The client signs the as-built set, because only it matches the building they own. Keep the original design issue in the archive — the pair of revisions tells the full story if questions arise years later.
Snag list procedure: acceptance without drama
Run acceptance as a walkthrough, not a paperwork ambush. Invite the client to the site with the printed plan, switch every group on and off, test RCD trip buttons, check labelling against the panel schedule, and write every remark into the snag list on the spot with a named owner and a date.
Split remarks into three buckets: fix before acceptance, fix within an agreed short window after acceptance with money retained, and change requests that become a new paid order. Read the list aloud at the end of the walkthrough and have both sides sign it. A signed snag list with dates ends arguments; an unsigned verbal list extends them for months.
- Walk the site with the plan in hand.
- Sort remarks: before, shortly after, new order.
- Sign the list the same day.
User notes: breakers, RCDs, spares
Most clients cannot read a single-line diagram — write them half a page in plain words. Which breaker feeds the kitchen, where the main switch lives, how to reset a tripped RCD and when a repeated trip means calling you instead of resetting again. Add the emergency procedure: smell of burning, water in the panel, partial outage — what to switch off first and which number to call.
List the spares handed over: spare ways in the panel, spare fuses or breakers, the key to the panel lock. Note the maintenance rhythm in one line — RCD test button quarterly, panel inspection yearly — and name who performs it. Half a page of user notes prevents more night calls than any amount of extra devices.
Liability boundary and signature
Until the approving engineer signs, all calculations and AI suggestions remain preliminary materials; responsibility for design decisions sits with the engineer who approves the set, as the licence and the calculation methodology state. The acceptance signature transfers the documented result — not a blank guarantee — to the client, within the contract's warranty terms.
Write the boundary explicitly: the contractor answers for the documented scope and workmanship, not for later client alterations, extra loads connected without approval, or third-party interventions. For kindergartens, schools and hospitals, independent expert review is mandatory — note it in the pack. A signature under a clear boundary protects the contractor and informs the client; vagueness protects nobody.
Archive: where the pack lives for years
Hand the client the signed PDF set and keep an identical copy yourself — same revision, same signatures, stored read-only. Name files so a stranger finds them: project address, handover date, revision code. Keep the model or its export alongside the PDF so a future extension starts from the as-built truth, not from a fresh survey.
Log the handover in one line in your register: project, date, pack revision, warranty end, who holds the keys and the spares list. When the client calls in two years asking which breaker feeds the extension, the answer should take two minutes. Local project data with offline PWA support means the archive survives network outages; disciplined naming means it survives staff turnover.
Acceptance checklist for this week
Take your nearest finishing project and run it through this article as a checklist: is the model updated to as-built, are the schedules regenerated, is the snag list signed, do the user notes exist? Whatever is missing becomes the template for every future handover.
Price the discipline into the next quote as a line item — documentation and handover take half a day and save weeks of disputes. A Pro subscription at €40/mo with exports to PDF, DXF, XLSX, IFC, BCF and GLTF plus 20,000 AI tokens a month costs less than one disputed site visit. Details live on the pricing page.
FAQ
What is in the handover pack?
The issued drawings (plan, single-line diagram, panel schedule), the cable schedule, the bill of materials and estimate, the check report, the panel passport where applicable, and the signed acceptance record with the snag list. Add short user notes: which breaker feeds what, how to test RCDs, where spares live.
As-built vs design?
The design shows what was planned; the as-built set shows what was actually installed, with redlines for every deviation — moved routes, substituted devices, resized cables. The as-built set is the one the client signs, because it matches the walls they own.
Snag window?
Fix it in the contract before handover: commonly 7 to 30 days for the client to report visible defects, with a named contact and a written snag list. Latent defects follow the warranty period in the contract and the law — the snag window never replaces warranty.
Who is liable after sign-off?
After acceptance and within the warranty terms, the contractor answers for workmanship and materials under the contract — but not for the client's later alterations, unapproved loads or third-party interventions. Every change after sign-off needs a new written record, or liability blurs within months.
Related articles
- Electrical documentation guide
- PDF set: specification and estimate
- Electrical drawing checklist
- Electrical project stages
One model, one handover set — open the editor
Export the full handover set — plan, single-line diagram, panel schedule, cable schedule, estimate — as one PDF from a single model. Start free in the browser.
Open GorkyCAD