Afternoon Brief

Last Night’s Builds

Howard → Inspectr+: Contractor Closure Rate Scorecard (v4.68.0) shipped

Commit 7abcd63 — Mon Aug 3 00:22 AM PT. 274 lines added to project_detail_page.dart. Adds a per-contractor accountability panel: computes lifetime close-out rate (items closed ÷ total assigned) across all inspection items per contractor, sorts worst-first (lowest closure rate at top), and renders a closureRate percentage with grade badges A–D (A = green ≥90%, B = blue ≥75%, C = orange ≥50%, D = red <50%). An “Overdue” chip fires when a contractor has open items untouched for 14+ days. Clipboard copy produces a structured scorecard report for PM distribution. This is the first contractor-accountability view in Inspectr+ — previously, deficiency aging was visible at the item level but no cross-contractor ranking existed.

Branch: direct commit to main — Howard. TestFlight bumped to 4.67.2+20260803002301, then review bump to 4.67.3.

Howard → Buildr+: Flag unassigned submittal reviewers shipped

Commit cc7fada — Mon Aug 3 01:17 AM PT. 2 files, 24 insertions (8 logic, 16 tests). Adds reviewerMissing detection to submittal_turnaround_risk_provider.dart: when reviewedBy is blank and the due window is ≤7 days, score is boosted by 20 points total (8 + 12) and reason is set to ‘Reviewer not assigned’. Previously a blank reviewer added a flat +8 regardless of timeline; the new logic escalates urgency as the deadline approaches and gives the reason field a specific, searchable string. Test coverage added in submittal_turnaround_risk_provider_test.dart. The risk flag is now live in the model — but not yet visible as a distinct UI badge in the radar page.

TestFlight bumped to 4.4.2 (c031551).

Howard → Closr+: isDark prop-drill cleanup in TurnoverRiskDigestCard polish

Commit 24dae2c — Mon Aug 3 01:21 AM PT. 2 files, net −12/+7. Drops the three-level bool isDark constructor parameter that was prop-drilled through TurnoverRiskDigestCard, _SummaryStrip, and _RiskRow. Replaces it with context.adaptiveTextPrimary and context.adaptiveTextSecondary directly in each widget’s build() method, using the AdaptiveColors extension already available in the app. The one per-widget dark-alpha check (0.18 vs 0.10) retains Theme.of(context).brightness since no extension maps that bare double. dashboard_page.dart drops the now-unnecessary isDark: argument at the call site. This is the same pattern Closr+ applied to other cards; TurnoverRiskDigestCard was the last prop-driller in the widget stack.

TestFlight bumped to 2.32.54, then 2.32.55 (9d3b617, 6a87353).

DailyReportr+ no feature build

No nightly feature build. Only an automated version bump: bcb3563 (Lab Architect UI Polish Bot, 04:44 AM) bumping pubspec to 2.34.51. Last meaningful feature build was Katey’s context.cardBorder polish (Aug 2). The TodaySetupCard is clean and stable — the TodaySetupKickoff Checklist depth pass remains unstarted.

Codebase Health

Sixth consecutive brief at 0 issues across all 4 apps. Tonight’s Inspectr+ scorecard (274 LOC in one page), Buildr+ provider change (8 logic lines + 16 tests), and Closr+ widget refactor (net −5 lines) all landed without introducing any new lint or analysis issues. The 0-issue floor holds. No build should ship that moves any counter above zero.

Recurring Themes from Morning Briefs

Patterns across the Aug 1, Aug 2, and Aug 3 morning briefs that remain unbuilt or only partially addressed:

• Submittal Risk Visibility — Badge Surface Gap (Buildr+) — Aug 1 brief: “Document Version Clarity Pass” (reusable DocumentVersionBadge, status banners). Aug 3 brief: “Submittal Risk Badge Polish” explicitly calling for a shared SubmittalRiskBadge with compact/expanded variants. Tonight’s Howard commit (cc7fada) added the risk flag to the provider — reason: ‘Reviewer not assigned’, +20 score. But submittal_review_radar_page.dart still renders “Unassigned reviewer” as plain gray text. The data knows; the UI does not show it differently from any other low-risk submittal.
• Inspectr+ Offline Draft Reliability (Inspectr+) — Aug 1: “Photo Attachment Reliability Sweep” (centralize upload state, stable thumbnails, queued/failed/retry states). Aug 3: “Offline Inspection Draft Recovery” (stable IDs, SyncRecoveryPanel, reconcile to Supabase). Three consecutive morning briefs have flagged offline reliability as the Inspectr+ trust gap. No SyncRecoveryPanel or DraftRecovery widget exists in lib/. Tonight added the Contractor Closure Scorecard — great for accountability, but sync reliability remains unaddressed.
• Closr+ Completeness & Evidence Chase (Closr+) — Aug 1 afternoon brief recommended EvidenceChaseBoard widget; still not built. Aug 3 morning brief raises “Closeout Package Completeness Matrix” — a per-spec-section dense table showing required item, responsible party, status, and blocker so PMs don’t have to open every record. The EvidenceChasePlan model in evidence_matrix_cell.dart is 3+ weeks old with no user-visible surface. Tonight’s isDark cleanup shows Closr+ momentum; the model-to-widget gap remains.
• DailyReportr+ Today Setup Card Depth (DailyReportr+) — Aug 2: “Today Setup Card Follow-Through” (structured morning kickoff with progress chips prefilling the daily log). Tonight: no feature build. The card is clean and stable after Katey’s Aug 2 border polish, but TodaySetupChecklist, today_setup_checklist, and SetupKickoff are all absent from lib/. The next step is depth, not polish.

