← Reports Hub 📚 Library

Warranty Expiration Calendar REPORT 11

90-day look-ahead on expiring warranties. Honest capture gap.
๐Ÿ’Ž
Implications (per memory rule 1)
๐ŸŽฏ Bucket touchedMigrated (HCP-era warranties) + Pure ST
โš ๏ธ ProblemWarranty windows expiring in next 30/60/90 days create a re-call-out window. Without calendar visibility, BSP loses the renewal touch.
๐Ÿ’ฐ $ at stakeAvg warranty-expiry call โ†’ $250-$400 inspection or upsell. 50 expiries/mo ร— $300 = $15K/mo.
โœ… Action unlockedAuto-email warranty-expiry-30-days touchpoint. Stephanie approval to enable.
๐Ÿ“Š Full bucket diagram + 4 data-integrity findings: BSP HCP Intelligence Report (๐Ÿ“Š The Buckets ยท ๐Ÿ“… Timeline ยท ๐Ÿ’ธ LTV ยท ๐Ÿ” Why this matters ยท ๐ŸŽฏ The 4 Findings)

Status: Not captured yet

Warranty end dates are not stored in the Nexus warehouse. Neither titan.jobs nor the HCP customer export contains a warranty_end_date field. No fabricated data is shown. When warranty capture is wired, this page will populate with all jobs whose warranty expires in the next 90 days.

Lookahead Window
90 days
Upcoming Expirations
N/A
Data Available
No

Remediation Plan

Requires adding a warranty_end_date column to titan.jobs (or a new titan.warranties table) plus pulling ST and HCP warranty endpoints nightly. Estimated effort: 6 hours. Owner: Robert.

SourceMissing FieldFix
Loading...

Verification Gate

Produced? Read-only endpoint /api/warranty/calendar returns available=false with a documented gap list.

Correct? Validated against titan.jobs schema (no warranty_* column) and HCP export index (no warranties field).

Changed real data? No writes performed. Read-only.