---
id: workforce-analytics
name: Workforce Analytics
description: Report workforce coverage — open roles and who has actually been hired into them.
category: analytics
pages:
  - analytics
status: active
version: 1
triggers:
  - workforce analytics
  - workforce coverage
  - roles covered
  - coverage
owliver:
  enabled: true
  suggestions:
    - label: How well are open roles covered?
      capability: summary
    - label: Coverage by role
      capability: table
  capabilities:
    - summary
    - stats
    - table
    - list
    - progress
    - insight
  responses:
    summary:
      title: Workforce coverage
      source: workforce.coverage
    stats:
      title: Workforce coverage
      source: workforce.coverage
    table:
      title: Coverage by role
      source: workforce.coverage
    list:
      title: Coverage by role
      source: workforce.coverage
    progress:
      title: Coverage by role
      source: workforce.coverage
    insight:
      title: Workforce coverage
      source: workforce.coverage
---

# Workforce Analytics

## Purpose

- Report how many open roles have somebody hired into them.
- Name the roles that have nobody yet.
- State plainly where a role has not said how many people it needs.

## Capabilities

- Count open roles, those with someone hired, and those with nobody.
- Report coverage per role.

## Data

Reads `workforce.coverage`, which reads open `JobPosting` records through
`demandFor` — the same reading the Positions page uses — joined to `Staff` by
`job_posting_id`.

## Analysis

A role's coverage is the number of people hired into it against the number it
asked for. Where a role has not declared a headcount, this reports the hires and
says the target is unstated. It does **not** assume one person per role: that
would produce a confident fill percentage that means nothing, and nothing on
screen would say so.

## Output

Counts of open roles, covered roles and uncovered roles, how many roles state a
headcount, and a row per role.

## Limitations

- No position in this workspace currently states a headcount, so no fill
  percentage is reported. The count of hires per role is real.
- Only open roles are counted. Paused and closed roles are excluded.
- Assignment records would refine this, but none exist yet; coverage is
  therefore counted from hires.