Why EQTracker
Field truth in 2 taps — complements telematics with the human context crews actually use.
Without EQTracker (today)
- Text/call chains to find machines.
- Moves happen before engines power on → telematics sees nothing.
- Notes live in group chats, not in a ledger.
- Apps with logins and 10 taps → people skip it.
With EQTracker
- Move: pick Project/Area, optional map link → save.
- Log Usage: work code chip + qty/note ("Pond E lift 2").
- Works offline; kiosk for folks who hate phones.
- Append-only history — no gotchas, no edits hiding mistakes.
Pain points
- "Where is it?" calls all day.
- Teeth/bucket swaps, small gear, rentals are invisible.
- Handoffs with no name/time/location trail.
- Telematics hours ≠ field usage → disputes.
What EQTracker gives you
- Live list by Project/Area/Custodian.
- Map button opens the exact dropped pin link.
- Append-only audit of Moves & Usage (CSV export).
- Spot hour-meter mismatches fast (usage notes vs telematics).
We don't replace telematics; we document the human context they can't see.
Cost of the status quo
- Minutes lost every time someone hunts a machine.
- Rework/idling from missed handoffs.
- Delayed repairs (no clear "down" moment).
Measurable outcomes
- –50% "where is it?" calls/texts.
- >85% same-day move/usage logging.
- –1 day from "down" to wrench-on.
Side-by-side
Problem
- No one knows who moved what, where.
- Notes scattered in chats.
- Pre-engine moves invisible to telematics.
EQTracker (2 taps)
- Move → Project/Area + optional map link.
- Log Usage → code + qty + short note.
- Append-only timeline per machine.
Impact
- Less hunting, faster handoffs.
- Clear responsibility and history.
- Better reconciliation with telematics.
What we intentionally don't do
No QR/NFC. No background GPS. No complex dashboards. No silent edits. We're the human ledger for the ground truth.