Afternoon Brief

Friday, May 15, 2026 — 12:00 PM PT

Last Night’s Builds

Submittal Exception Digest Buildr+

Dominique shipped the Submittal Exception Digest — a morning action list that surfaces submittals requiring immediate PM attention: overdue items, returned-with-comments records that haven’t been resubmitted, and entries missing required spec or drawing links. Each exception row shows the submittal number, spec section, days overdue, and a one-tap action button. This was yesterday’s afternoon brief idea #1 and closes the 3-day morning brief streak on submittal intelligence (May 12–14). The morning-to-nightly pipeline converted in 24 hours for the third consecutive day.

Branch: feature/nightly-20260515
Commits: 293388e (stub) → d180534 (feat) → 11448c8 (merge) → 3de60f2 (fix: version)
Version: v3.13.0 · TestFlight: Uploaded (0743a777)
Builder: Dominique

Weather Delay Evidence Pack DailyReportr+

Katey/Howard-3 shipped the Weather Delay Evidence Pack — a defensible documentation export that bundles weather API snapshots, affected crew lists, work areas impacted, site photos, and calculated lost hours into a single PDF titled “Delay Evidence.” It builds on the Crew Roster Quick-Select (v2.19.0, shipped May 13) by linking weather events to specific crews. This was yesterday’s afternoon brief idea #2 and closes the 2-day morning brief streak on weather delay defensibility (May 14–15).

Branch: feature/nightly2-20260515
Commits: 9d7219e (feat) → 90ead90 (merge)
Version: v2.20.0 · TestFlight: Uploaded (93a24756)
Builder: Katey / Howard-3

Drawing Revision Coordination Action Plan Buildr+

Howard-1 shipped the Drawing Revision Coordination Action Plan as a rebuild pass — turning the Drawing Revision Impact Flag (v3.12.0, shipped May 13) into a structured action plan. When a revision lands, the plan auto-generates coordination tasks: notify affected subcontractors, flag impacted submittals, update meeting-minute topics, and queue RFIs for review. This extends Buildr+’s revision intelligence from “what changed” to “what to do about it.”

Branch: feature/nightly2-20260515 (rebuild)
Commits: e8937fd (feat) → f39985a (version bump) → aa65bf9 (chore)
Version: v3.10.1 · TestFlight: Uploaded (a3cd9b9f)
Builder: Howard-1

Closr+ & Inspectr+ — No Builds

Neither Closr+ nor Inspectr+ received nightly builds. Last activity: Closr+ on May 14 (Commissioning Log / Cx Tracker v2.16.0 by Dominique, Retainage Release Radar v2.17.0 by Howard-1), Inspectr+ on May 14 (Deficiency Aging Dashboard v4.8.0 by Katey). Both are now tied for the longest gap and are top priorities for tonight’s build cycle.

Codebase Health

Flutter Analyze — All 4 Apps

Buildr+
0 errors · 0 warnings · 441 infos
Closr+
0 errors · 1 warning · 256 infos
Inspectr+
0 errors · 0 warnings · 969 infos
DailyReportr+
0 errors · 1 warning · 1,556 infos
Highlight: All four apps remain error-free — the clean streak extends to its fifth consecutive day. Closr+ stays the cleanest at 257 total issues. Closr+ picked up 1 warning (unused import in share_project_dialog.dart). DailyReportr+ retains its persistent assets/images/ directory warning. Inspectr+ carries the heaviest deprecation load (969 infos, mostly Color.withOpacity().withValues()). Buildr+ stable at 441 infos despite two new features landing overnight.
Recurring Themes from Morning Briefs

Shipped: Submittal Exception Digest — 3-Day Streak Closed

The Buildr+ submittal/RFI intelligence theme ran for 3 consecutive morning briefs (May 12–14): Drawing Revision Impact Flag, Submittal Exception Digest, and RFI Answer Impact Tracker. Dominique shipped the Submittal Exception Digest overnight (v3.13.0), directly converting yesterday’s afternoon brief idea #1. Combined with Howard-1’s Drawing Revision Coordination Action Plan, Buildr+ now has a proactive risk surface spanning revisions, submittals, and transmittals. Remaining gap: RFI Answer Impact Tracker — flagging RFI answers that affect scope, schedule, or cost.

Shipped: Weather Delay Evidence Pack — 2-Day Streak Closed

