Bus Factor for Solopreneurs

A one-person business naturally concentrates knowledge, authority, relationships, and decision-making in its founder.

This concentration can make the business fast and efficient. It can also mean that illness, injury, a family emergency, burnout, or permanent incapacity leaves nobody able to explain what is happening, contact customers, meet deadlines, access essential records, or decide what should happen next.

The bus factor provides a simple way to examine that dependence.

What Is the Bus Factor?

The bus factor is the smallest number of people whose sudden absence would leave a project, process, or organization unable to continue effectively.

A bus factor of one means that the loss of one specific person could stop the work. A bus factor of two means that at least two critical people would need to become unavailable before the same outcome occurred.

The concept is also called:

• Truck factor
• Lottery factor
• Key-person dependency
• Contributor absence factor
• Knowledge concentration risk
• Human continuity risk

The metaphor imagines critical contributors being hit by a bus, but the cause of absence is not important. The same problem can result from resignation, illness, retirement, a family emergency, loss of capacity, or an extended period without communication.

In June 2024, the CHAOSS project renamed its Bus Factor metric “Contributor Absence Factor” because the original expression was unnecessarily morbid. Its current metric identifies the smallest number of contributors responsible for 50% of a project’s contributions.

That definition works for contributor communities, but a solopreneur needs a broader operational test. Contribution volume does not reveal who holds legal authority, customer trust, undocumented knowledge, or the ability to make a critical decision.

What Is the Bus Factor of a Solopreneur?

The literal bus factor of an owner-dependent solo business is normally one.

If the owner becomes unavailable, no second internal person remains to operate the business. That does not automatically mean every solopreneur business is dangerously fragile.

The actual impact depends on whether the business can:

• Continue automatically for a defined period
• Complete existing customer commitments
• Pause new sales safely
• Communicate the owner’s unavailability
• Meet urgent financial and legal deadlines
• Preserve access to business-owned assets
• Transfer defined tasks to authorized contractors
• Refund or reschedule customers
• Enter an orderly succession or closure process

A consulting practice built entirely around the owner may need to pause delivery. A digital-product business may continue accepting and fulfilling orders automatically. Both businesses have one owner, but they have different continuity characteristics.

The useful question is therefore not only:

“What is the numerical bus factor?”

It is:

“What damage would the owner’s absence cause after one day, one week, one month, and permanently?”

Bus Factor Is Not a General Risk Score

Bus factor measures dependence on people. It does not measure every form of operational risk.

A business can have:

• A low bus factor but reliable technology
• A high bus factor but fragile infrastructure
• Several trained people but only one authorized account owner
• Complete documentation but nobody permitted to act
• Automated delivery but no person able to handle exceptions
• Multiple contractors who all depend on instructions from the founder

The bus factor also does not estimate the probability that someone will become unavailable. It measures the concentration of essential capability and the consequences of losing it.

A low score identifies exposure. It does not determine whether the exposure is unacceptable.

Bus Factor Versus a Single Point of Failure

A single point of failure can be a person, account, supplier, device, application, integration, or physical location.

Bus factor concerns the human part of that problem:

• Who knows how the business works?
• Who has the required skill?
• Who controls the relationships?
• Who can authorize action?
• Who can access essential resources?
• Who can make decisions when circumstances differ from the documented process?

The owner may be one single point of failure among several, but the bus-factor analysis should remain focused on human absence and knowledge concentration.

What Research Shows About Knowledge Concentration

Bus-factor research has primarily examined software projects because version-control histories make individual contributions measurable.

A 2016 GitHub study estimated the truck factor of 133 popular open-source projects covering more than 373,000 files, 41 million lines of code, and two million commits. It found that 65% of the examined projects had a truck factor of two or less.

Developers from 67 projects were asked to evaluate the estimates. In 84% of valid responses, developers agreed or partially agreed that the identified contributors were the main authors, while 53% agreed or partially agreed with the estimated truck-factor value.

The study also emphasized that there was no universally accepted calculation method. Its results should not be treated as a benchmark for solopreneur businesses because:

• The sample contained popular software projects.
• File authorship is easier to measure than commercial knowledge.
• Commit volume does not capture authority or customer relationships.
• An open-source project can recruit contributors differently from a business.
• Operational incapacity is difficult to define without a time horizon.

