Reporting cycle
A month in the life of an energy ledger
Whether you keep the process in-house after handover or retain us month to month, the cycle below is the rhythm we design engagements around.
Why a fixed cycle matters
Boards freeze packs on calendar dates. Utilities bill on their own schedule. Plant events ignore both. A reporting cycle that waits for “complete data” forever never ships; a cycle that invents missing meters loses trust.
We set cut-offs, label gaps, and still publish a note your facilities lead can stand behind.
Data cut-off
Usually by the 8th working day. Your team sends invoices, BMS exports, and a short list of plant or tenancy events. Late files are noted as late — not silently omitted.
Ledger update
kWh and chilled-water figures land against the baseline. Tariff bands are checked separately so bill spikes are not confused with energy spikes.
Anomaly pass
Rules flag night load, vacant-floor hold, and second-chiller staging. A human writes the first commentary draft — no auto-generated filler paragraphs.
Clarification call
Fifteen to thirty minutes with your nominated reviewer. Open questions become action items for contractors or tenancy managers.
Pack freeze
Final PDF or slide excerpt for the board pack. Estimates remain labelled. The same structure feeds the annual sustainability reporting pack when the year closes.