Coverage
Who is showing up where, and whether the right people are in the right places.
Coverage owns no data of its own. It reads events, participations, people, and zone affiliations that already exist in the core and other modules, and analyzes the pattern: where participation concentrates, where it's thin, and where a single person is quietly carrying something that should be shared.
What it tracks
- Participation concentration by zone — where people cluster, and where there are gaps
- Capacity by person — hours committed and events attended, across every zone they actually show up in, not just the one they're affiliated with
- Cross-zone participation — people who appear in a zone they aren't formally affiliated with
- Sole-contributor areas — a service-delivery or authorship role held up by exactly one person, with no one else behind them
What it reports
- A coverage heatmap and a concentration index per zone
- A capacity summary per person
- A double-booked view — scheduling conflicts where the same person is recorded at two events at once
- One measure published to Goals & Measures: areas with a single contributor
Who uses it
Coverage is read by org admins only. That's deliberate, not an oversight: a coverage area is a person, and a person can cross zones, so scoping the analysis to one zone would hide exactly the cross-zone concentration the module exists to surface. There is no zone-coordinator view of Coverage, not even of a coordinator's own zone.
Why it matters
An organization can have strong total participation numbers while carrying deep gaps in specific zones — the aggregate hides the distribution. Coverage makes the distribution visible, so leadership can act on it directly: redeploy people, recruit where representation is thin, or notice before a sole contributor leaves and takes the coverage with them.