Range
Observed
Observed
Systems
Switches
Points
Executive Summary
Apex Fleet Services' Riverside operation was observed across 31 Voyager sessions totaling 175+ hours of continuous behavioral capture, covering the complete lifecycle of commercial fleet collision repair — from claim intake through estimate creation, parts procurement, repair coordination, post-repair InspectAI inspection, and final billing.
Apex Fleet's stated mission is fast cycle times, high-quality body repairs, and real-time visibility to maximize fleet uptime. The technology stack — ApexFleet.app, TrackPro, CommEstimate, ClaimLink ONE, FleetAuth, AutoAuth, InspectAI, The Digital Checklist, and Google Sheets — was selected to support that mission. However, the behavioral data reveals that these systems operate as islands. The single automated integration observed across 175 hours was the CommEstimate EMS export to TrackPro. Everything else — VINs, claim numbers, part numbers, delivery dates, dollar amounts, status codes — is manually carried between systems by the workforce.
Apex Fleet leadership has already identified two immediate priorities: (1) an automated parts ordering process that eliminates wasted motion and gives all parties clear line of sight to delivered and back-ordered parts, and (2) evaluating the feasibility of replacing TrackPro to eliminate the duplicate entry associated with updating multiple FMC-required spreadsheets. The Voyager data validates both priorities with behavioral evidence and quantifies the operational cost: an estimated 4–5 hours per employee per day consumed by pure data transfer overhead rather than value-creating work.
Processes Observed
Auto-Sync
Workflow
Automation
AI Draft
Smart Scan
Auto-Sort
Auto-Report
Workflow
Friction Patterns Observed
Directly addresses Priority #1. Parts status has no single source of truth. Delivery confirmations arrive via email (Titan Delivery, BodyWorks Mfg, Regional Truck Parts), are manually logged in TrackPro, manually updated in ClaimLink ONE, and manually re-entered into FMC spreadsheets. Back-ordered parts (e.g., PART-00101 on b/o until 3/6/26) are tracked by memory and manual FedEx lookups — not system alerts.
Delivery → TrackPro
(manual note) → ClaimLink ONE
(invoice attach) → Google
Sheets → Gmail
(confirm)
Directly addresses Priority #2. Apex Fleet maintains 4+ Google Sheets for FMC tracking — Alpha Fleet Riverside Vans, GAMMA FLEET RIVERSIDE, Bravo Fleet Riverside, Tractor & Route Completions — as noted in the client brief: "all of which are present in TrackPro." The behavioral data confirms this: every single sheet update observed was a manual re-entry of data that already existed in TrackPro.
(source of truth) → Calculator
(arithmetic) → Alpha Fleet
Sheet → Gamma Fleet
Sheet → Tractor
Sheet
Supports the TrackPro replacement evaluation. TrackPro and ClaimLink ONE operate as completely separate systems with zero data sync. Every claim exists in both but is maintained independently — VINs, dates, amounts, notes, and status codes are entered twice. This is the single highest-volume friction pattern observed.
(claim mgmt) ⇄ ClaimLink ONE
(estimating)
Every physical document — invoices, ROs, credit memos, parts lists — passes through a 5-application pipeline before reaching its destination. The naming convention is perfectly predictable (Scan_[date]RO[number]) but no scan-to-system integration exists. The employee is the entire pipeline.
Scan 2 → Windows
Scan → Photos
(rename) → Explorer
(move) → ClaimLink ONE
(attach)
Application Landscape
What the Data Reveals
Apex Fleet leadership identified the right problems. Here's what 175 hours of behavioral evidence adds to the picture.
Priority #1 — Parts: Confirmed
The parts visibility problem is deeper than ordering. It extends to receipt verification (12x/day manual logging), back-order tracking (FedEx checked 5+ times manually), wrong-part handling (PART-00303 too small, PART-00202 quoted twice), and return processing (Adobe form fill → email → wait for ticket). An automated parts process needs to cover the full lifecycle, not just the purchase order.
Priority #2 — TrackPro: Nuanced
The spreadsheet problem is real — 20+ manual sheet updates per day, all duplicating TrackPro data. But the behavioral data suggests the issue isn't TrackPro itself — it's the absence of an integration layer. TrackPro is the most-used system (42h focus time, 680 context switches). Replacing it carries significant retraining risk. The faster, lower-risk path may be building the auto-fill bridge from TrackPro/ApexFleet.app to the FMC sheets rather than replacing the production system.
Surfaced: The Document Pipeline
Neither client priority mentioned document management, but it emerged as a top-3 time sink: 15+ scans/day through a 5-app chain, plus photo management (up to 63 photos per vehicle, individually renamed). This is 1.5–2 hours of daily overhead that wasn't visible without behavioral observation. It's also the easiest to automate.
Surfaced: Knowledge Concentration
The manual processes — exact cell references in 4+ Google Sheets (H11, K6, F13), file naming conventions, vendor email addresses, Notepad templates, calculator workflows — all exist in two employees' heads. None are documented. If either person leaves, Apex Fleet doesn't just lose an employee — it loses the integration layer between its own systems. Automation makes this knowledge system-resilient.
Process Inspection
Interesting Observations
📋Operational Strengths
- Highly systematic workforce — identical process sequences across every session, zero shortcuts taken
- 15+ active ROs at any time across Alpha Fleet, Gamma Fleet, Delta Carrier, Kilo Carrier, Bravo Fleet, Foxtrot Fleet, Papa Logistics, Xray Express
- Cross-location capability: TrackPro switches between Riverside, Phoenix/Embedded (National Mesa), and Greenville (Uniform Svc)
- InspectAI quality system integrated into closeout — post-repair inspections trigger supplement cycles when needed
- Proactive risk documentation: windshield supplement note added preemptively ("if it breaks during roof repair, submit supplement")
🔐Security & Access Signals
- Password captured in session: "[REDACTED]" visible during login
- Shared ClaimLink ONE login: "[shared_login]" used by parts specialist — not a personal credential
- Dual Gmail accounts: [email protected] + [email protected] used interchangeably
- Windows Credential Manager stores passwords for TrackPro, InspectAI, FleetAuth, ClaimLink ONE, RepairTech
- FleetAuth unique credential: "[REDACTED]" — separate from all other system logins
⚙️Workaround Inventory
- Notepad stores recurring email body text — copy-pasted into Gmail daily ("Today's invoices" template)
- Windows Calculator used for invoice totals and billing math — no formulas in source systems
- Microsoft Word used to create physical folder labels per job (unit #, job #, client, date)
- Snipping Tool captures Excel screenshots for "Tractor Completions" email reports to accounting
- Google Search used as parts catalog — part numbers searched to identify what they are
- Adobe Acrobat form-fill used for BodyWorks Mfg return requests and GraphicPro Decals decal orders
💡Parts Process Signals
- Duplicate ordering: PART-00202 quoted twice across Kilo Carrier RO-1234/RO-1234B — no system caught it
- Wrong part delivered: PART-00303 too small for Hino 2771100 — manual vendor correction
- Unneeded parts delivered: BodyWorks Mfg PART-00404L/R arrived after supplement changed scope
- No delivery alerts: FedEx [tracking-number] manually checked 5+ times — no push notification
- Vendor-specific return processes: BodyWorks Mfg (PDF form + email), Regional Truck Parts (email to Keith/Riverside parts), National Auto Parts (vendor return portal + printed return label) — no unified return workflow
- One-time pricing: 10% discount manually entered in ClaimLink ONE for Papa Logistics — no rules engine
Automation Recommendations
All automatable patterns identified across 175+ hours of observation — ranked from highest to lowest impact, regardless of implementation effort.
The highest-volume friction pattern observed. Every single claim exists independently in both TrackPro and ClaimLink ONE. VINs, claim numbers, dates, amounts, disposition notes, and status codes are entered twice — once in each system. This was observed in 100% of sessions for both employees and consumes an estimated 2+ hours daily across the operation. Directly supports the TrackPro replacement evaluation — if sync is built, replacement may not be necessary.
Bidirectional Field Sync: When a claim is created or updated in either TrackPro or ClaimLink ONE, Beam detects the change and mirrors it to the other system. VIN, claim #, dates, amounts, and status stay synchronized. Eliminates the need to maintain two parallel records. Could be the bridge that makes TrackPro replacement unnecessary.
Directly addresses Priority #2. Apex Fleet maintains 4+ Google Sheets for FMC tracking — Alpha Fleet Riverside Vans, GAMMA FLEET RIVERSIDE, Bravo Fleet Riverside, Tractor & Route Completions — all duplicating data already in TrackPro. Observed 20+ manual updates per day at 4 minutes each. The fastest path to value: build the auto-fill bridge rather than replace the production system.
Chrome Extension Trigger: When any user updates a TrackPro disposition, Beam detects the claim number and pushes the change to the correct row in the correct FMC Google Sheet via Sheets API. Alpha Fleet, Gamma Fleet, Bravo Fleet, and Tractor sheets all stay synchronized. Zero re-keying. Preserves TrackPro as-is.
Directly addresses Priority #1. The behavioral data shows the parts problem extends far beyond ordering: receipt logging (12x/day across 5 systems), back-order tracking (manual FedEx lookups), wrong-part detection (employee catches, not system), and return processing (PDF form + email). A complete parts automation solution needs to cover the full lifecycle.
Parts Dashboard + Auto-Log: Unified view across all active ROs — ordered, in-transit (carrier tracking auto-polled), delivered, back-ordered. On delivery, scan PO# → Beam auto-logs in TrackPro, auto-attaches to ClaimLink ONE, auto-updates FMC sheet, auto-sends confirmation. Duplicate detection flags cross-RO part issues before ordering.
Not in the client's stated priorities — surfaced entirely by Voyager. The 5-app scan chain (Epson → Windows Scan → Photos → Explorer → ClaimLink ONE) consumes 6 minutes per document, 15+ times per day. The naming convention is deterministic (Scan_[date]RO[number]) and destinations are predictable. No human judgment needed. Easiest win on the board.
Smart Scan Profile: Enter RO# once → Beam auto-names (Scan_[date]RO[number].pdf), auto-files to correct job folder, auto-attaches to ClaimLink ONE workfile and ApexFleet Portal. Eliminates Photos, Explorer, and manual file dialogs entirely.
Damage photos are downloaded from Google Drive, then individually renamed (up to 63 photos per vehicle — e.g., "RO-5678_01.jpg" through "RO-5678_30.jpg"), then uploaded to ClaimLink ONE estimates. This process was observed 10+ times daily and is entirely pattern-based: the naming convention is [RO]_[sequence]. Zero judgment required.
Auto-Sort & Bulk Rename: Beam watches the Google Drive folder, auto-sorts incoming photos by RO#/VIN, bulk-renames to standard convention, and pre-stages for ClaimLink ONE upload. One-click attach replaces the per-photo rename workflow.
Parts quote requests (Regional Truck Parts, CrossCountry Parts), return emails (BodyWorks Mfg, vendor contact), delivery confirmations, and daily reports follow predictable patterns — same recipients, same structure, same attachments. Currently composed by searching old sent mail or copying from Notepad templates. 15+ emails per day across the operation.
Context-Aware Email Composer: From inside a TrackPro job view, click "Request Parts Quote" — Clarion auto-drafts with correct vendor (Regional Parts, CrossCountry Parts, BodyWorks Mfg), populated subject/body (unit #, claim #, VIN), and auto-attached parts list PDF. User reviews and sends. Replaces Notepad templates, sent-mail searching, and manual attachments.
Two emails sent every single day without variation: "Today's invoices [date]" with attached scans, and "Tractor Completions - [date] - Oakdale OH" with a Snipping Tool screenshot. Same recipients, same subject format, same body text from Notepad. Observed in 100% of sessions. The definition of automatable.
One-Click Daily Report: End of day, user clicks "Send Daily Reports." Clarion auto-composes both emails with today's date, pre-attached scans from the day's job folder, Tractor Completions data auto-captured from Excel, same recipients pre-filled. Eliminates Notepad, Snipping Tool, and manual attachment.
FedEx tracking number [tracking-number] was manually checked 5+ times across two sessions. Back-ordered part PART-00101 (ETA 3/6/26) tracked by memory only. No push notifications exist for delivery status changes. This is a sub-component of Priority #1 — giving all parties "clear line of sight to delivered and back-ordered parts."
Carrier Tracking Auto-Poll: Beam monitors active tracking numbers (FedEx, ArcBest, UPS) and pushes status change notifications to a parts dashboard and/or email. "Part # PART-00101 delivered" triggers auto-log in TrackPro. "B/O ETA changed to 3/10" surfaces immediately instead of requiring manual lookup.
Part # PART-00202 was quoted twice across Kilo Carrier RO-1234 and RO-1234B — only 1 was needed between the two parts lists. Caught by the employee, not by any system. This represents wasted vendor time, potential wasted spend, and return processing overhead. A cross-RO comparison at order time would prevent this.
Cross-RO Part Comparison: When a parts order is created, Beam scans all active ROs for the same customer/unit and flags any part numbers that appear on multiple orders. Alert: "PART-00202 already ordered on RO 12286 — confirm before re-ordering."
Every new job requires: create Windows folder (JOB-00112315), create Word label document (unit #, job #, client, date, status), download CommEstimate estimate/photos/worksheet, create TrackPro disposition, upload files to ApexFleet Portal. Observed 3x per day, 12 minutes each. Each step is deterministic given the job number.
One-Click Job Setup: Enter job # and client → Beam creates Windows folder, generates label PDF, downloads CommEstimate files, creates TrackPro disposition with pre-filled fields, and stages files for Portal upload. 12 minutes → 3 minutes.
Each vendor has a unique return process: BodyWorks Mfg requires Adobe form fill + email, National Auto Parts uses vendor return portal + printed return label, Regional Truck Parts requires email to specific contacts. Observed 3–5 returns per week at 8–10 minutes each. Parts PART-00404L/R were delivered after scope changed — return triggered because no system flagged "parts no longer needed."
Vendor-Specific Return Templates: Select vendor + parts → Beam auto-fills the correct form (BodyWorks Mfg PDF, National Auto Parts portal, Regional Parts email), populates PO#/part#/reason, and routes to the correct contact. Also: auto-flag when a supplement removes parts that have already been ordered.
InspectAI post-repair inspection results are manually transcribed into TrackPro notes ("Tech A passed the InspectAI 2/25/26 @ 3:31pm") and status sheets. InspectAI failures trigger supplement cycles (observed with RO-7890, RO-7891). No automated connection between InspectAI grading and TrackPro/Sheet status. Observed across multiple sessions.
InspectAI Webhook → Auto-Update: When a InspectAI session completes (pass or fail), Beam captures the result and auto-posts to TrackPro note + updates Alpha Fleet/status sheet. InspectAI failures auto-create supplement flag in TrackPro. Eliminates manual transcription of inspection outcomes.
Decal orders and Titan Delivery vehicle forms require manual Adobe Acrobat fill (RO#, VIN, address, phone, name) → save with RO suffix → email to GraphicPro Decals ([email protected]). ProMaster 2026 form and Titan Delivery Alpha Fleet 26' Hino form both observed. 2–3 per week, 5 minutes each. Low volume but zero judgment — purely template-driven.
Form Auto-Fill & Send: From TrackPro job view, click "Order Decals" → Beam auto-fills the ProMaster/fleet delivery form with RO#, VIN, address, and contact from the existing claim record, saves with correct filename, and drafts the email to GraphicPro Decals with attachment. User confirms and sends.
Every new tractor/commercial job gets a physical folder with a Word-created label: unit #, job #, client code (Delta Carrier/Kilo Carrier/CrossCountry Parts), status ("Prequal requested"), and date. Observed for JOB-001/12315 and JOB-003/12316. Each label takes 2–3 minutes in Word. Low volume (3/day) but completely eliminable.
Auto-Label from Job Setup: When a new job is created in TrackPro, Beam auto-generates and prints the folder label with unit #, job #, client, date, and status. Eliminates Word entirely from the job setup workflow. Bundles naturally with the Job Setup recommendation.
Voyager captured a visible password ("[REDACTED]"), a shared ClaimLink ONE login ("[shared_login]"), dual Gmail accounts used interchangeably, and 5+ systems with credentials stored in Windows Credential Manager. FleetAuth uses a completely separate credential ("[REDACTED]"). This isn't a time-savings play — it's a security and audit risk that compounds across locations.
SSO / Password Manager Rollout: Consolidate credentials behind a single sign-on layer or managed password vault. Assign individual ClaimLink ONE logins (retire "[shared_login]"). Rotate the exposed password. Establish a policy for dual-account Gmail usage. This is a governance fix, not an automation play — but the behavioral data makes the risk visible.