Financial and Operational KPIs in Management Reporting: A Worked Example

Revenue has increased. Gross profit has increased too. Is performance improving at the same pace as the workforce supporting it?

A P&L shows the financial result. Hours, workforce figures and utilisation help finance investigate the operating activity behind that result. Measures such as revenue per full-time equivalent (FTE), gross profit per FTE and billable hours per billable FTE connect the financial result with the workforce supporting it.

A management statement can place these measures together so finance and AI assistants use a shared basis for reviewing performance and preparing plans. To make that useful, the report needs to answer some familiar finance questions correctly: which workforce figure belongs in the quarterly report, how should group margins be calculated, and are the comparisons using the same period and people?

What financial and operational KPIs tell you together

Financial measures describe outcomes: revenue, costs, gross profit and cash. Operational measures describe activity or capacity: delivered units, hours, workforce, production output or customer volumes.

The relevant combination depends on the business. A services example may use billable hours and FTEs; another business may use units produced, orders or locations. Choose operational measures with a defined relationship to the financial question rather than filling the report with every available KPI.

A useful statement lets the reviewer ask three connected questions: what happened financially, what changed operationally, and which relationships deserve investigation or a planning assumption. It supplies a basis for those questions; displaying two measures together does not establish causation.

A worked statement: growth with lower gross profit per FTE

NovaTech’s fictional Q1 2026 statement combines financial results with billable activity and workforce measures. The comparison below uses the same sample figures as the Précis management-reporting example. Per-FTE rows are calculated from those figures and rounded for display.

Revenue grew, but the workforce grew faster than gross profit. Gross profit per total FTE therefore fell slightly, even though total gross profit rose. The report can now raise a more precise question: is this consistent with planned investment, service mix, hiring timing or another operating change?

The figures do not answer that question on their own. They identify a relationship to investigate. They also show why “revenue growth” and “productivity improvement” should not be treated as interchangeable claims.

Keep the workforce basis visible. Revenue and gross profit above use average total FTEs; billable hours use average billable FTEs. Switching between all staff and billable staff changes what the measure tells you.

What your management reporting system needs to get right

Combining financial and operational KPIs creates calculation choices that affect the interpretation of performance. A report can have the right revenue and workforce figures in its monthly columns and still give the wrong answer for the quarter. These are three examples of what the system needs to handle.

1. Use the right quarterly figure for each measure

Quarterly revenue is the total for the three months. Quarterly workforce needs a different treatment: average FTEs show the workforce supporting the quarter’s activity, while FTEs at 31 March show the position entering the next quarter. Both can belong in the same management report.

For an illustration, suppose the workforce stays at 10 FTEs throughout January, 12 throughout February and 14 throughout March. Giving each month equal weight produces 12 average FTEs for Q1. The quarter-end figure is 14 FTEs. Adding the three monthly figures and reporting 36 FTEs would overstate the workforce.

That distinction matters when finance reviews hiring or calculates profit per FTE. Dividing the quarter’s profit by the March workforce can make a growing team look less productive than it was over the quarter.

Finance should agree how the average is calculated. Daily and monthly averages can differ when people join or leave during a month. The report also needs to flag missing periods or an out-of-date workforce snapshot, rather than presenting an incomplete figure as the quarter’s result.

2. Calculate ratios for the period or department being reviewed

Revenue per FTE needs the quarter’s revenue and its average workforce. Adding the monthly revenue-per-FTE figures does not produce the quarterly measure. Taking their simple average does not answer that question either.

Using the same illustrative workforce figures:

The calculation is €760,000 quarterly revenue ÷ 12 average FTEs = €63,333 per FTE for Q1. Adding the monthly ratios would give €60,000. Their simple average would give €20,000. Neither is revenue per average FTE for the quarter. Label the period clearly: a quarterly figure should not be compared directly with a monthly figure.

