· Operations
A practical handover for staff covering another shift
A handover needs more than a list of open jobs. Give the incoming person the next action, current documents and an explicit way to accept or question the work.
Before someone covers another shift, put the next action and the person accepting it beside the open job. A task count alone does not tell the incoming person what to do. Start by checking what they can find in the records you already use.
Why cover handovers break in facility management
A handoff should answer three things: who owns the work, what is the current status, and what happens next. When those answers only exist in separate conversations, managers become the process. In facility cover, the outgoing technician may know that a chiller was noisy or a client asked for a call back, but none of it is attached to the job record. [1]
Look at your last three covers. For each job that was open at the handoff, write down the owner, status, and next action as they were understood by the person leaving. Then compare with what the incoming person actually found. Gaps show where the process depends on memory.
The pattern is not unique to facilities. A process change can leave owners outdated and follow-up actions hidden when handoffs, workflow rules, or views are not updated. A cover handoff is a temporary process change: the owner leaves, but the system still shows that person. [2]
Diagnose where ownership disappears
Choose a recent cover period and list the jobs that were still open when it began. For each one, ask the incoming person to show where they found the owner, latest update and next action. Note which records needed a call to the outgoing colleague. This gives you a list of handovers to investigate; a raw count alone is not a failure rate.
Judge urgency by impact, not age. An unowned action matters more when delay could affect safety, compliance, a customer commitment, or a time-sensitive decision. A pending filter change is less urgent than an unowned AC fault in a server room. [2]
Some task tools separate the owner from collaborators and record whether a handoff was accepted, declined, or still waiting. The point is not the tool but the observable response: the incoming person must actively accept the next action, not just see it. [3]
Check whether your current system already records who accepted the work. If it does, use that feature consistently before adding another process. If it does not, trial a short acknowledgement in the job record, with the person’s name and the action they have accepted. Include a way to flag missing information, rather than making a tick mean that every detail has been checked.
Build a handoff that survives the shift change
Use a compact handover note: the job reference, current position, next action, responsible person and due time or trigger. Link the latest drawing, quotation, site instruction or work order where relevant. For example: “Site A, job M-18: replacement part requested; Maya to confirm the supplier’s delivery date before tomorrow’s visit. Current supplier reply is attached to the job.” This is an illustrative note, not a client record.
A task needs one accountable owner at a time, not a team. Other contributors can help without sharing that accountability. During cover, the incoming person should be named on the record as the owner for that period, even if the original owner returns later. [4]
An unfinished maintenance job can still need a handover. Record the last completed step, what remains open and the location of the current findings. Ask the incoming person to confirm that they can access those details. This note supports the existing site procedures and technical instructions; it does not replace them.
Try the proposed note on two current jobs. Ask the incoming person to locate the documents and describe the next action without prompting. If they cannot, identify the missing detail and fix the record. Keep phone calls for questions that need discussion; the aim is not to ban a useful conversation.
Use the records you already keep
Keep the handover where the team already tracks the job. Avoid a second spreadsheet that will need its own updates. If owner, due date and status already exist, use them. Add only the information that your trial showed was missing, such as the next action or an acknowledgement.
A view can hide owner or follow-up details even when the record exists. Search for a known affected action directly and compare its details with the usual list. If the record appears in a direct search but not the normal view, review the view's filters, sorting, and displayed fields. [2]
Agree what “accepted” means before adding a status or checkbox. It might mean that the incoming person can find the current information and understands the next action. It should not silently mean that they approved the previous person’s work. If they decline the handover, record the reason and name who will resolve it.
When custom software is not worth buying
Separate a missing working habit from a missing software feature. If the existing record can hold the necessary details, trial the change there first. If an important handover still depends on copying the same information between systems, document that specific gap and compare configuration, an integration and a custom build. Include the work of maintaining each option. A software purchase is not the predetermined outcome of this check.
For the next cover period, nominate the person handing over and the person accepting the work. Agree the open-job list, attach the current documents and record unresolved questions. After that cover, review which jobs still needed someone to reconstruct the story. Change the part that failed and keep the parts that the team could use.
Sources
[1] The Manager as the Process: A Communication Problem
[3] Lapaas: Team Tasks & Projects App - Lapaas: Team Tasks & Projects
[4] How Teams Can Improve Cross-Team Task Ownership When Choosing a Jira Alternative
