Every general contractor documents progress. The question is whether that documentation is a superintendent’s phone photos scattered across email threads, or a consistent monthly aerial record that owners, lenders, and subcontractors can actually use.

Here’s what drone progress documentation looks like when it’s done properly on a Bay Area project — and what it takes to run it here specifically.

What a progress documentation program actually delivers

A one-off flyover is a photo shoot. A documentation program is a repeatable capture executed the same way every visit, so month 14 is directly comparable to month 2. A typical package per visit:

  • Orthomosaic map — a stitched, top-down, to-scale image of the entire site. This is the workhorse: overlay it against the site plan, measure laydown areas, verify as-built locations against drawings.
  • Fixed-position obliques — the same 8-12 angled shots from the same GPS positions and altitudes every visit. Lined up in sequence, they become the project’s time-lapse and the exhibit every owner meeting opens with.
  • Full-site photo set — high-resolution coverage of active work areas, utility corridors, and stockpiles.
  • Short video orbit — for stakeholder updates and marketing; a 60-second orbit communicates more than a slide deck.

Delivered within a day or two of the flight, organized by date, in whatever structure your team already uses — most of our clients pull them straight into Procore, Autodesk Construction Cloud, or a shared drive with a naming convention.

Why cadence beats coverage

The value compounds when flights are regular. Monthly is the standard cadence for most vertical projects; two-week intervals are common during sitework and structural phases when conditions change fast. What regular cadence buys you:

  1. Dispute protection. When a delay claim or differing-site-conditions argument surfaces, a dated aerial record of exactly what was in place — and when — is the cheapest insurance a project carries.
  2. Draw support. Lenders increasingly expect visual verification with pay applications. A dated orthomosaic answers the question before it’s asked.
  3. Remote stakeholders. Bay Area projects routinely have owners, investors, or design teams out of state. Consistent aerials replace a plane ticket.
  4. Logistics planning. Crane placement, laydown reshuffles, delivery routing — decisions that are easier over a current to-scale site image than a six-month-old survey.

The Bay Area wrinkles

Two things make running a documentation program here different from, say, Phoenix.

Fog and marine layer. Summer mornings on the west side of San Francisco and along the coast are frequently socked in. It burns off — usually by late morning — and inland sites (San Jose, Walnut Creek, Tri-Valley) are barely affected. A local operator builds the capture window around the microclimate of your site rather than promising 8 AM flights everywhere. What matters for comparability is consistent sun position, not a consistent clock time.

Airspace. Most urban Bay Area sites sit in controlled airspace — beneath the SFO Class B shelves, or inside Oakland’s and San Jose’s Class C. For a recurring program this is mostly a solved problem: LAANC authorization is fast and repeatable at standard grid altitudes, and a standing monthly flight gets planned once, then executed. The exceptions — near-runway zero grids, stadium event TFRs around Oracle Park and Chase Center — are exactly the things to surface in the first planning conversation, not discover on flight day.

What it costs, roughly

Pricing scales with site size, deliverable depth, and cadence — but the framing that matters is per-month cost against the project budget. A monthly documentation program on a typical urban infill project runs a fraction of one percent of construction cost. Weighed against a single avoided dispute, a smoother draw process, or one prevented re-survey, programs pay for themselves quietly and repeatedly.

What to ask a provider before you start

  • Are captures flown from repeatable positions (saved flight plans), or hand-flown differently each visit?
  • What’s the turnaround commitment from flight to delivery?
  • How do they handle airspace on this specific parcel — and can they show you the LAANC grid for it?
  • Can deliverables land in your PM platform, not a link that expires?
  • Are they FAA Part 107 certified and insured at your GC’s required limits?

Any professional operator answers these in one email. If the answers are vague, keep looking.

We run recurring progress documentation programs across the Bay Area — same positions, same deliverables, every month, delivered into your workflow. If you have a project breaking ground, the best time to set the baseline flight is before the first excavator shows up.