Feature Ideas + UI/Code Health Recommendations

3 ideas (1 UI/code health, 2 features). Each verified against codebase and git history before listing.

UI Inconsistencies

• Buildr+ — Risk reason string rendered as plain gray text (concrete, new tonight) — cc7fada added reason = ‘Reviewer not assigned’ to SubmittalTurnaroundRisk, but submittal_review_radar_page.dart renders the same code path as plain text (‘Unassigned reviewer’) with no badge, color, or icon. Meanwhile, overdue items and high-risk states in the same radar page do use color-coded chips. A submittal with a missing reviewer now carries a +20 risk score internally but looks visually identical to a low-risk submittal in the list view. The inconsistency is between the model’s risk signal and the UI’s rendering of it — the same visual surface shows both high-risk (unlabeled) and lower-risk (unlabeled) submittals with equal visual weight.
• Inspectr+ — Contractor grade badge A–D color palette is new and undocumented — Tonight’s Contractor Closure Rate Scorecard adds A/B/C/D grade badges using inline green/blue/orange/red values. These colors don’t appear to reference the existing AppColors palette that governs deficiency aging, risk status chips, and inspection status indicators elsewhere in Inspectr+. If the Deficiency Aging Dashboard uses AppColors.riskHigh / AppColors.riskMedium for similar severity distinctions, the scorecard’s inline colors will drift visually. Not verified against every AppColors constant — recommend a one-pass check before the next Inspectr+ build extends the scorecard.

Competitive Intel

• Procore: New Products for Large Construction Owners (Summer 2026 Beta) — Procore announced Owner Hub, portfolio monitoring, concept projects, and asset management now in beta, with capital planning and funding source management entering beta this month (GA late 2026). This is a significant push into the owner-PM relationship tier — the enterprise layer above the project team. For Leonard’s apps, the play is the opposite direction: own the subcontractor and field side that Procore’s owner product will never touch directly. Closr+’s closeout chase, Inspectr+’s contractor scorecard, and DailyReportr+’s daily logs all live in that layer. Source
• Procore: Submittals Integrated with Project Schedule (Q1 2026 GA) — Submittals now appear as linked items on the project schedule; RFIs, Inspections, and Action Plans to follow. Teams are alerted when submittal review timelines conflict with critical-path activities. Buildr+’s submittal tracker should surface schedule slippage risk — when a submittal review bleeds into a linked activity, the “Reviewer not assigned” flag becomes a schedule risk, not just a paperwork gap. The new risk flag (tonight’s cc7fada) is the first step; schedule-linkage context is the natural follow-on. Source
• Procore: 20 Pre-Built AI Agents via Embedded Datagrid (May 2026) — AI agents auto-respond to punch items, observations, RFIs, and incidents based on customer-defined rules. For Closr+, automated evidence-chase reminders when a closeout package stalls are now table stakes in the enterprise tier. The Closeout Package Completeness Matrix (idea #3 above) is Closr+’s mobile-first, human-in-the-loop answer: make the gap visible before it needs an agent to chase it. Source
• Bluebeam Max: Claude AI Integration for Markup Automation (Global 2026) — Bluebeam Max integrates Anthropic Claude to enable natural-language prompts that automate markup tasks and transform markup data into actionable insights — launched globally in early 2026. For Closr+ and Buildr+: if annotated PDFs are a primary closeout and drawing-review artifact in the field, Bluebeam Max’s AI can now surface information from those markups directly. Tactical note: field users who run Bluebeam for redlines and then manually copy findings into Closr+ records are a friction point worth a future integration or deep-link target. Source

Tomorrow’s Build Suggestion

Night after tomorrow: Buildr+ SubmittalReviewerBadge widget (idea #1) is the cleanest single-session code health task — provider is live, widget is ~80 LOC, tests are clear. Either builder can take it. Inspectr+ SyncRecoveryPanel (idea #2) is the higher-impact pick if Katey has bandwidth after DailyReportr+.