Revenue Performance Board
Bring revenue, utilisation and rate together in one view so that a change in one is read against the others.
Inputs
What data is required?
- Completed and on-book revenue by location, class and period
- Fleet and utilisation for the same period
Outputs
What does it calculate, display or help you decide?
- Revenue, average rate and utilisation shown together with the definition used for each
- Period comparison with the basis of comparison stated
Build prompt
Not yet written. This module is proposed and not scheduled. The purpose, inputs, outputs and operating complication above describe what it would do; the build prompt, setup steps, dependencies and tests will be added if it is taken forward.
The part that catches people out
Define every metric on the page. Average rate can mean the average of what was quoted, of what was booked, or of what was finally paid after fees and adjustments. Utilisation can be measured against total fleet or against serviceable fleet. A board that shows a number without its definition invites two people to argue about a figure they are each calculating differently.
Optional RME connection
To be defined. Any supported data connection would require approved interfaces and verified data rights.
Any connection to RateHighway services would require approved interfaces, authorisation, tenant isolation and verified data rights. Nothing about access or availability is approved.
Proposed, not scheduled
There is nothing to build from yet. Start with a module that has a written prompt, or read the playbook to decide whether this one is worth building at all.