The study nevertheless demonstrates that substantial projects can depend on a surprisingly small number of knowledgeable contributors.

Why Headcount Alone Is Misleading

Adding a contractor or employee does not automatically increase the effective bus factor.

Suppose a business has one owner and three contractors, but:

• The owner approves every decision.
• Only the owner understands the pricing model.
• Contractors receive tasks without commercial context.
• Business accounts are controlled through the owner’s identity.
• Customer relationships belong exclusively to the owner.
• Contractors cannot pause sales, issue refunds, or contact customers.
• Nobody knows where current commitments are recorded.

The business still has an effective bus factor of one for many critical outcomes.

Conversely, a solopreneur may remain the only permanent worker while using authorized professionals, documented procedures, automated fulfilment, and predefined customer policies to reduce the consequences of temporary absence.

The number of people involved matters less than the number who can independently protect a specific outcome.

The Six Forms of Owner Dependency

Knowledge Dependency

The owner knows information that exists nowhere else.

Examples include:

• Current customer commitments
• Product-delivery logic
• Supplier arrangements
• Pricing exceptions
• Renewal dates
• Financial obligations
• Reasons behind unusual processes
• Location of original assets
• How revenue reports are reconciled
• Which activities may be paused safely

Information becomes a bus-factor problem when another capable person cannot discover it in time.

Skill Dependency

The owner may be the only person able to perform specialized work.

Examples include:

• Consulting
• Design
• Software development
• Writing
• Analysis
• Negotiation
• Campaign management
• Product configuration
• Financial interpretation
• Quality approval

Not every specialized skill needs a substitute. Some work can be postponed. The priority is identifying skills whose absence would cause contractual, financial, legal, or customer harm before the owner returns.

Relationship Dependency

Important relationships may exist primarily between individuals rather than organizations.

These can include:

• Major clients
• Referral partners
• Suppliers
• Professional advisers
• Contractors
• Affiliate managers
• Distribution partners
• Landlords
• Lenders
• Strategic collaborators

A contact list preserves names but not necessarily trust, history, expectations, or unwritten commitments.

The relationship record should explain the business context without documenting unnecessary private information.

Access Dependency

Another person may understand the required task but be unable to reach the relevant records or systems.

A continuity plan should identify which business-owned resources require legitimate emergency access. It should not rely on secretly sharing the owner’s personal passwords.

Authority Dependency

Access and authority are not the same.

A person may be able to view an account without being authorized to:

• Approve a payment
• Sign a contract
• Issue a refund
• Submit a filing
• Transfer an asset
• Instruct a professional adviser
• Close an account
• Communicate on behalf of the business
• Make a binding customer commitment

Authority must be established through appropriate platform roles, contracts, mandates, corporate arrangements, or legal documents.

Judgment Dependency

Procedures work well for predictable situations. They work poorly when the substitute must decide among several imperfect options.

Judgment dependencies include:

• Which client should be prioritized
• Whether sales should be paused
• When to refund rather than reschedule
• What level of expense is acceptable
• Which public statement is appropriate
• Whether a contract should be terminated
• When an incident requires legal advice
• Whether the business should continue, sell, or close

Decision rules, limits, and escalation criteria are more useful here than rigid step-by-step instructions.

Define the Required Continuity Period

Bus factor is meaningless without a time horizon.

A business that can operate without the owner for three days may still fail during a three-month absence. Different controls are required for each period.

The target does not need to be uninterrupted operation.

For many solopreneurs, the appropriate objective is:

“Existing customers and essential obligations can be protected for 30 days while new commitments are paused.”

That is more realistic than attempting to make a personal business operate indefinitely without its founder.

Decide What Must Continue, Pause, Transfer, or Stop

Classify every important activity into one of four states.

Continue

The activity must continue during the owner’s absence.

Examples:

• Automated product delivery
• Essential hosting payments
• Contractually required support
• Subscription fulfilment
• Regulatory or tax deadlines
• Security incident response

Pause

The activity can stop temporarily without unacceptable harm.

Examples:

• New consulting bookings
• Content publication
• Product development
• Non-essential advertising
• Experiments
• Optional meetings

A predefined pause is a valid continuity control.

Transfer

A qualified and authorized person can take responsibility.

Examples:

• Routine bookkeeping
• Customer notifications
• Approved refunds
• Contractor coordination
• Website maintenance
• Deadline monitoring

