2026-11-01 · 6 min
Make-safe repairs that never get the permanent fix
A taped-off cable, a bucket under a leak, a door held with a wedge. How multi-site operators turn each make-safe into a permanent fix that gets booked.
The roof leak over aisle four was made safe on a busy afternoon. The plumber sealed what he could reach, put a tray under the drip and told the store manager it needed a proper look from a roofer. Everyone agreed. The job was closed as attended, the invoice was paid, and the tray is still there.
Many multi-site operations have a list like this, even if nobody has written it down. A cracked glass panel covered with board. A freezer running on a bypass. A fire door that only shuts if you lean on it. Each one was the right call on the day. The problem is what happened next, which was nothing.
Temporary repairs are not a failure. They keep people safe and sites trading while the right trade, part or approval is lined up. They only become a problem when the second half of the job has nowhere to live.
Where the second job goes missing
The permanent fix tends to disappear in one of three places:
- In the contractor's notes. "Needs replacement" sits in a comment or on a photo caption that nobody reads after the job is closed.
- In the site manager's head. They know the board on the window is temporary, but they move on, go on leave or stop raising it because nobody seemed to act last time.
- In a quote that never comes back. Someone asked for pricing on the proper repair, the quote went to an inbox, and approval stalled with no date and no owner.
In all three cases the first job looks finished. Reports show it closed inside the attend-by time. Leadership sees a fast response, while the actual risk is still sitting on site.
Write the make-safe as half of a pair
The simplest change is to stop treating a make-safe as a complete job. When a contractor makes something safe instead of fixing it, the work order should record that plainly and raise the follow-up at the same moment:
- Mark the outcome honestly. "Made safe, permanent repair needed" is a different result from "fixed", and it should be counted differently.
- Capture what the proper repair needs. The trade, the part, any access or shutdown, and a photo of the temporary measure as it was left.
- Raise the follow-up job before the first one closes. Same site, same asset, linked to the make-safe so anyone opening either one sees the full story.
A contractor who has just been on site knows more about the permanent fix than anyone else will after they leave. That knowledge belongs on a job, not in a conversation.
Put a name and a deadline on the proper repair
A follow-up job with no owner is just a nicer-looking reminder. Each permanent repair needs:
- One person responsible for getting it booked, usually in ops rather than at the site.
- A target date based on the risk, not on when the budget feels easier. A board over a broken window and a bypassed safety switch should not sit in the same queue.
- An approval path agreed in advance, so a repair above a set amount goes to a named approver with the make-safe photos attached, instead of waiting for someone to notice it.
When the proper repair needs a different trade from the one who made it safe, send it to that trade's usual contractor straight away. Waiting for the first contractor to "sort someone out" is how good intentions turn into a tray on the floor.
Review the open make-safes before something forces you to
Once make-safes are recorded as their own outcome, the list of unfinished ones becomes something you can actually look at. Keep the review short and practical:
- Sort open make-safes by risk, then by age. Anything affecting safety or trading comes first, however recent.
- Ask one question per item: what is stopping the permanent fix? The answer is often a missing quote, a missing approval or a missing booking, and each has an owner.
- Watch for repeats. If the same asset has been made safe twice, the next visit should be the proper repair, not another patch.
To test whether this matters for you, walk one site and count the temporary measures you can see: tape, boards, buckets, wedges, signs saying "out of order". Then try to find the job that will remove each one. The gap between those two counts is your real backlog.
Make-safes that end in a proper repair
OpsChase keeps the temporary fix and the real one on the record. The site logs the problem with photos, ops set the trade and priority, and the job goes to your usual contractors in the order you choose. The contractor records what they did and what is still needed, attend-by times stay visible, reminders escalate if the follow-up isn't confirmed, and nothing closes until the photos, checklist and sign-off match your template. A bucket under a leak is much harder to pass off as a finished job. Datacat's OpsChase overview covers setup across your sites.
If your follow-up repairs need approval limits, capital planning or a customer relationship management (CRM) system behind them, we build that as part of a preferred contractor and work order system, and ops workflow automation can flag make-safes that have sat open too long for a manager to act on. Related reading: repeat callouts for the same fault and approvals that don't die in email. See what we have delivered, or send us a photo of the oldest temporary fix on your sites and we will help you work out what it would take to finish it.