How to Decide Whether Your Business Needs a Simple Key-Person Dependency List Before a Crisis Reveals It

Most small businesses run on a short list of people who each hold a disproportionate amount of know-how. One person knows how to run payroll in your specific software. Another knows the alarm code, the supplier's cell number, and the workaround for the printer that jams on cardstock. When that person is unavailable, for any reason, the business slows down or stops.

A key-person dependency list is a short document that names which tasks, accounts, or relationships currently live inside one person's head. Creating it is not complicated. Deciding whether you actually need one right now is the useful starting point.

Signs You May Need One

Consider whether any of the following situations describe your business.

Only one person can complete a recurring revenue-related task. If invoices, payroll, scheduling, or order fulfillment stalls when a specific individual is out sick, that is a documented dependency worth noting.

You have hired or are planning to hire. Once a second or third person joins your operation, institutional knowledge starts fragmenting. A list helps you see where you are relying on informal memory rather than shared process.

You or a key team member took unplanned time off recently and something was missed. If a customer call went unanswered, a bill was paid late, or a supplier order was skipped because no one else knew it was coming due, that gap is worth mapping before it repeats.

You are the only one who holds certain vendor or client relationships. If a supplier will only negotiate with you, or a long-term client calls your personal cell rather than a shared line, those relationships are dependencies too, not just tasks.

If none of these situations apply and your operation has very few moving parts, a formal list may be premature. A one-person shop where the owner does everything may not need a written list yet, though it can still be useful if that owner has any employees or contractors.

What the List Should Include

The goal is not to create an exhaustive operations manual. The goal is to surface the highest-risk concentrations of knowledge quickly so you can decide what to do about each one.

For each item, capture four things: what the task or relationship is, who currently owns it, what someone else would need to handle it in a pinch, and how urgent that task is if the owner is unavailable for 48 hours or more.

A simple spreadsheet or even a lined notebook page works fine. You do not need dedicated software for this.

Here is a hypothetical example of how three rows might look for a small landscaping company:

• Task: Weekly supplier order for mulch and seed. Owner: Maria (operations). Pinch coverage need: Supplier name, account number, standing order quantities, and delivery window. Urgency if Maria is out: High, job sites run short within four days.
• Task: Submitting payroll each Friday. Owner: Owner (you). Pinch coverage need: Login to payroll platform, approval steps, pay schedule. Urgency if out: High, employees must be paid on time.
• Task: Client relationship with Riverside HOA. Owner: Owner (you). Pinch coverage need: Contact name, preferred communication style, seasonal service schedule. Urgency if out: Medium, next scheduled contact is monthly.

Your own list may have anywhere from five to twenty items depending on your team size and complexity.

What to Do With the List Once You Have It

The list is not the solution. It is a map that shows you where solutions are needed.

For each high-urgency item, decide on one near-term action. Common options include writing a short process note so a second person can step in, cross-training a team member on a specific task, or making sure login credentials are stored somewhere accessible to a trusted backup person. The password and account handoff question is related but distinct; the dependency list tells you which accounts matter most and why.

For medium-urgency items, you can move more slowly. The goal is to work down the list over weeks or months, not to fix everything in a weekend.

For low-urgency items, simply knowing they exist is often enough. You may decide that some dependencies are acceptable risks given the effort required to address them.

Costs and Effort to Expect

Building a basic list for the first time typically takes one to three hours for a small team. Longer if your operation is complex or if you need to ask team members to contribute their sections.

Keeping it current takes occasional attention. A reasonable habit is to review the list whenever someone joins the team, whenever someone leaves, or once or twice a year during a slow period.

There is no software cost unless you choose to use a project management tool you already own. A shared cloud document that your coverage person can access is usually sufficient.

The main cost is time and the mild discomfort of acknowledging that your business may be fragile in specific ways. That discomfort is useful. Businesses that work through the list tend to find that many of the gaps are fixable with small, one-time actions.

A Reasonable Starting Point

If you are not sure where to begin, start with the single question: if I were unavailable for the next three business days with no advance notice, what would stop, and who, if anyone, could handle it?

Write the answers down. That rough list is your first draft. Refine it from there.

The dependency list is not a sign that your business is broken. It is a recognition that small businesses concentrate knowledge in people, and that people are unpredictable. Building the list before an absence forces the issue is a practical way to get ahead of a problem that almost every small operation eventually faces.

Consult a qualified business advisor if you are uncertain how to prioritize risk in your specific situation.