Four questions that come up on every implementation call, answered properly.
How is margin live instead of a month-end number?
Live margin is the difference between revenue earned and cost incurred, recomputed every time a record lands, not a figure rebuilt in a spreadsheet three weeks after the month closes. The moment an approved docket, a certified claim or a finalised diary line books cost against a budget line, the actual moves; the moment work is measured against an award item, earned revenue moves.
Because both sides resolve to the same cost-coded spine, the gap between them is always current, at every level of aggregation from a single budget line up to the whole project. The forecast rides on top, and it is the program loading itself: what the plan says a cost code will cost, never a performance-adjusted projection of what has been spent. A project manager sees variance the day it lands, and a commercial manager stops closing the month on a guess.
See also Budget line · Cost code · Forecast margin
How are variations tracked end to end?
A variation has five line types (additional work, omission, time extension, rate change, and provisional-sum adjustment) and each line moves through the same approval chain: raised, priced, submitted, accepted, rejected, or queried. Every state change carries a timestamp, the user who made it, and the supporting document, so the audit trail survives the project even when the people do not.
Time extensions push the contractual completion date, which feeds the liquidated-damages timeline so nothing falls between the cracks at close-out. Provisional-sum adjustments roll into the budget the same day they are accepted.
Variations are where margin slips quietly in construction: a verbal yes on site, no paperwork, no claim, and three months later the cost is in the actuals with no matching revenue. One structured ledger keeps the cost incurred and the revenue earned in step as the scope moves.
See also Variation · Budget line
What is a payment certificate, and why does it matter?
A payment certificate is your written response to an engaged contractor's payment claim: it states the amount you agree to pay, the amount you dispute, and the reasons line by line. Under the Security of Payment regimes each Australian jurisdiction sets a window to issue one, and letting that window pass generally means the claim is taken to be approved in full, including the amounts you dispute.
tectm generates the certificate from approved dockets, retention rules and back-charge ledger entries, so there is no spreadsheet handover to drop a line in. Every assumption that fed it stays linked to the source docket or variation, which is what makes it defensible line by line if the claim goes to adjudication.
See also Payment certificate · Payment claim · SoPA (Security of Payment Act) · Substantiation packet
Why do date-effective rates matter for cost control?
Rates change during a project (award increases, escalation clauses, agreed rate reviews, midstream renegotiations) and a docket priced on the wrong day is how margin disappears without anyone noticing. Every rate, whether a labour classification, a plant item or an overtime loading, is held with an effective-from date, and a docket pulls the rate that was in force on the day the work happened rather than the day the claim was raised. The history is immutable, so a rate review two years later still resolves correctly.
It handles the awkward days without anyone having to think about them: shifts that run past midnight, penalty rates, and the public holidays that apply where the work actually happened rather than where head office sits. Every figure opens onto the build-up behind it, so the result is audited on one docket instead of re-checked every week.
See also Internal rate card · Docket · SoR (Schedule of Rates)