General engineering
AuraScore 79/100

Autonomous Site Survey Drone Flight Readiness Checklist

Engineering checklist for preparing, executing, and auditing automated photogrammetry and LiDAR drone surveys on active construction sites.

Use this checklist before dispatching autonomous survey drones for high-precision volumetric and progress tracking on civil jobsites. It verifies sensor health, ground control network calibration, and real-time flight telemetry safety.

Template

Role: Senior Robotics and Geomatics Systems Engineer overseeing automated reality capture fleets on high-density construction sites.

Context

  • Active site identifier: {{site_identifier}}
  • Autonomous drone platform: {{drone_platform_model}}
  • Survey payload instrumentation: {{survey_payload_type}}
  • Ground control points network: {{ground_control_points_count}}
  • Site airspace classification: {{airspace_classification}}
  • Required spatial resolution tolerance: {{resolution_tolerance_cm}}

Task

Produce an operational pre-flight, in-flight telemetry, and post-mission raw data verification checklist to ensure autonomous reality capture meets strict civil survey standards while operating safely over an active construction zone.

Method

  1. Review site airspace constraints defined by {{airspace_classification}} and dynamic crane exclusion zones at {{site_identifier}}.
  2. Develop hardware and propulsion pre-flight diagnostics for the {{drone_platform_model}}.
  3. Formulate calibration steps for {{survey_payload_type}} including IMU alignment, sensor warmup, and lens calibration.
  4. Establish RTK/PPK base station connectivity and verify distribution across the {{ground_control_points_count}} ground markers.
  5. Define flight path parameter checks including speed, overlap percentages, and altitude ceilings to achieve {{resolution_tolerance_cm}}.
  6. Detail real-time geofence and failsafe triggers (e.g., lost link, battery sag, unmapped crane boom intrusion).
  7. Outline immediate post-flight data validation checks to confirm zero data corruption, complete coverage, and valid GNSS log files.
  8. Compile all validation checkpoints into chronological mission segments.

Constraints

  • Flight parameters MUST NOT permit autonomous launch without active RTK differential fix lock.
  • Checks MUST mandate physical site perimeter clearances and active crane operator radio confirmation.
  • All tolerances must guarantee output data aligns within {{resolution_tolerance_cm}}.
  • Maintain between 15 and 20 total checklist checkpoints.
  • Use a standard flight-readiness format with clear go/no-go gates.

Output format

  • Mission Envelope: Header listing {{site_identifier}}, {{drone_platform_model}}, and {{survey_payload_type}}.
  • Gate 1: Hardware & Airspace Pre-Flight Checks (5 items)
  • Gate 2: Geodetic Control & Sensor Calibration (4-5 items)
  • Gate 3: Live Mission Telemetry & Failsafe Parameters (3-4 items)
  • Gate 4: Post-Touchdown Data Integrity & QA (3-4 items)
  • Format: [ ] [Gate.Item] Verification Item | Protocol/Standard | Go/No-Go Standard | Recorded Value

Self-review

  • Confirm all 6 context variables appear naturally in the method and constraints.
  • Check that Go/No-Go criteria are strictly quantitative and non-ambiguous.
  • Ensure safety checks account for active jobsite hazards like cranes and personnel.
AuraScore breakdown
79/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

developers
developers-general
real-estate-construction
geomatics
drone-survey
reality-capture