Business Healthv1

Backlog-to-Revenue Ratio

Value of contracted but not yet executed work compared to annual revenue.

Owner: Unassigned
Updated: 10/30/2025
Calculation Formula
ENGLISH
Total Project Backlog / Annual Revenue
Python Example
With $10M backlog and $8M annual revenue, ratio is 1.25.
Entity Applicability
Which business entities use this KPI
Standard Calculation
8 of 8 entities
100%
Entity-Specific Notes

Indicates future revenue visibility. Ratio of 1.0-2.0 typically considered healthy.

Entity List (8)
MENA-01•Dubai Terminal
EU-02•Hamburg Terminal
HQ•Headquarters
ASIA-02•Hong Kong Terminal
EU-01•Rotterdam Terminal
ASIA-01•Singapore Hub
US-01•US East Terminal
US-02•US West Terminal
Additional Information
Industry
Construction, Engineering, Heavy Manufacturing
Tags
ConstructionEngineeringHeavy Manufacturing
Status
active
Local Network
Data Quality Dependencies
Critical DQ dimensions for this KPI
Accuracy
high

The degree of closeness of data values to real values.

Critical for Backlog-to-Revenue Ratio accuracy and reliability

Completeness (Data values)
high

The degree to which all required data values are present.

Critical for Backlog-to-Revenue Ratio accuracy and reliability

Completeness (Data values of an attribute)
high

The degree to which all required data values of an attribute are present.

Critical for Backlog-to-Revenue Ratio accuracy and reliability

Timeliness
high

The degree to which the period between the time of creation of the real value and the time that the dataset is available is appropriate.

Critical for Backlog-to-Revenue Ratio accuracy and reliability

Quick Stats
DQ Dependencies4
Applicable Entities8/8
Versionv1
API Access
GET /api/kpis/backlog-to-revenue-ratio