Drone Pre-Flight Briefing for Commercial Operations: What Should Be Documented?

By UAV Meteo Team · Updated 9/26/2026 · 6 min read

On a commercial job, the question after a flight — or after a flight that didn't happen — is rarely "did you check the propellers?". It's "what did you know when you made the call?". A client asks why the survey was postponed; a site supervisor wants to know the flight was planned properly; an insurer or your own team reviews an incident. A pre-flight briefing is the document that answers.

This guide explains how a briefing differs from a checklist and from an authorisation, what a good one records, and how to produce and share one in a few minutes. You can create one for free with the Drone Pre-Flight Brief tool.

Checklist, briefing, authorisation: three different things

Checklist Pre-flight briefing Authorisation
Answers Is the aircraft ready? Is the operation sensible right now? Is the operation allowed?
Covers Airframe, batteries, props, firmware, controller, return-home settings Weather, wind at height, rain timing, visibility, daylight, airspace status, NOTAMs, limitations, decision Category, zone permission, operator/pilot credentials
Who decides The pilot, item by item The pilot (and often the client) The aviation authority or airspace manager
Kept as Ticked list Timestamped record Official document

They complement each other. A perfect checklist doesn't tell you a squall line arrives in 40 minutes; a thorough briefing doesn't make a restricted zone legal. Keep all three.

What a professional briefing should record

The plan

  • Location — site name and coordinates.
  • Planned window — date, start and end in local time.
  • Aircraft — model and the limits you're flying to (wind, gusts, temperature).
  • Maximum height and the operation (inspection, survey, filming…).

The weather, for the window — not just "now"

  • Wind and gusts at the surface.
  • Wind at operating height. At 100–120 m it is often 1.5–2 times the surface wind; see why wind can be stronger at 120 m.
  • Precipitation — probability for the hours, and on showery days the timing from a 15-minute forecast and radar. See can you fly a drone in the rain?.
  • Visibility and cloud, temperature, daylight for the whole window, and space weather (Kp) if GNSS accuracy matters.
  • An observation — what the nearest official station is actually measuring. If it reads stronger than the forecast, say so. See weather station vs forecast.

Airspace and notices

  • Airspace status from your national source: clear, restricted with authorisation (and its reference), or restricted without.
  • NOTAMs affecting the area and time — including temporary restrictions for events, cranes, other aircraft activity.

The decision

  • Go, go with limitations, or no-go — and the limitations (max height, max wind, stop time, standby for rain).
  • Decision factors — the few things that drove the call.

Sources and timestamps

The single most overlooked item. "Wind 6 m/s" is meaningless without when and from where. Record the forecast source and time it was retrieved, the observation time, and when you checked airspace and NOTAMs.

A sample brief

PRE-FLIGHT BRIEF — Harbour crane inspection
26 Sep 2026, 10:30–11:15 local
Aircraft: DJI Mavic 3 Enterprise · max 90 m AGL

DECISION: GO WITH LIMITATIONS — max 60 m, land by 11:10

DECISION FACTORS
• Wind aloft (120 m): caution — 11.2 m/s
• Gusts: caution — 12.5 m/s
• Rain forecast within 10 km from 11:20
• Nearest airport measured 1.6 m/s more wind than forecast

WEATHER (rated for the aircraft)   Wind 6.2 m/s · Gust 12.5 · Vis 18 km · 14°C
RAIN        Nearest rain 25 km W, moving E ~30 km/h; dry at site until 11:20
OBSERVATION LGAV 7 km, 10:20: wind 7.8 m/s, gusts 13 m/s
AIRSPACE    Restricted (port CTR) — authorisation ref. XYZ-1234
NOTAMS      1 recorded — crane operations, reviewed

SOURCES     Forecast fetched 10:02 · Rain 10:02 · METAR observed 09:50
            Airspace/NOTAM/decision entered by pilot 10:02

Notice what it communicates to a client in ten seconds: the flight is going ahead, but lower and shorter than planned, and why.

Sharing it with clients and site supervisors

  • Send a link, not a screenshot. A link to a read-only brief can't be cropped or edited, and shows the timestamps.
  • Keep it immutable. If conditions change, make a new brief rather than editing the old one; the sequence of briefs shows how the decision evolved.
  • Make a PDF for your records if your contract or local rules require you to keep documentation for a set period.
  • Brief the no-go too. A documented "no-go — gusts 15 m/s at 120 m" protects you when a client asks why the job moved.

The Pre-Flight Brief tool does this: it fetches the forecast, 15-minute rain data and the nearest airport report itself at the moment you create the brief, rates the window against your aircraft, adds your airspace, NOTAM and decision notes, and gives you a frozen, printable link. From Flight Window, one button turns a checked window into a brief.

Is a briefing legally required?

It depends on where you fly and in which category. Some regulators require operational procedures, risk assessments or flight records for certain operations; others leave it to the operator. A briefing is good practice everywhere, but it does not replace registration, pilot competency, operational authorisations or your authority's own record-keeping requirements. Check your national aviation authority's rules for your category of operation.

FAQ

How long before the flight should I create the brief?

Close to take-off — within an hour is ideal — so the weather, observation and rain timing reflect what you'll fly in. For planning a day ahead, create one the day before and a fresh one on site.

What if conditions change after I've briefed?

Stop and re-brief. Changing wind, an approaching shower or a new NOTAM is exactly what a fresh brief is for; keep both.

Should the client see the full brief?

Usually yes — it's short, it shows the decision was made on evidence, and it sets expectations about limitations. Leave out anything confidential from the free-text notes.

Related: visual line of sight rules, NOTAMs for drone pilots and why a flight log matters.

Sources

This guide is general information for planning, not legal advice or aviation regulation.