Skip to main content

Profitability Control Tower

Route: /org/analytics/resource/profitability Permission: View Resource and Cost Profitability Analytics


1. What the control tower is​

The financial view of resource work: margin, utilisation, leakage and forecast in four tabs, with four headline metrics above them.

It is the only screen in Orbit Ops that puts revenue against cost. Every other analytics screen counts hours or tasks.

Control TowerBilling Analytics
MeasuresProfit — revenue against costBillable value
Generates anythingNoYes — bills
Period controlFour modesA date range
AudienceFinance and leadershipDelivery and billing

2. What the four headline metrics mean​

Each carries its own definition in a tooltip — these are the definitions, verbatim:

MetricFormula
Net Profitability"Gross Profit Margin calculated as (Actual Revenue − Actual Costs) / Actual Revenue."
Resource Efficiency"Ratio of Billed & Invoiced time versus Total Accrued time."
Budget Leakage"Total Unbilled Revenue as % of Total Accrued Revenue (Higher % indicates invoicing delays)."
Forecasting AccuracyForecast against actual — N/A with no forecast
Budget Leakage measures delay, not loss

The tooltip is explicit: a higher percentage "indicates invoicing delays". It is accrued revenue that has not been billed yet — usually because nobody has run generation for the period.

Leakage falling after a billing run is the system working, not money recovered.


3. The four tabs​

Figure 1 — The control tower with the four KPI tiles and the tab bar.
TabURLCovers
Profit & Loss?tab=p%26lRevenue against cost
Utilization?tab=utilizationHow resource time is used
Leakage?tab=leakageUnbilled revenue and budget variance
Forecasting?tab=forecastingWhat-if projections
The Profit & Loss tab's URL value contains an ampersand

The stored value is literally p&l, so a shared link needs it encoded as p%26l. An unencoded link drops the parameter and lands on the default tab.


4. Field reference​

ControlValues
Select View Periodfiscal_year · quarter · month (default) · billing_cycle
Project selectorOne project, or all
Export Financial Report"(Beta Feature)" — renders a PDF, reading "Generating PDF Report…"
Dashboard ModeFull screen

The four period modes​

ModeRange
fiscal_yearThe organization's fiscal year
quarterCalendar quarter
monthCalendar month — the default
billing_cycleThe configured billing cycle
billing_cycle is the mode that matches an invoice

The other three are calendar periods and will rarely line up with what was actually billed. When reconciling against a bill, use the billing cycle.

Currency​

Figures use the organization's configured currency symbol. There is no per-project currency override here.


5. The admin contract​

PrerequisiteWithout it
View Resource and Cost Profitability AnalyticsNo access
Project billing ratesNo revenue
Cost ratesNo margin — profitability reads 100% or zero
A fiscal yearThe fiscal_year mode is wrong
A billing cycleThe billing_cycle mode is wrong
Forecast dataForecasting Accuracy reads N/A
Generated billsLeakage stays high
Without cost rates, margin is meaningless rather than absent

Net Profitability is (Revenue − Costs) / Revenue. With no cost data the numerator equals the denominator and the screen reports a healthy-looking figure that measures nothing.

Confirm cost rates are configured before anyone acts on this number.


6. Downstream​

Read-only, apart from the exported PDF.


7. Don't confuse this with…​

ScreenMeasures
Control Tower (this page)Profit — revenue against cost
Billing AnalyticsBillable value, and generates bills
Resource BillsIndividual bills
Timesheet AnalyticsHours
Project BudgetProject Details — allocation, not realised margin

8. Troubleshooting​

SymptomCause
Profitability looks implausibly highNo cost rates configured
Forecasting Accuracy reads N/ANo forecast data
Leakage is persistently highPeriods have not been billed
A shared P&L link opens the wrong tabThe & in p&l must be encoded as %26
Figures do not match a billUse the billing_cycle period mode
Export produces nothingIt is a beta feature
Fiscal-year figures look wrongThe organization's fiscal year is not configured