Installation Completion Report Template: Record Tests, Exceptions and Customer Handover

An installation completion report template should show exactly what was installed, how it was checked, what remains open, and what the customer received. It must not turn “the technician left site” into an unsupported claim that the system is complete, compliant, commissioned, or accepted.

Adapt this framework to the equipment, contract, manufacturer requirements, site procedures, regulatory environment, and competent technical review. It is not engineering, safety, regulatory, or legal advice.

Define completion for this installation

Before the visit, identify the required completion criteria: physical installation, connection, configuration, inspection, test, commissioning, demonstration, documentation, training, and formal acceptance. These may occur on different dates and under different authorities.

Use precise labels. “Mechanical installation complete; electrical connection pending” is useful. “Job complete” is not, if required tests or handover remain outstanding.

Copyable installation completion report template

Customer / site / work order:
Installation date and report author:
Installer company, personnel, and roles:
Authorized scope and completion criteria:
Equipment / asset / model / serial number:
Location and asset identifier:
Approved drawing, specification, and revision:
Work completed:
Connections, configuration, and settings:
Inspections and tests — method — result — evidence:
Safety devices and protective measures checked:
Deviations, defects, unavailable tests, and restrictions:
Photos, certificates, and attachments:
Documentation, spares, keys, and credentials handed over:
Demonstration or training delivered:
Open actions — owner — due date:
Operational / acceptance status:
Installer review / customer acknowledgement:

Add fields required by the applicable quality plan or manufacturer. Do not copy irrelevant fields that encourage guessed answers.

Verify asset identity and controlled references

Record the model, serial number, asset tag, location, and work-order reference exactly. Check drawings, specifications, approved changes, and manufacturer information are current. If the physical asset differs from the planned one, pause and resolve the discrepancy.

Photos can support identity and condition where authorized, but captions should include asset and location. Protect customer addresses, screens, credentials, faces, and confidential site information.

Describe installed scope and exclusions

Write what was installed in verifiable terms: quantity, location, components, supports, connections, configuration, and interfaces. State excluded work, work by others, and temporary measures. Link approved variations rather than silently absorbing them into the original scope.

Reconcile installed quantities against issued materials and approved substitutions where the project requires it. Record unused, returned, damaged, or customer-retained components through the appropriate inventory route. This is especially important for serialized assets, controlled parts, keys, and removable media. The completion report should reference the accountable record rather than becoming an informal stock ledger.

The field service visit checklist supports the before-during-after visit workflow. The completion report is narrower: it is the evidence-backed closeout record for the installation itself.

Record inspections and tests with results

For each required check, capture method, acceptance criterion, instrument or reference where relevant, observed result, status, person, and evidence. Avoid writing only “tested OK.”

Only qualified people should perform specialist testing. Do not invent readings or mark unavailable tests as passed.

Record test conditions when they materially affect interpretation: supply state, load, environmental condition, software or firmware version, test equipment, and temporary configuration. If a result sits near an acceptance boundary, preserve the actual reading and criterion instead of rounding it into “pass.” Where retesting is required, keep the original result and link the later test so the evidence trail remains intact.

Distinguish installation, commissioning, and acceptance

Installation places and connects equipment. Commissioning may verify integrated operation and performance. Acceptance is a defined customer or contractual decision. The actual definitions vary by project.

Report each status separately and cite authority. If commissioning belongs to another party, state “installation complete to listed scope; commissioning by others pending.” A customer signature for receipt must not be relabelled as technical approval.

Manage exceptions and incomplete items openly

Create an exception line for every known defect, omission, failed or unavailable test, temporary configuration, access restriction, documentation gap, or customer concern. Include consequence and safe-use restriction where a competent authority establishes one.

Use the construction punch list template for systematic defect closeout and the equipment inspection checklist for condition-focused observations. Urgent safety concerns require immediate escalation through approved procedures.

Build an evidence pack that another person can navigate

Index evidence rather than attaching an unlabelled photo dump. A completion pack may include:

1. Approved drawings and revisions.
2. Product and asset records.
3. Inspection and test sheets.
4. Certificates and declarations where applicable.
5. Labelled photographs.
6. Configuration backup where authorized.
7. Manuals, maintenance instructions, and warranties.
8. Training or demonstration record.
9. Open-item list and acceptance record.

Follow the customer’s security, privacy, retention, and access requirements. Never place passwords or sensitive credentials in a broadly distributed report.

Conduct a clear customer handover

Explain normal operation, shutdown, alarms, limitations, maintenance, support, and emergency contacts within the installer’s competence. Record materials handed over and questions raised. Accessibility and language needs should be planned, not discovered at signature time.

Ask the receiving person to demonstrate critical routine steps where appropriate, such as identifying an alarm, locating an isolation point, or finding the support reference. This is a check of communication, not a substitute for required training or competence assessment. If the recipient cannot complete the step, clarify the instruction and record follow-up rather than obtaining a signature and leaving uncertainty behind.

Ask the customer representative to confirm what they are acknowledging. Options may include receipt of equipment, receipt of documents, attendance at a demonstration, awareness of open items, or formal acceptance. Do not combine these into one ambiguous checkbox.

Assign open actions and ownership

Every open item needs one owner, due date or trigger, required evidence, and effect on operational status. “Return later” is insufficient.

Open item: Protective cover missing from sensor S-04.
Owner: Installation supervisor.
Due: 22 July.
Status: Area remains restricted under site instruction SI-18.
Closure evidence: Photo and customer verification after fitment.

Use who completes the action item form to keep accountability unambiguous.

Turn an authorized technician recap into a structured draft. Kuno can support private dictation or consented capture, but the responsible professional must verify asset IDs, readings, tests, restrictions, and acceptance. Explore Kuno

Example completion summary

Scope: Install two monitoring units M-201 and M-202 in plant room B.
Completed: Units mounted, labelled, and connected according to drawing E-44 revision D.
Tests: Visual and functional checks recorded in TS-118. Integrated alarm test not performed because control-system access was unavailable.
Exception: M-202 protective cover damaged on delivery; temporary protection installed under site approval.
Operational status: M-201 available for authorized use; M-202 restricted pending replacement and retest.
Handover: Manual revision 3 and support contact provided. Customer acknowledged receipt, not final acceptance.
Action: Installer to replace cover and complete retest by 23 July.

The summary avoids a false all-or-nothing completion claim and gives every exception a route to closure.

Final review before issue

Check identity, scope, revisions, measurements, tests, evidence links, exceptions, operational restrictions, owners, dates, and the meaning of every signature. Reconcile the report with the field service report template where a broader visit record is also required, and preserve revisions under document control.

Set a post-handover review when performance can only be confirmed after operation over time. Identify the observation period, data source, acceptable outcome, responsible reviewer, and response if the result is outside the expected range. Do not call this future verification complete in the installation report; record it as a dated open action with clear operational limits.

Make the final record honest about both completion and limitations. Use Kuno only for appropriately authorized capture, then keep qualified humans responsible for tests, technical judgements, customer communication, and approval. See Kuno for field documentation