Module · Site Reports
Site reports your team will actually file.
Daily site reports captured from site on a phone, surfaced in the project record on a desktop. Photos, weather, attendance, delays — with the audit trail you'd want if a dispute lands six months later.
Why most site reporting fails
The site report is the most-required and least-loved document on every project.
When site reporting lives in a Word template emailed at the end of each day, two things happen: it gets skipped, and it never gets searched.
They get skipped
A Word template + four photos + Outlook is a 25-minute job at the end of a long day. Three weeks in, the daily reports stop. By month three, you have a gap.
They are unsearchable
When the dispute lands, you need to know what the site looked like on a specific Tuesday. The reports are 47 emails buried in a shared mailbox.
They never reach the cost report
The CM noted weather delay on day 14. The QS finds out on day 90 when the variation lands. By then the prelim claim is fait accompli.
What's inside
A site report your team will file because it takes 4 minutes.
Mobile-first capture
Filed from a phone on site. Photos uploaded inline, geo-tagged, automatically attached to the project. No dropbox, no email, no after-hours desk work.
Photographic log
Each report carries its photos. Searchable across the project — "what did the steel look like in week 6?" gets answered in 10 seconds.
Weather + attendance
Daily weather + on-site head count + key trade attendance, captured in seconds. Feeds prelim claims and delay analyses without re-keying.
Delay flagging
Mark a day as delayed. Cause, consequence, programme impact captured. Surfaces in the project Overview AND in the variation's programme-impact assessment.
Audit trail
Every report timestamped, signed by submitter, immutable after submission. The trail you wish you had when the dispute six months later asks "what did you observe on day 14?"
Cross-report search
Search every report in the project — by date, by trade, by keyword. The site report becomes a project asset, not a daily admin task.
Who uses it
Built for the people on site — and the people defending the project months later.
Construction Managers
Daily report in 4 minutes from a phone. Trade attendance, weather and delay flags feed straight into the prelim narrative.
Project Managers
Open the project, see the latest site report on the dashboard. No more "did the CM file today?" Slack pings.
Quantity Surveyors
Variation justification from the site reports. Delay events captured at source — no need to reconstruct them three months later.
See your CM file a site report in 4 minutes.
A 20-minute walkthrough — we'll set up a project and have you file a real site report from your phone live on the call.
Frequently asked questions
Can it run offline on a remote site?
Forms accept input offline; submission queues until the device reconnects. Photos upload as bandwidth allows. The submission is timestamped at capture, not at upload.
How does this connect to variations?
Delay events captured in site reports surface as evidence on the corresponding variation's programme-impact assessment.
Can subcontractors file their own site reports?
Designer / consultant roles can file site reports today. Subcontractor self-service site reports via a token link is on the roadmap.
Can the client see the site reports?
A redacted client-facing site report stream ships in the client portal. Toggle which days, which content, per project.
Connects to
Other Projavio modules that work alongside this one.
Programme Management
Phases, milestones, baseline tracking, slippage flags — feeding cashflow, cost forecast and the executive summary.
Risk Register
Project risk register with likelihood × impact scoring, mitigation owners, status, and close-out trail.
Variations
JCT/NEC-aware variation lifecycle: instruction → cost → approval → impact on programme + cost report.
Stop losing the daily site narrative.
A site report your team files — and a project history you can actually search.