Stop Permanently

An activity should be discontinued if the owner cannot return.

Examples may include:

• Personal advisory services
• Offers dependent on the owner’s identity
• Unprofitable experiments
• Licences that cannot be transferred
• Commitments that cannot be completed safely

Making these decisions in advance prevents an emergency contact from guessing what the owner would have wanted.

Measure Practical Continuity Instead of Chasing a Higher Number

A solopreneur cannot meaningfully raise the classic bus factor above one without involving another capable person. Documentation and automation reduce the consequences of absence, but they do not create a second human operator by themselves.

Three internal measures are more useful.

Owner-Free Operating Window

The owner-free operating window is the longest period the business can protect its critical outcomes without new decisions or work from the owner.

For example:

• Website orders: 30 days
• Consulting delivery: 2 days
• Customer support: 5 days
• Subscription billing: 60 days
• Tax compliance: Until the next filing deadline

Use the shortest critical window as the business constraint.

Continuity Coverage

A business can calculate:

Continuity coverage = critical obligations that can continue or pause safely ÷ total critical obligations × 100

This is an internal diagnostic rather than a recognized accounting or risk standard.

Count an obligation as covered only when:

• Its required information is current.
• A responsible person or automated process is identified.
• The necessary authority exists.
• The procedure has been tested.
• The outcome can be verified.

Transfer Readiness

Classify each critical activity:

• Owner-only: No usable transfer method exists.
• Recorded: Instructions or context exist.
• Accessible: Required information and systems are available.
• Authorized: Another person is permitted to act.
• Executable: The person can complete the activity independently.
• Tested: Independent execution has been demonstrated.

A folder of procedures may improve an activity from owner-only to recorded. It does not make it executable or tested.

Identify What Only the Owner Can Do

Create an owner-only work inventory.

For two to four weeks, record every activity that meets at least one of these conditions:

• Only the owner knows it must happen.
• Only the owner knows how to do it.
• Only the owner can access the required resource.
• Only the owner is authorized to act.
• Only the owner has the necessary relationship.
• Only the owner can interpret the result.
• Only the owner can approve an exception.
• Work would wait if the owner did nothing.

Do not record every minor task. Focus on activities connected to:

• Customer obligations
• Revenue collection
• Financial deadlines
• Legal compliance
• Asset ownership
• Essential suppliers
• Security incidents
• Reputation-sensitive communication
• Business continuation or closure

The resulting list shows where the owner is operationally irreplaceable.

Map Outcomes, Not Job Titles

A job description is too broad for bus-factor analysis.

Map specific outcomes instead:

This method prevents general documentation work from hiding specific uncovered outcomes.

Build a Minimum Viable Owner-Absence Pack

A small business does not need a large continuity manual. Official continuity guidance notes that a small organization may need only a short practical plan covering critical activities, priorities, contacts, workarounds, and recovery steps.

A minimum owner-absence pack should contain the following.

One-Page Business Summary

Include:

• What the business sells
• How customers buy
• How fulfilment works
• Main sources of revenue
• Current critical services
• Activities that may be paused
• Primary professional advisers
• Legal business identity
• Location of authoritative records

Active Commitments Register

Record:

• Customer or partner
• Commitment
• Deadline
• Current status
• Amount paid or owed
• Required next action
• Relevant contract
• Appropriate absence response

This register should be updated as part of normal work, not reconstructed during an emergency.

Critical Calendar

Include:

• Tax deadlines
• Domain and licence renewals
• Insurance renewals
• Loan or lease obligations
• Contractor payments
• Customer delivery dates
• Subscription commitments
• Filing dates
• Scheduled launches
• Time-sensitive cancellations

Responsibility Map

For each protected outcome, record:

• Who may act
• What they may do
• What they may not do
• When their authority begins
• When they must escalate
• Where the necessary information is located
• How completion is verified

Contact Directory

Include relevant:

• Customers
• Contractors
• Accountant
• Lawyer
• Insurer
• Bank contact
• Technology support
• Suppliers
• Property contact
• Emergency representative

Keep sensitive personal details proportionate and protected.

Asset and Ownership Map

Identify where authoritative ownership information is held for:

• Domains
• Websites
• Intellectual property
• Source files
• Customer contracts
• Business accounts
• Software licences
• Brand assets
• Financial records
• Physical inventory
• Insurance policies

