Learn how to build a drone construction progress report for solar projects with planned vs actual progress, S-curves, deviations and actions.
Karthik Mekala
CMO
Published on
Drone flights are a regular part of building a utility-scale solar project, and each one produces an orthomosaic, aerial photos or a PDF of the site. For the project manager, the question that matters is whether the project is on schedule, and which blocks or activities are falling behind.
A drone construction progress report is a practical way to answer it. A good one shows current site conditions, compares actual work against the project plan, and gives every stakeholder the same view of progress. What makes it useful is the link between visual evidence and measurable progress, planned milestones and clear next steps.
This guide covers what a useful report contains, how to build one step by step, and how SenseHawk turns drone data into reports project managers act on.
A drone construction progress report is a structured record of site conditions and construction activities, built from drone imagery, aerial mapping and progress analysis. It tells the project manager what has been completed since the last report, where work is behind plan, and what needs attention next.
It is the main output of construction progress monitoring. Because one flight covers the whole site, the report gives a consistent, site-wide view that manual walkdowns can’t match on a large solar project. Field inspections still matter, but the PM no longer depends on them alone to understand progress.
Most solar EPCs already fly drones. Getting a report out of each flight that a PM can act on is harder, and drone reports often fall short for three reasons.
An orthomosaic or a photo gallery shows what the site looks like. It doesn’t tell the PM how many piles went in this week, what share of tracker installation is complete, or how that compares with plan. The PM has to work those numbers out, usually by counting, measuring and cross-checking the schedule in a spreadsheet. If the PM has to interpret it, it isn’t a report yet.
Many drone reports are still compiled by hand into a weekly PDF. By the time it reaches the project team, the data is several days old and crews have moved on. Decisions get made on stale information or on someone’s best guess. That has a cost: in FMI and PlanGrid’s 2018 Construction Disconnected report, poor project data and miscommunication accounted for 48% of all rework on US construction projects.
A count of 12,000 piles installed sounds like progress, but on its own it can’t be read as ahead or behind. It only means something when it is compared with the planned quantity for that activity, on that date, in the Primavera P6 or MS Project schedule. Schedule linkage is what turns counts into progress.
Aerial images give visual context, but they don’t tell a PM whether work is on schedule or where to step in. That takes a consistent reporting process, one that ties what the drone sees to project milestones, the schedule and open issues. Two jobs matter most.
Comparing each new capture with the planned activities shows what is complete, what is partly done and where work is drifting from the schedule. On a solar site, construction progress tracking usually covers:
Civil activities: Earthwork, fencing progress, SWPPP management and road layouts
Mechanical activities: Piling, tracker erection and module mounting
Electrical activities: DC and AC cabling, trenching and backfilling, and stringing
When each activity is measured the same way on every flight, the PM sees progress by activity and by area instead of one site-wide number.
Repeat surveys show where work has stalled. A block where the pile count hasn’t moved in two flights, racking waiting on piling, or trenching running well ahead of cabling all stand out when consecutive captures are compared. So do site conditions such as standing water or blocked access in one area. Spotting these early lets the PM assign corrective actions before the delay reaches downstream activities and milestones.
These six sections work as a reusable construction progress report template for solar builds. They are ordered the way a PM reads: status first, evidence next, actions last.
One screen with overall percent complete against plan, a red, amber or green (RAG) status for each major activity, and the top schedule risks. A PM should be able to stop reading here and still know where to focus this week.
TaskMapper BI dashboard showing overall project progress and installed quantities by activity, each with its share of total scope.
For each activity a drone can measure, show the planned quantity, the actual quantity and the variance:
Piles installed
Trench length
Tracker rows
Modules installed
Cut and fill volumes
The units have to match the schedule’s units. If the schedule tracks piling as a count per block and the report shows percent of area, the comparison breaks.
An S-curve plots cumulative planned progress against cumulative actual progress over time. When the actual curve sits below the planned curve, the project is behind. When the actual curve starts to flatten while the planned curve keeps climbing, production has slowed and the next milestones are at risk. The trend across several reports tells the PM more than any single week’s number.
A colour-coded map of progress by block, laid over the latest orthomosaic, shows lagging areas at a glance. One annotated map does more than a gallery of photos. It shows where the problem is, and the PM can open the imagery for that block when they need the detail.
AI-detected progress on a drone map in TaskMapper, colour-coded by construction stage, from predrilling and piles to trackers and modules.
This is a list of everything that doesn’t match the plan: deviations from the IFC layout, work done out of sequence, and quantities that were planned but missed. Each entry should be geo-referenced and time-stamped. This record is what settles percent-complete disputes with contractors, because both sides can see what was there, where and when.
Every flagged issue gets an owner, a due date and a link to a task or non-conformance report (NCR). The next flight confirms whether it was closed. This section is what turns the report into something the team uses, because every finding leads straight to a follow-up.
A repeatable process keeps reports consistent from one cycle to the next, cuts manual reporting time and makes progress comparisons reliable. It comes down to five steps, from defining what the report is for to sharing it with stakeholders.
Start with what the report needs to help the PM judge: schedule adherence, completed work, site changes or construction risk. Map each goal to the milestones it supports and the site areas that need watching. If mechanical completion of Block 3 is the next milestone, for example, the report should track piling, tracker and module progress in Block 3 specifically.
Schedule flights just before each reporting cycle, and use the same flight parameters every time so that orthomosaics and digital elevation models (DEMs) can be compared from one flight to the next. Flight frequency usually follows the construction phase, with more frequent flights during earthwork and piling. For more on capture and processing, see Tracking EPC Milestones on Solar Projects with Drone Construction Monitoring.
Compare the latest flight with the previous one, with the IFC design layout and with the schedule to measure visible progress. Set completion rules before the first report and keep them fixed, such as whether a pile counts once it is driven or only once it has been inspected and accepted. Fixed rules keep the numbers consistent across reporting periods and across contractors.
Relate what the drone shows to scheduled activities, milestones and known constraints, such as a late equipment delivery or an area that can’t be worked yet. Drone imagery is strong evidence of physical progress, but it can’t verify everything on its own. Schedule status and percent complete may need other project records, such as QA/QC inspections and electrical sign-offs, before work counts as done.
Bring the status summary, annotated map, planned vs actual comparisons, risks and open actions into the same format every cycle. Live dashboards serve stakeholders better than static PDFs: the numbers stay current, and the supporting imagery is one click away when someone wants to check a finding.
SenseHawk connects drone data to schedules, tasks and reporting on one map-based platform, the TaskMapper digital twin. It has supported more than 200 GW of solar and storage projects.
SenseHawk Drone Construction Monitoring processes drone imagery into orthomosaics, DEMs and terrain data, and most site surveys are available on the digital twin within 24 to 48 hours. AI detection picks up construction progress on the drone map, from pile counts and trench lengths to tracker and module installation, and civil workfronts such as roads and grading are tracked too. Terrain tools support cut and fill analysis, and overlaying the drone map on the IFC design shows deviations early. Progress and insights are filed automatically to the TaskMapper digital twin for reporting and dashboards, and a compare view puts two scan dates side by side.
TaskMapper imports schedules from Primavera P6 or MS Project and links them to L5 construction activities, such as individual pile driving or module mounting. Once progress sync is set up, drone and field updates flow into the schedule automatically, so S-curves and planned vs actual dashboards stay current without manual updates. Progress shows block by block on the map, and teams can require QA/QC verification before an activity is marked complete. When the report flags a deviation, it becomes an assigned task in the same platform, with an owner and a location.
NaaviX AI lets PMs ask questions of live project data in plain language, such as “Give me a summary of lagging electrical activities” or “Which activities are at risk of missing the month-end milestone?” It answers with map overlays, S-curves and trend charts, so the PM gets the view they need without building it in Excel.
A drone construction progress report earns its place when it answers schedule questions and assigns action. More imagery won’t help a PM who still has to work out percent complete and variance by hand. Build the report around status, evidence and actions, tie it to the schedule, and keep it current with every flight.
Request a SenseHawk demo to see how your drone data can become a progress report your team acts on.
How often should construction teams create drone progress reports?
Most teams match the report to their reporting cycle and the construction phase. Monthly flights are common early in a project, moving to weekly or more often during busy phases such as earthwork and piling, when progress changes quickly. Whatever the frequency, fly just before each reporting cycle so the report reflects current conditions.
What is the difference between drone construction monitoring and a drone progress report?
Drone construction monitoring is the ongoing process of flying the site, processing the imagery and measuring progress. The drone progress report is what the PM uses: a summary of status against the schedule, the evidence behind it and the actions that follow. Monitoring produces the data, and the report turns it into decisions.
What metrics should a solar construction progress report include?
Overall percent complete against plan, planned vs actual quantities for each activity (piles, trench length, tracker rows, modules installed and cut and fill volumes), S-curve trends, progress by block, deviations from the IFC layout, and open actions with owners and due dates.
Who should receive the drone construction progress report on a solar EPC project?
The EPC’s project and construction managers use it most. Planners use it to update the schedule, QA/QC leads work from the deviation log, and subcontractors receive the actions assigned to them. Owners, developers and their Owner’s Engineers usually get the status summary for milestone tracking.
If the PM has to interpret it, it isn’t a report yet.
Karthik Mekala
CMO
