Cileccta Review

Operation and maintenance

Build an operating-cost register for a building

Cileccta Review · Published 4 November 2026 · Original editorial guide

Turn invoices, meter readings and maintenance agreements into a cost register with units, dates, sources and explicit gaps.

Start with a defined building and period

Write the building, included spaces, reporting period and responsible team at the top of the register. A mixed-use property needs a stated rule for shared services. Record occupancy and operating hours next to the costs so that a quiet month is not treated as the normal basis for a fully occupied year.

Keep quantity and price in separate fields

For a measured service, retain consumption, unit, tariff, standing charge and billing period. Keep the invoice total as a reconciliation field. If the tariff has several bands, preserve the original breakdown. A single annual amount hides whether a change came from consumption, price or the length of the billing period.

Separate recurrent work from major events

Routine inspections, cleaning of plant, replacement consumables and service agreements belong in named rows. Put an overhaul or plant replacement on its own event row. Check whether the agreement already includes labour or parts before adding them again. A category label alone will not reveal double counting.

Original register template — blank amounts are not zero
FieldWhat to record
Service / boundaryNamed system, spaces and included work
Quantity / unit / periodObserved consumption or task count and exact dates
Unit price / fixed chargePrice basis, currency and tax treatment
Amount / payment yearSource amount or an explicitly unestimated entry
Evidence / statusInvoice, contract or assumption; confirmed, not estimated or not applicable
Owner / review datePerson responsible for the next update

Use a small register that people will maintain

The example below is an original blank working template. Copy the fields into the team's existing system and assign one owner to each row. Leave the amount empty until supported. Use the status field to distinguish not estimated, not applicable and confirmed zero.

Reconcile before forecasting

Compare the register total with the source invoices for the same boundary and dates. Explain credits, shared charges and missing periods. Keep exceptional repairs visible. When converting observations into a future annual assumption, write the adjustment and its reason in a separate field; preserve the observed amount.

Close one evidence gap at a time

Choose the row most likely to affect the comparison and request the missing record. For a service contract, ask for the included tasks and exclusions. For consumption, confirm meter coverage. At the next review, record the new source and revision date instead of overwriting the audit trail.