
It is the last afternoon of Thandi’s notice period. There is cake in the canteen, a card signed by most of the warehouse and a handover document that runs to a page and a half. Everyone agrees she will be hard to replace.
On Monday morning, a reach truck at the second site stops halfway through the shift. Her successor opens the handover document, then the shared drive, then Thandi’s old mailbox. Somewhere in there is the service history, the name of the technician who fixed the same fault in July and the quotation that was approved but never booked.
“Where would she have kept that?” is a fair question. It is also the moment a resignation becomes an operational problem.
Fleet knowledge tends to collect in one person
In most operations, there is someone who simply knows. They know which forklift is due for its load test, which supplier to phone for which site and why the older counterbalance truck is never sent to the cold store. Nobody planned it that way. They were reliable, so the questions came to them, and over time the answers stayed with them.
That person is usually an asset to the business, not a weakness. The risk is not that they know too much. It is that nobody else can see what they know.
While they are there, it works. Until it doesn’t: a long leave, a promotion, a resignation or simply a week off sick in the middle of a busy month.
What walks out the door is rarely written down
A handover document tends to capture what the leaving person thinks to mention, usually in the last few days of a notice period. What it misses is the working knowledge that never felt worth recording.
Which machines have a recurring fault and which technician has already tried the obvious fix. Which certificates are due next quarter. Which repairs were quoted, which were approved and which are still waiting on someone’s signature. Which site manager prefers a call and which only reads email. The informal arrangement with a supplier about after-hours callouts.
None of this is secret. It is simply scattered across a mailbox, a phone, a desk drawer and a spreadsheet with a name like “Fleet FINAL v3”. When the person leaves, the scattering becomes permanent.
An inbox is not a record
Email is a fine way to have a conversation. It is a poor place to keep a fleet’s history.
A service report sent as an attachment lives in one mailbox. The reply approving a repair sits in another thread. The photograph of the damaged mast is in a WhatsApp group the successor was never added to. Each piece made sense at the time, and each one depended on the same person remembering how they fitted together.
Once that mailbox is archived or handed over, the successor is left with an inbox treasure hunt, often while a machine is standing and a site is asking for answers.
A shared record works differently. The information belongs to the asset and the job, not to whoever happened to receive the email. It stays where the next person expects to find it.
What a successor needs on day one
Someone taking over a fleet does not need every conversation from the past three years. They need a reliable starting point. In practice, that usually means being able to answer a few plain questions without asking anyone:
- What equipment do we have, and where is each machine allocated?
- What service work is open, and who owns the next step?
- Which inspections and load tests are due, and where are the certificates?
- What has happened to this machine before?
- Which supplier looks after which site, and on what terms?
If those answers live in a shared record, the first week is about learning the operation. If they live in a former colleague’s head, the first week is about detective work.
Continuity matters to suppliers and sites too
A handover is not only an internal concern. Service providers feel it when their trusted contact disappears and nobody can confirm which quotations were approved. Site managers feel it when breakdowns that used to be sorted with one call now take several.
Good suppliers can help here, provided they also work from a record rather than from memory. When both sides can see the same service history and outstanding work, the change of name on one side of the relationship becomes a minor event rather than a reset.
It also protects the person who left. A clear record shows the work they did and the decisions they made, rather than leaving their successor to wonder whether anything was missed.
Where FMC supports handover continuity
FMC is built so that fleet information belongs to the operation rather than to an individual mailbox. FMC Asset Management gives every machine a clear digital identity and central record, with its documents, location, allocation and lifecycle history kept together.
FMC Service Management keeps planned services, breakdowns, inspections, load tests and follow-up work visible from the moment a job is raised until its outcome is recorded, including who owns each job and what remains outstanding. For service providers and dealers, the FMC Customer Portal gives authorised customer users access to the asset records, job progress, service history and compliance documents relevant to their fleet.
A shared record makes a handover easier to manage. It does not replace a proper handover conversation, and the people taking over remain responsible for understanding the operation and making the decisions.
A handover check worth doing before anyone resigns
The best time to test a handover is while the key person is still in the building. A simple exercise is to ask a colleague to answer these questions using only the shared records:
- Could they find the full service history of the machine that breaks down most often?
- Could they list every open job and say who owns it?
- Could they retrieve the latest inspection certificate for any machine on request?
- Could they tell which quotations are waiting for approval?
- Could they contact the right supplier for each site without asking anyone?
Wherever the answer is “only if I ask Thandi”, that is the next record worth putting in order.
A good fleet coordinator should be missed for who they are, not for what only they could find.

