Wednesday, June 3, 2026 — 12:00 PM PT
Dominique shipped Closeout Evidence Matrix (v2.29.0) — yesterday’s afternoon brief idea #2 built in under 18 hours. A two-dimensional grid where rows are spec sections (CSI divisions) and columns are evidence types: warranty letter, O&M manual, test/balance report, as-built drawing, certificate of compliance, and training record. Each cell shows color-coded status (green/yellow/red) with tap-to-upload. A summary bar shows overall evidence collection percentage. Items auto-mapped from BuildrPlus submittals via the Submittal-to-Closeout Reuse Map show a source badge. This is the capstone feature that turns Closr+ from project-level health views into document-level gap resolution. Howard-1 reviewed clean — no fixes needed.
feature/nightly-20260603Katey/Howard-3 shipped Sync Health Receipt (v4.47.0) — yesterday’s afternoon brief idea #1 and the longest-standing unbuilt idea in the pipeline (proposed across 4 consecutive briefs since May 31). After an inspector reconnects from an offline site walk, a bottom sheet shows exactly what synced: inspection items, photos, deficiency notes, evidence scores — and what’s still queued. Each receipt item shows status with tap-to-retry. A Sync History page lets inspectors audit past sync events. Ported from DailyReportr+’s battle-tested implementation. Howard-1 caught a VERSION_OVERRIDE regression (4.43.2 was behind pubspec 4.47.0) and corrected it.
feature/nightly2-20260603No new commits overnight. Last feature: June 2, RFI Location Assist (v3.25.0) by Katey — 1-day gap.
No new commits overnight. Last feature: June 2, Large-Text Field Mode (v2.30.0) by Dominique — 1-day gap.
share_project_dialog.dart). Inspectr+ steady at 979 despite shipping Sync Health Receipt — also clean new code. DailyReportr+ steady at 1,663 (no build). Persistent lint debt remains deprecated_member_use (withOpacity) and require_trailing_commas. DailyReportr+’s missing assets/images/ directory warning persists.
Both ideas #1 and #2 from yesterday’s afternoon brief shipped overnight: Dominique built the Closeout Evidence Matrix (Closr+) and Katey built the Sync Health Receipt (Inspectr+). The Evidence Matrix was the morning briefs’ most-requested feature — proposed in 4 different forms across 6 briefs (Missing Evidence Map, Exception-Only View, Turnover Gap Guard, Closeout Missing Evidence Map). The Sync Health Receipt was the longest-standing unbuilt idea at 4 consecutive briefs. Both assignments matched the builder-app gap heuristic (longest-gap pairings). Running total: 14 of 18 ideas converted to production (78% conversion rate). Only yesterday’s idea #3 (Repeat Defect Radar) remains unbuilt.
With the Sync Health Receipt shipping tonight for Inspectr+, three of four apps now have offline sync visibility: DailyReportr+ (Sync Receipt, Offline Sync Outbox, Offline Attachment Queue, Offline Conflict Review Queue), Inspectr+ (Offline Sync Outbox, Sync Health Receipt), and BuildrPlus (Offline Drawing Snapshot, Offline Sync Outbox). Closr+ is the only app without an offline sync system. The morning briefs continue to surface offline-first ideas: today’s “Offline Inspection Packet” (preload assignments before leaving Wi-Fi) and the recurring “Photo Upload Triage Queue” suggest the field still has unmet needs around pre-departure confidence — knowing your work is safely captured before leaving the jobsite.
The last 3 morning briefs all proposed features that span multiple apps: Submittal Commitment Tracker (Buildr+ submittals → field commitments), Turnover Gap Guard (Buildr+ docs → Closr+ closeout), and Field Condition Delta (DailyReportr+ logs → Inspectr+ inspections). The Submittal-to-Closeout Reuse Map (shipped June 1) and Evidence Matrix (shipped tonight) form the first working cross-app pipeline. Procore’s June 3 announcement of a Connected CDE with agentic AI agents across submittals, RFIs, and daily logs confirms this is the competitive direction — our multi-app architecture has a natural advantage here.
A dashboard card that analyzes inspection items across recent walk sessions to detect recurring defect patterns: same location flagged repeatedly, same subcontractor accumulating similar deficiencies, or same defect type (e.g., “fire-stopping incomplete”) appearing across multiple floors or units. Displays a compact radar view with badges — “3 repeat locations,” “2 contractors with patterns” — each expandable into a detail list with links to the source inspection items. Helps inspectors and PMs prioritize systemic issues over one-off findings and bring data-backed evidence to subcontractor conversations.
Why now: Carried forward from yesterday’s brief as the only remaining unbuilt idea from the last 18. Inspectr+ has zero trend or analytics features despite capturing rich structured data (items with locations, contractors, categories, photos, severity). The morning briefs have mentioned anomaly/variance detection 3 times. Procore just announced AI agents that “search across specifications, drawings, and RFIs” to “highlight conflicts” — our Repeat Defect Radar applies the same “find patterns humans miss” principle to inspection data, differentiating Inspectr+ from Fieldwire and Procore’s inspection modules.
RepeatDefectService queries inspection items from the last 30 days, groups by (location + category), (contractor + category), and (category alone), flags groups with count ≥ 2 as clusters. RepeatDefectCluster model with clusterType (location/contractor/category), key, items list, count, severity. RepeatDefectRadarCard widget shows badge row on the project dashboard with expandable tiles. repeat_defect_provider.dart as FutureProvider.family(projectId). All local computation — no Supabase views needed, just queries against existing Drift tables.
A burndown-style chart on the project dashboard that uses the current evidence collection velocity to project when 100% closeout will be achieved. Tracks daily completion rate across all evidence types (warranties, O&M manuals, as-builts, certificates, training records, test reports), shows a trend line of items resolved per week, and displays a projected completion date with confidence bands. A summary card shows “At current pace: 100% by July 18” or “Slowing — 3 items/week vs. 7 last week.” Tapping the chart reveals the bottleneck breakdown: which evidence types and responsible parties are dragging the forecast.
Why now: The Evidence Matrix (shipped tonight) gives Closr+ its first spec-section × document-type view of completeness. The Completion Forecast is the time dimension that the matrix needs: the matrix answers “what’s missing?” while the forecast answers “when will we be done?” Together they give PMs a complete story for owner reporting. Closr+ already computes completionRate for lien waivers and trade stats but has no predictive forecasting or burndown visualization. With 8 closeout intelligence features now shipped, this analytical layer ties them together into a single “project readiness trajectory” view.
CompletionForecastService queries evidence matrix items, groups by date resolved, computes rolling 7-day and 14-day velocity, projects remaining items ÷ velocity to get estimated completion date. CompletionForecastModel with totalItems, completedItems, dailyVelocity, projectedDate, bottlenecks (list of evidence type + party pairs with zero velocity). CompletionForecastCard on dashboard with a mini sparkline and projected date. CompletionForecastPage with full burndown chart using fl_chart (already a dependency in Closr+). completion_forecast_provider.dart as FutureProvider.family(projectId).
Before a user sends a submittal, show the full routing path in one compact review screen: each reviewer in sequence with their role, due duration, and current workload; required attachments with missing-file warnings; auto-calculated deadline based on review durations and calendar; and a “ready to send” checklist that blocks submission until all requirements are met. This catches coordination mistakes — wrong reviewer, missing specs, unrealistic deadlines — before the clock starts, preventing the cascading delays that come from a rejected or bounced submittal.
Why now: Proposed in this morning’s brief (June 3) as the third idea. Buildr+ has shipped 5 submittal features in 3 weeks (Auto-Deadline Calculator, Exception Digest, Review Watchlist, Aging Tracker, Bulk Status Update) but all operate after a submittal is sent. The Route Preview is the pre-send quality gate that completes the submittal lifecycle from preparation through resolution. With the RFI Location Assist (shipped June 2) proving that “smart pre-fill before user action” is effective, applying the same pattern to submittals is a natural extension.
SubmittalRoutePreview widget shown as a bottom sheet when user taps “Send Submittal.” SubmittalRouteService reads from a submittal_routing_rules Supabase table (reviewer role, due duration, required file types, status transitions). Displays a vertical stepper with reviewer avatars, due dates, and attachment checklist. RouteValidation model checks: all required attachments present, all reviewers assigned, deadline within business days. Red/green indicators per step. “Send” button disabled until all validations pass. submittal_route_provider.dart as FutureProvider.family(submittalId).
Procore: Agentic AI Agents (June 1-3) — At Digital Construction Week in London, Procore launched a Connected Common Data Environment with agentic AI “coworkers” powered by Datagrid (acquired January 2026). Five native AI agents ship: Deep Search (cross-references specs, drawings, RFIs to find conflicts), Submittals (compares submittals to specs and flags discrepancies), RFI, Daily Log (aggregates photos, emails, voice notes to draft logs), and Contract Review (identifies conflicts and adds comments). These agents can now execute work inside Procore, not just surface information. (source)
Procore Connect — New infrastructure transforming Procore from a single-company tool into an interconnected construction network. Owners, GCs, and subcontractors can link their respective Procore projects and share data bidirectionally. European CDE launching first in UK/Ireland with ISO 19650 support, EU Data Zone planned for fall 2026. (source)
Bluebeam Max: Global AI Launch — Bluebeam Max now globally available with AI features: Magic Markups (automate repetitive markup for faster takeoffs), Smart Overlay (identify design changes across entire drawing sets), Smart Review (read AEC drawings and flag scope gaps, contradictions, missing info), and Connected Sessions with Revit (tie 2D markups to 3D model elements). AI powered by Claude. (source)
Dominique hasn’t built Inspectr+ since May 20 (Inspector Route Pack, 14 days ago) — the longest builder-app gap in the system. Tonight Dominique built Closr+; yesterday, DailyReportr+. Suggest building the Repeat Defect Radar (idea #1) — the only remaining unbuilt idea from 18 proposals. This would give Inspectr+ its first analytics feature, a significant differentiation point. With the Sync Health Receipt just shipped tonight, Inspectr+ is primed for the next capability layer.
Katey hasn’t built Closr+ since May 20 (Closeout Exposure Aging Buckets, 14 days ago) — tied for the longest builder-app gap. Tonight Katey built Inspectr+; yesterday, Buildr+. Suggest building the Closeout Completion Forecast (idea #2) — the time-based complement to the Evidence Matrix that Dominique just shipped. The matrix shows what’s missing; the forecast shows when it’ll be done. Together they give PMs a complete readiness story for owner reporting.