Procore + Drone Data: What Superintendents Actually Do With the Ortho Once It Lands

A bi-weekly ortho is only useful if the superintendent opens it. Most never do. The ortho lands in a folder, the link gets forwarded once, and by Friday morning it's buried under three days of RFIs. The drone provider delivers a ZIP, calls it done, and bills the next month. Nobody wins.

Procore changes that — but only if you deliver into it the right way.

The real problem: a data folder no one checks

The failure mode isn't a missing file format. The failure mode is that the ortho, the point cloud, and the progress report live in your folder on your cloud, behind a link the superintendent clicked once and forgot. Meanwhile, the same superintendent is logging into Procore three times a day because that's where RFIs, submittals, daily reports, and photos already live.

A peer pilot put it bluntly on a recent industry call: when a superintendent asks for "the file," what they mean is the PDF they can pull out of Procore without making a phone call. They don't want your DXF. They don't want your LAZ. They want the thing that shows up in the Photos tool next to the daily log, where they're already looking. Anything else is an extra step they won't take.

That's the integration problem in one sentence: drone data has to meet the superintendent where they already are, not drag them to a new place.

What Procore actually consumes

Procore isn't a GIS platform. It's a project-management platform that happens to render images and PDFs well. The list of formats that survive a round-trip into Procore without losing context is short:

• GeoTIFF orthomosaics — drop into the Photos tool or Documents folder with their world-file (.tfw) intact. AutoCAD Map 3D and Civil 3D read the .tfw natively; the ortho lands on the survey grid without manual registration.
• PDF progress reports — the format a superintendent forwards to the owner without thinking. Annotated side-by-side comparisons, change-detection callouts, timeline strips. This is the deliverable that gets opened.
• JPEG / PNG thumbnails — quick-preview tiles that link to the full ortho. Without these, nobody scrolls through a 200MB GeoTIFF in Procore's web viewer.
• .e57 / .rcp point clouds — Autodesk ReCap / Revit link these as coordination models. This is where the VDC manager lives, not the superintendent. Different audience, different deliverable.

The point: Procore is the front door for the field team. Autodesk is the front door for the VDC team. Your delivery has to serve both — and know which deliverable goes to which door.

The hand-off that actually sticks

Here's the workflow that works on a bi-weekly cadence:

1. Flight day AM. Same SD card workflow, same base station, same GCP layout. Nothing changes on-site.
2. Overnight processing. Pix4D batch, QA against the previous cycle's GCPs, DEM/DTM, ortho, change-detection overlay, PDF report. Internal target: 12 hours from wheels-up to deliverable. Client-facing SLA: 24–48 hours, so deliverables land on the morning OAC meeting table.
3. Procore upload by 6 AM. Folder convention Drone / YYYY-MM-DD / [Ortho | Report | Point Cloud]. Photos tool gets the JPEG thumbnail + PDF report. Documents gets the GeoTIFF and the .e57.
4. Tag the OAC meeting. A link in the meeting agenda under "Progress Documentation" — not buried in an email thread.
5. VDC hand-off in parallel. The .rcp point cloud goes to the BIM lead through Autodesk's coordination model workflow, aligned to the project base point using the same GCP coordinates the ortho uses. As-built vs. design clash detection runs the same day.

Step 3 is the one most providers skip. They upload to their own cloud, send a Dropbox link, and consider the job shipped. The ortho is correct. The superintendent still doesn't open it.

What superintendents actually forward

Three formats get forwarded inside a GC's organization without a follow-up phone call:

• The PDF progress report with the previous-cycle overlay. Owner sees this on the monthly billing walk.
• The JPEG thumbnail dropped into the daily log. The project engineer pulls it up on a phone at the trailer.
• The ortho link in the Photos tool when a dispute needs georeferenced evidence. This is the one that paid for the year's contract on a single change-order fight.

Everything else — the LAZ, the .obj mesh, the DEM GeoTIFF — is for the VDC manager, the surveyor of record, or the estimating team. They're a different audience. Don't make the superintendent wade through them.

The VDC side: what the BIM lead actually wants

The VDC lead doesn't care about the ortho. They care about the point cloud in Revit, aligned to the same coordinate system as the design model, with a clean import path.

Standard formats that round-trip cleanly:

• .las / .laz — universal, opens in CloudCompare, Bentley, Civil 3D.
• .e57 — ASTM standard, direct import into ReCap and Revit.
• .rcp / .rcs — Autodesk ReCap project files, link directly into Revit as a coordination model.

The hand-off the BIM lead wants: an .rcp file dropped into a shared BIM 360 / ACC folder, linked into Revit via Insert → Link → Coordination Model, aligned to the project base point using shared GCPs. They overlay the design model against the as-built scan, flag deviations, export a clash report. That's the deliverable that earns the next quarter of retainer.

What aggregators don't tell you

The big national drone-services marketplaces sell "Procore integration" as a checkbox. What they mean is: they will upload a JPEG of the ortho to your Photos tool. That's not integration — that's file delivery with extra steps. Integration means the deliverables are navigable, geo-referenced, and cross-linked between the field-side workflow (Photos tool, daily log, OAC agenda) and the office-side workflow (coordination model, clash detection, as-built verification).

Two questions to ask any provider that claims Procore integration:

1. "What folder structure do you upload into, and who in our org gets tagged on the upload?" If the answer is "we send a link," they don't integrate — they courier.
2. "Does the ortho round-trip into Civil 3D on our state-plane grid without manual registration?" If the answer is "we can include a world file," they understand the workflow. If it's "we can export a PDF of the ortho," find another provider.

Related reading

• Drone Data Integration: Procore + VDC Workflows — the technical hand-off pipeline in detail
• Severance Library — how the ortho earns its keep on a $24M, 16-month bi-weekly engagement
• Wet Dog Drones Services Overview — why we deliver against an OAC-meeting deadline, not a calendar week