What a Bus-Factor Report looks like

The three sections

Single points of failure: every system, vendor, shared mailbox, site, and recurring meeting that exactly one person owns or touches, ranked by how much would stall.

Directory drift: job titles and group memberships that disagree with observed activity. Directory says, activity says, confidence.

A continuity page per seat: what only this person covers, what others also touch, and the two-week-absence stall list.

A sample seat page

Seat: Office Manager. Only they: vendor-payments mailbox (sole sender, 90 days), payroll portal (sole assigned user), supplier onboarding site (sole owner). Also touched by others: monthly close meeting (organizer plus one), client intake form (two owners). Named backup: none recorded. Two-week stall list: vendor payments, payroll, new supplier setup.

Reading confidence grades

Every finding carries a grade and the date it was observed. Observed means the tenant showed it directly, such as a sole owner on a mailbox. Inferred means it was derived, such as a person being the only sender to a vendor domain. Inferred rows are real leads, not verdicts. Absence of evidence is reported as a gap, never as safety: a person with no observed activity is unknown, not safe.

What to do with a red row

Add a second owner. That is the fix for most red rows and it takes a minute in the admin center. For processes rather than objects, schedule one supervised cycle with the backup. Then re-run the report; the row should go green or move to inferred with two people.