Working with engineers and certifiers,
two roles, two kinds of sign-off.

Two different kinds of professional put their name to a residential build. Design consultants (the architect or building designer, the structural engineer, the geotechnical consultant, the hydraulic designer, the energy assessor and any specialist the job needs) produce the documentation the work is built from, and certify their own design where the approval or the contract requires it. The certifier, known as a principal certifier, building surveyor, building certifier or the council depending on the jurisdiction, holds an independent statutory role: checking the work against the approval and the applicable codes, carrying out or receiving the required inspections, and issuing the certificates the job cannot complete without.

The distinction that matters on site is not about qualifications. It is about direction. A consultant is engaged, and can be asked to design something differently. A certifier is appointed, and cannot be asked to accept something. Most coordination failures on a residential job trace back to that one line being crossed: a design question sent to the certifier, or a compliance decision assumed from a consultant.

Why it matters

Because both roles sit on the programme, not beside it. An engineering detail that has not arrived stops a trade. A certifier hold point that has not cleared stops a stage. Neither of them is a task the builder can complete by working harder, which makes them the two dependencies most worth managing early and most commonly managed late. The builder who treats consultant input and certification as scheduled work with owners and dates runs a job with fewer surprises than the builder who treats them as things that happen to the job.

The design consultants come first and never quite leave. Their documentation supports the approval application, then supports the construction, then supports the closing certificates. The certifier is engaged around the approval, appears at defined points through construction, and returns at the end for the occupation certificate or its local equivalent. Between those points the builder is holding both relationships open while running trades against a programme that assumes both will respond in time.

That is the structural reason coordination is a builder problem rather than a consultant problem. The consultant sees their scope; the certifier sees their inspection; only the builder sees the sequence that connects them to a trade standing on site. The construction schedule is where that sequence becomes visible, which is why design decision dates and certification hold points belong on the programme alongside the trades that depend on them.

Design is resolved in the order the designer needs, and construction happens in the order the trades need. Those two orders are not the same, and nobody is at fault for that. The architectural set generally has to settle before the structural detail can be finalised; the structural detail generally has to settle before the fabricator can price and make. Each dependency is reasonable on its own, and stacked together they push the detail towards the moment it is needed rather than the moment it can be used.

The builder feels this as a late detail. What is actually happening is a lead time colliding with a decision date. By the time the missing detail is obvious on site, the procurement window it governs has usually already been spent, which is why chasing harder rarely recovers the days. The fix is upstream: work backwards from each trade start date through the lead time for the materials it consumes, and set a decision-by date for the design input behind them. A decision-by date with a name against it is schedulable. An assumption that the drawings will be finished in time is not.

The trade-off is real and worth stating plainly. Demanding every detail resolved at contract signing is neither achievable nor free: some detail legitimately follows client decisions that have not been made, and detail produced before those decisions gets reworked. The judgement is which details sit on the critical path and which can be released later without stalling anyone. Builders who make that judgement explicitly, and put the answer on the programme, spend far less of the job chasing.

An inspection is a comparison. The inspector compares what is in front of them against what the approval and the documentation say should be there, so the paperwork that defines the second half of that comparison has to exist before they arrive. The specific list is set by the approval conditions and by the certifier, and it differs by jurisdiction and by job, so ask for it rather than inferring it from any general reference, this page included. In practice the packet usually assembles from:

• The approval itself and its conditions, because a condition attached to the approval is a construction requirement whether or not it appears on a drawing.
• The current revision of the drawings and specification the work was actually built to, which is only useful if the site was working from that revision.
• The engineer's detail for the element being inspected, including any sketch or marked-up drawing issued in response to a site query.
• Any design or compliance certificate the approval requires from a consultant, and the product or system documentation for materials whose compliance is claimed rather than visible.
• The site record of work about to be covered up: dated photographs of reinforcement, depths, connections and waterproofing, taken on the day, filed against the job.

That last item is the one builders undervalue, because it is the only one that becomes impossible to produce later. Once the concrete is poured, the photograph taken that morning is the entire remaining evidence that the detail was followed. The site diary and photo log is not administration in that moment; it is the record the sign-off rests on.

Every structural design rests on assumptions about things nobody could see when it was drawn: the soil classification, the founding material, the water table, the condition of an existing structure being built onto. Excavation is where those assumptions get tested, and sometimes fail. This is normal, not a failure of the engineer, and it has a sequence that works.

Stop the work on that element. Record what was actually found, with dated photographs and a scale reference, before anything is disturbed further. Notify the engineer in writing, with the record attached, and ask for a revised detail rather than an opinion. Then, and only then, price the change. Running the sequence in that order keeps three things intact at once: the safety of the decision, the evidence for the certifier, and the builder's commercial position.

The commercial answer comes from the contract rather than the engineer. Where the contract carries a provisional sum or allowance over that work, the price commonly moves under the allowance machinery. Where nothing covered it, the change is normally handled as a variation, documented and priced before the work proceeds. There is a time side as well, claimed under the contract's own machinery and covered in extensions of time and delay. None of these move by themselves because the ground was different.

The expensive version of this is familiar to anyone who has run sites: the pour is booked, the pump is coming, and the hole does not look right. Proceeding on the original detail because the day is committed converts a priced variation into a possible rectification, and rectification of covered work is the most expensive form of any construction problem. A cancelled pour costs a day. Concrete over the wrong assumption can cost the element.

