Why the last hour before handoff matters

The final hour before a handoff is usually spent closing tickets, not testing what the next shift can absorb. A coordinator who carries twelve open items into a busy evening creates a backlog that looks like poor effort rather than poor planning. The check described here takes about fifteen minutes and produces one honest statement of capacity. It replaces the hopeful phrase that everything is under control with a short record the receiver can challenge.

The purpose is not to finish every item before the shift ends. The purpose is to hand over a workload that matches the hours, skills, and access available on the other side. A receiver who starts the shift already behind will triage by instinct and may drop the item that mattered most. A written capacity statement gives both shifts the same starting picture.

Define the handoff boundary

Write down the exact moment when responsibility changes hands and the system where that change is recorded. Include the queue, the escalation log, the shift calendar, and any tracker that holds a promised date. Exclude work that is still being discussed in chat and has never become a tracked request. A boundary that lives only in memory will move whenever the conversation becomes inconvenient.

Name the people on both sides of the handoff and the time each one is expected to be available. State whether the receiver has access to the same tools and whether a supervisor must approve any reassignment. Record the cutoff time for the snapshot so a late addition cannot silently change the count. Clear boundaries make the capacity check repeatable on the next shift.

Count unfinished work rather than activity

Count the items that still need an action after the handoff, not the items that were touched during the shift. An item can be opened, commented on, and reassigned without moving any closer to completion. Separate genuine progress from motion by asking what evidence would prove the item advanced. The count should include work that arrived late and work that was reopened after a failed check.

Group unfinished work by the kind of attention it needs rather than by the team that owns it. A decision request, a data correction, and a customer callback consume very different amounts of time. Show the count for each group so the receiver can judge the shape of the load. A total of twenty items means little when nineteen of them need the same specialist.

Separate urgent work from merely late work

Age alone does not make an item urgent, and a recent request can still carry a hard deadline. Mark each carried item with the date it entered the queue and the date a promise becomes due. Treat an item as urgent only when a missed date would break a commitment to a customer or another team. Everything else belongs in a separate list that the next shift can reach when time allows.

Write the consequence of a missed date in one plain sentence beside the item. A vague label such as high priority gives the receiver no way to compare two competing requests. The consequence also helps a supervisor decide whether to add staff or renegotiate the promise. Urgency that cannot be explained in a sentence is usually a preference rather than a commitment.

Confirm that every carried item has a next action

Open each item that crosses the handoff and read the last note before writing the carry-over line. Many stale items are waiting on a decision that nobody recorded, not on additional effort from the assigned person. Name the next action, the person who will take it, and the evidence that would show it happened. An item without a next action is a reminder, not work.

If the next action belongs to another team, record the request date and the response time that was agreed. If it belongs to a customer, note the last contact attempt and the date of the promised follow-up. If nobody knows what comes next, ask the owner before the handoff rather than after it. A clear next action is the smallest unit that makes a handoff useful.

Test whether the receiving shift can absorb the load

Compare the carried workload with the hours the receiving shift actually has available for planned work. Subtract meetings, planned leave, training, and any incident response that is already underway before the shift begins. The remaining time is the only capacity that can honestly be promised to the handoff. A plan built on the full shift length will fail as soon as the first unplanned request arrives.

Decide which carried items must finish during the receiving shift and which can wait without breaking a promise. Give every must-finish item a realistic time block and one named owner on the receiving side. Leave a buffer for the interruptions that occur in a normal week. If the load cannot fit, ask for a trade before the handoff rather than after the first missed date.

Write the note in the receiver's language

Write the carry-over note for someone who did not watch the shift unfold and cannot ask the sender a quick question. Replace internal shorthand with the actual system name, the record number, and the action that is expected. State what has already been tried so the receiver does not repeat a failed step or contact the wrong person. A note that requires a phone call to understand is not a handoff record.

Put the most time-sensitive item first and keep the whole note to one screen of text. Use short paragraphs that describe one item each rather than a long narrative about the whole day. Include the name of the person who can answer a question about each item and the time that person is available. The receiver should be able to start work without reconstructing the sender's memory from scattered messages.

Protect the check from becoming a status meeting

A capacity check works best as a private review followed by a short written handover. It does not need a meeting, a slide, or a round of verbal updates from the whole team. Keep the conversation focused on items that cannot be carried safely and decisions that must happen before the shift ends. Anything else can wait for the normal operating review.

Set a firm time limit and stop when the written note is complete. If the discussion turns into problem solving, park the issue with an owner and a review time. The check is a control on the handoff, not a substitute for the work itself. A short routine that happens every day beats a thorough meeting that happens once a month.

Record one unresolved risk and one open question

End the check by naming one risk that could disrupt the receiving shift and one question that still needs an answer. Describe the risk as a condition, such as missing access to the billing export, rather than as a general worry. Describe the question as a choice between named options with a short recommendation. Both entries give the next shift something specific to act on.

Assign a review time to each entry so it does not drift into a list of permanent concerns. If the risk clears, record what changed and who resolved it. If the question remains open, carry it forward with the date it was first raised. Aging a decision is as important as aging an item because both delay the same work.

Review the handoff trend weekly

Collect the daily capacity statements into a weekly view and look for repeated patterns rather than single difficult days. A load that grows every Friday may point to an intake process that nobody planned for. A recurring access problem may point to a role that needs a different set of permissions. The weekly review should end with one change, one owner, and one check date.

Keep the notes and the counts together in one folder so a later reviewer can compare like periods. Mark any change to the handoff process on the same timeline as the results, including the date it started and the person who approved it. If a change helps, keep it for another month before calling it a success. If it makes no difference, remove it rather than letting the routine accumulate unused steps.

Sources