The map should identify locations and responsible parties without placing unrestricted credentials in an ordinary document.

Approved Communications

Prepare short messages for:

• Temporary owner unavailability
• Delayed delivery
• Rescheduling
• Paused sales
• Contractor handover
• Refund processing
• Extended absence
• Business closure or succession

Templates should specify who may send them and when.

Decision Limits

Define:

• Maximum routine refund
• Maximum emergency expense
• Customers to prioritize
• Activities to suspend first
• Commitments that must not be accepted
• Situations requiring legal advice
• Conditions for pausing sales
• Conditions for closing a service
• Decisions reserved for a legally authorized representative

Write Transferable Runbooks

A useful runbook enables a capable person to complete an outcome without a live explanation from the owner.

Each runbook should contain:

Purpose

What outcome does the procedure protect?

Trigger

What event causes the procedure to begin?

Time Limit

How quickly must action occur?

Required Inputs

Which records, files, approvals, or current data are needed?

Authorized Role

Who is permitted to complete the procedure?

Steps

What actions should be performed, in order?

Decision Points

What conditions change the normal response?

Limits

What must the person not do?

Verification

How can the person confirm that the intended result occurred?

Escalation

When should a professional adviser, supplier, or other authorized person be contacted?

Return to Normal

How should temporary work be reconciled when the owner returns?

Maintenance

Who updates the procedure, and when was it last tested?

Screenshots can help, but they become outdated quickly. Record the purpose and expected result of each step so that the procedure remains understandable after an interface changes.

Document State, Not Just Process

A procedure may explain how work is normally performed while failing to show what is happening now.

A substitute needs current state:

• Which orders are incomplete
• Which customers are waiting
• Which invoices are disputed
• Which contractors have open work
• Which renewals are approaching
• Which campaigns are active
• Which exceptions have been promised
• Which incidents are unresolved
• Which records are authoritative
• Which decisions have already been made

Use a visible system for active commitments rather than scattering status across private notes, inboxes, and memory.

Current state is often more valuable during an absence than a detailed description of the ideal process.

Preserve Decision Context

Solopreneur businesses contain many decisions that appear arbitrary without their history.

Record decisions that affect future action:

• Why a customer received unusual terms
• Why a supplier was rejected
• Why a product was paused
• Why a price differs from the public rate
• Why an automation has a manual exception
• Why a particular jurisdiction is excluded
• Why a contractor has limited access
• Why a refund policy was applied differently

A concise decision record should contain:

• Decision
• Date
• Reason
• Evidence or constraint
• Affected people or systems
• Conditions that would justify reconsideration

This prevents another person from accidentally reversing a protective decision.

Use an Emergency Steward

An emergency steward is a trusted, appropriately authorized person who can coordinate the initial response when the owner is unavailable.

The steward does not need to run the whole business or reproduce the owner’s specialist work.

Possible responsibilities include:

• Confirming that the absence procedure has been activated
• Locating the current commitments register
• Informing affected customers
• Contacting professional advisers
• Pausing new commitments
• Coordinating approved contractors
• Monitoring urgent deadlines
• Recording actions taken
• Escalating prolonged absence

The steward may be a business partner, family member, contractor, employee, lawyer, accountant, executor, or other suitable person, depending on the business and jurisdiction.

The role should be established legitimately. Personal trust does not automatically provide legal authority, platform access, or permission to process customer information.

Reduce Bus-Factor Exposure Without Hiring Employees

Hiring is not the only way to improve human continuity.

A solopreneur can:

• Remove unnecessary owner approvals.
• Keep active commitments in one current register.
• Use business-owned rather than contractor-owned accounts.
• Give professional advisers appropriate records in advance.
• Define work that can pause automatically.
• Productize repeatable parts of delivery.
• Use written customer policies for common exceptions.
• Assign role-based access to qualified contractors.
• Maintain source files in controlled business storage.
• Record supplier specifications and commercial terms.
• Create a visible financial and renewal calendar.
• Separate personal assets from business assets.
• Arrange lawful emergency authority.
• Test a limited handover periodically.
• Reduce the number of simultaneous custom commitments.

The goal is controlled transferability, not maximum delegation.

Manage Contractor Bus Factor

Contractors can reduce owner dependency while creating a new human dependency.

A contractor may become a hidden bus-factor problem when:

