Perla Engineering · 2026
Daily Site Reporting System
Standardizing how a construction site reports progress, one day at a time.
01 — Context
Engineers across several active project sites were reporting daily progress informally, with no consistent structure for what got captured or how it reached management.
02 — The Problem
Daily activity on site wasn't being captured in a form that could reliably feed weekly or monthly reporting — so reporting further up the chain depended on reconstructing what happened after the fact.
03 — My Role
Operations at Perla Engineering
04 — The Approach
Designed a short daily report — work completed, plan for tomorrow, workers on site, materials needed, issues — paired with a simple compliance rule: at least one site photo shared in the project's WhatsApp group as visual confirmation.
05 — The System
A daily reporting workflow built on tools the site teams already used, with a defined review path before a report becomes part of the official record.
06 — How It Works
An engineer submits the daily report and it's logged automatically. For higher-stakes reporting contexts, submissions pass through a technical review step before approval, and only approved reports become eligible for management-level reporting.
07 — Tools
- Google Forms
- Google Sheets
- Google Drive
08 — Implementation
In active use across multiple project sites, with weeks of real submissions from site engineers. A more structured version of the same workflow — including a formal technical-review and approval chain — has also been designed as a reference build for a future, more integrated reporting system.
09 — Current Evidence
No formal adoption or time-saved metric exists yet — that evidence is still in development.
The reference build for the more integrated version of this system includes real project data from a client engagement that can’t be shown publicly — this write-up describes the workflow without exposing that data.