Skip to content

Workforce Analytics

Dashboards and reports that read directly off the workforce model. Same employees, same allocations, same exchange rates, same cost formulas as the rest of the app — which means the headcount number on a dashboard matches the headcount number on the finance page matches the number you tell the board. No exports, no spreadsheets, no "let me check why those don't agree".

Most companies build their workforce reporting in a BI tool stitched together with twelve other sources. Then they spend the next two years reconciling. Skip that step.

Four ways in

PageWhat it is for
DashboardsPinned charts, your default landing, share with a team.
ReportsBuild, save, and share individual chart queries.
Strategy viewPre-built operational charts — driver mix, project health, headcount bridge.
Financial viewPre-built financial charts — burn rate, labor mix, cumulative CapEx.

Open Workforce Analytics and you land on your default dashboard if you have one set, or the dashboards index if you do not.

What you can ask

The model exposes a uniform analytics surface across:

  • Headcount — employees, contractors, vacancies, AI agents.
  • Allocations and FTE — by team, by project, by driver, by cost centre.
  • Effort — actual time captured from PMS or manual entry.
  • Cost — fully loaded, in your reporting currency, sliced any direction.
  • Variance — actual vs forecast, period over period.

Every chart accepts a date range, a scenario context (so you can run analytics against a what if), and the same filters used on the operational screens.

Scenario-aware

Every analytics page runs inside the active plan — your live plan by default, but flip to a scenario and the same dashboards re-render with the scenario's changes applied. Useful for "show me the strategy view if this restructure goes through" without leaving the analytics surface.

Permission gating

Some charts require finance permissions (cost data) or team-employee read permissions (employee-level detail). Charts you cannot see render as a permission-required placeholder with the missing permission name. Ask your admin or check your role.

Where to go next

Flowstate Documentation