The same issue appears when departments are combined. Suppose one department has €100,000 revenue and a 40% gross margin, while another has €900,000 revenue and a 20% gross margin. Together they have €220,000 gross profit on €1m revenue: 22% gross margin, not the 30% obtained by averaging the two percentages.

Gross profit per FTE and utilisation need the same care. The system should calculate them from the relevant profit, workforce and hours figures each time finance changes the period or department selection. Otherwise, a quarterly total or group report can suggest an improvement or decline that the underlying figures do not support.

3. Make comparisons use the same basis

A correct calculation can still mislead if the figures describe different people or periods. Billable hours per billable FTE measures delivery activity; billable hours divided by all staff includes a different workforce. Neither should silently replace the other between reports.

Likewise, “margin per FTE” needs a clear profit definition. Gross profit per FTE and EBITDA per FTE answer different questions about costs and performance. The report should name the measure, show whether it uses all staff or a specific team, and keep that basis consistent between actuals, budget and prior year.

If there are no FTEs recorded for a period, the report cannot calculate a meaningful profit-per-FTE figure. Show that it is unavailable and why; a zero would imply measured performance. Missing time records or different reporting dates also need to be visible before finance draws a conclusion.

These details determine whether a comparison is fit for the management meeting. Finance should be able to check them without rebuilding the calculation in a separate spreadsheet.

Give finance and AI the same definitions

An assistant asked to “explain productivity” needs to know which measure the team means. Revenue per total FTE, gross profit per total FTE and billable hours per billable FTE can move differently.

For each reported measure, retain:

• what the measure includes and how it is calculated;
• whether it covers all staff, billable staff or another defined group;
• how the monthly, quarterly and department figures are calculated;
• which actual, budget or forecast period it covers, and how current the data is; and
• where finance can check the supporting records.

With those definitions, a report, spreadsheet and AI conversation can use the same calculated result. The assistant can prepare comparisons and relevant questions using the agreed workforce figure and calculation for each measure.

Finance still needs to challenge the interpretation. Lower gross profit per FTE may reflect an intended investment phase, a change in mix or a genuine operating issue. The shared statement makes the change visible; source detail and business context establish what it means.

Read what a finance semantic layer contains for how those reporting definitions can be maintained and shared.

Carry the measures into a planning scenario

Historical ratios can inform assumptions, but they are not instructions for the future. A higher workforce does not automatically create more demand, and more billable hours do not automatically produce the same realised rate.

For an illustrative next-quarter scenario, finance specifies 10 additional average billable FTEs throughout the quarter, 400 available hours per average billable FTE, 75% billable utilisation, and a €120 realised time-and-materials rate. These are teaching assumptions, separate from the NovaTech actual figures above.

The incremental activity and revenue would be:

That revenue requires enough work at the assumed rate. It is a conditional scenario, not a prediction or an automatic consequence of hiring. If finance instead plans to finish the quarter with 10 additional FTEs, their start dates determine how much extra capacity is available during the quarter.

The scenario still needs the relevant costs. Gross profit depends on the defined direct costs; EBITDA also needs operating costs. Keep fixed-price revenue separate unless finance explicitly defines its relationship to hours. Check that workforce costs appear once in the statement and are not counted again through another cost line.

Finance can then compare the scenario with the baseline using the same statement definitions. The team owns the assumptions and reviews any proposed plan changes before they are saved.

How Précis brings financial and operational figures together

In a configured Précis management statement, revenue and costs can sit alongside hours, average and quarter-end workforce figures, and measures such as gross profit per FTE. Their reporting definitions specify how each figure is calculated when finance changes the period or views a supported department or business-unit breakdown.

The same maintained definitions can serve reports, Excel and AI assistants. The full Précis platform adds workflows for preparing scenarios and reporting material that finance reviews. The read-only Précis Finance MCP server supplies reporting access; it does not commit planning changes.

Start with the management-reporting workflow, or explore reporting in Excel.