A 14,000 SF warehouse roof inspection. 32 photos. The carrier wanted a defensible PDF in 48 hours. Manual assembly took three days and cost the GC time and a $9,500 scrap claim fight.
This guide is for field supervisors, inspectors, property managers, and small GC crews who write the reports or depend on them. You’ll get choices for form layout, hard rules for photos and annotations, and a phone workflow that forces the office to close the loop. Run an audit current report process before redesigning your template to find the biggest time sinks.
If you follow the steps in each section, you’ll reduce turnaround and prevent avoidable claims. Decide one change and roll it out this week.
Design the PDF for real field use
Make the PDF a working record, not a pretty file. It must be fillable on a phone and readable when printed or scanned.
Keep the header minimal but exact
- Project ID, site name, and address. Fix these at the top so the PDF always ties to the job.
- Report date and prepared by. Use a single obvious box for the date so it’s not skipped.
- Shift/period and weather summary. A one-line weather field prevents vague delay notes later.
Form fields that matter in the PDF
- Work performed — checkboxes plus one open line for specifics. Checkboxes curb rambling entries.
- Personnel on site — list supervisors and trades present. Record leads, not every laborer.
- Equipment and materials received — include material condition notes (e.g., "wet box", "damaged pallet").
- Inspections and testing — reference test reports or results; don’t bury test data in the daily report.
- Safety and incidents — separate minor observations from incidents that trigger stop-work forms.
- Delays and reasons — use standardized reasons (weather, access, sub no-show, material delay).
- Signature block — allow digital or handwritten signature plus printed name and company. Add a witness line if phone signatures are accepted.
Layout tips
- Use wide margins for sticky notes and attachments. Field notes get photographed or stapled.
- Group related fields together. Put people and equipment near the work-performed area.
- Keep note lines short. Forced brevity improves clarity on punch lists and claims.
Common PDF mistakes to avoid
- Too many rarely-used fields. Cut anything crews never fill; long forms get ignored.
- Tiny or buried date/location fields. Make critical identifiers obvious and compulsory.
- No attachment space. If photos live separately, link them clearly in the PDF.
- No clear signature method. Publish whether you accept phone signatures and where to sign.
Decide which fields to remove and publish the final template before training the crew.
Set strict photo and annotation rules
Photos are evidence. Without rules you get useless panoramas and missing context. Set and enforce a photo sequence.
Simple photo rules we use
- Start with a wide shot, then a close-up, then a verification shot. Never submit only close-ups.
- Include a person or company sticker in at least one photo per job area for scale and presence.
- Name photos consistently on the phone (site-area_issue). Consistent names speed office triage.
- Annotate one arrow and a short label on the key photo. For more framing guidance see what photos to take.
How many photos are enough?
Use the sequence: context, detail, verification. If those three tell the story, you’re done. Avoid redundant images that slow claim reviews and backups.
Quick phone annotation methods
- Standardize one annotation tool, one color, and one arrow style so reviewers read images fast.
- Keep annotations to a single short phrase and one arrow. Put longer notes in the PDF caption line.
- Use timestamps and GPS when possible and note that in the report. Standardize your photo logs GPS and timestamps.
- If voice is preferred, attach a 10–20 second clip describing the image. A short voice note beats a vague caption.
Enforce the photo sequence at the office. Reject reports missing context and require a re-shoot.
Phone workflow: capture, annotate, submit in minutes
Field crews work on phones. The workflow must be repeatable and fast. Aim for same-day submission.
Step-by-step phone workflow
- Open the job folder in the phone app or file manager. Use the same folder every time.
- Take photos following the photo rules. Annotate the key photo immediately on site.
- Fill the PDF template on the phone: header, work performed, people present, and any delays or incidents.
- Attach photos to the PDF or a clearly labeled folder. Embed photos in the PDF when possible.
- Submit the package to the office inbox or project folder with a standard subject line and a short list of attachments.
Tools and tricks that actually help
- Use a fillable PDF app that works offline. Crews often hit no-signal sites; save locally until upload.
- Auto-fill repeated fields like project ID and address to cut typing time on daily visits.
- Keep a subject-line template so the office can triage by subject alone.
Handling urgent incidents from the field
For accidents, major material damage, or safety risks, treat the report differently. Start an incident tag in the PDF, add a wide photo, and call the PM before finalizing the submission.
Secure the area, collect witness names, and take a clear shot showing the hazard and context. Then add a one-line factual entry: what happened, who was present, and immediate actions taken. The office handles the rest, but the daily report must provide an initial, timestamped record.
Require the crew to call the PM on any incident and mark the checkbox that triggers escalation from the office.
Mini case: the warehouse roof day we almost lost
We were watching a 14,000 SF warehouse roof install. A late delivery arrived and a roll showed a scuff after placement. The crew followed the phone workflow and saved the owner from a costly mistake.
What we did
- Took a wide photo of the roof area with the delivery truck in frame, then a close-up of the scuff, and a verification shot after temporary protection was added. Total photos: 32.
- Annotated the close-up to show the scuff line and noted where the material box had been staged.
- Filled the PDF on the phone: logged work performed, recorded the delayed shipment, and named the site supervisor who saw the damage.
- Uploaded the PDF with annotated photos to the project folder and emailed procurement for a material check.
Result: procurement confirmed the affected roll wasn’t used elsewhere and avoided a $9,500 replacement claim. Inspection caught it — not the closeout audit. Copy that photo sequence and log counts in your template.
Handoff: what the office does next
When the report arrives, the office must triage it quickly. A predictable office workflow closes the loop for field crews.
Office triage steps
- Immediate triage: confirm receipt, check for missing photos, and flag urgent safety or QC issues to the PM.
- Standardize filenames and move the package to the archived daily reports folder for easy retrieval at punchlist time.
- Create a tracker entry for outstanding items that require vendor response or an RFI. Link to the PDF and key photos.
QA rules the office should enforce
- If photos lack context, ask the field for a re-shoot before closing the report.
- Reject reports missing the signature or supervisor name. Follow up immediately on missing signatures.
- Log incomplete reports. If a pattern appears, schedule targeted training using 7 field documentation habits.
What to log in the tracker
- One-line issue description, reference to the daily report PDF, and filenames of the annotated photos.
- Responsible party and due date for response or fix.
- Status updates: requested, vendor responded, in progress, verified. Timestamp each update.
- Attach a verification photo when closed. One clear shot is enough to clear the tracker item.
Office rule: confirm receipt and assign ownership within one business day. If not, escalate to the PM.
Key takeaways
- Make the PDF short, clear, and phone-fillable. Put essential fields front and center.
- Enforce a photo sequence: wide context, detail, verification. Annotate one key photo per issue.
- Require same-day submission and save drafts offline for low-signal sites.
- Office must confirm receipt, demand missing context, and archive consistently.
Pick one change from this list and implement it on your next site visit.
FAQ
How many photos should we attach to a daily report?
No fixed number. Cover context, detail, and verification for each issue. Stop when that sequence tells the story.
Can we accept handwritten reports instead of PDFs?
Yes, in a pinch. Scan and upload the handwritten report the same day. Make sure it follows the template fields and includes photos and signatures.
What if the crew doesn’t have signal to upload the report?
Use an app or PDF tool that saves locally and uploads automatically when connected. Train crews to queue uploads and verify once they hit signal.
Should photos be embedded in the PDF or attached separately?
Embed photos where possible so the record stays together. If you can’t embed, use a clearly named folder and reference filenames in the PDF.
How do we keep the team consistent with the form?
Publish one standard version and train everyone on it. Office QA should reject incomplete reports and require re-shoots for missing context.
Decide the rule that fits your program and publish it to the crew. Enforce it from day one.
Before You Send the Report, Check This:
- Project ID and address are correct in the header.
- Photos follow the context-detail-verification sequence and include one annotation.
- Header fields: date, prepared by, shift, and weather are complete.
- Lead personnel and subcontractors are listed.
- Received materials logged with condition notes.
- Incident checkbox used for anything escalated and PM notified if urgent.
- Photos embedded or attached with consistent filenames.
- Report signed and queued for upload if offline.
If any item is unchecked, fix it before uploading the package.