Problem guide
The business stops when one person is out
The business stops when one person is out because that person holds two things nobody else has: the know-how in their head and the access in their login. Business software often concentrates both by design. Housecall Pro, for example, allows only one dispatch and messaging point of contact per account, and that person receives every customer reply to automated texts. Write each process down where the work happens, and give a second person working access before anyone needs it.

How it actually happens
Take a typical service company with one dispatcher who has been there eight years. This is an illustration, not a client. She knows which commercial customer needs a call before the technician arrives, which technician cannot go to which building, and which jobs can slide a day without a complaint. None of that is in the software. The software holds the appointments. She holds the rules for when to break them.
She calls in sick on a Monday in July. The service manager sits down at her screen. The appointments are there, but the exceptions are not: the rush call from a property manager who always gets priority, the part that arrived Friday for a job nobody rebooked, the technician who is out on a workers' comp claim and is still showing as available. By ten o'clock the day is being run by phone, and by afternoon two customers have been told different arrival times.
Then the access problems surface. Customer replies to the automated reminder texts are still going to her, because she is set as the single point of contact. The office manager needs to change the bank account for a payout, but only the account owner can do that, and the owner is out with no signal. Payroll is due Wednesday, and she is the only person set up to run it.
Swap the names and the same morning happens elsewhere. At a clinic it is the billing coordinator, and the denials queue sits for a week. At a law firm it is the person who enters court deadlines. At a distributor it is the one buyer who knows which vendor ships short and which customer always gets the first allocation.
In construction the same pattern sits with the controller. One person knows how the work-in-progress schedule is built, which labor gets coded to which job, and which owner wants the pay application in which format. Nimbl, a back-office service firm, sums it up in its own sales article: if the business relies on one person's memory to keep things straight, it does not have a system, it has a single point of failure.
The fix is not to make that person less important. It is to separate the two things they carry. Knowledge gets written down by the person who has it, in the place the work is done. Access gets shared on purpose, ahead of time, because in several common tools the change takes the owner's own login or a call to the vendor.
Two kinds of dependency
When you run the test above, sort every stall into one of two piles. Access stalls, where nobody else had the login or permission, are usually fixed in a week. Knowledge stalls, where nobody else knew the rule, take longer, and they are the ones that cost customers. Fix access first so the backup can at least sit in the chair, then work through the knowledge pile one exception at a time.
Signs you have this problem
- When the scheduler or dispatcher is sick, the day is rebuilt from memory and phone calls
- Customer replies and online bookings pile up in one person's inbox while they are on vacation
- Payroll cannot run because only one person has the access or knows the steps
- Questions that start with 'how do we usually' all go to the same person
- The owner cannot change a setting in the company's own software without the person who set it up
What usually causes it
- Exceptions are handled by one experienced person who knows the workarounds, and the workarounds are never written downThe exception swamp
- Work owed to the absent person keeps arriving in their queue, and nobody else can see itThe invisible queue
- Roles, logins and settings were assigned once at setup, so the handoff to a backup was never designedThe handoff gap
Find your cause
Ask these in order. The first yes is usually where yours starts.
- Does one person's absence stop customer replies, online bookings or dispatch?If yes: a single-contact setting is routing work to one inbox. Check who holds it and who can change it.
- Can only one person run payroll or change the payout bank account?If yes: the stop is access, not knowledge. Add a second person with the right permission this week.
- Do exceptions, such as warranty calls or disputed bills, always go to the same person?If yes: the rules for exceptions live in one head. Have that person write them down first.
- Is there a procedure document that nobody has opened in a year?If yes: it was written for a shared folder, not for the work. Move it to the tool the work happens in and give it an owner.
How it breaks in each industry
- HVAC and plumbing service
- The dispatcher carries the board: which technician knows which customer, which jobs can slide, who is waiting on a part. In a peak week one sick day can mean missed maintenance visits and callbacks that land on nobody's list.
- Commercial construction
- The controller or project accountant often owns the work-in-progress schedule, the labor coding to jobs and the progress billing routine. When that person is out, pay applications and cost reports wait, because nobody else knows how the numbers were assembled.
- Law firms
- One legal assistant or docketing clerk knows how deadlines get entered, which matters need a reminder before a filing, and how each client wants its bills. When that person is out, new deadlines wait in an inbox and bills go out late or in the wrong format.
- Healthcare practices and clinics
- One billing coordinator knows which payers need which modifiers, which claims are waiting on a resubmission and how to work the denials queue. When that person is out, claims and denials sit untouched, and the cash stops with them.
Where it breaks between systems
- Housecall Pro (dispatch and messaging point of contact)
- Only one employee can be the dispatch and messaging point of contact. That person receives all customer replies to automated texts in the mobile app chat and is automatically assigned every job booked online. While they are out, those replies and bookings keep landing on them until someone with access changes the setting.[1]
- Housecall Pro (Payroll Admin)
- Who can see payroll settings and run payroll is controlled by a Payroll Admin permission. Housecall Pro's help says changes to that access are made by contacting its support team, not from account settings, so a second payroll person is a request to plan ahead.[2]
- Jobber (account owner)
- An account has one owner, who must be an admin, and no other user can edit the owner's information or settings. Jobber's help describes the ownership transfer as starting from the current owner's login and finishing when the new owner accepts by email.[3]
- Jobber Payments
- Admins and account owners can open the payments settings, but Jobber's help says only the account owner can update the payout bank account details.[4]
- QuickBooks Online (primary admin)
- Whoever first set up the company is the primary admin. Intuit's help says only that person can change the business details in Company info, and a company admin cannot change or reassign the primary admin role.[5]
- FieldEdge and QuickBooks Desktop
- The connector integrates with whoever is logged into QuickBooks on the one computer where it is installed, and FieldEdge entries post under that user. A password change for that user or the admin can mean the connection certificate has to be redone.[6]
By the numbers
No industry association or government survey publishes a figure for this. The measurement below gives you your own.
Measure it in your own shop
From: Your user lists and permission settings in each system, plus the jobs, invoices and payroll runs from a recent day or week when a key person was out.
- From each system, export the user list with roles, and mark every permission held by exactly one person.
- Pick a recent stretch when a key person was out. List the jobs, invoices, bookings and payroll steps that were due in that stretch.
- Mark each one as done on time, done late, or not done until the person returned.
- For each late or missed item, note whether the cause was missing knowledge or missing access.
Reading it: This is our own test, not an industry benchmark. The share of late or missed items is your exposure, and the split between knowledge and access tells you which fix comes first. Access problems are usually faster to solve.
What does not fix it
- A big operations manual in a shared folder
- A business succession checklist from The Owner's Shortlist warns against exactly this: a large manual that sits untouched. Procedures belong where employees already work, each with an owner and a review routine.
- Buying new software
- Nimbl, a firm that sells outsourced construction back-office services, puts it plainly in its own sales article: software does not replace process. New software also comes with its own owner, admin and payroll roles to assign.
- Telling the key person to cross-train someone
- Without written steps and real access, the backup learns by watching and forgets by the next absence. The test is whether the backup can do the work with the key person unreachable.
What to try this week
- List the single-owner settingsFor each system you run, write down who is the account owner, who is the primary admin, who receives customer replies, who can run payroll, and who can change the payout bank account. Any line with one name on it is a stop point. A disaster recovery guide from 911 IT, a managed IT provider, suggests the same inventory for every business function: the application, who uses it and who administers it.
- Give a backup real access nowSome changes take a support request or the current owner's own login. Make them on a normal week, not during an absence. A backup who has to call the vendor first is not a backup.
- Have the doer write the procedureAsk the scheduler, bookkeeper or office manager to write their own steps, with the trigger, the role, the information needed, the decisions, the software used, how to escalate and what done looks like. Store it in the tool they already work in.
- Run one planned day outPick a day when the key person is reachable but does not answer questions. Have the backup run the work from the written steps, and note every place they get stuck.
- Give every procedure an owner and a review datePricing, software and staff change. A procedure with no owner is out of date within a season.
Where do-it-yourself stops
These steps reduce the risk, but the knowledge still lives in documents beside the work instead of in the work itself. The lasting fix is a tool shaped around your existing systems, so the next step, the exception rules and the queue are visible to whoever sits in the chair. That is what a Workflow Spec designs.
Questions people ask
How do I keep dispatch running when my dispatcher is out?
Start with access: in tools that route customer replies or bookings to one point of contact, make sure a second person can change that setting. Then have the dispatcher write down how they handle the exceptions, such as rush calls and techs who run late, and test it on a planned day.
Who should be the account owner of our field service software?
Usually an owner of the business, with a second admin who can do the daily work. In Jobber only an admin can be the account owner, and the transfer starts from the current owner's own login, so it is not something to sort out in an emergency.
Can someone else take over QuickBooks Online if the person who set it up leaves?
The person who set up the account is the primary admin, and a company admin cannot reassign that role. Plan the change while the original admin is still available rather than relying on recovering it later.
What should a written procedure include?
One useful checklist lists the trigger, the responsible role, the information needed, the decision points, the software used, the escalation path and what completion looks like. The person who does the job writes the first draft, because their version is usually more accurate than the owner's recollection.
Is there a law that requires a backup for key roles?
No. No regulation turns on one person being absent. The obligations that matter, such as payroll deadlines, OSHA reporting or certified payroll on federal work, apply to the business whoever is out, which is the reason to plan for it.
Next step
How we fix this
This guide is how to find it and work around it. If it keeps coming back, it is rarely the only thing costing you. We come on site, find the issues costing you the most, and fix them, starting with the most pressing.
Fox & Santiago, Genesee, Idaho. We work nationwide, for clients across the United States, from our headquarters in Genesee, Idaho.
