How to Conduct a Public Hearing on Your Agency’s Drone Policy
Australian agencies often call this a community consultation, town hall or listening session, even when evidence is given on the record. That familiar language makes the process easier to understand. Promote it through council libraries, local newspapers and community radio so residents recognise it as a “have your say” event rather than a parliamentary-style hearing.
This guide explains how to conduct a public hearing on your agency’s proposed drone operations policy. Treat the event as a test of evidence, proportionality and public trust, not a product demonstration. Participants need to know what the agency can change, which rules apply, what will be published and how submissions affect the final policy.
Selecting a format people will recognise
Match the engagement method to the decision. A broad policy or contested deployment benefits from a hearing, while technical procedures may work better in smaller scenario workshops.
| Format | Best use | Participation | Main limitation |
|---|---|---|---|
| Public hearing | A contested policy | Spoken evidence and questions | Prepared speakers may dominate |
| Community workshop | Scenarios and safeguards | Collaborative testing | Hard to record formal positions |
| Written submissions | Evidence from people unable to attend | Considered individually | No real-time clarification |
| Open information session | General questions and materials | Low-pressure access | Limited dispute resolution |
Use one session with several methods rather than forcing every concern into speeches. Accept written and audio submissions, reserve time for less experienced speakers, and publish the same answers given at the event. This suits a national market where agencies, councils, suppliers and residents operate at different scales.
Setting the scope before promotion
Publish a plain-English draft, an executive summary, the proposed operating area and a non-confidential outline of aircraft types and missions. State whether launch and landing areas, routine photography, thermal imaging, automated tracking and data sharing are in scope. Give participants the legal baseline and the decisions still open to change.
Regulation is layered. The Civil Aviation Safety Authority sets national flight-safety requirements, including registration, operator authorisations and airspace restrictions, while states and territories apply different privacy, surveillance, records and information-access laws. NSW and Victoria, for example, operate under distinct privacy and public-records regimes, and Commonwealth privacy legislation does not displace state regimes for state police. Local councils may also regulate land use or particular sites. The hearing should identify which authority owns each answer.
The Australian supply market is fragmented. Agencies often buy aircraft, training, analytics, maintenance and insurance through tenders, while local operators may work closely with regional services. Keep vendors in the same evidence queue as residents; hearings are for scrutiny, not sales pitches. Melbourne and Sydney residents may seek clearer urban flight corridors, while regional councils in Queensland or Western Australia may focus on bushfire, flood and remote-response value.
Explaining operations, privacy and accountability
Explain that “drone”, remotely piloted aircraft (RPA) and small unmanned aircraft system (sUAS) describe the same broad technology. Then say who may fly, why, when and under what limits; distinguish a routine flight, an emergency deployment and planned surveillance. Use a simple map without sensitive locations, and present anonymised examples of public benefit. Legal compliance alone does not settle whether an operation is proportionate.
Attach or summarise the privacy impact assessment before taking evidence. Explain the data management plan: what is collected, how long it is kept, who can view it, whether facial recognition or automated identification is prohibited, and when incidents are reported. State the applicable state or territory law, complaint route and independent oversight arrangement. If footage is supplied to another agency, describe the approval test and audit trail.
Make accountability operational. Name the accountable executive, remote pilot, privacy officer and public contact; require training, mission logs and post-flight review. Publish measures such as response-time improvements, complaints, misuse reports, data breaches and missions using unnecessary personal data. Residents need standards they can test over time.
A practical checklist for an accessible public hearing
Design participation around Australian communities. Hold sessions outside shift hours and repeat them at accessible daytime times. Use venues such as council chambers, libraries, community centres or regional showgrounds. Offer telephone, paper and accessible online options rather than assuming reliable connections across northern Australia. Work with Aboriginal and Torres Strait Islander representative organisations early, allowing adequate time and local facilitation.
Use an independent chair, disclose conflicts and publish the agenda, time limits and method for accepting written evidence. Allow questions on notice for people who cannot attend, publish rulings on relevance, and separate personal information from submitters’ names. Record proceedings when participants consent and explain any limits on public release.
- Publish the draft policy, hearing notice and submission guide at least four weeks ahead, with dates and access details repeated in local media.
- Provide a one-page summary, large-print material, interpreters, hearing loops and accessible digital documents on request.
- Test the agenda with residents, emergency workers, aviation experts, privacy specialists and agency staff.
- Reserve unallocated speaking time for rank-and-file workers and residents who have not submitted in advance.
- Keep aircraft and vendors away from the decision panel unless participants are discussing a specific operational proposal.
- Use a secure note-taker to record commitments, questions and owners without recording confidential operational details.
Any live flight display needs a separate risk assessment, defined flight area, exclusion zone and regulator-compliant plan. It should not distract from consultation or expose data-collection practices before safeguards are agreed.
Turning feedback into accountable drone operations
Publish what happened. Within a stated period, release accepted submissions where lawful, a summary of evidence, responses to key questions and the reasons for policy changes. Note points the agency cannot adopt and explain the legal, safety, budget or operational reason. A tracked revision showing draft wording beside the final version is more transparent than a clean document with no record of change.
Set an implementation clock. Publish a risk register, training milestones, compliance audits, complaint and breach procedures, and a date for the first public report. Assign each action to a named owner and revisit unresolved issues at a follow-up session. Local councils, unions and community groups can then check progress without reconstructing the decision from meeting minutes.
Publish the consultation plan and hearing details now, and invite residents, workers, privacy advocates, aviation representatives and emergency-service partners to put evidence on the record. Make the route from feedback to revised policy visible, so the agency earns trust through a documented, repeatable process rather than broad assurances.