Skip to content

Resource · installation

Prepare the fitting handover.

Record scope, access, dependencies, installation contact and completion checks before the job leaves the workshop.

Spectra guide · Source review: 3 November 2026

Use the working documents

Start blank, or inspect the clearly labelled fictional example.

Download editable CSVOpen printable A4 sheetOpen fictional completed exampleDownload fictional example CSV

At a glance

A good handover exposes current information and records what happened. It does not replace the competent safety, structural, electrical, work-at-height or contractual controls required for the installation.

01 / Release

Confirm the pack before departure.

Identify the current scope, site contact, access window, delivery plan, item count, escalation owner and the approved safe-working records the team must use.

02 / Complete

Record outcome item by item.

Link completed items to evidence. If a location, component or customer dependency prevents completion, state it plainly and assign the next action instead of marking the whole visit complete.

Use one row per issued item or location. installed_or_delivered should say what happened to that row only. A snag stays in exception_or_snag with a next_action and owner; it is not cleared by a successful row elsewhere on the sheet.

03 / Return

Bring exceptions back into the job trail.

Customer comments, snags, return visits and potential variations need distinct ownership. Reconcile them with the quoted scope under approved commercial controls.

Bring the job. Explore the next step.

Discuss your workflow