The Monday Digest: What an AI Operations Supervisor Actually Sends
Every Monday at 8:47am, a Telegram message arrives in the PM channel. It is from the Ops Supervisor. No one asked for it. No one had to compile it. It just shows up, every week, with the same format and the same level of detail.
The PMs read it. That is the highest praise I can give a reporting system. They read it because it saves them from opening five different spreadsheets, scrolling through email threads, and asking foremen for status updates. It tells them what happened, what is at risk, and what needs attention — all in under 300 words.
Here is what the digest actually looks like.
Weekly Ops Digest — Apr 6 to Apr 12
Portfolio: 15 active projects
Completed this week:
- PROJ-0038 — Inspection passed (Bakersfield)
- PROJ-0041 — AHJ revision submitted (Fresno)
- PROJ-0044 — Closeout package complete
At risk:
- PROJ-0033 — Permit expires in 9 days, no response from Kern County
- PROJ-0047 — Missing daily report for 3 consecutive days
Upcoming milestones (next 7 days):
- PROJ-0038 — PTO submission due Thursday
- PROJ-0041 — Inspection scheduled Wednesday
The structure is intentional. The first section is positive: here is what we got done. The second section is the reason PMs open the message: here is what might blow up. The third section is forward-looking: here is what is coming this week. There are no charts, no colors, no attachments. Just text, because text is what people read on Monday mornings.
How it is built: The Ops Supervisor wakes at 8am on Mondays. It queries Supabase for the past 7 days of agent activity: permit updates from the Permit Agent, field logs from the Field Agent, and milestone status changes. It also checks for at-risk conditions: permits expiring within 14 days, missing daily reports, and projects stalled in the same phase for more than 10 days.
The agent then passes this structured data to Claude Sonnet 4 with a prompt that says: "Write a concise weekly digest for a solar EPC project manager. Lead with completions, then risks, then upcoming milestones. Use plain language. No jargon. No exclamation points." The result is the Telegram message above.
The metric: The average PM at a 15-project EPC spends 2–3 hours every Monday morning compiling status updates. The Ops Supervisor reduces that to 15 minutes of reading and acting on the digest.
An honest limitation: The digest is only as good as the data in Supabase. If a foreman forgets to send his daily report, the agent flags the project as at risk — which may be a false alarm. The digest surfaces the gap, but a human still has to verify whether the work actually happened.
Want to see this in action? Here's the demo →
Sample Monday Digest output — a formatted example you can share with your team.
Get the sample →