Bus Factor Calculator
Calculate your team's bus factor and knowledge concentration risk. Identify critical knowledge silos before they become problems.
Our Take
Bus factor is really a 'knowledge distribution' metric. A bus factor of 1 isn't bad because someone might leave—it's bad because knowledge silos slow everyone down every day.
When only one person understands a critical system, every question, every bug, every decision routes through them. This creates bottlenecks during normal operations, not just during emergencies. Teams with low bus factors experience longer incident resolution times, slower feature development, and higher stress on key individuals—regardless of whether anyone actually leaves.
"Codebases with bus factor 1 on critical modules have 3x longer incident resolution times."
— Industry research on knowledge distribution and incident response
Enter Your Team Data
Key Capabilities
Critical Systems/Modules
Optional: List specific critical areas and how many people can maintain each
Enter your team size and at least one capability metric to see your bus factor analysis.
About Bus Factor
The bus factor (also known as the "lottery factor" or "truck factor") is the minimum number of team members who would need to suddenly disappear before critical knowledge is lost. It measures your team's resilience to unexpected departures, whether from resignations, illness, promotions, or winning the lottery.
Why It Matters
- • Business continuity and risk management
- • Reduced stress on key individuals
- • Better vacation coverage and work-life balance
- • Faster onboarding for new team members
- • More flexible team assignments
How to Improve
- • Pair programming and mob programming
- • Comprehensive documentation and runbooks
- • Cross-training and rotation schedules
- • Code reviews as learning opportunities
- • Regular knowledge-sharing sessions
Critical - Single point of failure
High Risk - Still vulnerable
Medium - Some resilience
Healthy - Well distributed
Frequently Asked Questions
Bus factor (also called truck factor or lottery factor) is the minimum number of team members who would need to suddenly disappear before a project or team loses critical knowledge and ability to function. A bus factor of 1 means a single person holds critical knowledge that nobody else possesses. The term comes from the morbid question: "How many team members would need to be hit by a bus before the project fails?" It's a key metric for measuring organizational risk and knowledge distribution.
Want to track this automatically?
CodePulse connects to your GitHub and calculates these metrics in real-time. No more manual data entry or spreadsheets.
Free tier available. No credit card required.
Learn More
The 'Bus Factor' File That Could Kill Your Project
Use the Bus Factor Risk Matrix to identify where knowledge concentration creates hidden vulnerabilities before someone leaves.
The Tech Lead Dashboard Your Manager Shouldn't See
The metrics that matter for tech leads—code quality, technical debt, architecture decisions, and delivery. Different from EM metrics, focused on technical excellence.
The Git Query That Finds Your New Hire's Perfect Mentor
Use Git activity data to accelerate new hire onboarding, identify domain experts for pairing, and track ramp-up progress.
Related Tools
PR Size Analyzer
Analyze your pull request sizes and get recommendations. Learn the optimal PR size for faster reviews and fewer bugs.
Technical Debt Cost Calculator
Quantify the cost of technical debt. Calculate how much productivity you're losing and build a case for refactoring.
SPACE Framework Assessment
Assess your team across all 5 SPACE dimensions: Satisfaction, Performance, Activity, Communication, and Efficiency. Get a visual radar chart and recommendations.