Lodging DBP declarations without holding up handover

A Design and Building Practitioners declaration is a statement that the work was carried out in accordance with the regulated design. That sounds simple until you are three days from practical completion and the design compliance declaration for a variation is still sitting in someone’s inbox. The declaration itself is not the hard part. The hard part is having the documents, the verification and the sign-off in place so that the declaration can be made without holding up handover.

This article is about the mechanics of lodgement: what has to be in the pipeline, who does what, and how to programme the work so that the declaration is a formality rather than a bottleneck. It sits alongside the question of who is eligible to make a declaration, but it does not cover that ground. If you are sorting out registration and eligibility, start with the related article on Design and Building Practitioners registration for builders.

The commercial reality is that handover is where the money is. Progress payments, retention and the release of security all sit behind practical completion, and practical completion is increasingly tied to the compliance documents being in order. A declaration that cannot be made on time is a cashflow problem before it is a legal problem.

What a declaration actually certifies

The Design and Building Practitioners Act 2020 (NSW) requires certain declarations in relation to regulated design and building work. The declaration that matters at handover is the one that confirms the building work was carried out in accordance with the regulated design. That is not a statement that the work is good, or that it complies with the NCC in every respect. It is a statement about consistency with the design documents that were prepared and declared for that work.

That distinction drives everything about the pipeline. If the as-built work differs from the regulated design, the declaration cannot honestly be made until either the work is brought back to the design or the design is amended and re-declared. Both of those take time, and both are much cheaper to do while the trades are still on site.

It also means the declaration is only as good as the design documents behind it. If the regulated design was never properly declared, or if a variation was built without an amended design, the builder is left trying to declare that work was carried out in accordance with a design that does not exist in the right form. That is the situation that stalls handover.

The document set that has to exist before anyone signs

Before a declaration can be lodged, the following need to be in the one place:

• The current regulated design for each part of the work, prepared by the relevant design practitioner.
• The design compliance declaration that goes with each design, made by the practitioner who prepared it.
• Any amended regulated design and its accompanying declaration, clearly marked as superseding the earlier version.
• Evidence that the as-built work has been checked against the current design, including inspection records, hold points and any non-conformance reports.
• Any variation documentation that explains a departure from the original design, and the amended design that resulted from it.

None of that is exotic. The problem is that on most jobs it lives in four different places: the designer’s file, the builder’s document control system, the site office, and email. The declaration process forces it into one register, and that is where the time goes.

The fix is to run a single document register from the start of the job, with a column for the design version, a column for the declaration status, and a column for the date the declaration was received. The builder does not need to own the design content, but the builder does need to own the register, because the builder is the one who will be chasing the missing pieces at the end.

Who lodges, and who actually does the work

The obligation to make a declaration sits with the person the Act requires to make it. On a typical residential project, that means the relevant practitioner makes the design compliance declaration, and the builder makes the declaration about the building work. The builder cannot make a declaration on behalf of a designer, and a designer cannot declare that the builder’s work was carried out in accordance with the design.

In practice, though, the builder as principal contractor runs the programme and controls the document flow. That means the administrative work of chasing declarations, checking versions, and filing acknowledgements falls on the contract administrator or site supervisor. It is worth being explicit about this in the head contract and in subcontracts, because the alternative is a standoff at handover while everyone argues about whose job it was to ask.

A useful division of labour is set out below. It is not a substitute for the Act, but it reflects how the work actually flows on site.

One practical point: the person who signs needs to be satisfied they have everything they need. If the builder is chasing a declaration, the fastest way to get it is to send the practitioner the exact set of documents they will rely on, not a link to a folder. Practitioners sign more readily when the evidence is in front of them.

Programming the pipeline so it does not land on handover

The single most effective change a builder can make is to treat declaration readiness as a standing item from the first design issue, not as a handover task. That means:

• At design issue, confirm the regulated design and the design compliance declaration are both in the register, and note the version.
• At each variation, ask whether the change affects the regulated design. If it does, the amended design and its declaration need to be in the register before the variation is closed out.
• At each hold point or inspection, record whether the as-built work matches the current design. If it does not, raise it then, not at the end.
• At least a month before the expected practical completion date, run a full reconciliation of the register and identify every missing declaration.
• At least two weeks before, confirm the person who will make the builder declaration has everything they need and knows the lodgement channel.

The reconciliation step is the one that saves handover. It is much easier to chase a designer for a declaration while they are still engaged on the job than after they have moved on to the next project. It is also much easier to fix a departure from the design while the relevant trade is still mobilised.

The timing figures here are indicative, not prescriptive. What matters is that the reconciliation happens before the pressure of handover, when there is still room to fix things. Check the current requirements for any mandated timing in the Act or in your contract.

