How to Handle Extra Work When a Coworker Leaves

When a coworker leaves, their work rarely disappears. Reports still have due dates, customers still expect replies, approvals still need owners, and recurring processes keep running. The danger is that this work transfers invisibly: everyone assumes someone else has it, or one reliable person quietly accepts everything.

A better response begins with continuity and capacity. Identify what could fail, decide what the team will continue, and make every trade-off visible. Your personal planner can help you execute the agreed plan, but it should not replace your organization’s official task, HR, customer, security, or compliance systems.

If extra work affects pay, contracted hours, protected leave, safety, or employment terms, check employer policies and local requirements or seek qualified guidance; details vary by jurisdiction.

Start with continuity, not permanent ownership

The first question is not “Who gets everything?” It is “What must not fail in the next few days?” A sudden departure creates an information problem before it creates a scheduling problem.

Make a short continuity list:

• commitments due in the next one to two weeks;

• customers, vendors, or internal teams expecting a response;

• recurring processes such as payroll inputs, reports, rotations, or renewals;

• approvals, credentials, or access that only one person may have;

• work with safety, legal, financial, privacy, or service consequences;

• decisions that exist only in messages, notes, or one person’s memory.

Assign a temporary contact for each critical area, even if the long-term owner is unknown. A temporary owner is responsible for surfacing the next decision—not automatically for doing the entire former role.

If the coworker is available for a handover, use your organization’s approved process and prioritize access, status, and known risks.

Build an inherited-work inventory

You cannot prioritize a vague instruction like “cover Alex’s work.” Turn it into a list of outcomes and obligations. For each item, capture only the context needed to make a decision:

• expected outcome or service;

• next deadline and recurrence;

• current status;

• stakeholders or approver;

• required systems and access;

• dependencies and known blockers;

• rough effort and skill needed;

• consequence if delayed or stopped;

• temporary owner and decision date.

Keep confidential, personal, customer, health, financial, or security-sensitive data in the approved system. A personal task can say “review renewal in vendor system”; it does not need to copy the contract, account number, or private conversation.

Ask teammates to correct the inventory. Departing employees often carry hidden coordination work: the Friday reminder that prevents a missed filing, the relationship that unblocks a supplier, or the spreadsheet someone quietly reconciles each month. Treat the first inventory as a working map, not complete truth.

Triage what continues, transfers, pauses, or stops

Once the work is visible, sort it into four explicit decisions.

Continue now

These items protect people, customers, cash flow, compliance, safety, or a near-term commitment. Give them a named owner, a clear deadline, and enough authority to act.

Transfer

These items belong with another existing role, a replacement hire, another team, or an external provider. Name the receiving owner and the handoff condition. “Finance will take it” is not complete until a person accepts it and has access.

Pause

Useful work can wait while the team stabilizes. Record who approved the pause, what would restart it, and when to review the decision. Otherwise paused work returns as a surprise.

Stop

Some recurring work exists only because nobody has challenged it. If the outcome no longer justifies the effort, get the right owner to stop it deliberately and communicate the change.

This is a management decision, not a private productivity exercise. The person inheriting work can prepare options, but the accountable manager should confirm priorities and acceptable service changes.

Measure capacity before promising dates

Government workplace guidance from the UK’s Health and Safety Executive recommends assessing workload when roles and responsibilities change and when determining whether capacity exists for additional tasks. That is the right principle even outside the UK: changed staffing should trigger a capacity conversation, not an assumption that the same output will come from fewer hours.

Open the calendar and account for existing commitments first: meetings, deadlines, customer coverage, focused production, travel, training, and non-negotiable responsibilities. Then estimate the inherited work in workable units. “Monthly reporting” may include collecting inputs, resolving missing data, drafting, review, corrections, and distribution.

Do not fill every open block. New ownership creates questions, access delays, interruptions, and rework. The more uncertain the transition, the more unassigned capacity the plan needs.

If the work cannot fit, show the conflict in outcomes:

• “I can maintain the weekly report and customer escalations, but the process-improvement project would move to October.”

• “Covering the support rotation takes six scheduled hours, so one of the two analysis deadlines needs a new owner or date.”

• “I can be the temporary contact, but I do not have approval authority for the final decision.”

Specific trade-offs are easier to decide than “I am too busy.”

Have the alignment conversation early

Ask for a focused conversation with the person who can set priorities. Bring the inventory, your current commitments, and two or three viable options. A useful structure is:

1. State the continuity risk: what needs an owner now.

2. Show current capacity: the work and fixed commitments already in your week.

3. Offer choices: what can continue under each staffing or deadline scenario.

