Making your objection count

A development objection is not a petition. It is not a neighbourhood diary. It is not a competition to see who can sound the angriest.

The best objections do something much more useful. They identify planning problems that Council can lawfully take into account, explain why those problems matter, and give the decision-maker a clear path to refuse, redesign or condition the development.

That is the difference between a submission that gets noted and a submission that changes the assessment.

In NSW, public submissions are part of the development assessment process, and the NSW Planning Portal provides pathways for the community to make submissions on exhibited applications. For State significant development, the NSW Government also identifies public exhibition and submissions as part of the assessment process.  

The practical point is simple: your submission should help the consent authority do its job.

1. Object on planning grounds, not just personal preference

Council is not deciding whether neighbours like the proposal. It is deciding whether the development should be approved under the planning controls and assessment framework.

That means objections should focus on matters such as height, bulk, scale, privacy, overshadowing, traffic, parking, stormwater, flooding, heritage, tree removal, streetscape, acoustic impacts, contamination, land use conflict, public interest and compliance with the local environmental plan or development control plan.

A submission saying “this development is ugly and we do not want it here” is easy to dismiss.

A submission saying “the proposed second-storey rear balcony creates direct overlooking into the principal private open space of 12 Smith Street, contrary to the privacy objectives in the applicable DCP” is much harder to ignore.

2. Start with the strongest point

Do not bury the lead under six pages of background.

If the proposal is too high, say that first. If the stormwater report is inadequate, say that first. If the driveway is unsafe, say that first. If the development is inconsistent with the zone objectives, say that first.

Council officers are busy. Panel members are busy. A strong submission should make the core issue obvious within the first few paragraphs.

A useful structure is:

“I object to the development for three reasons. First, the proposal produces unacceptable privacy impacts. Secondly, the traffic material does not properly assess vehicle movements from the basement driveway. Thirdly, the proposed built form is inconsistent with the desired future character of the street.”

That opening gives the assessor a map.

3. Make your submission different from everyone else’s

A common trap is for residents to send near-identical objections. This may show community concern, but it does not necessarily add much analytical weight.

Your submission should include site-specific evidence that only you can provide.

For example, instead of saying “traffic is already bad”, explain when the street becomes congested, where cars queue, whether garbage trucks already struggle to pass, where children cross, where sightlines are poor, and how the proposed access point interacts with those conditions.

Instead of saying “privacy will be affected”, identify the exact window, balcony, terrace or raised area that will overlook your living room, bedroom, backyard or pool.

The more specific the submission, the harder it is to treat as generic opposition.

4. Use the plans against the application

Many objections fail because they do not engage with the actual DA material.

Read the architectural plans, survey, shadow diagrams, statement of environmental effects, traffic report, arborist report, stormwater plan, acoustic report and any clause 4.6 variation request.

Then refer to them directly.

For example:

“The shadow diagrams appear to show additional overshadowing to the north-facing living room windows at 9 am and 12 noon on 21 June. The applicant’s Statement of Environmental Effects does not explain how this impact is acceptable.”

That kind of objection is useful because it identifies a gap in the applicant’s own material.

5. Do not exaggerate

Overstatement weakens good objections.

If a proposal will create some additional overlooking, do not say it will “destroy all privacy forever”. If traffic will be worse at school pick-up times, do not say the street will become “impossible to use” unless that can be demonstrated.

Decision-makers are trained to discount exaggeration. They are more likely to listen to calibrated, credible objections.

A good objector sounds measured, not theatrical.

The tone should be: “This is the planning problem. This is the evidence. This is why the impact has not been properly addressed.”

6. Identify missing information

Sometimes the best objection is not “refuse the DA”. It is “Council cannot safely approve the DA on the material presently before it.”

That is particularly useful where the application lacks proper technical support.

For example, you may say the DA should not be determined until the applicant provides a swept path analysis, updated stormwater design, contamination assessment, arborist impact assessment, acoustic report, view analysis or amended shadow diagrams.

This approach is powerful because it attacks the adequacy of the assessment, not just the outcome.

It also gives Council a practical reason to request further information.

7. Link impacts to controls

The strongest submissions connect real-world impacts to planning controls.

Do not simply say “the building is too bulky”. Identify the height control, floor space ratio, setback control, landscaped area requirement, privacy control, solar access control, heritage provision or desired character statement.

The legal machinery does not need to dominate the submission, but it should support it.

For example:

“The proposal is not merely larger than adjoining dwellings. Its height, wall length and upper-level setbacks produce a built form that is inconsistent with the DCP’s desired streetscape outcome for this part of the street.”

That is more useful than a general complaint about size.

8. Offer practical alternatives

A sophisticated objection does not always need to demand total refusal.

Sometimes the better strategy is to identify amendments or conditions that would reduce the impact.

For example, you might ask for the deletion of a rear balcony, obscure glazing to a side-facing window, increased side setbacks, retention of a significant tree, relocation of an air-conditioning unit, amended driveway design, reduced operating hours, acoustic fencing, or a revised stormwater solution.

This can make the submission more persuasive because it shows you are not simply opposed to all development. You are identifying the specific changes needed to make the proposal acceptable.

That distinction matters.

9. Think ahead to appeal

If Council refuses the DA, the applicant may appeal to the Land and Environment Court. The Court’s development appeal guidance explains that applicants can appeal determinations of development applications, including refusals.  

That means a good objection should be written with the possibility of litigation in mind.

Council may later rely on resident evidence. A clear, factual, site-specific objection is more useful than an emotional submission that cannot be translated into planning contentions.

Write as though your submission may later be read by a commissioner, planner, lawyer or expert witness.

That does not mean making it legalistic. It means making it disciplined.

10. Submit early, but update if needed

Do not wait until the last hour of exhibition.

Submitting early gives Council time to understand the issue. It may also allow you to make a further submission if amended plans or new reports are lodged.

For major projects and State significant development, the NSW Planning Portal provides formal “Have Your Say” submission pathways.   For local DAs, councils generally provide their own DA tracking and submission systems, and some councils expressly note that the relevance and content of a submission can affect how much weight it receives.  

The timing matters because a late, rushed objection often reads like panic. A timely, organised objection reads like evidence.

The practical takeaway

A strong objection is not the loudest objection. It is the most useful objection.

It tells Council what the real planning problem is, where it appears in the plans, which control or impact is engaged, why the applicant’s material is inadequate, and what should happen next.

The best submissions are specific, evidenced, proportionate and different from the pile.