use cases

 The problem

A lawn care company runs 14 crews through spring and summer. The operations lead knows everything — which clients want cut short, which properties have irrigation systems that need shutting down before the first frost, which crew leads work well together and which do not, which commercial accounts pay late and need a call before invoice day. He has built that knowledge over three seasons.

He takes a full-time job in October. He gives two weeks notice.

The owner has 200 client accounts, 14 crew leads, and no document that captures any of what just walked out the door. Next April the new operations lead starts from zero. Three clients cancel in the first month because something was missed that should not have been.

What changes with Lastday

The moment the operations lead gives notice Lastday is triggered. He spends 40 minutes — not days — working through a guided handover. Client quirks. Crew dynamics. Equipment maintenance schedules. Seasonal patterns. A direct message to whoever comes next.

When the new operations lead starts in March she opens a complete briefing. She knows the accounts, the crew, and the things that matter before she makes a single call. The clients who were going to cancel do not cancel. The season starts clean.

 The problem

A quick service franchise with eight locations runs on consistency. Every location is supposed to operate the same way. The regional manager enforces that standard across all eight sites — supplier relationships, staff scheduling patterns, local health inspection requirements, the three equipment quirks that corporate does not know about, the two locations that need extra oversight.

She gets recruited away by a competitor. Six weeks later the franchise owner realizes how much lived operational knowledge she was carrying. Corporate documentation covers what the job is supposed to look like. It does not cover what the job actually requires in practice.

What changes with Lastday

When the regional manager hands in her notice Lastday captures the operational layer that corporate documentation never reaches. Location-specific supplier contacts. The maintenance issues that recur at location three and four. The staff members who are ready for more responsibility. The accounts that need attention before the end of the quarter.

Her replacement steps into a role that has context. Not a job description. Actual working knowledge from the person who held the role before him.

 The problem

A mid-sized commercial construction company has a site foreman who has run their largest projects for six years. He knows the subcontractors personally — who delivers on time, who needs chasing, who will cut corners if nobody is watching. He knows which inspectors are strict and which are flexible. He knows the client's actual preferences versus what is written in the contract. He knows where every body is buried on the current three sites.

He retires. The company throws a party and gives him a gift card. Nobody asks him to write anything down.

Twelve months later the new foreman is still asking questions that nobody on site can answer. Two subcontractor relationships have deteriorated. One client has escalated a complaint about a change in how the site is being run.

What changes with Lastday

Six weeks before the foreman retires Lastday begins the handover. Subcontractor assessments. Site-specific notes on each active project. Supplier contacts and the context behind each relationship. Equipment maintenance history. A direct briefing for the incoming foreman in his own words.

The six years of operational knowledge that was about to walk out the door is now on the platform. The new foreman is not starting from zero. He is starting from where the last one left off.

 The problem

A mid-sized accounting firm loses a senior manager after nine years. She was the primary relationship holder for 34 client accounts. She knew which clients were relaxed about deadlines and which called on the first of every month. She knew the history behind three long-running files that nobody else had ever touched. She knew which clients had been with the firm since the founding partner days and required particular care.

Her replacement is technically qualified. He has her files. He does not have her context.

Three clients request meetings in the first 90 days to assess whether they want to stay with the firm. One leaves. The other two stay but the relationship takes a year to rebuild to where it was.

What changes with Lastday

Before the senior manager's last day Lastday captures the client relationship layer that files and billing history cannot. Which clients require which communication style. The backstory on the sensitive files. The relationship history with the three founding-era accounts. What her replacement needs to know before he makes his first call to each client.

The clients who were going to request meetings still request meetings. But this time her replacement walks in knowing exactly who he is talking to and why it matters. One of those meetings becomes an opportunity to deepen the relationship rather than defend it.

The problem

A boutique hotel property loses its guest relations manager after two years. She knew the VIP guests by name and preference. She knew which corporate accounts had standing arrangements that were never written into the system. She knew which suppliers answered calls after hours and which did not. She knew the three maintenance issues that recur every winter and how to handle them before they become guest complaints.

Her knowledge was not in the property management system. It was not in any document. It was in her.

Her replacement is attentive and professional. But for the first three months the property feels slightly off to its most loyal guests. Small things are missed. A returning VIP does not get the room he always gets. A corporate account calls to ask why something that was always handled automatically is suddenly not.

What changes with Lastday

When the guest relations manager gives notice Lastday is triggered. She documents the VIP preferences, the corporate account arrangements, the supplier relationships, and the seasonal maintenance patterns. She writes a direct briefing to her replacement — the things she wishes someone had told her when she started.

Her replacement opens Lastday on her first shift. She knows the guests before they arrive. She knows the accounts before they call. She knows the property the way someone who has worked there for two years knows it — not the way someone on their first week knows it.

The returning VIP gets his room. The corporate account does not call.

The problem

A mid-sized municipality loses its infrastructure coordinator after 14 years. She knew every capital project that had been started, stalled, restarted, and quietly shelved over the past decade. She knew which contractors had performed well and which had disputes outstanding. She knew the history behind three ongoing projects that had political sensitivities nobody had written down anywhere. She knew which department heads communicated well with each other and which required careful handling. She knew where the skeletons were.

She gives four weeks notice. HR processes her departure. IT deactivates her accounts. Facilities collects her access card.

Nobody captures what she knew.

Her replacement is hired three months later. He is qualified, experienced, and completely without context. His first six months are spent reconstructing what happened before him — calling contractors, reading through years of meeting minutes, asking colleagues questions they can only partially answer. Two capital projects stall during the transition because a decision that needed her context cannot be made without it. A contractor dispute that was on the verge of resolution goes cold because nobody knows the history of the negotiation.

The public does not see the internal disruption. But they feel it in delayed timelines, inconsistent service, and the quiet frustration of staff who keep answering the same questions for someone who should already know.

What changes with Lastday

Six weeks before the infrastructure coordinator's last day Lastday begins the handover. Active projects and their status. Contractor relationships and the context behind each one. The political sensitivities on the three files that require careful handling. The interdepartmental dynamics that are not in any org chart. A direct briefing for her replacement — written in her own words — covering the things that matter most and the things that are most likely to go wrong.

When her replacement starts he does not begin from zero. He begins from where she left off. The capital projects move forward. The contractor dispute is resolved with the history intact. The institutional knowledge that 14 years of public service built does not evaporate on her last Friday.

The taxpayers who fund the organisation never know what almost happened. That is exactly how it should be.