4. Clarify authority: which decisions, systems, budgets, or approvals come with the work.

5. Set a review date: when temporary coverage will be reassessed.

You can say: “I can cover the client queue and weekly forecast through September 25. To do that, we need to move the onboarding refresh or assign it elsewhere. Which outcome should take priority?”

Also ask whether the responsibility is temporary or ongoing, how success will be measured, who provides training, and how an ongoing role change is handled under company policy. Put the agreed decisions in the team’s authoritative system and send a concise written recap.

Turn the decision into a two-week transition plan

A short transition horizon is more reliable than pretending the whole quarter is known.

Days 1–2: stabilize

Confirm critical commitments, temporary contacts, access requests, and escalation routes. Cancel or defer work that has already been approved to pause. Protect time for urgent knowledge transfer.

Days 3–5: make the work repeatable

Run each critical process once if timing permits. Record missing steps in the approved documentation system, identify reviewers, and note where judgment or permission is still unclear. Avoid redesigning every process during emergency coverage.

Week 2: test the workload

Compare estimates with actual effort. Look for repeated interruptions, work that requires a specialist, and tasks that cannot be completed with current authority. Reassign, reduce scope, or move dates before temporary overload becomes the new baseline.

Schedule the review meeting now. Without a date, “temporary” coverage can continue indefinitely.

Protect the handoff and the official record

A transition can expose weak documentation and risky access practices. Use it to strengthen the system without turning your personal planner into a shadow database.

For each important process, the official record should make clear:

• who owns the outcome and who can approve it;

• where source files and decisions live;

• which account or role grants access;

• when the next action is due;

• how another person can detect a missed step;

• where to escalate when information or authority is missing.

Never share passwords through notes or messages. Follow the organization’s access-transfer and offboarding process. If client, patient, employee, financial, or regulated data is involved, use only approved tools and retention rules.

Watch for signs that the plan is failing

Longer hours are not proof that the transition is working. The CDC’s workplace-fatigue guidance notes that fatigue can reduce attention, short-term memory, reaction time, and judgment, and that employers and workers should manage the risk together.

Reassess the plan when you see:

• repeated work outside agreed hours;

• missed breaks or recovery time;

• rising errors, rework, or forgotten follow-ups;

• decisions delayed because authority is unclear;

• important existing work slipping without an explicit decision;

• no progress toward hiring, transfer, training, or scope reduction.

Bring evidence: hours required, deadlines at risk, work paused, errors, and the decisions you need. In safety-critical work, follow the formal escalation process immediately rather than waiting for the next planning meeting.

Example: inheriting an operations workload

Imagine a project coordinator leaves and you are asked to cover a monthly report, a supplier renewal, and the team rota while keeping your own launch work.

First, the manager confirms the rota and supplier renewal are continuity-critical. The report can move by one week, and a process-cleanup initiative pauses. You become the temporary contact for the renewal, but procurement retains approval authority.

Next, you break the renewal into access, current terms, stakeholder review, negotiation, approval, and signature. You reserve calendar blocks for the work and keep room for questions. The rota gets a named backup. The report receives a new deadline and stakeholder notice.

At the end of week two, actual effort shows that the rota consumes more time than expected. The manager transfers it to another trained teammate and keeps the renewal with you until completion. Nothing was “absorbed” invisibly: ownership, capacity, and trade-offs stayed explicit.

How Flick helps turn temporary coverage into a realistic plan

Flick can hold your personal execution plan beside the meetings and commitments already on your calendar. Create a project for the transition, use sections such as Critical, Waiting, This week, and Review, then give each next action a date, deadline, priority, reminder, or recurrence as appropriate.

Drag only ready work into open calendar time. If an access request or manager decision blocks a task, keep the follow-up visible rather than reserving production time you cannot use. For unpredictable coverage, leave gaps instead of scheduling the day edge to edge.

Keep organizational records, sensitive information, approvals, and team ownership in the approved system. Flick should answer “What do I need to do, and when can I do it?”—not become the only place the transition exists.

If unfinished work keeps rolling into tomorrow, use the guide to dealing with unfinished tasks. If every inherited request appears equally urgent, apply the task-prioritization method. To see tasks and fixed commitments together, explore Flick Planner.

Conclusion

Handling extra work after a coworker leaves is not about becoming more efficient at doing two jobs. It is a continuity and capacity problem that needs explicit decisions. Inventory the work, protect critical outcomes, transfer what belongs elsewhere, pause or stop lower-value work, and agree what your available time can actually support.

Then review the arrangement quickly. A good transition plan makes ownership and trade-offs visible enough to change. That protects the work, the team, and the person who stepped in to help.