Tuesday, May 12, 2026 — 12:00 PM PT
Dominique shipped the callback-to-punchlist bridge, linking owner callbacks in the Owner Callback Queue to formal punchlist items and closeout tasks. PMs can now attach a callback to an existing punch item (or create one inline) and the callback auto-resolves when the linked item clears. This was yesterday’s afternoon brief idea #1 and a 2-day morning brief streak — now shipped.
feature/nightly-20260512Howard-3 shipped the certified delivery packet for transmittals — a one-tap bundle that packages the transmittal PDF, recipient list, timestamps, and receipt status into a dispute-ready packet. This was yesterday’s morning brief idea and extends the Transmittal Delivery Risk Queue (v3.10.0) that Howard-1 shipped the night before.
feature/nightly2-20260512Katey shipped report search and status filters, giving inspectors the ability to search across inspection reports and filter by status (open, in progress, closed). This layers on top of the Scan-to-History Panel (v4.6.0) and makes it practical to find specific reports in large project histories. Howard-1 followed up with a version bump fix after merge.
feature/nightly-20260512No commits landed on DailyReportr+ in the last 18 hours. Last nightly activity: Howard-3 on May 11 (Offline Sync Receipt v2.18.0). DailyReportr+ now has the longest gap across all repos and is the top priority for the next nightly cycle.
assets/images/ pubspec warning persists; the dominant info-level issue across all apps remains Color.withOpacity() deprecation.
The Callback-to-Punchlist Bridge was raised in morning briefs on May 10–11 and was yesterday’s afternoon brief idea #1. Dominique shipped it overnight (v2.15.0). The Owner Callback Queue (v2.14.0) now connects directly to punchlist tracking, completing the closeout communication loop. The morning-to-nightly pipeline continues converting at high velocity.
Three consecutive morning briefs (May 10–12) have called for reducing manual text entry in DailyReportr+: Offline Conflict Receipt (shipped May 11), Voice-to-Daily-Log Draft (May 11), and No-Data-Tax Field Capture / tap chips (May 12). The pattern is clear — supers need faster data input methods that don’t require typing on a dusty jobsite. The Offline Sync Receipt addressed trust in offline workflows, but the typing-reduction gap remains wide open.
Morning briefs on May 10 (route heatmap), May 11 (photo coverage meter), and May 12 (closeout gap concierge cross-referencing inspections) all push for aggregate views on top of per-asset data. The Scan-to-History Panel (v4.6.0) and Report Search & Status Filters (v4.7.0) now handle individual records well — the next layer is project-level rollups answering “how much have I covered?” and “where should I look next?”
A persistent, per-project crew roster that lets superintendents tap crew members from a saved list rather than typing names and trades into each day’s work log. On first use the user builds a roster (name, trade, company) which syncs to Supabase. On subsequent daily reports, the work log section presents the roster as a grid of tappable chips. Tapping a chip auto-fills a work log row with that crew member’s name, trade, and company. Chips show a green check for members already logged today, and the roster learns from prior days (most-frequent members float to top).
Why now: Three consecutive morning briefs have called for less typing in DailyReportr+. The work log section is the single most repetitive data entry point in daily reporting — supers type the same crew names every day. Voice input and Quick Log exist, but neither eliminates the per-row name entry. DailyReportr+ has the longest nightly build gap (last built May 11), making it the top priority. Procore’s punch notification overhaul shows competitors polishing core field workflows — our crew roster shortcut differentiates on input speed.
crew_rosters Supabase table (id, project_id, user_id, name, trade, company, frequency_score). Create crew_roster_provider.dart (Riverpod AsyncNotifierFamily keyed on projectId). Build CrewChipGrid widget — a Wrap of FilterChip widgets reading from the roster. Tap toggles selection and calls workLogProvider.addFromCrew(member). Long-press opens edit sheet. Embed above the existing work log ListView in daily_report_page.dart behind a “Tap to add crew” expansion tile. Offline: use existing Drift/SQLite cache with sync queue.
A project-level dashboard card displaying three radial gauge meters: (1) Asset Inspection Coverage — percentage of tagged assets inspected at least once, (2) Overdue Reinspection Count — assets past their reinspection interval with a countdown badge, and (3) Inspection Cadence Score — rolling 30-day average of inspections per week vs. the project’s target frequency. Each meter is tappable, drilling into the filtered list of relevant assets. The card surfaces on the project detail page below the Scan-to-History Panel.
Why now: Three morning briefs (May 10–12) have called for aggregated views on top of per-asset Scan-to-History data. The Scan-to-History Panel (v4.6.0) and Report Search & Status Filters (v4.7.0) handle individual records but there’s no project-level rollup answering “how much of my site have I actually covered?” Autodesk CC just shipped asset inspection filtering by active forms — our coverage meter goes further with a KPI dashboard that turns passive data into an accountability signal.
rpc_inspection_coverage_stats(project_id) Supabase RPC returning total_assets, inspected_assets, overdue_count, inspections_last_30d, target_weekly_rate. Create inspection_coverage_provider.dart (Riverpod FutureProvider.family). Build InspectionCoverageMeterCard with three radial gauge arcs via CustomPainter, each with percentage label and subtitle. Tap handler pushes filtered InspectionItemsPage. Add to project_detail_page.dart after the Scan-to-History Panel section.
A dashboard card that computes a projected closeout completion date for each active project based on historical resolution velocity. It divides remaining open items (punch list + checklist) by the rolling 14-day average items-closed-per-day rate to produce an ETA. Projects are color-coded: green if the ETA is before the contract closeout deadline, yellow if within 7 days, red if projected to overshoot. Tapping opens a detail view with a mini burndown sparkline and a breakdown of which categories (punch items, documents, checklist items) are dragging the forecast.
Why now: The Callback-to-Punchlist Bridge (v2.15.0) just shipped, generating more trackable items flowing into Closr+’s punchlist system. The existing Closeout Timeline shows where a project is in the pipeline but not when it will finish. PMs need a forward-looking signal to prioritize effort across projects. Procore’s redesigned submittal experience with automated deadline calculations shows the market moving toward predictive project intelligence — our velocity forecast applies that pattern to closeout.
rpc_closeout_velocity(project_id) Supabase RPC returning open_items, resolved_last_14d, avg_per_day, projected_completion_date, contract_deadline, status_color. Create closeout_velocity_provider.dart (Riverpod FutureProvider.family). Build CloseoutVelocityCard showing projected date in large text with color-coded risk badge, a Sparkline widget (via fl_chart) for the burndown, and “View Breakdown” link. Embed on project detail page and optionally on portfolio dashboard. Offline: fall back to last-cached forecast with “Last updated” timestamp.
Procore — Redesigned Submittal Experience shipping May 19: a centralized “Submittal Plan” card replaces manual data entry with automated deadline calculations across the submittal workflow. Separately, the Punch Tool email notifications are getting overhauled with improved hierarchy, clearer CTAs, and better readability as part of their Email Modernization Initiative. (source)
Autodesk Construction Cloud — RFI workflow enhancements: new “Pending action from” and “Last updated on” fields for at-a-glance status tracking, plus RFI managers can now include attachments in official responses. Asset Inspections filtering allows users to filter assets on sheets and model files by “Active Forms” to find which assets have open inspections. (source)
Fieldwire / Bluebeam — No new May 2026 feature announcements from either. Fieldwire’s recent investment remains in 3D task creation and Matterpoint integration. Bluebeam Max (AI-powered premium tier with Claude) launched Q1 2026 but no new closeout or field features this week.
Build the Crew Roster Quick-Select. DailyReportr+ has the longest nightly build gap (last built May 11) and is the only app that didn’t receive a build tonight. Three consecutive morning briefs have called for reduced typing in field capture. The crew roster addresses the most repetitive data entry point — typing the same crew names every single day — and converts it into a tap-based workflow that learns from usage.
Build the Closeout Velocity Forecast. The Callback-to-Punchlist Bridge just shipped tonight, generating more trackable items that feed into the closeout pipeline. With the bridge live, the natural next question is “when will we finish?” — the velocity forecast answers it. Closr+’s App Store submission is on the to-do list; shipping a forward-looking KPI card strengthens the value proposition before review.