Amended designs: the most common source of delay

Most handover delays trace back to a variation that changed the design but was never reflected in an amended regulated design. It might be a structural steel connection, a change to the waterproofing detail, or a window schedule that moved. The work is built, the trade has been paid, and the design document on file no longer matches what is in the ground.

When that happens, the builder has three options, and only one of them is quick. The first is to amend the design and have it re-declared, which is the correct path but takes time. The second is to argue that the change is not a departure from the design, which is risky and usually wrong. The third is to declare against a design that does not match the work, which is the option that creates the real liability.

The way to avoid all three is to make the design practitioner part of the variation process. When a variation is raised, the question should be asked: does this change the regulated design? If the answer is yes, the amended design and its declaration become a condition of closing out the variation. That keeps the document set current and means the declaration at handover is a summary of a process that has already happened, not a scramble.

It is worth noting that the Act deals with amended designs specifically, and the requirements for re-declaring them. The detail is in the legislation, and builders should check the current provisions rather than relying on a summary.

What it costs when the declaration is late

The direct cost is delay to practical completion. If the contract ties practical completion to the compliance documents being in place, a missing declaration can push out the date, which can trigger liquidated damages, delay the release of retention, and hold up the owner’s move-in. On a residential project, that is often the difference between a satisfied client and a dispute.

The indirect cost is harder to see but larger. A declaration made under pressure, over work that has not been verified, is a risk that sits on the practitioner who signed it and on the builder who relied on it. If it later turns out that the work did not match the design, the declaration is evidence that someone got it wrong. That can affect insurance, future work, and the builder’s relationship with the certifier and the regulator.

There is also the cost of the records themselves. If the declaration and its supporting documents are not filed in a way that can be produced later, the builder can find themselves reconstructing the history years after the job, usually for an insurer or a regulator. A clean register is cheap to keep and expensive to rebuild.

Worked example: a builder in western Sydney

A builder in western Sydney is finishing a two-storey dwelling. The structural design was amended during construction to change a beam connection, and the amended design was issued by the engineer but never re-declared. The work was built to the amended detail and passed inspection, so nobody flagged it at the time.

Three weeks before practical completion, the builder runs a reconciliation of the document register and finds the gap. The original design compliance declaration covers the original design, not the amendment. The builder contacts the engineer, who is now on another project and needs to be reminded of the change. It takes a week to get the amended design re-declared, which pushes the declaration and the handover date by the same amount.

The cost in this case was a week of delay and a difficult conversation with the owner. The fix would have been to make the amended design and its declaration a condition of closing out the variation, which would have cost nothing at the time. This is the pattern on most jobs: the delay is not caused by the declaration itself, but by a document that was allowed to fall out of the pipeline.

There is nothing unusual about this example, which is the point. It is the ordinary case, and it is avoidable with a register and a standing agenda item.

Records: what to keep and for how long

The declaration is a record, but it is not the only record. The supporting documents — the regulated designs, the design compliance declarations, the amended designs, the inspection records and the variation documentation — are all part of the evidence that the declaration was properly made. They should be kept together, in a system that survives the project, for as long as the Act and the contract require.

In practice, that means the project document control system should have a compliance folder with a clear index. The index should show, for each regulated design, the version, the declaration status, and the date the declaration was received. When a certifier or an insurer asks a question years later, the answer should be a file reference, not a search through email.

It is also worth keeping the lodgement acknowledgement. If the declaration was lodged through an online channel, the acknowledgement is the proof that it was made. Without it, the builder is relying on memory and on the other party’s records.

How this fits with the rest of your compliance obligations

The declaration process does not sit on its own. It interacts with the construction certificate conditions, with the principal certifier’s role, and with the broader CPD obligations that keep a builder’s knowledge current. The related articles on NSW construction certificate conditions and principal certifier appointment duties cover those areas. The point here is that the declaration is one output of a document pipeline that runs across the whole job.

For builders who want to go deeper on the regulatory framework, the guide to how NSW builder CPD works explains how the annual requirements are structured and what counts. The PointCPD course catalogue lists the courses that cover compliance topics, including the Design and Building Practitioners regime.

None of this replaces the Act. It is a practical overlay on it, and the current requirements should always be checked against the legislation and the contract. But the principle is sound: run the pipeline from the start, reconcile before handover, and the declaration becomes a step rather than a stoppage.

Questions builders ask

• Certification
• Compliance
• Records

Published 12 August 2026. General information for builders, not legal, financial or engineering advice for a specific job. Check current requirements with the relevant regulator or standard before relying on them.