Sunday, May 17, 2026 — 12:00 PM PT
Dominique shipped the Weather Delay Claim Timeline — an interactive chronological view that connects weather events, crew impacts, site photos, and calculated lost hours into a defensible schedule-impact narrative. This was yesterday’s afternoon brief idea #1 and extends the Weather Delay Evidence Pack (v2.20.0) from static PDF export into a living timeline for delay claims. The morning-to-nightly pipeline converted in 24 hours for the fifth consecutive day.
feature/nightly-20260517Howard-3 shipped RFI Answer Field Verification — a follow-up mechanism ensuring RFI answers are actually acted on in the field, not just acknowledged in the document log. Assignees confirm field implementation with photo evidence, notes, and timestamps. Overdue verifications surface as badges via Supabase Realtime. This was called out in yesterday’s afternoon brief themes and closes the RFI intelligence loop: from tracking answers (v3.14.0) to confirming they were implemented on site.
feature/nightly2-20260517Howard-1 shipped a double feature for DailyReportr+: the Field Handoff Digest summarizes shift-change context (open tasks, safety notes, weather status, pending items) for incoming crews, while Unsigned Report Closure adds a card that flags reports older than a configurable threshold that still lack signatures. Together they close the gap between daily report creation and daily report accountability. DailyReportr+ received two builds in a single night for the first time since May 11.
feature/nightly-20260517-field-handoffClosr+ received no nightly build. Last activity: May 16, Owner Training Readiness Card (v2.18.0) by Dominique. With a 24+ hour gap, Closr+ is a priority for tonight’s build cycle.
Inspectr+ received no nightly build. Last activity: May 16, Trade Readiness Matrix (v4.9.0) by Howard-1. With a 24+ hour gap, Inspectr+ shares priority status with Closr+.
require_trailing_commas lint. Warning counts are stable across all four apps. DailyReportr+ also has a asset_directory_does_not_exist warning for assets/images/ that should be addressed.
Two of the three strongest themes from recent morning briefs were built overnight. The Weather Delay Claim Timeline (May 15 morning brief) extends DailyReportr+’s weather stack into defensible claim documentation. The RFI Answer Field Verification (May 16 morning brief) closes Buildr+’s RFI loop from office acknowledgment to field confirmation. The morning-to-nightly conversion streak now stands at 5 consecutive days (May 13–17).
The strongest cross-app pattern across the last 3 morning briefs remains “evidence-backed validation” — gating progress behind photo or document proof. Yesterday’s afternoon brief proposed a Trade Readiness Photo Gate for Inspectr+ (layering on the Trade Readiness Matrix v4.9.0). This was not built overnight and remains the top unbuilt Inspectr+ idea. Today’s morning brief reinforces this with an Access Constraint Snapshot concept.
Closr+ has excellent blocker visibility (Retainage Release Radar v2.17.0, Owner Training Readiness Card v2.18.0) but still lacks actionability: converting blockers into per-subcontractor remediation plans. Yesterday’s Retainage Release Action Plan idea was not built. Today’s morning brief adds an Owner Training Evidence Packet concept. Both serve the same theme: making closeout data actionable, not just visible.
A quick-capture mechanism for field inspectors to document why an inspection failed or was only partially completed due to access issues — not workmanship defects. When an inspector encounters a blocked area (another trade occupying it, safety cordon, missing scaffold, traffic control), they open a bottom sheet to log constraint type, responsible party, photo evidence, and next action. Aggregated constraint data feeds a weekly blocker chart showing which areas and trades are most frequently blocked, turning individual inspection failures into coordination intelligence.
Why now: The Trade Readiness Matrix (v4.9.0) and Deficiency Aging Dashboard (v4.8.0) give Inspectr+ readiness and deficiency tracking, but neither captures why an inspection couldn’t happen in the first place. Access constraints are the #1 unreported cause of inspection delays on active jobsites. Today’s morning brief explicitly proposed this. Inspectr+ has a 24+ hour build gap and is due for a new feature.
access_constraints Supabase table (id, project_id, inspection_id, area, constraint_type [trade_conflict, safety, access, material, weather], responsible_party, photo_url, next_action, reported_by, reported_at, resolved_at). Create access_constraint_provider.dart (Riverpod AsyncNotifierFamily keyed on project_id). Build AccessConstraintSheet bottom sheet with picker chips for constraint type, camera capture via image_picker, responsible-party dropdown from project contacts, and free-text next action. Add an “Access Blocked” quick-action button on the inspection detail page. Create ConstraintHeatmapCard widget showing weekly aggregation by area/type using simple bar segments.
An exportable PDF packet that bundles all owner training artifacts per building system: training session date, attendee sign-in sheet (photo or digital), trainer name and credentials, O&M manual references, training video links, and completion signatures. Instead of owners receiving scattered proof across emails and folders, they get a single closeout-ready document per system that satisfies both contractual requirements and owner expectations. Integrates directly with the Owner Training Readiness Card (v2.18.0) — when all evidence slots for a system are filled, a “Generate Packet” button appears.
Why now: The Owner Training Readiness Card shipped yesterday and provides the per-system tracking scaffold. The missing piece is the exportable artifact. The May 16 morning brief explicitly called for this feature. Closr+ has a 24+ hour build gap. No competitor offers a structured, per-system training evidence bundle — Procore’s closeout workflows handle punch and submittals but don’t address training documentation at this granularity.
training_evidence_items Supabase table (id, project_id, system_id, evidence_type [signin_sheet, video_link, om_reference, certification, photo], file_url, description, uploaded_by, uploaded_at). Create training_evidence_provider.dart (Riverpod AsyncNotifierFamily keyed on system_id). Build TrainingEvidenceSlots widget showing required vs. uploaded evidence per system with camera/file-picker chips. Add “Generate Packet” button that assembles a multi-page PDF via pdf package: cover page with system name and project info, then grouped sections per evidence type with embedded images and metadata. Store generated PDFs in Supabase Storage with sharing link.
A conditional card that appears automatically on reports created during weekends, holidays, or outside normal working hours (configurable per project). Prompts for: crew count, reason for weekend/after-hours work, who authorized it, access constraints (gate codes, security escort needed), and supporting photos. The card makes weekend logs defensible for dispute resolution — documenting not just what happened but why work occurred outside normal hours and who approved it. Completed exception cards feed a monthly summary showing weekend work frequency, authorization patterns, and associated costs.
Why now: DailyReportr+ received two builds tonight (v2.21.0 and v2.22.0), making it the most feature-rich app in the suite. But weekend/after-hours reporting remains a gap — daily logs thin out on weekends with smaller crews and higher dispute risk. Today’s morning brief (Sunday) explicitly proposed this. With the Field Handoff Digest now handling shift changes, the Weekend Work Exception Card addresses the other major gap in report completeness.
work_exceptions Supabase table (id, report_id, exception_type [weekend, holiday, after_hours], crew_count, reason, authorizer_name, authorizer_role, access_notes, photo_urls [], created_at). Create work_exception_provider.dart (Riverpod AsyncNotifier). Add a date/time check in the report creation flow: if DateTime.now().weekday >= 6 or hour is outside project’s configured range, auto-insert a WeekendExceptionCard widget with required fields. Build monthly summary query grouping exceptions by type and project. Include exception data in PDF report exports as a highlighted section.
Procore — Dynamic Submittal Plan launches May 19: automated deadline calculations (Submit By, Open By, Workflow Due Dates) computed backward from Required On-Site Date and Lead Times. Also shipping mobile resource requests for Workforce Planning (iOS + Android). Punch tool received refreshed email notifications with improved hierarchy and clearer CTAs. (source)
Autodesk Construction Cloud — Recent releases include “Open for Manager” RFI status for internal routing before manager assignment, “Download All Attachments” on submittals, custom submittal types, and specs linked directly to files, sheets, RFIs, and submittals for full traceability. Excel schedule export also added. (source)
Bluebeam — Bluebeam Max (launched Q1 2026) continues gaining traction: AI-powered by Claude with “Magic Wand” markup tools for automating repetitive tasks, plus MCP-based integrations connecting Bluebeam to Procore, SharePoint, and ACC. Revu 21.6 runs 30% faster on ARM devices. (source)
Build the Access Constraint Snapshot. Inspectr+ has a 24+ hour build gap (last: May 16, Trade Readiness Matrix v4.9.0) and hasn’t been assigned to Dominique since May 7 (QR/Barcode Scanner was Howard-3). Rotating Dominique to Inspectr+ maximizes builder diversity and addresses the longest Dominique-specific gap. The Access Constraint Snapshot fills the “why inspections fail” gap that the Trade Readiness Matrix exposed.
Build the Owner Training Evidence Packet. Closr+ shares the 24+ hour build gap with Inspectr+ (last: May 16, Owner Training Readiness Card v2.18.0). The Evidence Packet is the natural follow-up — the Readiness Card tracks what’s needed; the Packet exports what’s been collected. Katey last built Buildr+ (RFI Answer Field Verification tonight); rotating to Closr+ continues the builder-diversity pattern.