There's a moment on every contract where someone has to make a call that neither the principal nor the contractor will fully agree with, and it has to be right regardless of who feels it first. That's the job of the Superintendent — not to represent either party, but to sit above the argument and settle it fairly, under the powers the contract itself gives them.
It's a role that gets misunderstood easily, because the language around it sounds adjacent to project management, and the two are often held by the same person. But they're not the same job. A project manager is retained by the principal and works in the principal's interest — that's the whole point of the role, and it's a good one. A Superintendent, even when appointed by the principal, has to set that interest aside the moment a progress claim, a variation, or an extension of time crosses their desk. The contract says so explicitly: the role is performed fairly and impartially, favouring neither party. That's not a courtesy. It's the mechanism that makes the certificate mean something.
Contract-agnostic in practice — AS 2124, AS 4902, AS 4000, the GC21-style forms used on civil packages — the mechanics stay largely the same. A contractor submits a progress claim, and the Superintendent has a fixed window, set by the contract, to assess it and issue a certificate. A variation or an extension-of-time claim gets a similarly fixed window to be properly assessed on its merits — the ground conditions that turned out different from what the drawings showed, the scope that grew after a design change, the delay that was or wasn't the contractor's doing. None of this is discretionary in the sense of being optional. It's discretionary in the sense that it requires judgement, and judgement only carries weight when it isn't compromised by whose side you're on.
This is where thirty years of site-level construction experience earns its keep. Assessing a claim properly means understanding what a genuine latent condition actually looks like on the ground, what a reasonable programme impact from a given delay actually is, and where a contractor's number is padded versus fair. That's not a skill a contract administrator picks up from the documents alone. It comes from having stood on enough sites, under enough pressure, to know the difference between a real problem and a negotiating position.
On smaller, privately funded regional projects, it's common — and entirely legitimate — for a client to engage the same person as both Project Lead and Superintendent. Where that happens, the two roles are still held separately: the duties, the standard of impartiality on the Superintendent side, and the client-side advocacy on the Project Lead side don't blur into one undifferentiated job. On larger or institutionally financed developments, engineering firms and lenders more often want that wall to be structural — a Superintendent with no other role on the project, engaged for exactly that reason.
Either way, the discipline is the same. Someone has to be willing to tell a principal their variation claim doesn't stack up, or tell a contractor their extension of time is fair and should be granted, regardless of which answer is more comfortable in the room. That's the actual job. Everything else — the forms, the certificates, the timeframes — is just the structure that makes it enforceable.