The Lack of Quality Control Before Plan Sealing Lodgement
Most plan sealing applications in Queensland are submitted without a thorough pre-lodgement review. The application goes out when it feels ready — when the obvious gaps have been filled and there's commercial pressure to get it lodged.
The implicit assumption is that council will identify any remaining issues during assessment. The outstanding matters process becomes the quality control mechanism — except it operates at the worst possible time, when settlements are pending and the project team has no buffer left.
A pre-lodgement quality control process isn't standard practice. It should be.
How this shows up on projects
The surveyor has pulled together the application. It looks complete. The main documents are there. The covering letter references each condition. There's been no systematic check of whether each condition has actually been addressed — the review has been a high-level scan, not a condition-by-condition assessment.
Two weeks after lodgement, council issues an outstanding matters letter. Three conditions relating to landscaping haven't been addressed. One infrastructure charge has been paid but the receipt isn't in the application. A referral agency approval from the Department of Transport was requested but the response was never received.
The project team works through the items. The landscaping issue takes ten days to resolve — the landscape architect needs to provide a completion certificate that wasn't part of their original scope. The Department of Transport response has to be chased again. The receipt is found and submitted.
The resubmission adds three weeks to the plan sealing timeline. Contracts were already unconditional. Settlement extensions are negotiated.
Why it happens
Pre-lodgement quality control takes time and requires a structured approach. On projects where the plan sealing application has been assembled at speed, there isn't always capacity for a thorough review before lodgement.
There's also a systemic issue: without a condition-by-condition record of what has been addressed and what evidence is on file, a proper pre-lodgement review is hard to do. You can't check completeness against a list you don't have.
Commercial pressure plays a role too. When developers are pushing for lodgement, the path of least resistance is to submit and see what happens. The cost of that decision — in delays and rework — is visible in retrospect but not always weighed clearly at the time.
Finally, teams that have lodged incomplete applications before and had them resolved through the outstanding matters process may treat that process as normal. It becomes accepted practice rather than a sign of a process problem.
Impact on plan sealing
Without pre-lodgement quality control, the outstanding matters process does the work that should have been done before lodgement. The difference is timing. Issues identified before lodgement can be resolved without affecting the assessment timeline. Issues identified by council delay the plan sealing process for everyone.
Multiple rounds of outstanding matters extend the overall timeline significantly. Each round involves a response period for the project team and a review period for council. On projects where this happens two or three times, the additional time is measured in months.
There's also a pressure and relationship dimension. Repeated requests for additional information put strain on the project team at a time when they're already managing settlement pressure. The relationship with council can also be affected over time.
The straightforward fix is to catch gaps before lodgement rather than after. That requires a process — not just effort.
Improving the process
A pre-lodgement review should work through each DA condition systematically and confirm that the evidence on file is current, complete, and clearly referenced. This isn't a document count — it's a condition-by-condition assessment of whether each requirement has actually been met.
For conditions involving external parties — referral agencies, utility authorities, certifiers — the review should confirm that responses have been received and are on file. These are the conditions most likely to create gaps, because they depend on parties outside the project team's direct control.
Timing matters. A pre-lodgement review done a week before intended lodgement gives the team time to resolve gaps. A review done on the day of lodgement doesn't.
For larger or more complex applications, a structured checklist — worked through by someone other than the person who assembled the application — is an effective quality control step. A second set of eyes catches things that familiarity misses.
Using a structured system
Planease supports pre-lodgement quality control by maintaining a live record of condition status throughout the project. Before lodgement, the full condition schedule is visible — what's been addressed, what evidence is attached, and what's still outstanding.
Rather than conducting a review from scratch at lodgement time, the quality control process runs continuously. Outstanding items are visible as they arise, not discovered in a pre-lodgement scan. By the time lodgement comes around, the review is a confirmation — not an investigation.
Practical benefits
- — Outstanding conditions visible before lodgement
- — Gaps identified and resolved before they reach council
- — Referral agency conditions tracked and followed up in time
- — Reduced outstanding matters letters from council
- — More confidence in application completeness at lodgement
- — Less pressure at settlement stage
Frequently asked questions
What should a pre-lodgement review cover?
A pre-lodgement review should work through each condition in the DA approval and confirm: that the condition has been addressed, that the evidence on file is current and sufficient, that external party approvals or responses have been received, and that financial conditions — contributions, bonds — have been paid or lodged and receipts are on file.
How early before lodgement should a quality control review be done?
Early enough to fix what you find. For most projects, a review two to four weeks before intended lodgement gives the team enough time to resolve gaps without delaying the lodgement date. Conditions that require external party action — certifications, authority sign-offs — may need even more lead time.
Who should conduct the pre-lodgement review?
The review is most effective when done by someone who has oversight of the full condition schedule — typically the surveyor or town planner leading the plan sealing application. On larger projects, having a second person review the application before lodgement catches things that the primary preparer misses through familiarity.
Can you meet with council before lodging a plan sealing application?
Yes, and for complex projects or applications involving ambiguous conditions, a pre-lodgement meeting can be valuable. It allows the project team to confirm council's expectations before the formal application is submitted and reduces the risk of submitting documentation that council considers insufficient.
Pre-lodgement quality control is not a complex process. It requires a clear condition register and enough lead time to resolve what's found. The projects that do it consistently have fewer outstanding matters, faster plan sealing, and less pressure at the point when it matters most.
Learn more about Planease
Live condition tracking that supports quality control before plan sealing lodgement.
See how Planease works →