Metrics and schedule

Every group carries a small set of figures that answer the questions a delivery leader asks first: how many people, how many empty seats, who is coming and going, and what it costs. Nothing needs configuring; the figures come from the positions and occupancies on the As-of day.

The figures on every row

Figure	What it counts on the As-of day
Headcount	Distinct people holding a seat in the group. A person in two seats counts once.
Positions	Seats filled out of seats open — 5 / 7 — then "2 open" when seats are short.
FTE gap	How far the group's seats are from fully staffed: the sum over its seats of required FTE minus the occupants' shares. Shown as an amber dot and "−1.5 FTE"; blank when fully staffed.
Next 30 days	People arriving (+) and leaving (−) within 30 days of the As-of day. Arrivals are occupancies starting in the window, including vacancies; leavers are occupancies ending in it. Blank when nobody moves.
Monthly cost	The run-rate of the people in the group's seats for the As-of month, in the reporting currency. Shown only to people allowed to see cost.

The same four figures head the group's page. Hover any of them, or the dot and badge in the list, for a tooltip saying what was counted and on which day. A row that is fully staffed with a quiet month shows nothing in the last two columns, so the rows that do show something are the ones to look at.

These figures are per group: a stream's row counts the seats directly in the stream, not the teams beneath it.

Arrivals and leavers

At the top of a group's page, a sentence names who is leaving and who is due to arrive within 30 days, each name opening that person. It is the same count as the badge, spelled out.

Metrics: the headcount bridge and cost

The Metrics view on the group page holds the headcount bridge: a waterfall over the twelve months from the As-of month. It starts at the opening headcount, steps up for each joiner and down for each leaver, and lands on the closing headcount, month by month. Closing always equals opening plus joiners minus leavers, so a step that looks wrong is a date that is wrong.

Beneath it, for readers who may see cost, the monthly cost over the same twelve months: this month's run-rate and the forecast for the year ahead as occupancies start and end.

How cost is calculated

Cost is a run-rate, not a budget. For each occupancy, each month, Flowstate takes the person's salary or rate as it stands in that month, applies their share of the seat, and pro-rates for the days they hold it. Employees and vacancies use their daily rate on the forecast engine's monthly basis; contractors use their daily rate, or working days when your organisation costs contractors that way. It is the same basis as the cost forecast, so the two agree.

A month in which a salary changes mid-month is split at the change, so that one month can differ from the forecast's whole-month figure.

Who sees cost

That is your organisation's choice, under Settings → Delivery → Functional groups: nobody, managers and viewers of the group (the default), or everybody. People with the summary financials permission always see cost. When a reader may not see it, cost is absent rather than zero — the column, the figure and the cost strip are simply not drawn.

Schedule

The Schedule view is a timeline over the same twelve months: one row per position open at any point in the window, one bar per occupant, each bar carrying the person's name. A marker sits on the As-of day.

• A bar that starts inside the window is an arrival; one that ends inside it is a leaver. Both take their own colour, so the changes stand out from the bars that simply run on.
• A bar that began before the window, or has no end date, is drawn to the edge and marked as ongoing.
• A position with an end date shows where it ends.
• Click a row or a bar to open that position.

The schedule reports the plan. Click an occupant's name to open the person, or right-click a row for Edit position, Fill position and Change reporting line. Other changes are made on the Structure view or in the position's panel.

History

Every change is recorded: who did it, when, and what changed, field by field. The group's History view lists them newest first; each position has its own History tab. Auditability is the point — a headcount that moved can always be traced to the occupancy that moved it.

Doing it from Claude

The figures are returned by the same reads that power the screens:

How many people are in Servicing & Operations today, how many seats are short, and what does it cost per month?

list_functional_groups { }

Each group in the result carries headcount, positions, filledPositions, openPositions, requiredFte, filledFte, arrivals30, leavers30 and monthlyCost (null when the caller may not see cost). The FTE gap is requiredFte − filledFte.

Who is leaving Early Arrears in the next 30 days, and what does its headcount look like month by month for the next year?

get_functional_group { "functionalGroupId": "<T-1024 id>" }

The group read includes its occupants with dates, the 30-day arrivals and leavers by name, and the headcount bridge by month.

Let everybody see functional group cost.

set_functional_group_cost_visibility { "costVisibility": "EVERYONE" }

Needs the settings permission; the values are HIDDEN, MANAGERS and EVERYONE.