• Only the contractor understands a custom implementation.
• The contractor owns the working files or account.
• No current documentation exists.
• Another professional cannot take over the work.
• Important decisions remain in private messages.
• The owner cannot verify the contractor’s output.
• The contract contains no handover requirement.
• Access cannot be removed without disrupting the service.

For critical contractor work, confirm:

• The business owns the account and source assets.
• Deliverables are stored in a controlled location.
• Configuration and dependencies are recorded.
• Another qualified person could inspect the work.
• Handover obligations are contractual.
• Open work and known defects are visible.
• Access can be transferred or revoked safely.
• The owner can determine whether the service is functioning.

Replacing one owner-only dependency with one contractor-only dependency does not improve continuity.

Design for Safe Pausing

Some solo businesses cannot deliver their core value without the founder.

A therapist, consultant, artist, coach, writer, or specialist adviser may not have an appropriate substitute. Attempting to make the personal service transferable could damage quality or customer trust.

The correct control may be safe pausing.

A safe-pause procedure can define:

1. How new bookings are disabled.
2. How customers are informed.
3. How active work is assessed.
4. Which work may be rescheduled.
5. Which payments should be refunded.
6. Which recurring expenses continue.
7. Who handles urgent requests.
8. How confidential records remain protected.
9. When the service may reopen.
10. What happens after prolonged absence.

A business that can pause without harming customers is more resilient than one that continues badly.

Connect Bus Factor With Succession Planning

Temporary continuity and permanent succession are related but different.

Temporary continuity asks:

“How will the business protect its obligations until the owner returns?”

Succession planning asks:

“What happens if the owner cannot return?”

Official succession guidance treats continuity, data recovery, and succession as separate but connected planning pillars.

Permanent-absence planning may need to address:

• Legal authority
• Business ownership
• Intellectual-property rights
• Contract transferability
• Customer communication
• Outstanding liabilities
• Access to financial records
• Sale or transfer of assets
• Continuation of licences
• Contractor termination
• Refund obligations
• Data-retention duties
• Orderly closure

The correct arrangements depend on legal structure and jurisdiction. Wills, powers of attorney, company mandates, insurance, and executor responsibilities require qualified legal and financial advice.

An operations document cannot create authority that the law or a contract does not recognize.

Test Whether Knowledge Is Truly Transferable

Documentation should be tested through execution.

Cold-Read Test

Give an authorized person a runbook they have not previously discussed with the owner. Ask them to explain:

• What outcome it protects
• When it should be activated
• What information is required
• What they are permitted to do
• How success is verified
• When they must escalate

Questions reveal missing context.

Owner-Unavailable Tabletop

Assume the owner became unreachable this morning.

Work through:

• Which commitments are due first?
• Who recognizes the problem?
• Who contacts customers?
• Who can pause sales?
• Which deadlines occur this week?
• Which decisions can wait?
• Which person has authority?
• What information cannot be found?
• What would happen after seven days?
• What would happen after 30 days?

Limited Handover Test

Choose a non-destructive activity, such as:

• Producing a routine report
• Sending an approved status message
• Finding an active contract
• Checking a renewal date
• Updating a current commitments register
• Processing a test exception
• Coordinating a contractor
• Confirming completion of an automated workflow

The substitute should complete the outcome without the owner taking over.

Extended-Absence Exercise

For a higher-risk business, simulate a one-week absence by routing defined questions and tasks through the documented process.

Google’s SRE experience shows that documentation alone may not remove concentrated knowledge; recurring opportunities for other people to apply and share that knowledge are what gradually improve the bus factor.

Define a Successful Handover Test

A test passes only when:

• The correct person recognizes the trigger.
• Instructions can be found without the owner.
• Current information is available.
• Access is legitimate and functional.
• The person understands their authority limits.
• The task is completed within the required time.
• The intended business result is verified.
• Customer information remains protected.
• Actions are recorded.
• Temporary changes can be reconciled.
• No undocumented owner decision is required.

Classify the result as:

• Pass
• Partial pass
• Fail
• Not tested

A partial pass should produce a specific corrective action and review date.

Create a Bus-Factor Register

Use one entry for every material owner-only dependency.

Activity

• Critical activity:
• Protected outcome:
• Normal frequency:
• Maximum safe delay:
• Current owner:

Dependency

