The AmplifierReal cases · Civil engineering · Site manager
Harish, 34: a construction site, forty vendors, and a daily report written at 11 p.m.
Twelve hours on site, then two hours turning WhatsApp photos and phone calls into a report the client reads at 8 a.m.
Planned for release phase 2. The page is complete as a draft; interactive parts run in the browser and do not yet save to an account.
In brief
The situation. Harish manages a mid-rise residential site in Ahmedabad. Forty vendors, three subcontractors, a client's project-management consultant who wants a daily progress report with photos, quantities and issues, and a labour contractor who communicates only in voice notes. The report takes him two hours every night. It is usually late, usually incomplete, and the only thing the client sees of his day.
Step 1 — Define the End State
"The 8 a.m. report is on time, complete and shows the site as it is — including the problems — so the consultant trusts it and the client stops calling me at 9. I use the two evening hours for tomorrow's sequencing, which is the actual job. My labour contractor's voice notes become a record I can hold him to." Audiences: the consultant, the client, the contractor, and Harish at 7 a.m.
Step 2 — Map the Flow
His list: a fixed report format, a way to capture during the day instead of reconstruct at night, transcribing voice notes, photo organising. AI review adds: a quantities reconciliation against the schedule (he had been reporting work done, not work done against plan); and an issues log that persists day to day so problems are not reported once and forgotten. It suggests drone surveys. Not this project's budget.
Step 3 — Assign Tasks
What the client needs to trust: his. The report template: hers to design — AI drafts three, he chooses. Transcribing and summarising voice notes: AI, verifiable against the audio, low cost. Turning his own dictated site walk into the report body: AI drafts, he edits in five minutes. Deciding what is an "issue" and what is normal: his, always. Tomorrow's sequencing: his, with the tool as a checker for clashes.
Step 4 — Select the Tool
A voice tool for his walk-around dictation and the contractor's notes (audio to text, high frequency — set up once); a conversational tool for the report draft; the project's existing scheduling software for quantities against plan. Photos stay in a folder with a naming rule, not in an AI.
Step 5 — Prepare and Direct
Criteria: the report has the same six headings every day; every quantity is against the planned quantity, not alone; every issue has an owner and a date and stays until closed; nothing in the report is a claim I did not see or hear myself; done by 7.30 a.m.
Steps 6 and 7 — Execute and Evaluate
The first drafts read well and soften everything — "minor delay" for a two-day slip. His criterion says the site as it is; he adds "no adjectives about delays, only days" to the brief. The voice-note transcripts are rough in Gujarati but usable, and the contractor's promises are now written down. Quantities against plan reveal a slab pour is behind that he had been reporting as "in progress".
Step 8 — Integrate and Stress-Test
Two weeks in. Small fixes: photos out of order; the contractor's name spelled three ways. Structural: the report is now honest and the client calls more, not less — because issues are visible and nobody had told him they would be. A Step 1 audience problem: the report changed and the client's expectations did not. Harish calls him once, explains the new format, and the calls drop to one a week.
What changed
On time, complete, trusted. Two evening hours go to sequencing, and the site runs smoother for it. The contractor is held to voice notes he did not know were being kept. The consultant, at the next review, uses Harish's report format for another site.
Capture during the day, in your own voice; reconstructing at night is where reports go wrong. "No adjectives about delays, only days." When a report becomes honest, tell the reader before they notice.
A composite case, not a client engagement; the person is invented, the situation is not.