Operations-maintenance handoffs: make the next owner clear

A status update does not tell you who owns the next decision.

Maintenance says the job is finished. Operations says it is still waiting. Both statements may be accurate because the teams mean different things by “finished.” The work may be complete while a review, access agreement, or follow-up decision remains open.

An operations-maintenance handoff needs a shared record of the current state, the next action or decision, and a receiver who accepts responsibility within their authority. Sending a message proves only that a message was sent. The receiver still needs to understand what is being handed over and identify anything they cannot accept.

This guide concerns coordination and ownership across teams and shifts. Technical acceptance and authorization to operate belong to the site’s approved processes; a handoff conversation does not replace them.

Locate the missing agreement

Pick a recent job that required repeated calls between operations and maintenance. Reconstruct the last handoff using the work order, shift log, and decision history. Ask both sides these questions before discussing attitude or effort:

• What did the sender believe was complete, and what did the receiver believe was still pending?
• Which record described the latest state? Could both teams access the same version?
• Was the next action assigned to a named role with a person covering it on that shift?
• Did that person accept the action, or were they merely copied into a message?
• Could they make the needed decision? If not, was the authorized decision owner identified?
• What checkpoint or change in circumstances should have triggered another conversation?

Separate an information gap from an authority gap. A supervisor can understand the issue perfectly and still lack the authority to resolve it. Asking for better communication will not settle a decision that neither side owns.

A handoff checklist for open work

Use one shared record and a two-way discussion where the work requires it. Prepare it before the transfer, allow questions, and have the receiver cross-check the information they need. HSE identifies preparation, information exchange, and incoming checks as core elements of handover, including between operations and maintenance.

• Reference: asset, work order, linked actions, and the time the status was last checked.
• Window and participants: agreed access or handback window, the operations owner responsible for release, and the sending and receiving maintenance shifts. Reference readiness evidence and record unresolved constraints instead of assuming the next shift knows them.
• Current state: what is complete, incomplete, or unconfirmed. Point to the authoritative status and approval records instead of replacing them with “all good.”
• Next step: the specific action or decision needed, its dependencies, and the supporting information still missing.
• Owner and authority: the receiving person or covered role, what they accepted, and who can resolve decisions outside their authority.
• Checkpoint: when the teams will review the item again and where a changed condition or missed commitment is escalated under local rules.
• Incoming check: the receiver confirms their understanding of the next step and records any disagreement or gap before it becomes an assumption.

If the window, scope, or owner changes, retain the original agreement and add the revised commitment, reason, decision owner, and who was notified. A changed date without that trail leaves the receiving shift unable to tell whether it is seeing a proposal or an accepted change.

“Maintenance to follow up” is too broad when several crews are involved. “Incoming maintenance supervisor to obtain the missing contractor report before the afternoon review” identifies an action someone can accept. It still does not delegate technical approval to that supervisor.

Remove the dependence on the person who remembers

If every unclear handoff ends with “call the day supervisor,” that person is carrying information the process should make available. Ask what they routinely reconstruct: the decision owner, a verbal agreement, an unresolved dependency, or the location of a record. Put that missing element into the shared handoff.

Agree the expectations jointly. Operations and maintenance need to use the same meanings for pending, accepted, and complete, even if their systems use different status names. Test those meanings against an actual job. Identify cover when the usual owner is absent and a route for disagreements that cannot be resolved at shift level.

Leaders also need to protect time for preparation and questions. A form completed after both shifts have left cannot repair the opportunity to challenge an unclear statement. Start with one recurring transfer and involve the people who send and receive it.

Check the next comparable handoffs

Review whether the receiver could locate the current record, name their accepted action, and identify the next decision owner. Log unresolved ownership gaps and revisit them at the agreed checkpoint. Keep the sample and work context visible; do not turn a few observations into a plant-wide score.

A clean checklist is not enough if the next shift still needs the same private phone call. Use those calls as evidence of information or authority that remains missing, and change the handoff accordingly.

Choose the tool for the gap you found

The free Shift Start Checklist helps prepare incoming work and carry forward open items. Adapt its proposed timing to the demands of the work. For dependence on a single coordinator, use the Dependency Test to identify what would become unclear when that person is unavailable.

If an agreement never became a request, start with the CMMS intake guide. If the completed work record lacks usable evidence, use the close-out notes guide. The weekly schedule guide addresses the separate question of why committed jobs miss their windows.

For the production decisions behind protected maintenance access, read The Floor Report #14: Reliability Is a Production Decision. Use the handoff record here to make the resulting agreement visible to the people who must carry it out.