• Owner-only knowledge:
• Owner-only skill:
• Owner-only relationship:
• Owner-only access:
• Owner-only authority:
• Owner-only judgment:

Continuity Response

• Continue, pause, transfer, or stop:
• Responsible substitute:
• Required information:
• Required authority:
• Procedure location:
• Escalation contact:
• Customer response:

Validation

• Last reviewed:
• Last tested:
• Test result:
• Missing capability:
• Corrective action:
• Next test date:

The register should remain small enough to review. Do not fill it with tasks whose interruption would create only minor inconvenience.

A 60-Minute Bus-Factor Audit

First 15 Minutes: Identify Owner-Only Outcomes

1. List the five most important customer, revenue, financial, or legal outcomes.
2. Identify which outcomes stop when the owner stops working.
3. Record the maximum safe delay for each.
4. Separate activities that must continue from those that can pause.
5. Mark every outcome requiring owner judgment.

Next 15 Minutes: Locate Hidden Knowledge

1. Review current customer commitments.
2. Review the next 30 days of deadlines.
3. Identify information held only in memory.
4. Identify decisions explained only in private messages.
5. Record relationships that another person could not interpret.

Next 15 Minutes: Check Capability and Authority

1. Identify who could coordinate an absence response.
2. Confirm what that person is allowed to do.
3. Check whether current records are accessible.
4. Identify actions that require formal legal or platform authority.
5. Mark every procedure that still depends on the owner’s explanation.

Final 15 Minutes: Improve One Critical Outcome

1. Choose the activity with the shortest safe delay.
2. Decide whether it should continue, pause, transfer, or stop.
3. Write or update the minimum procedure.
4. Assign a legitimate responsible person.
5. Schedule a cold-read or limited handover test.

Bus Factor Checklist

1. Define what bus factor means for the business.
2. Choose explicit absence periods.
3. Identify critical customer obligations.
4. Identify urgent financial obligations.
5. Identify legal and regulatory deadlines.
6. List activities that stop without the owner.
7. Separate essential activities from optional work.
8. Decide what must continue.
9. Decide what may pause.
10. Decide what can transfer.
11. Decide what should stop after permanent absence.
12. Record owner-only knowledge.
13. Record owner-only skills.
14. Record owner-only relationships.
15. Record owner-only access.
16. Record owner-only authority.
17. Record owner-only judgment.
18. Create a current commitments register.
19. Maintain a critical calendar.
20. Record authoritative sources of information.
21. Document important decision context.
22. Identify the location of business-owned assets.
23. Confirm that foundational accounts belong to the business.
24. Define an emergency steward where appropriate.
25. Establish authority legitimately.
26. Avoid informal password sharing.
27. Give substitutes only the access they require.
28. Prepare approved customer messages.
29. Define refund and rescheduling limits.
30. Define conditions for pausing sales.
31. Define escalation conditions.
32. Create outcome-based runbooks.
33. Include verification in every runbook.
34. Include return-to-normal procedures.
35. Keep active state visible.
36. Record contractor dependencies.
37. Require contractor handover where appropriate.
38. Preserve source files and configuration.
39. Ensure another professional can inspect critical work.
40. Test instructions through cold reading.
41. Run an owner-unavailable tabletop.
42. Test one limited handover.
43. Record actual completion time.
44. Correct unclear authority.
45. Correct missing context.
46. Review procedures after business changes.
47. Review upcoming deadlines regularly.
48. Connect temporary continuity with permanent succession.
49. Obtain professional advice for legal authority.
50. Treat untested transferability as unverified.

Common Bus-Factor Mistakes

• Assuming that documentation changes a bus factor of one into two
• Measuring headcount instead of independent capability
• Documenting every task instead of critical outcomes
• Creating procedures that require the owner’s explanation
• Recording process without recording current state
• Giving someone access without authority
• Giving someone authority without enough information
• Storing passwords inside an ordinary continuity document
• Relying on personal accounts for business ownership
• Expecting a family member to understand the business automatically
• Assuming an accountant or lawyer can act without prior arrangements
• Treating a contractor as a substitute without testing handover
• Allowing a contractor to own essential accounts or files
• Failing to document customer exceptions
• Omitting active commitments and deadlines
• Trying to continue personal services that should pause
• Failing to define who can stop new sales
• Automating normal work without planning for exceptions
• Creating instructions that become outdated after every interface change
• Confusing data availability with operational capability
• Ignoring the owner’s decision authority
• Preparing only for permanent death rather than temporary absence
• Preparing only for short illness rather than prolonged incapacity
• Testing access without testing the full outcome
• Assuming the owner will be available by telephone
• Failing to record actions taken during the absence
• Attempting to eliminate all owner dependence regardless of cost
• Hiring people without transferring knowledge or authority
• Treating the numerical score as the objective
• Failing to decide what should pause safely

