A standard handover for Australian day and night drone teams
A handover procedure between day shift and night shift drone teams should transfer more than aircraft and batteries. It must transfer authority, situational awareness and an honest account of open risks. For Australian public-safety agencies, that means a repeatable routine suited to metropolitan patrols, regional stations and major events.
There is no single national operating model for police drone use. The Civil Aviation Safety Authority administers Commonwealth aviation rules, while state and territory police, privacy regulators, emergency services and councils apply their own laws, procedures and local airspace arrangements. Teams supporting events in Sydney or Melbourne, responding with the SES in regional Australia, or operating around Brisbane must check the requirements applying to their task rather than assuming another jurisdiction’s procedure can be copied unchanged.
A good handover also recognises that night operations create different risks. Darkness, reduced visibility, fatigue and changing weather can alter aircraft performance and crew judgement. The incoming team needs to know whether a flight was routine, marginal or completed under incident pressure, because a brief handover can otherwise hide unfinished risk.
The Centre for Unmanned Aircraft Systems in Public Safety publishes practical guidance for agencies integrating drones into emergency response. Its focus on training, lawful use, data governance and community transparency fits the handover problem: continuity depends on treating the aircraft, crew, information and mission as one accountable system.
Why handovers fail without a standard
Without a common procedure, crews rely on memory, hurried verbal briefings and separate spreadsheets. Australian workplace shorthand such as “all good” can sound reassuring while leaving an incoming officer unaware of a battery defect, low-light limitation or unresolved privacy issue. A missed handover then becomes an operational, legal and reputational risk.
Standardisation should define a minimum handover, not prescribe every flight. It creates shared terminology and a traceable record while allowing an incident commander or shift supervisor to add urgent information. This supports the public expectation of a “fair go”: lawful, consistent and accountable use of drone technology.
Set the handover boundary and ownership
Set the handover boundary around the operational period rather than relying only on clock time. Account for daylight-saving changes, continuous deployments and crews working across stations in NSW, Victoria or Queensland. The outgoing coordinator can remain available for a 15-minute overlap, while an active emergency response takes precedence over the routine briefing.
Name the outgoing UAS coordinator, incoming UAS coordinator and shift supervisor in the procedure. One person should speak, one should record the briefing and the supervisor should confirm unresolved actions. In smaller stations, roles may be combined, but accountability must remain explicit. The handover is not complete when the outgoing crew clocks off; it is complete when the incoming team accepts the aircraft status, tasking and custody of relevant information.
Build one handover record
The handover record should use one digital log with standard fields for aircraft identification, battery cycles, defects, maintenance status, payloads and flight hours. It should also identify the latest flight log, incident details, restricted areas, personnel involved and any action that remains open. A crew member should be able to distinguish an aircraft that is serviceable from one restricted to daylight or grounded pending repair.
Standard status terms reduce confusion across shifts. Definitions such as “serviceable”, “restricted”, “grounded” and “awaiting parts” should appear consistently in every log. Handover notes should also include geotagged media locations, approved storage links and the credentials needed to access them. Sensitive material should be referenced through secure systems rather than copied into informal messages.
Transfer the live operational picture
A face-to-face briefing is preferable, but an approved encrypted video call can support crews covering distant stations or specialist units. Critical details should be read back, especially aircraft defects, live tasking, damaged equipment and restrictions affecting the next flight. A written handover record remains the authoritative account when verbal descriptions differ.
Brief the incoming team on local conditions that can change after sunset. These include coastal winds, fog, temperature inversions, urban glare, construction activity and event-specific airspace restrictions. Crews should check the CASA Drone Safety app, relevant NOTAM information through AusAIRS and local notices before operating. The handover should also show whether the team is committed to a 000 call, supporting emergency services or awaiting tasking.
Protect sensitive information and evidence
Privacy duties differ across Australian jurisdictions. Depending on the agency and activity, the Australian Privacy Principles, NSW privacy legislation, the Victorian Privacy and Data Protection Act or Queensland privacy law may apply. The handover procedure should identify which rules govern each dataset and who may receive operational imagery, location records and incident intelligence.
Use role-based access, multifactor authentication and approved retention schedules. When material may support an investigation, record its case reference, original storage location, transfer time and custody details. Preserve the source file rather than relying on an edited copy, and log any access or export. A separate public-release process should determine what can later be shared with the community, particularly where faces, vehicles or private premises are visible.
Compare fragmented and standard practice
A compact comparison shows where consistency creates operational value:
| Handover element | Fragmented practice | Standardised practice |
|---|---|---|
| Accountability | Verbal transfer with unclear ownership | Named outgoing and incoming coordinators confirm acceptance |
| Operational status | Separate notes and informal messages | One shared log with defined status terms |
| Aircraft condition | Defects described from memory | Maintenance history, defects and restrictions recorded by aircraft ID |
| Sensitive information | Files shared through ad hoc channels | Approved system, access controls and documented transfer |
| Open actions | Incoming team infers what remains | Every open task is assigned and acknowledged |
Review the procedure at regular intervals. Measure record completeness, unresolved aircraft defects, handover-related corrections and crew feedback. A quarterly review should capture regulatory changes, incident lessons and differences between metropolitan and regional deployments before the next version is issued.
Put the standard into practice
Begin with a controlled pilot involving one metropolitan command and one regional deployment. This exposes differences in staffing, connectivity and operating tempo while keeping the scale manageable. Give every participating crew member access to the same template, and ask supervisors to assess each pilot handover against the required fields.
Use the Centre for Unmanned Aircraft Systems in Public Safety resources alongside agency policy, training material and state or territory legal guidance. The procedure should then be adapted for local airspace, privacy requirements, public-safety command structures and the equipment actually used by each agency.
Nominate the two handover coordinators today, issue the template at the next shift briefing and audit the first completed transition at the end of the month.