2026-11-04 · 6 min
When a site manager leaves, open jobs shouldn’t leave too
A site manager moves on and the open repairs, contractor contacts and access notes go too. How multi-site operators keep that knowledge with the site.
The new manager at the northern site had been in the job for nine days when the electrician arrived to finish a switchboard repair. Nobody on shift knew it had been booked. Nobody knew the quote had been approved, where the spare keys to the plant room lived, or that the same contractor had been out twice already. The previous manager knew all of it. She had been promoted to another region and her phone number had changed.
That visit cost a callout fee and a morning. The bigger cost was everything else she knew that nobody had thought to ask about: the roller door that only the second locksmith could fix, the cool room that ran warm on busy days, the landlord’s contractor who had to be told before anyone touched the roof.
Staff turnover at site level is normal. What makes it expensive is how much of a site’s maintenance history lives in one person’s memory, inbox and phone.
What walks out the door with a site manager
When a manager leaves, moves sites or goes on extended leave, the same things tend to disappear:
- Open jobs only they were tracking. The repair waiting on a quote, the make-safe that still needs a proper fix, the warranty claim with the supplier.
- Who to call for what. The plumber who answers on a weekend, the refrigeration tech who knows the old units, the landlord contact for anything structural.
- How to get in. Key safes, alarm codes held by ops, dock times, which door contractors should use and who signs them in.
- The site’s quirks. Equipment that fails in a pattern, areas that flood, assets that are under warranty and should not be touched by just anyone.
- The promises. “The painter is coming back to finish the bathroom.” “Head office approved the new hand dryers.” Agreed, but never written down where the next person would look.
None of this shows up in a handover email written in the last week, because the person leaving doesn’t know what they know until someone needs it.
Keep the site’s knowledge on the site, not the person
The fix is not a better exit interview. It is making sure the facts belong to the site record from day one, so a change of manager changes who reads them, not whether they exist.
- Every open job sits in one shared list for the site. Not in a personal inbox, a notebook or a text thread. If a job is open, anyone responsible for the site can see it, its status and what it is waiting on.
- Regular contractors are named per site and per trade. The plumber, electrician and refrigeration tech for each site are written against that site, with contact details ops can see, so nobody has to inherit a phone contact list.
- Access notes live with the site. Where contractors enter, who signs them in and any restrictions, kept current by ops rather than remembered by one person.
- Assets carry their own history. Each major piece of equipment has its past jobs, warranty status and service schedule attached, as we set out in planned maintenance that actually gets done.
A site set up this way is far less dependent on any single manager, which also makes leave, sick days and weekend cover less risky.
A handover that takes an hour instead of weeks
Even with good records, a changeover deserves a short, structured handover. When the records are in place, it takes an hour:
- Walk the open jobs list together. For each one: what is it waiting on, who owns the next step, and is the target date still right.
- Walk the site, not just the screen. Point out every temporary measure, every asset with a known pattern and every area contractors cannot access without help.
- Confirm the contractor names against the site record. If the departing manager calls a different plumber from the one written down, find out why, and fix the record.
- Move ownership on paper, not just in conversation. Every job the old manager was responsible for gets the new manager’s name, on the day of the change.
If the hour turns into a day of “oh, and there’s also…”, that is a sign the site record has been running on memory.
Give the new manager a clean start
A new manager will not learn a site’s maintenance story from a list on day one. A few habits help it stick:
- Show them what is already booked. Every contractor visit due in the next two weeks, with the scope, so nobody is surprised at the loading dock.
- Close or re-date anything stale. Jobs that have been open for a long time with no movement are either still needed, and get a fresh date and owner, or are no longer needed, and get closed with a reason.
- Give ops a quick check-in point. A short call with the regional or facilities lead after their first few repairs catches the gaps that only show up once real work starts.
Handoffs that don’t restart the job covers the same problem between office and field. The site-manager version is slower and quieter, which is why it is easy to miss.
Test one site before the next change happens
Pick one site and imagine its manager resigned this morning. Then, without calling them, try to answer:
- What repair and maintenance jobs are open, and what is each one waiting on?
- Which contractor would you call for an electrical fault there, and how would they get in?
- Which assets have failed more than once, and are any under warranty?
- What has been promised to the site that has not happened yet?
Every question you can’t answer from a shared record is something that would leave with that person. Across a portfolio of sites, those gaps add up to second visits, duplicate quotes and repairs that quietly stall.
Sites that keep their history when people move
OpsChase holds a site’s maintenance history in one place that outlasts any one manager. Every site’s open jobs and their status sit in a single view, regular contractors are named per site and per trade, and each job keeps its photos, notes and sign-off on the record. With Assets & planned maintenance, equipment history and service schedules sit on the same site record, so a new manager can see what has failed before and what is due next without having to ask the person who left. Dashboards and reports show open work by site, which makes a manager changeover something ops can check rather than hope about. Datacat’s OpsChase overview explains how it is set up across a portfolio.
When the bigger problem is that site knowledge is scattered across several systems, we can bring it into OpsChase as part of an OpsChase implementation for your sites, and ops workflow automation can draft a handover summary of a site’s open jobs for a person to check and send. Related reading: multi-site maintenance without forty inboxes. See what we have delivered, or tell us about the last site that changed hands and we will help you work out which of its history should have stayed behind.