Failure PatternDecision layer
The Perifleet Retention Illusion Trap: When Agencies Sell 2-Year Archives That Never Get Written
Symptom: Client asks for footage from a collision 14 months ago and the MyGeotab video tab returns nothing, even though the retainer promised two-year retention. Root cause: Retention is plan-gated, not universal: Standard holds 90 days, Plus holds one year, and only Premium reaches the two-year archive, so agencies quoting the headline retention while provisioning Standard create a coverage gap they cannot close retroactively.
By InnovaAI ResearchPublished
How do you recognize it?
- •Client asks for footage from a collision 14 months ago and the MyGeotab video tab returns nothing, even though the retainer promised two-year retention
- •Storage buckets in Azure Blob or AWS S3 show near-zero object counts months into the engagement while Perifleet dashboards look healthy
- •Incident clips exist only for Geotab rule triggers, so camera-native AI events the client cares about never appear in the archive
- •Agency invoices the Standard tier at $12/mo per vehicle but the client's insurance claim needs clips older than the 90-day window Standard actually covers
- •Onboarding stalls at the camera adapter step and the agency bills setup hours without a single validated incident trigger
Why does it happen?
- •Retention is plan-gated, not universal: Standard holds 90 days, Plus holds one year, and only Premium reaches the two-year archive, so agencies quoting the headline retention while provisioning Standard create a coverage gap they cannot close retroactively
- •Perifleet only archives triggered clips, so a client expecting continuous recording discovers that untriggered footage was never captured regardless of storage configuration
- •The camera-agnostic REST adapter layer must be connected and validated per vendor before any clip lands in Azure Blob or AWS S3, and skipping validation leaves the bucket provisioned but empty
- •Because Perifleet runs as a native MyGeotab add-in, agencies without admin access to the client's database cannot confirm storage bucket region, redundancy, or retention settings, and misconfiguration surfaces only at claim time
How do you fix it?
- •Open the Perifleet add-in inside the client's MyGeotab database and confirm the active plan tier against the retention the contract promises, then upgrade to Plus or Premium before the first incident window closes
- •Trigger a test incident through a Geotab rule and verify the clip appears in the Azure Blob or AWS S3 bucket with the expected retention tag, repeating per camera vendor
- •Audit the camera adapter connections for every vehicle and re-run validation on any vendor that shows no clips in the last 30 days
- •Rebuild the client-facing scope document around the exact retention tier sold, listing which incident types are captured by Geotab rules versus camera AI triggers
More on Perifleet
- StrategyWhy Perifleet Turns Fleet Video Retention Into Agency Retainer Revenue
- ConceptPerifleet Retention Window Math
- Evaluation RulePerifleet Rule: Adopt Only When the Client's Liability Window Exceeds 90 Days
- Decision FrameworkPerifleet: Buy vs Skip (Geotab Fleets With Long-Tail Liability Exposure)
- Implementation BlueprintPerifleet Fleet Safety Retainer Build (7-10 days)
- Operating ProcedurePerifleet Incident Clip Retention Setup (Onboarding)
More for Analytics and Reporting Tools
- Failure PatternsThe AgencyAnalytics Dashboard Bloat Trap: Why Agencies Fail With AgencyAnalytics in Multi-Client Reporting
- Failure PatternsWhy Agencies Fail With Adriel in the Dashboard Bloat Trap
- Failure PatternsWhy Agencies Fail With Agency Dashboard in Client Reporting
- Failure PatternsWhy Agencies Fail With Amplitude in Client Reporting