Employer guide · Site handover
Prepare a Supervisor Handover Before a Workforce Assignment Starts
A workforce brief explains what the employer wants. A supervisor handover explains how the agreed assignment will be managed at the actual site. Use this guide to connect the approved scope, reporting arrangements and site readiness before accepting a start. The sample below illustrates a planning method; it does not confirm personnel availability, equipment authority or a mobilisation date.
Start with the assignment that was actually accepted
Bring the current scope, role schedule and agreed operating assumptions to the handover. Identify their version and approval status. A supplier proposal, an employer request and an accepted assignment can describe different things. If the documents disagree, record the difference and refer it to the people authorized to resolve it before presenting the scope as settled.
Separate routine tasks from specialist duties. “Warehouse support” does not establish permission to operate equipment, and “maintenance support” does not establish competence or authorization for electrical work. The employer should describe the actual task and the evidence or site approval needed for it. A supervisor should not use a convenient job title to expand an individual’s duties.
Record the work location, designated areas, coverage window and expected reporting point. If two buildings have different access arrangements or supervision, give each its own entry. An employer’s commercial contact may coordinate the contract while another person controls day-to-day site acceptance. Name both responsibilities so instructions reach the right person.
Allocate responsibilities without assuming the supervisor owns everything
A handover is useful when each issue has a decision owner. The following table is a discussion template, not a statement that a supplier or employer automatically carries a particular contractual obligation. Agree responsibilities against the actual contract and the site’s operating arrangements.
| Topic | Decision to record | Handover evidence |
|---|---|---|
| Site access | Who confirms the reporting point, access process and restrictions? | Named site contact and current access instructions |
| Task allocation | Who can assign work within the accepted duty boundary? | Approved task list and escalation contact |
| Materials and equipment | Who supplies, checks and authorizes the items required? | Agreed responsibility and outstanding readiness issues |
| Attendance | Who records attendance and who accepts corrections? | Record format, cut-off and dispute route |
| Changes and replacements | Who may approve a changed requirement or proposed replacement? | Approval route and updated acceptance record |
Use names or accountable roles rather than “the team will handle it.” Provide a backup contact for a person who may be unavailable. Keep routine reporting and urgent escalation distinguishable, and confirm which communication channel the site accepts.
Walk through readiness before planning the first shift
Review the route from arrival to the assigned work area. Confirm where individuals report, who meets them and how the site communicates relevant instructions. Identify any induction, task briefing, competence review or access approval that must occur before the agreed duties begin. A completed attendance list alone does not prove that these checks are complete.
Check whether the task area, materials, supervision and reporting process are ready for the requested coverage window. Record transport or accommodation arrangements only as agreed responsibilities; do not infer them from a quotation label. Where dependencies remain unresolved, state the issue, owner and next review. Keep a requested date separate from an accepted joining plan.
The handover should identify the site’s existing emergency and incident-reporting routes. This guide does not replace the site’s procedures or provide operating instructions for equipment or specialist work. Relevant instructions should come from the authorized site personnel and the applicable task process.
Use an illustrative first-shift example to test the plan
Suppose a warehouse brief describes four receiving-support positions and three dispatch-support positions during two named coverage windows. These seven working positions are illustrative. They do not establish the number of individuals needed once rest, relief, eligibility and the actual schedule are reviewed.
The supervisor handover records a receiving reporting point and a separate dispatch reporting point. It names the site contact who confirms task boundaries and the person who reviews attendance. Equipment operation is excluded from the support scope unless separately reviewed and accepted with the necessary evidence. This prevents a general support request from becoming an assumed operator assignment.
Before the first shift, the receiving area is ready but dispatch access remains unresolved. Record dispatch access as an open issue and ask the authorized parties to decide how it affects the assignment. Do not quietly move the dispatch positions to receiving or call the original requirement fulfilled. Any changed allocation needs an updated scope and the appropriate acceptance.
At the review, compare the actual reporting and allocated duties with the accepted plan. Record differences, their effect and the agreed next action. The value of the example is the sequence of decisions, not a recommended headcount or a promise that a team can start.
Manage changes through a visible decision record
Distinguish an instruction within an accepted task from a new requirement. A different work area, additional shift, specialist duty or added location may change readiness, qualifications or commercial assumptions. Capture the requested change and refer it for review instead of treating verbal agreement between individuals as a contract amendment.
Use a simple record: what changed, who requested it, which document it affects, who must approve it and when the revised arrangement applies. Keep unresolved requests separate from accepted changes. If the employer and supplier interpret the request differently, preserve the question and seek an explicit decision.
A proposed replacement also needs review against the actual role and site requirements. Record the reason, required evidence, acceptance contact and handover status without promising an automatic replacement time. Protect personal information: the general operations record should contain only the information needed for its purpose, with any required personal documents handled through an appropriate restricted route.
Record a coverage gap before requesting a replacement
First identify the operating issue: an uncovered position, a mismatch with the accepted task, a site-access dependency or a proposed change in the required role. These situations need different decisions. Record the affected site, duty, coverage window and operational impact. Keep allegations and unnecessary personal details out of the shared operating log; a personnel matter should follow the appropriate restricted process.
Use this four-step review record alongside the accepted assignment. It is a planning template, not a guaranteed replacement service or response-time commitment.
| Stage | Information to record | Decision before proceeding |
|---|---|---|
| Report the gap | Site, role, affected coverage period, current duty boundary and reporting contact | Confirm whether the accepted requirement is unchanged or needs a scope review |
| Review a proposed person | Task-specific evidence, required site approvals and unresolved dependencies | The named acceptance owner records what has been checked and what remains open |
| Confirm joining readiness | Reporting point, induction, access, supervision and agreed commercial implications | Record the accepted joining arrangement separately from the originally requested date |
| Close the handover | Actual attendance, briefing completion, accepted duties and remaining follow-up | Confirm the operating record reflects what actually happened; keep unresolved issues visible |
For example, an illustrative evening dispatch position may become uncovered while the workload stays the same. The employer records the existing duties and affected period, then asks for a review. A proposed person still needs the relevant task and site checks. If the employer now requests equipment operation that was excluded from the accepted duty list, that is a changed requirement rather than a like-for-like substitution. Availability, timing and any commercial effect require separate confirmation.
Do not close the record merely because a name appears on a proposed list. Close the operating gap only after the authorized site contact confirms the actual arrangement. Retain the previous assignment version, the acceptance decision and the next review date so the following supervisor can distinguish a proposal from an implemented change.
Close the handover with an action list and review point
Read back the agreed scope, reporting route and open issues before closing the meeting. Allocate each unresolved item to an owner and record the next review. An issue marked “pending” without a responsible person is unlikely to be resolved reliably. Make the current document available to the people who will use it and identify who maintains the next version.
Agree a review point after the initial assignment begins, subject to the accepted start plan. Compare actual duties, attendance, supervision and readiness with the record. A successful review is evidence that the arrangement matches what was accepted; it should not conceal a different scope behind a completed checklist.
- Confirm the accepted scope and document version.
- Identify duty boundaries and task-specific evidence.
- Name site acceptance, task allocation and attendance owners.
- Record access, materials and other readiness dependencies.
- Set the escalation and change-approval routes.
- Keep open issues, accepted decisions and provisional dates separate.
- Agree who maintains the record and when it will be reviewed.
Prepare the initial inputs with the requirement-brief guide. For responsibilities across locations, use multi-site workforce planning. Review commercial accountability through the workforce outsourcing guide, then send the actual scope through the manpower quotation route.
