Construction Daily Report Photo Workflow (Owner-Ready Excel)

A modern jobsite generates 50-200 photos per day. By Friday, the superintendent has 300+ photos and an owner who expects a weekly progress report. The daily report software handles narrative; the photos are an afterthought — but they’re also the only objective record of conditions on the date in question. This post walks through the photo workflow we recommend for construction PMs and supers who need to turn the week’s iPhone photos into an owner-ready Excel log in under a minute.

Short answer: Use one iOS Photos album per project (shared between team members). Capture site photos as you normally do. Each Friday — or each Monday for the prior week — export an Excel log from Photo Metadata Exporter with Filename, Date Taken, Time Taken, GPS Latitude/Longitude, Altitude (for high-rises), and Camera Model. Attach the .xlsx to your weekly progress report alongside the Procore/Buildertrend narrative. For change-order or RFI disputes, bundle photos + Excel in one ZIP using “Include original photos.”

Why daily-report photo discipline matters

A construction daily report has two audiences:

The owner / architect: reading for progress, schedule, and quality
Future you (and your attorney): reading 18 months later when there’s a dispute over schedule slip, defect timing, or change-order conditions

For audience 1, the narrative + photo gallery in Procore is often enough. For audience 2 — when there’s a $200k schedule-slip dispute or a contested change order — the structured photo log with timestamps and GPS is what wins.

The gap is rarely “did we capture the photos.” It’s “can we surface the right photos with defensible metadata fast enough.” A weekly Excel export per project closes that gap permanently.

The weekly workflow

1. Shared album per project

Set up an iOS Shared Album per active project. Invite the supers, the QA leads, the safety officer. Everyone’s contributed photos accumulate in one album with original capture EXIF preserved.

Naming convention:

2026 Smith Tower — Site Photos

Or by phase:

2026 Smith Tower — Frame
2026 Smith Tower — MEP
2026 Smith Tower — Finishes

Either works. Phase-based gives faster lookback for specific trade disputes; project-based is simpler operationally.

2. Capture as you walk

Standard construction photo discipline: wide shots first, then close-ups of specific conditions, model labels on equipment, deficient work, completed work. Each photo’s EXIF captures when and where automatically.

For multi-building or multi-tower sites, GPS coordinates in the EXIF distinguish buildings. For high-rise work, the Altitude field distinguishes floors.

3. Friday export — or Monday morning

Open Photo Metadata Exporter. Tap Album. Select your project album. (If you only want the week’s photos, use the manual multi-pick mode and filter by Friday-of-this-week.)

Configure these fields for site documentation:

Field	Why it matters
Filename	Anchor each row to the photo file
Date Taken	What day was the photo captured — owners read chronologically
Time Taken	Within-day chronology for delivery, safety, weather correlation
GPS Latitude / Longitude	Distinguishes buildings on a multi-building site
Altitude	Distinguishes floors on a high-rise (especially useful for tower-crane projects)
Camera Model	Authenticates the device (your phone, the safety officer’s phone, the super’s phone)
File Size	Sanity-checks photos are originals, not screenshots

Save the configuration as “Weekly Progress” — reuse on every future export.

Tap Create Excel. Even 1,000+ photo weekly batches complete in 1-2 minutes.

4. Attach to the weekly progress report

Three common patterns:

Procore / Buildertrend users: Upload the .xlsx as a supplemental attachment to the weekly report. Procore handles photos in its own gallery; the Excel is the structured chronology.
Email-based reporting: Include the .xlsx as an email attachment alongside the narrative PDF.
High-stakes / litigation-adjacent: Enable Include original photos in the export. The output is a single ZIP — photos + Excel. Save in your project’s litigation hold folder.

What the Excel looks like

