Workplace safetyWorkplace inspections
Contractor handovers: connect scope, site information and outstanding issues
A contractor handover should identify the parties, work scope, relevant site information and unresolved matters. It documents the exchange; it does not replace authorisations, competence checks or work-control arrangements required for the activity.
At a glance
A contractor handover should identify the parties, work scope, relevant site information and unresolved matters. It documents the exchange; it does not replace authorisations, competence checks or work-control arrangements required for the activity.
Define the decision behind the record
Clarify who gives and accepts the handover. Link the approved documents instead of copying fragments into an informal note that can become outdated. Distinguish information supplied from information acknowledged and any matter still requiring a decision.
Make the scope and remaining restrictions explicit
Identify the contractor work, location, relevant site information and responsible contacts. Define which permissions or other controlled records are referenced under the site procedure. A handover documents communication; it should not be mistaken for a permission or specialist assessment it does not provide.
Record the information actually transferred, current restrictions, unresolved questions and receiving role. Keep document versions and relevant work boundaries visible. If scope changes, record the change and required review instead of treating the original acknowledgement as coverage for different work.
Test whether the receiving person can retrieve the references and state the next required step. Preserve open actions and the owner responsible for clarifying them. A signature against a generic briefing is insufficient context when a reviewer cannot identify what site-specific information was communicated.
Worked example
A contractor team arrives for a defined task. The site representative records the relevant handover and outstanding question. The responsible person resolves the question through the applicable process, and the handover record links to that decision.
Build a usable record
Use the fields below to capture the facts needed for this particular decision. Keep the actual observation separate from any later correction or approval.
- Site and contractor identity
- Defined work scope
- Relevant controlled references
- Outstanding issues and restrictions
- Participants and acknowledgement
Example record and review decision
Fictional record example: HANDOVER-03: work scope, site information, contacts, relevant permissions and outstanding restrictions; ACK-03: receiving role.
Confirm that the receiving contractor understands the actual scope and unresolved conditions before work proceeds under site rules.
A signature against a generic briefing does not show which specific information or restrictions were communicated.
Test the review, not just the form
Use a practice handover containing an unresolved matter. Check that the record preserves it and does not allow a generic acknowledgement to imply it was solved. Make responsibility for the next step explicit.
A few useful answers
Is a signed handover the same as permission to start?
Not automatically. Follow the activity’s required approval and work-control procedures.
Does a handover signature authorise all contractor work?
Its meaning depends on the actual controlled process. Keep the communicated scope and references explicit; do not imply that a communication record replaces other required decisions or permissions.
Sources and further reading
MarkdownExplore starter templates
Start with a useful checklist
English
