INFINITE UPSIDE

A departure plan that closes real tasks

How do I plan an employee’s last working day?

Make the next morning work, with a handover that fits the hours you actually have.

Plan an employee’s last working day around five things: unfinished work, the person taking it over, company records, authorized access changes and the actual pay-and-benefits process. Give each task a responsible person, a completion time and evidence that it happened. Then check whether the work fits into the paid hours available. A checklist cannot squeeze ten hours into eight.

The awkward handover is often the one that looks tidy. The laptop is back, the goodbye message has gone out and an urgent customer job is sitting in a folder nobody knows how to find. I would start with what has to work the following morning, then build the departure plan backward from there.

Start with the work that will outlive the role

Make a short inventory of open commitments. Include customer promises, supplier questions, internal approvals and recurring tasks due soon after departure. Identify the current version of each relevant record, where it belongs and who can legitimately use it.

“Alex knows about this” is a warning, not an assignment. Replace it with a named successor, the next action and the date it must happen. If nobody has the authority or skill to take responsibility, escalate that gap while there is still time to change the plan.

Separate three states: work finished, work handed over and work still unassigned. Moving a file into a shared folder does not prove that another person has accepted the job. An honest unassigned item is more useful than a false green check mark.

Keep customer communications proportionate. The new contact needs the relevant commitment and context, not a dramatic account of why someone is leaving. Decide who is authorized to communicate the change and how incoming questions will reach a responsible person.

Write a handoff a successor can use

A useful handoff answers a small set of questions: What was promised? What is complete? What remains? Which version is current? What decision comes next? Who can make it?

For a customer project, include the agreed scope, outstanding dependencies, relevant correspondence and any acceptance still needed. Label a draft as a draft. If two versions disagree, resolve the discrepancy or identify it explicitly; do not leave the successor to discover it during a customer call.

Give the recipient time to inspect the material. A brief walkthrough lets them ask about a missing decision or an unexplained exception. Their acceptance should describe what they can take on, rather than implying that every historical problem is now solved.

Some knowledge will remain uncertain. Record the uncertainty and its consequence. “Supplier has not confirmed Friday delivery; Jordan will check before promising the installation date” is actionable. “All suppliers handled” is comforting until Friday arrives.

Check the paid hours before assigning the day

Consider an entirely fictional planned departure. The employee has eight paid working hours on the last day, at an all-in employment cost of $30 an hour. Customer work already accepted requires six hours. A properly scoped handover requires another four.

That is ten hours of work in an eight-hour day. The two-hour shortfall is real even if the employee is cooperative and the manager calls the handover quick. An extra unpaid evening is not a sound planning assumption.

In this original example, a qualified colleague has two genuinely available paid hours and can take a clearly defined part of the customer work without displacing another commitment. The customer arrangement permits that reassignment. The departing employee now has four hours of customer work and four hours for the handover.

The handover block contains one hour to check the work inventory and current records, one to prepare job briefs, one for a successor walkthrough and one for property return and final checks. These are illustrative allocations, not standard times every employer should copy.

The manager also has two paid hours available. One is spent in the joint walkthrough and one on assignment, approvals and completion checks. Both participants’ time in the meeting is counted; one meeting hour consumes an hour from each person’s separate capacity.

Price the complete defined work plan

The colleague costs the same all-in $30 hourly rate. The manager costs $50 an hour. Authorized IT staff have one available hour at $80, and a payroll reviewer has thirty minutes at $60 an hour. All are available without silently displacing other accepted work.

Scroll across for the original last-day work allocation. These costs do not calculate the employee’s final settlement.

Person and defined workPaid time and all-in rateAllocated cost
Departing employee: customer work and handover8 hours × $30$240
Colleague: transferred customer work2 hours × $30$60
Manager: walkthrough, assignments and checks2 hours × $50$100
Authorized IT: planned access and asset tasks1 hour × $80$80
Payroll reviewer: review and routing0.5 hour × $60$30
Complete defined work allocation13.5 paid person-hours$510

The $510 is a work-cost allocation for this finite plan. It is not a final paycheck, an incremental cash-saving claim or the total cost of the departure. Earned compensation, applicable leave, benefits, contractual obligations and any separation arrangement require their own actual review and funding.

If the colleague becomes unavailable, the two-hour gap returns. Reassign, reschedule with the necessary agreement or change the work scope. Do not preserve the old completion promise merely because the departure spreadsheet has already been approved.

Inventory access with the authorized people

List relevant company systems, shared records, administrative roles, physical keys, devices and provider relationships. Ask the authorized administrators to identify any company operation that depends on the departing employee’s account or recovery route.

