Your business office manager is out for three days, and the payroll run is due. The assistant opens the payroll software and discovers that only one person knows how to import the hours, fix the exceptions and approve the batch. Nobody wrote it down.
This is key-person risk. It is not a criticism of a good employee. It is what happens when a task lives in one head and one login. In a care setting, where paychecks, resident billing and vendor payments cannot wait, a single point of failure is worth fixing before it fails.
Sit down with each person in billing, accounts payable and payroll and ask them to list what they do on a daily, weekly, monthly and yearly basis. Then ask the harder question: what would break if you were out for two weeks?
Look especially for tasks that:
Happen only at month end, quarter end or year end, so nobody else has seen them done
Require a specific permission level or a second login that only one person holds
Depend on a workaround, such as exporting to Excel, fixing it by hand and importing it back
Involve a payer, a state portal or a bank where only one person knows the steps
Are done differently from how the software manual describes them
Rank the list by consequence. A late payroll or a missed claim submission matters more than a rarely used report.
Some knowledge is in the software and can be learned from its screens or its help documentation. Other knowledge is in the person: the order of steps, the quirks of your payers, the reason one resident account is set up differently. The second kind is what disappears when someone leaves.
Ask your staff to record it as they work. A screen recording on a laptop while they talk through a task is often faster and clearer than a written procedure. Pair each recording with a short checklist.
A good procedure for a billing or payroll task contains the following.
What the task is for and when it is due
Where to log in, and who holds the access (never write passwords in the document)
The steps in order, with the name of each screen or report
What a correct result looks like, so the backup knows when they are finished
Common problems and who to call, including the software support line and your IT provider
The date it was last reviewed
Store these in a protected shared location, such as a SharePoint library with limited access, rather than a personal desktop. Because the documents describe financial and sometimes resident information, keep access limited to those who need it.
Reading a procedure is not the same as running payroll. Choose a backup for each critical task and have them do it while the primary watches, preferably during a real cycle. Then switch: the backup does the work and the primary observes and corrects.
Rotate this on a schedule. If the backup only practices once, the knowledge fades. Many offices find it useful to have the backup run a full cycle on a normal month, so the first time is not an emergency.
Cross-training creates a temptation to share one login. Do not. Each person should have their own account with the permissions their role requires, so the system records who did what. That record matters for audits, for fraud prevention and for investigating mistakes. If your software lacks the ability to add a backup user, raise it with the vendor or your IT provider.
Also check segregation of duties. The person who can approve payments should not be the same person who can add a new vendor. Your accountant or auditor can tell you how to divide these appropriately for your size.
Not every departure comes with notice. Decide in advance what happens the day a key person resigns or is out unexpectedly.
Who takes over each critical task, and has that person already been trained?
Where are the procedures stored, and can the administrator open them without the departing employee?
Which accounts need to be disabled or reassigned, and who does it the same day?
Are any systems, bank portals or payer accounts registered to that person's personal email?
The last point catches many offices off guard, and fixing it ahead of time saves a scramble.
UnityCare IT helps business offices see who holds access to billing, payroll and financial systems and sets up individual accounts so a backup can step in without sharing passwords. We can help store procedures in protected shared locations and make sure access is turned off or reassigned promptly when someone leaves. If you want a quick review of which systems depend on a single person, we can walk through them with your administrator.
Security monitoring, HIPAA safeguards, backups and staff training for healthcare and small businesses.
Call or text: 405-285-3845
New customers: start@unitycareit.com
Existing customers: support@unitycareit.com
Service area: based in Edmond, Oklahoma, serving Oklahoma, Texas and Kansas
Hours: Mon–Fri 8 AM–5 PM CT; 24/7 after-hours support