The question comes up in almost every conversation with a new project team: how often do we need to fly? The honest answer is that it depends on where you are in the schedule and what decisions you need to make next week. "Weekly" is a reasonable baseline, but it's not always sufficient, and it's sometimes more than necessary. Getting the frequency right means thinking about capture as a decision-support tool, not a documentation ritual.

The framing that makes this clearer: drone frequency is a function of your schedule buffer and your trade coordination risk. When you have three weeks of float on the next critical milestone and the active work is proceeding predictably, once-weekly capture is probably adequate. When you're within five days of float on a critical path activity and four subcontractor trades are supposed to be coordinating handoffs between floors, daily capture can give you information you can actually act on before the handoff window closes.

The Baseline Case: Weekly Capture

For most commercial construction projects in active framing, MEP rough-in, or interior build-out phases, once-weekly capture provides enough resolution to support the primary PM workflow: the OAC meeting, the 3-week look-ahead update, and pay application review. At weekly frequency, a seven-day deviation doesn't go undetected for more than a week — which is usually within the intervention window for most non-critical schedule activities.

Weekly also aligns naturally with how construction teams structure their work. The Monday morning crew count meeting, the Wednesday coordination meeting, the Friday look-ahead update — these rhythms mean that a capture flown Thursday afternoon feeds directly into Friday's meetings and Monday's decisions. The data doesn't sit stale for days before it's useful.

Weekly capture is adequate when the following conditions hold:

  • No critical path activity is within 10 days of its late-start date
  • Trade sequencing between floors has a buffer of at least 3-4 days between handoff activities
  • No active RFI or design deviation is pending resolution that affects upcoming work
  • Subcontractor productivity on current activities is within 10% of planned

When any of those conditions shifts, it's worth asking whether weekly is still enough.

When to Go Daily or Near-Daily

Daily capture — or capture every two days — becomes valuable during the schedule windows that carry the highest consequence for a slip. These are almost always critical path activities where float has been consumed or where the downstream trade sequencing is tight.

The clearest trigger is the pour cycle on a concrete high-rise. Post-tensioned deck pours on a typical commercial tower run on 5-to-7-day cycles per floor, and each pour cycle gates the next three to five trades: fireproofing, MEP sleeves and inserts, underfloor MEP, and eventually interior framing and overhead MEP rough-in. A one-day slip in the pour cycle on Floor 14 doesn't cause a problem on Floor 14 — it causes a problem on Floor 8 three weeks later when the framing crew arrives and the MEP sub hasn't completed the ceiling rough-in they needed clear deck to finish. Daily capture during active pour cycles lets you see a concrete placement that ran half a day short of its planned deck completion before the form stripping crew shows up expecting to strip and move on.

Other windows where daily capture pays off:

  • Steel erection during crane jump cycles: Tower crane jumps typically require 8-12 hours of downtime, and any steel erection behind schedule heading into a jump cycle compresses the window to make it up before the crane is repositioned at a height where certain areas become inaccessible for backfill work.
  • MEP coordination milestones before overhead close-in: The 72-96 hour window before a scheduled above-ceiling rough-in inspection is a high-value capture window. If MEP rough-in is incomplete or incorrect heading into that inspection, a failed inspection costs 5-10 days of rework scheduling on a floor that has probably already been committed to the drywall crew.
  • Exterior envelope installation: Curtain wall and cladding installation typically drives weather exposure, temporary heat requirements, and interior finish sequencing. Weekly capture often isn't granular enough to catch a panel installation that's running behind until it's already affecting interior work.

The Cost Argument for Appropriate Frequency

The pushback on daily or near-daily capture is usually cost. A drone flight has an operational cost — pilot time, processing time, data storage — and on a 200-unit residential tower or a mid-size commercial office build, the direct cost of daily capture for a month adds up. The right way to think about this is capture frequency as a variable that should track your schedule risk exposure, not a fixed setting for the project.

Most projects have four or five high-intensity schedule windows — typically lasting two to four weeks each — where the consequence of a schedule deviation is highest and the intervention window is shortest. Outside those windows, the consequence of a one-week detection lag is modest. Using daily capture during those five windows and weekly capture the rest of the time produces a capture frequency profile that concentrates data collection where it adds the most value.

The practical implementation of this is a capture calendar tied to the CPM schedule's critical path activities. As activities near their late-start dates, capture frequency increases. As float rebuilds, it decreases. Your drone operator needs that schedule visibility to plan their flight schedule three to four weeks out — they're not going to be available same-day if you decide Thursday morning that you need a Friday capture.

What Weekly Capture Misses (And What That Costs You)

It's worth being explicit about the failure mode of weekly-only capture during tight schedule windows. The scenario: a critical path concrete pour is planned for Monday. Weekly capture on Friday shows the formwork at 85% complete with two days of forming work remaining. The field report says "on track." Monday arrives, the formwork isn't ready, the pour gets pushed to Wednesday. The concrete sub works overtime to make it up. You find out about it on the following Friday's capture — nine days after the original plan date. By that point, the fireproofing crew scheduled to mobilize Thursday has already been on-site for two days with limited access, and the overhead MEP rough-in inspection scheduled for the following week can't happen on schedule.

That nine-day detection lag is a cost. Not necessarily a catastrophic one, but a real one measured in extended overhead, coordination burn, and subcontractor mobilization/demobilization. A capture on Tuesday morning — two days after the planned pour — would have shown the delay immediately, while recovery was still achievable without chain-reaction disruption.

We're not saying weekly capture is inadequate — for most of the project's duration it's sufficient. The point is that frequency should vary with risk exposure, and the risk exposure is a function of where you are in the CPM schedule relative to critical path float. Treating drone frequency as a fixed cadence ignores most of the information that would tell you when to increase it.

Practical Scheduling: Aligning Capture with Meeting Rhythms

The mechanical details of flight timing matter more than people usually think when setting up a monitoring program. A capture that completes on Friday afternoon, processes overnight, and is available in the PM's dashboard Saturday morning isn't as useful as one that completes Wednesday, processes Thursday morning, and is available before Friday's coordination meeting. The data has to arrive within the decision cycle it's intended to serve.

Common patterns that work well in practice:

  • Tuesday/Wednesday baseline capture: Processes by Thursday, informs Friday OAC or coordination meeting. PM gets updated floor-level status before the weekend work planning meeting with field supers.
  • Pre-inspection capture: Fly 48-72 hours before any scheduled inspection or pour. This gives enough time to catch a problem and make a call on whether to proceed or request a delay without the subcontractor already staging equipment on-site.
  • Pre-pay-app capture: Fly 5-7 days before the payment application cutoff date. Processed data available for PM cross-reference before payment application review meeting with owner.

The capture frequency question is ultimately a resource allocation question. Where in the schedule are the decisions that most need reliable, current progress data? Concentrate your capture bandwidth there. For the periods where the schedule has room to absorb a detection lag, weekly is sufficient and daily is overcapture. That judgment call is the PM's job — the data capture infrastructure just needs to be flexible enough to execute on it.