Skip to content

Operations at Perla Engineering · 2026

Daily Site Reporting System

Standardizing how a construction site reports progress, one day at a time.

10 — Limitations / Confidentiality. This write-up uses a recreated, redacted description rather than the real internal documents — some details are withheld to protect confidential company information.

02 — 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.

03 — 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.

04 — The System

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.

What was built — 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.

05 — 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.

06 — 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.

07 — Current Evidence

No formal adoption or time-saved metric exists yet — that evidence is still in development.

06a — Tools

  • Google Forms
  • Google Sheets
  • WhatsApp
  • Google Drive

09 — Evidence

CONFIRMED
That this system was designed and built by Milad. Stated directly by Milad, independent of any single file.
SUPPORTED
The system description above (what it does, how it works). Consistent with real project files reviewed; not independently verified by a third party.
NEEDS VERIFICATION
A measurable outcome. No before/after metric exists yet for this system — shown as "current evidence" above rather than implied.

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.