Field Sales

Field reps lie about where they are. They clock in from the car three blocks away. They mark a site "visited" without leaving the truck. Managers know this happens, reps know managers know, and everyone pretends. The usual fix is constant GPS tracking — phone pings every 30 seconds, red geofences screaming on a dashboard. But that breeds resentment, burns battery, and says "we don't trust you" louder than any policy memo. Velocity X check-in takes a different angle: one-tap GPS capture at the moment you want proof, paired with falsification detection that spots the obvious lies without watching the day-long breadcrumb trail.

What One-Tap Check-In Actually Solves

The core problem: when did the rep actually arrive at the site? Not "sometime during a 4-hour window" — what time did their wheels hit the ground? One-tap check-in captures GPS coords, timestamp, and accuracy radius the moment the rep opens a customer record and presses "here now". That signal is legally defensible, timestamped, and attached to the deal in your CRM. Admin sees "rep checked in at 2:47pm, 47 metres accuracy, coordinates verified". Done. No shift-long surveillance, no privacy theatre, no low-battery complaints.

Why one-tap beats full-shift tracking: a rep clocking in from a McDonald's parking lot before driving to the real site is a cultural problem, not a technology problem. Full-time GPS logging does catch it (until they leave the phone at home or give it to the intern). But you've now built a system that screams "we monitor you constantly" — which means you're hiring people you don't trust, or you've created a workplace where trust eroded. One-tap says "we need proof at the moment that matters" and implicitly trusts the rest of the day. Paradoxically, that builds more compliance than surveillance.

The Architecture — Web Geolocation API + Falsification Detection

Under the hood, Velocity X uses the Geolocation API (navigator.geolocation.getCurrentPosition in modern browsers). When the rep taps, the app requests location permission once, grabs the current coords with an accuracy radius, and sends it to your Supabase backend. The backend logs the GPS point, timestamp, and accuracy (in metres).

Falsification detection runs in a second pass: the backend cross-checks the GPS coords against known cell-tower coverage maps for that geographic region. If a rep claims to be at 40 Queen Street but the cell signal points to a tower 2km away, or if they're in an area with zero cellular coverage but somehow report from a single location ten times in one hour, the system flags the check-in as "low confidence" and asks for visual proof (photo of storefront, business card, etc.). This isn't about catching every lie — it's about stopping the stupidest ones without requiring a human investigator.

Accuracy radius matters. Outdoors, GPS is typically 10–50 metres. Indoors in a dense building, it blurs to 50–200 metres. The system stores the raw accuracy and lets you set a tolerance per customer — a sprawling retail park might allow 100m, a small office building might require 30m. If accuracy falls outside the threshold, the check-in is logged but flagged for manual review.

What Admins Actually See

The admin dashboard shows a live map of today's check-ins. Each pin is a rep, coloured by check-in time: green for on-time, yellow for late, red for flagged (low-confidence coords). Click a pin and see the customer name, scheduled arrival time, actual arrival time, accuracy radius, and whether the check-in is verified or pending. Drill into a flagged check-in and see the cell-tower cross-check result. If you want photo proof, there's a "request evidence" button that sends a push notification to the rep's app asking for a timestamped photo.

No rep-tracking map. No "where are they now" voyeurism. Just check-in moments, timestamped, with enough context to spot the pattern liars and trust the rest.

Privacy and Battery

Because check-in is one-tap and infrequent (typically 3–8 times per day), there's no constant battery drain. Geolocation API calls that run once per visit are negligible. The rep's phone stays private the rest of the day — no background GPS daemon, no data-sharing clause buried in an employment contract, no creepy "activity timeline" of where they grabbed lunch.

For compliance with regional privacy law (GDPR, Australia's Privacy Act), one-tap check-in is easier to justify than shift-long tracking. You're capturing location at a business-critical moment (customer arrival) for a specific purpose (verifying the visit). That's a legitimate use case. Constant location logging is harassment wearing a tech costume.

Frequently Asked Questions

What if a rep spoofs GPS?

Spoofing requires rooting the phone (Android) or jailbreaking (iOS) and installing a mock location app, then disabling safety checks. It's technically possible but it requires effort and intent — which is the point. You're not trying to stop a determined attacker, you're catching reps who are lazy about honesty. If a rep is determined enough to root their phone to lie about location, you have a bigger hiring problem anyway.

Does it work without cell service?

GPS works without cellular. But the falsification check (cell-tower cross-reference) requires internet, so you can't validate the check-in until signal returns. The raw GPS capture happens offline and syncs once the phone has data. In remote areas where cell coverage is intermittent, lower the bar for accuracy-radius verification or skip the cell-tower check entirely.

What about privacy objections from reps?

One-tap check-in is privacy-forward compared to alternatives. Frame it as: "We capture your location only at check-in moments, not throughout the day. We verify you arrived when you said, then trust you for the rest of your shift." That's a clear trade-off, not surveillance creep. If reps still object, they're telling you something else is wrong (manager relationship, compensation, autonomy). Fix that instead of tweaking the tech.

How accurate is Web Geolocation on Android vs iPhone?

Both use GPS + WiFi + cellular triangulation. Accuracy is device and environment dependent, not OS-dependent. Outdoors with clear sky: both hit 5–15m. In a dense building: both degrade to 50–100m. Set your tolerance by location type, not device type. If you need higher accuracy, consider adding Bluetooth beacons at the entry point, but that's overkill for most field sales use cases.

Can I require a photo alongside GPS?

Yes. Enable the "proof" mode in Velocity X and the rep gets a camera prompt after check-in. The app captures a timestamped photo, embeds the GPS coords in the EXIF metadata, and attaches both to the deal. This is insurance against "the GPS must be wrong" disputes and proves the rep was actually there. Useful for high-value or high-doubt scenarios.

What if check-ins cluster but routes look unrealistic?

One-tap check-in is orthogonal to route planning. You might notice a rep has three check-ins on the same street in 2 minutes, which smells like they're gaming the system (checking in for three different deals from a car parked in one spot). That's a conversation with the rep, not a tech problem. Velocity X surfaces the data cleanly; you interpret the pattern.

The Bottom Line

Shift-long GPS tracking treats field staff like parolees. One-tap check-in treats them like professionals who need to prove they showed up. It's a smaller technical surface, a simpler privacy story, and a clearer message about what you're measuring and why. Pair it with multi-stop route optimisation to remove the "I was stuck in traffic" excuse, bundle check-in proof with the right Velocity tier, and you've got a system that verifies without patronising.