Daily Log Synthesizer
Pulls today's voice notes, photos with AI captions, procurement deliveries, RFIs, schedule activities, and submitted change orders, then composes a structured daily report covering work performed, manpower, deliveries, safety, issues, weather, and follow-ups.
What it does
Daily Log Synthesizer is the end-of-day engine that turns the day's raw signal into a structured daily report. It reads today's voice recordings, project_media photos with AI-generated captions, procurement deliveries logged, RFIs created or answered, schedule activities in progress, and submitted change orders — then composes a daily report with the standard sections every owner expects: headline, work performed by location, manpower by trade, deliveries received, safety observations, issues, weather notes, and tomorrow's follow-ups.
Zero new schema — the engine reuses daily_log_entries, voice_recordings, and project_media. The PM doesn't have to re-enter anything that's already in the trackers. Just trigger the engine at end-of-day and review the draft.
When to use it
- End of every working day — the standard cadence.
- Friday catch-up — backfill a week of daily reports from the trackers if you fell behind.
- After a busy site visit — turn the voice notes and photos you captured into the formal log.
- Before sending the weekly owner report — daily reports are the source data.
If the engine surfaces weather delays, manpower shortfalls, or rework, chain into Schedule Risk to model whether the day's events ate into critical-path float.
What to upload
Nothing — this is an aggregation engine. It reads voice_recordings, project_media (photos), procurement_items (deliveries), rfis, schedule_items (activities marked in progress today), and change_orders for the active project on the target date.
What it needs is a populated day: voice notes captured during walks, photos uploaded with location tags, deliveries logged when they arrived, schedule activities marked in-progress, RFIs filed as they came up. The engine is only as good as the day's source data.
Step by step
Open the engine
Sidebar → Engines → Daily Log Synthesizer.
Confirm the target date
Defaults to today. Override to backfill prior days.
Review the source preview
Banner lists everything the engine will read: N voice notes, M photos, K deliveries, J RFIs, X schedule activities. If anything's missing, add it before running.
Run synthesis
20–30 seconds.
Read the headline
Engine writes a one-sentence summary of the day. "Concrete pour on Level 3 East completed; framing inspection passed; weather delay 2 hours."
Walk the sections
Work performed, manpower, deliveries, safety, issues, weather, follow-ups — each populated from the day's source data with quotes from voice notes.
Edit and stamp
PM-polish the draft. Add anything the trackers didn't capture. Stamp to file the final report.
Distribute
Export PDF or share via the owner report distribution list.
Understanding the results
One-sentence summary of the day. The line owner-meeting people will quote.
Grouped by location and trade. Each entry sourced from a voice note, a photo caption, or a schedule activity marked in-progress.
Trade-by-trade count for the day. Sourced from the manpower log; if not logged, the engine infers from voice notes and flags the inference.
Materials received today with the PO reference, supplier, and any condition notes. Pulled from procurement_items.
Near-misses, incidents, or noteworthy positive observations. Sourced from voice notes and photo captions tagged with safety.
Open items needing attention tomorrow. Source: RFIs filed today, voice notes flagged as questions, photos tagged with issues. Each item carries its source link.
Every control, explained
Run synthesisConsumes one run. 20–30 seconds.
Target dateDefault is today; override to backfill prior days.
Edit sectionIn-place edit on any section of the draft.
Add manual entryInsert observations not captured in the trackers. Tags as PM-entered.
Stamp daily logFiles the final report as the official daily log entry for the date.
Chain to Schedule RiskOpens Schedule Risk to model the day's weather / manpower / rework impact on the critical path.
Export PDFFormatted daily report. Standard format for owner distribution and project records.