#	Filename	Date	Time	Lat	Long	Alt	Camera
1	IMG_5012.HEIC	2026-05-18	07:14:32	30.27124	-97.74331	162 m	iPhone 15 Pro
2	IMG_5013.HEIC	2026-05-18	07:16:58	30.27124	-97.74331	162 m	iPhone 15 Pro
3	IMG_5014.HEIC	2026-05-18	09:23:11	30.27124	-97.74331	188 m	iPhone 15 Pro
4	IMG_5015.HEIC	2026-05-18	09:23:48	30.27124	-97.74331	188 m	iPhone 15 Pro

Owner reads this and sees: same day, started at 7:14am, moved up from grade (162m altitude) to second floor (188m). Cross-reference to the day’s planned work. The Excel speaks for itself.

Photo-driven change orders

The single highest-ROI use of structured photo metadata in construction is change-order substantiation.

Typical scenario: existing condition different from drawings, scope addition needed. The CO request includes:

Narrative description of the field condition
Photos of the field condition
Reference to the design intent in the drawings

The Excel adds:

A structured photo log showing exactly when each photo was captured, at what location and elevation, in what sequence

For the design team or owner reviewing the CO, that fourth element is the difference between “trust us, here’s a photo” and “the GC was at floor 3, structural grid C-7, on Tuesday at 9:23am, when the condition was first observed and documented.”

CO approval rates improve. Disputes about whether the GC documented the condition before working through it dry up.

Photo-driven schedule defenses

The second highest-ROI use is schedule-slip defense.

Owners and architects sometimes (often, candidly) blame the GC for schedule slip caused by their own design changes or material-supply issues. The defense:

“On [date], we documented [condition] that blocked work. We notified you in the same week’s RFI.”
The Excel proves the date of documentation.
The Procore RFI proves the date of notification.
The photos themselves prove what was documented.

Without the Excel, the documentation date is “the date we say we took the photo.” With the Excel, it’s the date the iPhone’s clock recorded at capture — which carries materially more weight in a delay dispute or arbitration.

A note on multi-team contributions

A shared iOS Album means safety, QA, and the supers all contribute. But it also means the export needs to handle inconsistent capture habits.

Practical tips:

Encourage everyone to enable Camera Location Services (Settings → Privacy & Security → Location Services → Camera). Without it, GPS columns are empty.
Discourage photo editing in third-party apps before sharing. Editors can strip or alter EXIF; ask team members to share originals.
Avoid screenshotting field photos. Screenshots have minimal useful EXIF. Original photo files only.

Common questions

”We use Procore — does this replace photo management there?”

No. Procore’s photo handling is for the in-app gallery and report attachment. The Excel is a supplemental structured log that Procore doesn’t surface natively. Most teams use both: photos go to Procore; Excel log goes alongside as a supplemental attachment.

”What if my supers don’t use iPhones?”

If they’re on Android, they can share to a shared cloud folder (Google Drive, Dropbox), and you import to the iPhone Photos library on your device before exporting. The EXIF survives the import. Workflow has a small extra step but works.

”What about drone photos for site overviews?”

If the drone deck is imported into the iPhone Photos library (most drone apps support this), the original EXIF is preserved including the drone’s GPS coordinates. Drone photos in the album appear with their original metadata.

”Does this work for multi-project portfolios?”

Yes. One shared album per active project. Run separate exports per project. Each .xlsx is project-specific.

”Multi-building projects?”

GPS distinguishes buildings 50+ feet apart at iPhone GPS precision (3-5m outdoor accuracy). For closer-spaced buildings, use the album naming convention to keep them straight: Tower A — Frame, Tower B — Frame, etc.

”Are project photos uploaded to a server?”

Never. Photo Metadata Exporter has no server. All processing is on-device. Important for IP-sensitive projects (federal, defense, healthcare) where photo content cannot leave authorized devices.

Bottom line

For the construction PM or superintendent:

Setup: 5 minutes once per project (shared album + saved field config)
Per-day: zero added time
Per-week: 60 seconds to export the weekly Excel
Per-dispute / per-CO: the Excel and photos are already filed, ready to defend or substantiate

Annual time investment: about 1 hour per project. Annual defense value: easily six figures across a portfolio.