Sunday, May 10, 2026 — 12:00 PM PT
Dominique shipped the certificate evidence bundle export, attaching supporting documents (warranties, O&M manuals, punch sign-offs, training records) to the completion certificate as a downloadable package. This was yesterday’s afternoon brief idea #2 and a 4-day morning brief streak — now shipped.
feature/nightly-20260510Katey/Howard-3 shipped the scan-to-history panel that displays an asset’s full inspection timeline after scanning a QR/barcode tag. Every deficiency, photo, resolution status, and inspector is now visible in a bottom-sheet panel. This was yesterday’s afternoon brief idea #1 and a 4-day morning brief streak — now shipped.
feature/nightly2-20260510Howard-1 shipped the owner callback queue, giving closeout teams a structured way to track owner follow-ups — urgent callbacks, punch counts, and contact details — in one prioritized list. This was today’s morning brief springboard idea (callback-to-punchlist bridge).
feature/nightly-20260510-owner-callback-queueNo commits landed on Buildr+ or DailyReportr+ in the last 18 hours. Last nightly activity: Katey on Buildr+ May 9 (Submittal Aging Tracker v3.8.0) and Howard-1 on DailyReportr+ May 9 (Material Delivery Risk Watch v2.17.0). Both are now tied for the longest gap across all repos.
dotenv dependency in tools/upload_sql_migrations.dart. All 4 apps are now error-free. Cleanest: Closr+ (257 total issues). Needs attention: DailyReportr+’s warning persists — assets/images/ declared in pubspec.yaml but the directory doesn’t exist. Inspectr+ climbed from 962 to 969 infos after the new feature.
The two most persistent morning brief themes have both been built overnight. Certificate evidence bundling was raised May 7–10 (4 consecutive days) and the scan-to-history panel was raised May 7–10 (also 4 days). Both were yesterday’s afternoon brief top ideas, and both shipped within 12 hours. The morning brief → afternoon idea → nightly build pipeline is converting at 2 of 3 ideas per cycle.
Yesterday’s morning and afternoon briefs both called for escalation rules on top of the Submittal Aging Tracker (v3.8.0). The tracker shipped May 9 with passive dashboard warnings; the missing layer is configurable notifications when submittals age past thresholds. This is the oldest unbuilt idea in the pipeline.
Today’s morning brief introduced the “Offline Conflict Receipt” concept: after reconnect, show the user exactly what was accepted, merged, or needs review. The Offline Conflict Review Queue shipped May 9 (v2.16.0), but it surfaces conflicts without a post-sync confirmation. This is the natural second step.
The Submittal Aging Tracker (v3.8.0) shipped May 9 with color-coded dashboard warnings. Add configurable escalation rules so overdue submittals move from passive banners to “notify PM / architect / GC” action queues. Define thresholds (7/14/21 days) and auto-generate in-app notifications or shareable follow-up packets when aging exceeds the configured tier.
Why now: Two consecutive morning briefs (May 9–10) have called for this. The aging tracker is live but passive — it shows the problem without driving action. Procore’s Dynamic Submittal Plan (DSP) enters open beta May 19 with automated deadline tracking and buffer time management. Shipping escalation rules before DSP goes GA keeps Buildr+ ahead on submittal action for small/mid GCs who don’t need Procore’s planning-first approach.
submittal_escalation_rules in Supabase with columns for threshold_days, action_type (notify/email/flag), and recipient_role. Create escalation_rules_page.dart with a simple rule builder. In submittal_aging_service.dart, check rules on each sync and queue notifications via flutter_local_notifications. Render rule hits in a compact ListView on the aging dashboard.
After reconnecting from offline mode, display a clean “sync receipt” showing what was accepted, merged, or flagged for human review. Field users trust offline mode more when they can see exactly what happened during sync. The receipt should show green/amber/red status per report section with a one-tap “review conflicts” action for amber items.
Why now: The Offline Conflict Review Queue shipped May 9 (v2.16.0) and surfaces conflicts for resolution, but there’s no post-sync confirmation. Today’s morning brief specifically raised this as the next step. Autodesk CC is investing in mobile-first document access (Issues routing, closed-issue filtering on mobile) — our offline-first advantage is strongest when sync feels transparent, not opaque.
sync_receipts table in Supabase with columns for queue_id, status (accepted/merged/needs_review), field_path, and synced_at. Create sync_receipt_card.dart as a dismissible bottom sheet that appears after each sync. Color-code each item: green (accepted), amber (auto-merged), red (needs review). Wire it into the existing offline_conflict_review_queue.dart sync callback.
The Owner Callback Queue shipped tonight (v2.14.0). Let any callback become a linked punchlist or closeout task with owner, due date, evidence needed, and final signoff status. This keeps owner follow-ups from living in a separate bucket after substantial completion — every callback resolves as a tracked task.
Why now: Today’s morning brief raised this as the immediate next layer on the callback queue. Closr+ just received two features in one night (v2.13.0 + v2.14.0) and is the most active app this cycle. Linking callbacks to punchlist items creates a closed loop that makes the App Store submission stronger: “from owner call to resolved task in one app.”
callback_task_links table in Supabase linking callback_id to task_id with link_type (punchlist/closeout). In the callback detail screen, add a “Create Task” FAB that pre-fills owner, due date, and evidence requirements. Show linked tasks as Flutter chips inside each callback card. Reuse the existing punchlist/closeout task model.
Procore — Dynamic Submittal Plan (DSP) entering open beta May 19. Automates submittal deadlines based on a single completion date, calculates Final Due Dates and Submit-By Dates with lead times, integrates with Procore Schedule, and adds Buffer Time management. Procore Explore also rolling out an “Early Access” lifecycle stage for faster feature iteration. (source)
Autodesk Construction Cloud — 35+ product releases in May. Key shipped features: Bridge As-Builts now work across data storage regions; folder permission report export for admins; Issues re-routing so members can reassign without full visibility; closed Issues hidden by default on mobile; new Insight Builder tool for custom reports and dashboards (Enterprise agreements). (source)
Fieldwire / Hilti — 3D task creation and Matterport integration shipped in Jan–Feb 2026. No new May 2026 feature announcements found. Their focus remains on BIM/3D overlays and voice-to-task integrations (Hardline). (source)
Bluebeam — No new feature announcements in the past 7 days.
Build the Submittal Aging Escalation Rules. Buildr+ hasn’t been built since May 9 and is tied with DailyReportr+ for the longest gap. Escalation rules have been the top unbuilt idea for 2 consecutive briefs. The aging tracker is live — this converts passive warnings into actionable notifications before Procore’s DSP beta launches May 19.
Build the Offline Sync Receipt. DailyReportr+ is also tied for the longest gap (last built May 9) and has the most total analyzer issues (1,496). The offline conflict queue is live but lacks post-sync confirmation. Sync receipts complete the offline story and differentiate against ACC’s mobile-only approach to field workflows.