Skip to main content
Tradejoy
Run Your BusinessFor Everyone

What Happens When Your Ops Person Calls in Sick

For most property maintenance companies, one person calling in sick means 25 jobs don't get closed and ten quotes don't go out. Here's why that happens and how to fix it.

Tradejoy Editorial Team··7 min read

The Single Point of Failure Most Owners Don't See Coming

Ask most property maintenance company owners what happens when their ops person calls in sick and you'll get an uncomfortable pause.

The honest answer is: everything stops.

Jobs sit completed but uninvoiced. Quotes that were almost ready never go out. Customers who were waiting for a follow-up don't hear anything. Traders call the office and nobody answers. By the end of the day, 25 jobs haven't been closed and ten quotes haven't been sent — not because the work didn't happen, but because the one person who holds it all together isn't there.

This is one of the most common and most preventable problems in the trades. And most owners only discover how serious it is the first time their key person takes a sick day.

Why Ops Knowledge Lives in One Person's Head

It usually happens gradually. When a business is small, the owner handles everything. As it grows, one capable person takes over the coordination — answering enquiries, booking jobs, chasing traders, invoicing. They're good at it. The owner stops worrying about it.

Over time, that person becomes the central nervous system of the operation. They know which customers prefer morning appointments. They know which traders are reliable for emergency callouts. They know the custom pricing for the landlord clients. They know who's been chased already this week.

None of this is written down anywhere. It's all in their head, in their inbox, and in a series of WhatsApp threads that nobody else has access to.

This is institutional knowledge trapped in a single human being. And it's fragile in a way that's easy to miss when everything is running smoothly.

What a Single Sick Day Actually Costs

Let's put numbers to it. Assume a company doing 20 jobs per day at an average value of £400:

  • Daily revenue potential: £8,000
  • Jobs completed but not invoiced that day: 25 (2 days' worth, since tomorrow's backlog starts immediately)
  • Invoices at risk: £10,000
  • Quotes not sent that day (lost conversion opportunity): 10
  • At 60% conversion and £400 average: £2,400 in potential revenue not captured

One sick day can put £12,000+ of revenue at risk — either delayed, lost, or requiring expensive catch-up time the following week.

That's before accounting for customer experience damage. Clients who were expecting a follow-up and didn't get one. Landlords chasing for certificates that weren't issued. Tenants who didn't receive their appointment confirmation. The reputational cost of these drops is harder to quantify but very real.

The Cascade Effect on the Rest of the Team

When the ops person is out, the pressure doesn't disappear — it redistributes. The owner gets pulled back into coordination, handling the calls that would normally be filtered and managed. Traders can't get answers about their jobs for the day. Customers reaching out via email or web form get silence.

The owner ends up doing triage instead of running the business. Decisions that should be automatic — which trader goes to which job, whether to accept a rescheduling request, when to follow up on an unpaid invoice — all require a human decision that day.

And because the owner is the most expensive person in the business to spend time on coordination, this is an extraordinarily expensive way to handle one sick day.

How to Break the Dependency

The fix isn't hiring two ops people (though that helps). The fix is removing the dependency on any single person for routine coordination by making the operations systematic rather than personal.

Document the processes

Start with the most common jobs: new enquiry intake, quote generation, booking confirmation, appointment reminders, job completion, invoicing, payment chasing. Write down the exact steps, templates, and decision rules for each. If your ops person left tomorrow, could someone else follow the process? If not, it needs documenting.

Move job information out of inboxes

Every job should have a single source of truth — not a combination of WhatsApp, email, and memory. A job management system where status, customer details, trader assignment, quotes, and payments all live in one place means any team member can pick up where another left off.

Automate the routine steps

Appointment reminders, job confirmation messages, payment chase sequences, and certificate issuance don't require human judgement for every instance. Automating these removes a significant chunk of the daily ops workload and means they happen whether or not anyone is in the office.

Use AI for intake and coordination

Platforms like Tradejoy handle inbound enquiries, gather job details, prepare quotes, send confirmations, update customers, and chase payments automatically. The operations don't stop because one person is out — they continue running without anyone needing to step in.

The Test Every Ops-Dependent Business Should Run

Here's a useful exercise. Imagine your most operationally critical person takes two weeks off tomorrow with no notice. Answer these questions honestly:

  • Could someone else handle inbound enquiries without calling them?
  • Could quotes go out without them?
  • Would customers get appointment confirmations?
  • Would invoices be issued on completion?
  • Would unpaid invoices be chased?
  • Would traders know their jobs for the day?

If the answer to most of these is no, the business has a structural vulnerability that will surface eventually — through illness, resignation, or simply a busy period where one person can't keep up.

The goal isn't to make people redundant. It's to make the business resilient enough that the loss of any single person creates inconvenience rather than crisis.

Frequently Asked Questions

We’re happy to answer all your questions.

How dependent is the average trade business on one ops person?

Very. Most property maintenance companies with 5–15 employees have one person handling the majority of coordination — enquiries, bookings, trader comms, invoicing. When that person is unavailable, the default is usually the owner stepping back into an operational role they'd grown out of.

What's the best first step to reducing ops dependency?

Document your most frequent process: how a new enquiry becomes a booked job. Write down every step, every template message, every decision point. Once it's written down, it can be followed by someone else, automated, or handed to a system.

Can automation really replace an ops person?

For routine, repeatable tasks — yes, largely. Appointment reminders, booking confirmations, payment chasing, customer updates — these don't require human judgement for each instance. A good platform handles them automatically, freeing your ops person for the genuinely complex situations that do need human judgement.

How do I calculate the cost of ops dependency in my business?

Start with your daily revenue and the number of jobs in flight at any time. Estimate how many of those would stall for a full day if your key ops person was out. That revenue-at-risk figure, multiplied by the realistic frequency of disruption (illness, holiday, turnover), gives you a good sense of the annual cost of the dependency.

Need an electrician?

Book an Electrician