The FTC’s Start with Security guide recommends limiting sensitive-data access to legitimate job needs and limiting administrative privileges to employees responsible for that work. This helps frame the question: what access is still needed for the remaining assigned work, and what must end when that need ends?

NIST’s small-business cybersecurity guide similarly asks whether access is removed when it is no longer needed. The practical departure plan needs an authorized owner and a verified completion record for that change.

Do not solve an ownership problem by asking for a personal password or impersonating the former employee. Use the organization’s approved, provider-supported administrative process for business records and continuity. Company business tied to a personal account needs appropriate review, not an improvised credential exchange.

The actual access sequence depends on the departure and systems involved. An ordinary planned departure may require access for agreed work until a defined time. An urgent or involuntary departure may require a different response from authorized HR and security personnel. Neither case supports a universal instruction to switch everything off at five o’clock.

Preserve records before making them unreachable

Account removal, record preservation and business continuity are related tasks with different consequences. Deleting an account first can make needed records difficult to recover. Keeping everything indefinitely creates its own record-handling problem.

Have the responsible people establish what must be retained, where the controlled business copy belongs, who may access it and which actual retention or preservation requirements apply. Follow legal holds and other applicable obligations. Do not treat this article as a schedule authorizing deletion.

Check whether the successor can locate and open the needed current records through their own authorized access. A file path copied from someone else’s desktop is not enough. Do not broadly copy unrelated customer or employee information just to feel certain that nothing was missed.

The founder-absence guide examines how operations function when a key person is away. A permanent employee departure adds a different completion requirement: responsibilities and authorized access must have a durable owner after the person has left.

Make property and pay separate completion records

For company property, identify the item, its business owner, the return arrangement and the person who will confirm receipt. Record an exception such as equipment still in transit. A scheduled collection is not the same as an item received.

Use appropriate procedures for devices that contain both personal and business material. Ownership alone does not supply a universal right to inspect or erase every item of information. Authorized staff should follow the actual agreement, policy and applicable requirements.

For pay and benefits, identify the responsible reviewer, required inputs and unresolved questions. Applicable timing, leave treatment, deductions and notices depend on the actual employment circumstances and governing requirements. Have those checked through the proper process rather than copying a deadline from an unrelated example.

Keep equipment disagreements and payroll obligations separately visible. Do not assume a missing laptop authorizes withholding wages. The plan should show who is resolving each question and when the employee will receive accurate information.

Close with evidence and a route for exceptions

Use a compact completion record: task, responsible person, due time, status, evidence and unresolved condition. “Requested,” “approved” and “completed” should remain separate. An administrator’s completed action and the appropriate verification provide stronger evidence than an email asking someone to do it.

For the fictional customer handoff, completion means the successor has accepted the defined work and can use the current records. For a returned device, it means the authorized recipient confirms receipt. For an access change, the authorized administrator records the actual action and appropriate verification, without distributing credentials in the checklist.

Choose a responsible contact for issues discovered afterward. Do not make free, indefinite support from the former employee the hidden operating model. Any later work needs an appropriate agreed arrangement; the successor and manager still own the business’s commitments.

Feedback can have its own conversation and record. It should not become a condition for a proper operational handover or accurate treatment of pay. The last day is complete when the actual tasks are resolved or honestly assigned, not when everybody has said something pleasant.

  1. Identify commitments and current records.
  2. Assign capable successors and acceptance steps.
  3. Fit the work into funded, available hours.
  4. Coordinate authorized access, preservation and property tasks.
  5. Route pay and benefits through their actual requirements.
  6. Record completion evidence and owners for remaining exceptions.

Read alongside the book

Original commentary and discussion material. Read the full personal accounts in Infinite Upside: Building Wealth With Room to Live, by Vijay Sheth.

Find your edition · Chapter companion

Choose an edition

Choose an edition

ABOUT THE CONTRIBUTOR

Luna Lim

DIRECTOR OF FINANCIAL RESEARCH & EDITORIAL STRATEGY

SHETH CAPITAL, INC.

Luna Lim writes about business, investing, and the judgment behind financial decisions. She joined PCH Exotics Inc. as Director of Operations in 2022, working across La Jolla and Miami. Today, she reports directly to Vijay Sheth at Sheth Capital, Inc., bringing an operator’s perspective to the ideas she covers.

Based in Pacific Beach, California, Luna is curious about the people behind the numbers: what they’re building, how they weigh uncertainty, and what makes a risk worth taking. Her articles for Infinite Upside follow those questions through the details, with clear explanations and a feel for how decisions play out in everyday business.

More from Luna Lim

The Infinite Upside store