Price the guarding, then bill the hours it actually took

The problem this solves

A guarding bid is usually priced in a spreadsheet nobody else can open, from an hourly rate and an optimistic view of how many hours the post really needs. It prices last year’s contract, and when the margin turns out wrong there is no way to find which line was wrong.

GuardCore prices the work. Guard hours split by day type, a static post, a mobile patrol run whose cost is allocated across the sites it covers, alarm response, event crowd control, control-room monitoring, equipment and vehicles, mobilisation, and a premium for a licence class — nine calculators, each with its own unit, all through one build-up: the base rate, the divisor that turns paid hours into productive ones, the on-costs, the overhead, the margin and the GST.

It is not an award engine, and that is a decision rather than a shortfall. Penalty rates arrive as your own effective-dated rows, minimum engagements arrive as your own bands, and a crowd ratio arrives with the label its provenance is written on. Nothing is ever priced at zero: an unresolvable rate produces no unit cost and a named warning instead of a line that quietly costs nothing.

Then the commercial record is continuous. An accepted security estimate writes a static-guard contract on the security service line, with its rates. Approved hours are priced against those rates — site, then contract, then organisation — into invoice lines that keep the hours they were built from, so an attempt to bill the same hour twice is refused and told to raise a credit note instead. The month leaves as a Xero or MYOB import file, column for column.