Frequently Asked Questions

What does bus factor mean?

Bus factor is the smallest number of people whose sudden absence would leave a project, process, or organization unable to continue effectively.

Why is it called the bus factor?

The term imagines critical contributors being hit by a bus. The cause is not important; illness, resignation, incapacity, retirement, or another extended absence creates the same dependency problem.

Is there a less morbid term than bus factor?

Yes. Alternatives include contributor absence factor, key-person dependency, knowledge concentration risk, human continuity risk, and lottery factor.

What is the bus factor of a solopreneur?

It is normally one when the business depends on the owner’s continuing work or decisions. The practical level of risk depends on how long operations can continue or pause safely without the owner.

Is a bus factor of one always bad?

No. It may be acceptable for non-critical, personal, easily paused, or inexpensive-to-recover activities. It becomes material when one person’s absence could cause unacceptable customer, financial, legal, or operational harm.

Can a solopreneur increase the bus factor without hiring?

The classic numerical factor cannot exceed one without another capable person. However, automation, safe-pause procedures, authorized contractors, professional advisers, and tested handovers can substantially reduce the consequences of the owner’s absence.

Does documentation increase the bus factor?

Documentation reduces knowledge concentration, but it does not create another capable operator by itself. The information must be current, accessible, understandable, authorized, and tested through independent execution.

Does automation increase the bus factor?

Automation can extend the owner-free operating window, but it does not necessarily increase the human bus factor. Someone may still be required to handle failures, disputes, changes, security incidents, and long-term decisions.

What is the difference between bus factor and key-person risk?

Bus factor counts how few people must become unavailable before capability is lost. Key-person risk is the broader exposure created by dependence on a particular person’s knowledge, authority, skills, or relationships.

What is the difference between bus factor and succession planning?

Bus-factor work identifies concentrated human dependencies. Succession planning establishes what happens when an important person leaves permanently or cannot return. Temporary continuity and permanent succession should be coordinated.

How is bus factor calculated?

In its simplest form, identify the minimum number of people whose absence would stop a defined outcome. Some software metrics estimate it from contribution or file-authorship data, but there is no universal calculation for an entire business.

What is a good bus factor?

There is no universal target. A higher factor generally indicates less concentration, but the appropriate level depends on the activity’s importance, the acceptable interruption, and the cost of maintaining additional capability.

Does a contractor count toward the bus factor?

Only if the contractor has enough knowledge, access, authority, and capacity to protect the defined outcome without the owner’s help. Being familiar with the business is not sufficient.

Does a family member count toward the bus factor?

Only when the person is willing, capable, properly informed, legitimately authorized, and tested. A personal relationship does not provide automatic business or legal authority.

Should an emergency contact receive all business passwords?

No. Use appropriate administrative roles, delegated permissions, recovery mechanisms, professional arrangements, and legally recognized authority. Unrestricted password sharing creates security, privacy, and accountability risks.

What if the business depends on the owner’s personal brand?

Personal-brand activity may need to pause during the owner’s absence. The continuity plan should focus on protecting customers, payments, assets, communications, and contractual obligations rather than impersonating or replacing the owner.

What should be documented first?

Start with active customer commitments, the next 30 days of deadlines, activities that must continue, activities that should pause, and the person authorized to coordinate the response.

How often should bus-factor documentation be reviewed?

Review it after material changes to products, customers, contractors, accounts, business structure, professional advisers, or delivery processes. Active commitments and deadlines require more frequent updates than stable procedures.

How often should handovers be tested?

Test high-impact, fast-changing activities at least annually and after material changes. Activities with short deadlines or frequent operational changes may require quarterly or semiannual exercises.

What is the best first step for a solopreneur?

Assume you will be unavailable for seven days starting tomorrow. List every customer, financial, legal, and operational obligation that would be missed, then make the most urgent one capable of continuing or pausing safely without your intervention.