Avoiding Requests for Additional Information: What a Complete DA Package Looks Like

One of the most common frustrations I hear from applicants is that a development application has been lodged, only for Council to come back weeks later with a request for further information (RFI). Sometimes the issue is minor. At other times, it reveals that a key report is missing, or worse — plans and reports are telling different stories.

The problem isn't usually that you're missing documents. It's that the documents you do have aren't aligned with each other. A complete DA package doesn't mean “thick”. It means coordinated.

The Real Problem: Disconnected Documents

The most common DA failures aren't about what's absent — they're about what's inconsistent. For example:

• Traffic Report vs. Site Plan: Report assesses 20 car spaces, but the site plan shows 18.

• Acoustic Report vs. SEE: Report assumes daytime operation only, but the SEE describes evening deliveries.

• Bushfire Report vs. Landscaping: Recommended asset protection zones conflict with proposed planting.

• Stormwater Plan vs. Architectural Drawings: Layout changed during design revisions, but the stormwater plan wasn't updated.

These gaps create uncertainty for Council. When numbers, layouts, hours or assumptions don't match, assessment officers can't proceed — and that's when RFIs kick in.

What a Complete DA Package Usually Includes

The exact requirements will depend on your proposal, but a well-prepared DA package commonly includes:

1. A clear project description. What is proposed, where it will occur, how it will operate and whether staging is involved.

2. Consistent architectural, site and civil plans. Plans should clearly show boundaries, existing site features, proposed works, access, parking, landscaping, stormwater management, waste areas, services, signage and any demolition.

3. A planning assessment that addresses the correct controls. The SEE should assess the relevant LEP, DCP, SEPPs, section 4.15 matters under the Environmental Planning and Assessment Act 1979 and other relevant legislation.

4. Specialist reports targeted to the site constraints. Reports should respond to known or likely constraints such as bushfire, flooding, biodiversity, contamination, heritage, traffic, noise, odour, stormwater and servicing.

5. A clear operational description. For many non-residential proposals, this is essential. Council needs to understand hours, staffing, deliveries, vehicle movements, equipment, waste, lighting, noise, security and management measures — as a minimum.

6. An approvals and referral check. This should identify whether the proposal is integrated development, whether concurrence is required, and whether referral to agencies or other authorities may be relevant.

7. A response to likely community concerns. Where neighbour impacts are likely, the package should directly address privacy, visual impact, noise, traffic, lighting, amenity, landscaping and construction management.

The Statement of Environmental Effects Should Be Your Anchor

The SEE is often treated as a formality, prepared in a hurry once plans and reports are finished. That is never a successful approach.

A strong SEE should tie together every element of your proposal, such as:

• How bushfire recommendations have been integrated into the site layout

• How truck movements connect to parking, access and road authority requirements

• How operational details (hours, staffing, deliveries) align with acoustic and traffic assumptions

If your SEE reads as a disconnected summary rather than a cohesive narrative, Council won't understand the proposal — and that creates risk.

What to Check Before You Lodge

Before submitting, review your DA package against this checklist:

✓ Numbers match. Parking spaces, floor areas, setbacks and capacities etc. are identical across all documents.

✓ Assumptions align. Operating hours, delivery schedules and staffing levels are consistent in the SEE, acoustic report and traffic assessment.

✓ Constraints are integrated. Bushfire APZs, flood levels and biodiversity values etc. have been translated into actual design changes, not just referenced.

✓ Referrals are identified. Integrated development requirements are flagged.

Key Takeaways

1. Alignment beats volume. A thinner, well-coordinated DA moves faster than a thick, inconsistent one.

2. Use the SEE as your narrative anchor. It should explain how every specialist recommendation has been built into the design.

3. Check for misalignments early. Number mismatches, assumption conflicts and outdated drawings are the most common RFI triggers.

4. Know what a complete package includes. Use the seven-item list above as your baseline for bringing your DA package together.

The Bottom Line

Requests for further information aren't always avoidable — some issues genuinely emerge through assessment. But many can be eliminated through better coordination between your design team, specialists and planning consultant.

Completeness is not just an administrative requirement. It's a project risk-management tool.

Need help coordinating your DA package? At Blue Sky Planning & Environment, we help clients align specialist inputs and prepare clear, practical planning documentation that stands up to scrutiny across regional and rural NSW. Get in touch to discuss your project.

---