Operations at Perla Engineering · 2026

Project Operations System

Turning "operations manager" from a job title into an hour-by-hour system.

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

The operations function touched site execution, materials, finance, and cross-department coordination — but without one documented rhythm, consistency depended on memory and habit.

03 — The Problem

There was no single reference for what the operations role owned each day, what decisions it could make alone, and when something needed to be escalated.

04 — The System

Approach — Documented the role as a literal hour-by-hour schedule rather than a general job description, paired with a clear decision-authority matrix so escalation stopped being a judgment call.

What was built — A daily operating system for the role: an hour-by-hour schedule, a one-page job description, a decision-authority matrix, and a defined set of tracking instruments — a daily report log, a project progress tracker, a cost tracker, and an issue log.

05 — How It Works

The day runs on a fixed structure — site reports reviewed each morning, materials and procurement reviewed mid-morning, finance coordination before noon, cross-department check-ins at midday, site follow-up in the afternoon, and reporting closed out by end of day — with a matching weekly rhythm for planning and review.

06 — Implementation

In active use as the standing operating rhythm for the role.

07 — Current Evidence

This is a process and accountability system rather than one with its own standalone before/after metric — its effect shows up in the consistency of the systems it coordinates, including daily site reporting and material request tracking.

06a — Tools

Google Sheets
WhatsApp

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 full internal document this system is drawn from is marked confidential — the description above reflects its structure and purpose without reproducing internal thresholds or policy detail.