The DailyReportr+ weather delay defensibility theme ran May 14–15: first the evidence pack concept, then a claim timeline extension. Katey shipped the Weather Delay Evidence Pack overnight (v2.20.0), converting yesterday’s idea #2. DailyReportr+ now has a full delay documentation chain: weather data capture → crew impact linking → evidence PDF export. Remaining gap: Weather Delay Claim Timeline — connecting forecast, crew, photos, and lost hours into a visual timeline for schedule-impact arguments.

Closr+ Retainage & Closeout Pipeline — 4-Day Streak, Still Open

The Closr+ closeout completeness theme is the longest-running unresolved streak (May 12–15), evolving across four morning briefs: Closeout Gap Concierge, Owner Training Readiness Card, Retainage Release Action Plan, and Retainage Release Checklist Gate. Yesterday’s idea #3 (Retainage Release Action Plan) was not built overnight. The retainage radar (v2.17.0) and Cx tracker (v2.16.0) shipped on May 14 but the action/task layer remains missing — the radar shows risk but doesn’t convert it into assignable work items. Owner training evidence tracking also remains unbuilt.

Feature Ideas

1. Owner Training Readiness Card Closr+

A per-system readiness card that shows exactly which owner training requirements are complete and which are missing before turnover week. Tracks training videos, attendee sign-in sheets, O&M manual handoffs, and system-specific certifications. Each card displays a completion percentage with drill-down into individual evidence items — giving both the GC team and the owner a shared view of what’s blocking final handover. The card surfaces “request update” actions so PMs can nudge subcontractors on missing items without leaving the app.

Why now: The Closr+ closeout pipeline streak is the longest unresolved theme at 4 days. The Cx Tracker (v2.16.0) and Retainage Radar (v2.17.0) both shipped this week, but training evidence is the remaining closeout blind spot. The May 13 morning brief specifically called for an Owner Training Readiness Card. With Autodesk Construction Cloud shipping automation rules for document review workflows this month, Closr+ needs to stay ahead on structured closeout intelligence.

Sketch: Add training_requirements Supabase table (id, project_id, system_name, requirement_type [video, sign_in, manual, certification], status, assignee, due_date, evidence_url). Create training_readiness_provider.dart (Riverpod AsyncNotifierFamily keyed on project_id). Build OwnerTrainingReadinessCard widget with a progress ring per system, expandable checklist rows showing requirement status with colored chips, and “Request Update” action buttons that generate notifications. Embed in the owner handover tab alongside the existing closeout readiness score. Store evidence files in Supabase Storage with typed metadata for audit.

2. RFI Answer Impact Tracker Buildr+

Flag RFI answers that change scope, schedule, cost, or drawings — not just mark them “answered.” When an RFI response comes back, the PM selects impact chips (scope change, schedule shift, cost delta, drawing revision needed) and the tracker surfaces a filtered “Needs Follow-Up” list linking to affected change orders, submittals, or drawing records. This turns the RFI log from a Q&A archive into an active risk register that catches downstream work before a response quietly becomes a field delay.

Why now: The May 14 morning brief called for an RFI Answer Impact Tracker, and now that the Submittal Exception Digest (v3.13.0) and Drawing Revision Coordination Action Plan (v3.10.1) have both shipped, Buildr+’s proactive intelligence surface has a clear gap at the RFI layer. The adjacent DrawingRevisionImpactPage already tracks revision-to-document impacts — the RFI tracker completes the loop by tracking answer-to-action impacts. Procore’s Dynamic Submittal Plan (shipping May 19) automates submittal deadlines; impact tracking on RFI answers is a differentiated angle they haven’t addressed.

Sketch: Add impact_type enum column to the existing RFI model (scope, schedule, cost, drawing). Create rfi_impact_provider.dart (Riverpod FutureProvider.family) that queries RFIs where status = 'answered' AND impact_type IS NOT NULL AND follow_up_status = 'pending'. Build RfiImpactChipSelector widget for the RFI response form — multi-select chips with color coding (red=scope, amber=schedule, blue=cost, purple=drawing). Add RfiImpactFollowUpList as a filtered view with linked CO/submittal/drawing records and one-tap “create follow-up” actions. Embed at the top of the RFI list page with a badge count.

3. Deficiency Resolution Velocity Tracker Inspectr+

