Monday, May 11, 2026 — 12:00 PM PT
Dominique shipped submittal aging escalation rules, adding configurable notification tiers on top of the Submittal Aging Tracker (v3.8.0). When submittals age past defined thresholds, the system queues notifications for PM, architect, or GC. This was yesterday’s afternoon brief idea #1 and a 3-day morning brief streak — now shipped.
feature/nightly-20260511Howard-1 rescued Dominique’s failed TestFlight upload and shipped a follow-on feature: the transmittal delivery risk queue, which surfaces transmittals at risk of missed delivery deadlines based on recipient response patterns and lead times. A vtool architecture fix was applied to resolve the build failure.
feature/nightly-20260511-transmittal-delivery-riskKatey/Howard-3 shipped the offline sync receipt, displaying a post-sync confirmation card after reconnecting from offline mode. Each synced item shows green (accepted), amber (auto-merged), or red (needs review) status. This was yesterday’s afternoon brief idea #2 and a 2-day morning brief streak — now shipped.
feature/nightly2-20260511No commits landed on Closr+ or Inspectr+ in the last 18 hours. Last nightly activity: Dominique on Closr+ May 10 (Certificate Evidence Bundle v2.13.0) and Katey on Inspectr+ May 10 (Scan-to-History Panel v4.6.0). Both are now tied for the longest gap across all repos.
assets/images/ declared in pubspec.yaml but the directory doesn’t exist. Closr+’s warning is an unused import in share_project_dialog.dart. DailyReportr+ info count climbed from 1,496 to 1,511 after the Offline Sync Receipt feature.
The two most persistent morning brief themes from this cycle have both been built overnight. Submittal Aging Escalation Rules were raised May 9–11 (3 consecutive days) and shipped by Dominique. Offline Sync Receipts were raised May 10–11 (2 days) and shipped by Katey/Howard-3. The morning brief → afternoon idea → nightly build pipeline continues converting at 2 of 3 ideas per cycle.
Yesterday’s morning and afternoon briefs both called for linking owner callbacks to tracked punchlist items. The Owner Callback Queue shipped May 10 (v2.14.0) and surfaces which owners need follow-ups, but there’s no way to attach a callback to a specific punch item or closeout task. This is now the oldest unbuilt idea in the pipeline.
The Asset Tag Coverage Radar shipped in v4.5.0, and the Scan-to-History Panel shipped May 10 (v4.6.0). Morning briefs on May 10 and 11 have both called for deeper intelligence: a route heatmap (May 10) and a photo coverage staleness meter (May 11). The aggregate pattern is clear — field supervisors need spatial views of which assets are chronically skipped or failing, not just a percentage score.
From any row in the Owner Callback Queue, a “Link to Punch Item” action sheet lets the PM search open punch items for that project and attach one (or create a new one on the spot). The callback row then shows a badge with the linked item’s trade and status. When the punch item is cleared, the callback row auto-resolves. This turns a communication log into a traceable closeout action — from owner call to resolved task in one app.
Why now: Two consecutive briefs (May 10–11) have called for this. The Owner Callback Queue is live but disconnected from the punchlist data model. Closr+ has extensive punchlist structures (PunchListSummary, PunchListDeadlineTracker, Procore import) and a separate callback widget — but zero code linking the two. Autodesk CC just shipped issue-routing improvements and handover documentation that includes issues; linking callbacks to punch items keeps Closr+’s closeout story ahead.
callback_punch_link.dart model with callbackItemId, punchItemId, linkedAt, resolvedAt. Create callback_punch_link_provider.dart (Riverpod StateNotifierProvider over Supabase). In owner_callback_queue_card.dart, add onLinkTap callback showing a bottom sheet with punch item search + “Create new” option. Wire resolution: watch punchListCleared flag on RetainageEntry; auto-mark link resolved.
A new “Route Heatmap” tab on the project detail page renders a ranked list of each asset colored by scan frequency and failure rate over a configurable lookback window (7/30/90 days). Red-tier assets are either never scanned or failing every time; green assets are regularly scanned and clean. A “Suggest Route” button reorders the next inspection session to front-load red-tier assets. Tapping an asset row deep-links to its Scan-to-History panel.
Why now: The Asset Tag Coverage Radar (v4.5.0) tells you what percentage of assets have been scanned. The Scan-to-History Panel (v4.6.0) shows one asset’s timeline. Neither tells a supervisor which specific assets are chronically skipped, repeatedly failing, or over-inspected. Two consecutive morning briefs (route heatmap May 10, photo coverage meter May 11) have called for this spatial layer. Procore’s Inspections Bulk Create feature shows they’re investing in inspection workflow efficiency — our heatmap answers the “where to look next” question they haven’t.
asset_scan_heat.dart computed model with assetId, scanCount, failureCount, daysSinceLastScan, heatScore. Create route_heatmap_provider.dart aggregating InspectionItem history with a window filter. Build route_heatmap_page.dart with ListView of AssetHeatTile widgets, date-range SegmentedButton. Deep-link tap → AssetHistoryPanel (already exists). “Suggest Route” reorders local InspectionItem list by heatScore descending.
A microphone FAB on the daily report wizard launches a full-screen dictation sheet. The PM speaks freely (“got 6 ironworkers on deck 3, lost 2 hours to rain delay around noon, rebar delivery showed up late”). On stop, the transcript is sent to an AI prompt that extracts and slots content into work-performed, labor headcount, equipment, weather delay, and materials sections. The PM reviews pre-filled fields before confirming. Nothing overwrites existing entries — draft text is merged as a suggestion.
Why now: Raw voice capture already exists via voice_input_field.dart across individual form fields, but there’s no “dump it all at once” flow. Today’s morning brief specifically raised this. Fieldwire’s Hardline voice-to-task integration shows the market is moving toward voice-first field workflows. This differentiates DailyReportr+ from Procore’s Daily Log (which added 360 Reporting but no voice-draft capability).
voice_draft_sheet.dart full-screen BottomSheet with VoiceInputField in transcript mode + waveform animation. Create voice_draft_parser.dart service sending transcript to Claude API with a construction-log system prompt; returns DailyLogDraft model (workPerformed, laborCount, equipmentNotes, weatherDelay, materialsReceived). Wire FAB into daily_report_enhanced_wizard.dart; on return, merge draft into wizard state via existing WorkLogItem controllers. Gate behind Pro entitlement flag.
Procore — Inspections tool got a modernized layout plus Bulk Create (create multiple inspections at once). Daily Log and Scheduling tools received new 360 Reporting data fields (Feb/Apr 2026 rollout now fully live). AI agents via Datagrid acquisition: automate RFI generation, submittal review, and document analysis. Workflow Template Management now has a dedicated Type column for faster cross-tool template identification. (source)
Autodesk Construction Cloud — Handover documentation now includes issues (coordination conflicts, field observations) as part of the final project package. Issue permissions embedded in project templates for multi-project consistency. Mobile form attachments can be restricted by user role. New Insight Builder tool for custom reports (Enterprise tier). (source)
Bluebeam — Bluebeam Max launched Q1 2026 as a premium tier with AI Chat powered by Claude, natural-language document commands, and context-aware project assistance. Focus is on automating repetitive markup and data-extraction tasks while preserving professional judgment. (source)
Fieldwire / Hilti — No new May 2026 feature announcements. Their recent investment is in 3D task creation, Matterport integration, and Hardline voice-to-task workflows. Punch list tasks now require on-site verification by separate personnel before closing. (source)
Build the Callback-to-Punchlist Bridge. Closr+ hasn’t been built since May 10 and is tied with Inspectr+ for the longest gap. The callback-to-punchlist link has been the top unbuilt idea for 2 consecutive briefs. The Owner Callback Queue is live but disconnected from punchlist tracking — this closes the loop before Closr+’s App Store submission.
Build the Inspection Route Heatmap. Inspectr+ is also tied for the longest gap (last built May 10) and has the emerging “asset intelligence” theme from two consecutive morning briefs. The Scan-to-History Panel and Asset Tag Coverage Radar are live — the heatmap adds the spatial “where to look next” layer that turns passive metrics into actionable routing.