Resources
Key-person dependency risk in business spreadsheets
6 min read
A key-person dependency exists when a single individual is the only person who fully understands a critical business process or system. In spreadsheets, this happens constantly — and it's almost invisible until it isn't.
What it looks like in practice
The clearest signal is metadata: the person who created the workbook is the same person who last modified it. If that workbook is used in a regular business process and has a complex formula structure, you have a key-person dependency.
Secondary signals:
- No documentation of what the workbook does or how it works
- Complex, undocumented formula logic with no named ranges or comments
- Hardcoded values with no obvious source or rationale
- Hidden sheets that contain "the real logic"
- The workbook is the source of truth for a process that affects multiple teams
The business risk
When the key person leaves — through resignation, illness, or restructuring — the business is left with a black box. Nobody knows what assumptions are baked in, which cells are safe to modify, or why certain values are what they are.
The typical response is to leave the workbook untouched ("it works, don't touch it"), which means accumulating technical debt and eventually having a process that can never be safely changed or replaced.
How to find it
Look at file metadata — specifically the creator and last-modified-by fields. Excel workbooks store this in the document properties. Any workbook where these are the same person, and that workbook hasn't been modified in more than six months but is still actively used, is a candidate for review.
At portfolio scale — if you have dozens or hundreds of workbooks — scanning for this pattern manually is impractical. Automated detection across your workbook estate is the only way to identify it systematically.
What to do about it
Document the workbook while the key person is still available
Have them walk through the logic, inputs, and outputs. Record assumptions. Name key ranges. This is the fastest way to spread the knowledge.
Identify a backup maintainer
At minimum, there should be a second person who understands the workbook well enough to use it and make minor changes without breaking it.
Reduce hidden complexity
Move hardcoded values to an explicit inputs sheet. Give named ranges meaningful names. Add comments to formulas that aren't self-explanatory.
Track it in your audit
Key-person risk doesn't go away until ownership is genuinely distributed. Treat it as an open finding with a remediation status.
Detect key-person risk automatically
SheetSift detects key-person dependency risk from file metadata as part of every scan — flagging workbooks where the creator and last-modified-by are the same person. Team plans include an estate-wide view so you can see the pattern across all your workbooks at once.