The operator's observation is that most consultant delays are not caused by missing work. They are caused by evidence being in the wrong place or the wrong format. An engineer asks a supervisor for footing and pier photos; the supervisor takes them and texts them from his phone; the engineer then has to ask again, because a photo on a phone is not something they can put in the formal record. The work was done correctly and on time. The job still lost days, twice, to a formatting problem nobody thought of as a problem.

The habit that removes it is unglamorous. Ask each consultant and the certifier, once at the start of the job, exactly what they need and in what form: emailed or uploaded, what has to appear in the subject line, whether depth and dimension need a scale reference in frame, whether they want the element identified against a drawing reference. Write the answer down where the site team can see it. Then capture at source, against the job, every time, so that responding to a request is retrieval rather than a scramble.

Two more disciplines separate the coordinated jobs from the chased ones. First, one named owner for consultant and certifier coordination, so that a query is never in three inboxes and nobody's responsibility. Second, a register of open queries with the date raised and the date an answer is needed by, reviewed at the same meeting the programme is reviewed. A query without a needed-by date is a request; a query with one is a schedulable commitment at the other end, and consultants generally respond to the second better than the first. The wider discipline of raising and tracking those queries is covered in RFIs and site queries.

Where software fits the workflow

Every part of this is a capture problem before it is a coordination problem. In VIABUILD the ViaSite daily diary and photo log are filled in on site as part of the supervisor's day, with photos logged straight to the job and dated as they are taken, so the reinforcement photo, the pier record and the diary entry already exist against the right job when an engineer or a certifier asks for them. What gets sent, to whom and in what form remains the builder's judgement; the contribution is that the record was made at the moment it could still be made.

Certification and consultant obligations sit inside each state and territory's building framework, and the terminology alone differs enough to cause confusion between jurisdictions. The points below are labelled by evidence class. Requirements differ by jurisdiction and change over time, so confirm the current source before relying on any of them, and treat this page as general information rather than legal, planning or engineering advice.

• Legislation. Building certification is a regulated function in the states and territories, with registration or accreditation requirements, appointment obligations and defined certificates. The title of the role and the scope of what it covers differ by jurisdiction, and no jurisdiction-specific detail is asserted here. Confirm the current position with your state or territory building regulator.
• Industry best practice. The National Construction Code, published by the Australian Building Codes Board and adopted by each jurisdiction with its own variations, sets the technical requirements the work is assessed against, and calls up Australian Standards for many elements. Which edition and which variations apply to a given job depends on the approval and the jurisdiction, so read them from the approval rather than from memory.
• Common practice. Approvals commonly attach conditions that must be satisfied before work starts, at defined stages, or before occupation. Conditions are construction requirements even when they never appear on a drawing, which is why the approval document belongs on site rather than in a file.
• Common practice. Critical stage or mandatory inspections operate as hold points on the programme, and evidence of covered work is commonly required to support them. Builders who put those hold points on the schedule alongside the trades treat them as planned duration rather than as interruptions.
• Professional recommendation. Treat the certifier as the assessor of a solution rather than the source of one. Certification is an independent function, and certifiers are commonly constrained in how far they can advise on work they will later assess. Where a compliance path is genuinely unclear, get the design consultant to propose it and put the proposal to the certifier in writing.

Illustrative only, not a benchmark. Two builders are boring piers on similar sites, and in both cases a run of holes reaches the design depth without getting into the material the geotechnical report assumed. The first builder's supervisor stops that run, photographs each hole with a staff in frame and the spoil laid out beside it, records the depths in the diary that morning, and emails the engineer a written query with the photos attached, the drawing reference, and the date the pour is booked for. The engineer issues a revised detail with deeper piers on the affected holes. The builder prices the additional work against the contract before proceeding, the revised detail goes into the current set, and the inspection clears against a record that shows exactly what was found and what was done about it.

The second builder's crew keeps boring, because the pump is booked and the day is committed. Someone texts two photos to the engineer, who cannot use them for the record and asks for them properly a day later, by which time the holes are poured. The engineer now has to assess an element they cannot see, on evidence that does not show depth. The certifier at the hold point has a query, the builder has a rectification conversation rather than a variation conversation, and the client hears about it as a problem rather than as a decision. Same ground, same engineer, same day's work. The difference was entirely in what got recorded, when, and where it was sent.

Certifier (the independent statutory role that assesses work against the approval and the codes, known by different titles in different jurisdictions), design consultant (an engaged professional who produces documentation and can be instructed by whoever engaged them), design certificate (a consultant's certification that a design or its execution meets a stated requirement), hold point (a stage the programme cannot pass until an inspection or approval clears it), approval condition (a requirement attached to an approval that binds construction whether or not it appears on a drawing), site query or RFI (a written request for information or a detail, with a date an answer is needed by), covered work (work that becomes inaccessible once the next stage proceeds, so the contemporaneous record is the only later evidence), decision-by date (the date a design input must be settled to protect a downstream lead time). Definitions for the wider vocabulary live in the construction glossary.

Almost everything on this page is really a document moving between parties at the right time and in the right form, which is its own subject; the next reference is construction documents.

• Your state or territory's building regulator, for the current certification framework, the title and scope of the certifying role, and the inspection requirements that apply where you build.
• Australian Building Codes Board , publisher of the National Construction Code, which each jurisdiction adopts with its own variations.
• Standards Australia , publisher of the Australian Standards the Code calls up for structural and other elements.
• The approval document for your own job, including every condition attached to it, which governs that job ahead of any general reference.