A project-level analytics card that tracks how fast inspection deficiencies are being resolved over time. Shows median resolution time by trade and severity, a rolling 14-day trend line (improving vs. degrading), and SLA indicators that flag when resolution speed drops below configurable thresholds. Unlike the Deficiency Aging Dashboard (v4.8.0, which shows current open items by age bucket), this tracker measures throughput — how quickly the team closes items once they’re opened. PMs can spot accountability problems before the aging buckets fill up.

Why now: The Deficiency Aging Dashboard shipped yesterday and gives Inspectr+ a snapshot of current open deficiencies. The natural next layer is temporal intelligence — are things getting better or worse? Autodesk Construction Cloud’s Issue Thumbnail History (shipping this month) adds visual change tracking to issues; our velocity tracker offers a more actionable metric: resolution speed by trade, which directly maps to subcontractor accountability conversations. No competitor currently provides deficiency resolution SLA tracking at the inspection level.

Sketch: Add rpc_deficiency_resolution_stats(project_id, window_days) Supabase RPC that computes median resolution time, resolution count, and open-vs-closed ratio grouped by trade and severity over a rolling window. Create resolution_velocity_provider.dart (Riverpod AsyncNotifierFamily). Build DeficiencyResolutionVelocityCard widget with a sparkline trend chart (using fl_chart), trade-level breakdown rows with median days and delta arrows (green=improving, red=degrading), and configurable SLA threshold badges. Embed below the Deficiency Aging Dashboard card on the project detail page. Add a “Copy velocity report” button for clipboard export.
Competitive Intel

Industry Moves — Last 7 Days

Procore — Dynamic Submittal Plan shipping May 19: replaces manual submittal data entry with automated deadline calculations, working backward from Required On-Site Date through lead times. Also launched a new Locations Tool bringing spatial management into a dedicated, permission-controlled project tool with hierarchical list and tree views. Over 2,000 companies have adopted Procore Scheduling since its February launch, making it one of their fastest product adoptions. Q1 2026 earnings highlighted AI integrations as a growth priority. (source)

Autodesk Construction Cloud — 50+ product releases in May across Build, BIM Collaborate, Takeoff, and BuildingConnected. Key features: Issue Thumbnail History for visual change tracking on inspection items, issue reassignment permissions without full project visibility, Apple Pencil markup support on mobile, and folder-level automation rules that trigger Review workflows on file upload. Activity Log expanded to cover Issues and Sheets with additional filters. (source)

Bluebeam — Launched an Integrations Directory as a centralized hub connecting Procore Documents, SharePoint, ACC, and Vectorworks. Revu 21.6 now runs natively and 30% faster on ARM devices (Surface tablets, Apple M-series via Parallels). No new closeout or inspection features this cycle. (source)

Fieldwire — No new May 2026 feature announcements. Continues investing in BIM viewer, RFI, and change order tooling at Business Plus tier ($89/user/month).

Takeaway: Three signals: (1) Submittal deadline automation — Procore’s Dynamic Submittal Plan auto-calculates deadlines; our Submittal Exception Digest (just shipped) differentiates by surfacing exceptions and actionable follow-ups, not just computed dates. (2) Visual issue history — ACC’s Issue Thumbnail History adds image-based change tracking; our Deficiency Resolution Velocity idea goes deeper with time-based throughput analytics and SLA tracking per trade. (3) Automated document workflows — ACC’s folder-level automation rules target document review; Closr+’s Owner Training Readiness Card idea targets a more specific closeout bottleneck with structured evidence tracking and notification-driven follow-ups.
Tomorrow’s Build Suggestion

Dominique → Closr+

Build the Owner Training Readiness Card. Closr+ last received a build on May 14 (Cx Tracker v2.16.0) and is tied for the longest gap. The closeout pipeline streak is 4 days old and unresolved — training evidence is the remaining blind spot after the Cx tracker and retainage radar shipped. Dominique’s last Closr+ build was the Cx Tracker itself, so he has fresh context on the owner handover tab where this card will live.

Katey → Inspectr+

Build the Deficiency Resolution Velocity Tracker. Inspectr+ last received a build on May 14 (Deficiency Aging Dashboard v4.8.0) and is the other longest-gap app. Katey shipped the aging dashboard yesterday, so she has direct context on the data model and project detail page layout. The velocity tracker extends her work by adding temporal analytics below the aging card — a natural vertical expansion with minimal new infrastructure.