Field-team & dispatch
location check-ins via a link.
Send a tech or driver a check-in link. On arrival they see a clear notice, tap "Share my location", and approve their browser's own "Allow location access" prompt. Dispatch sees who's where — a Maps pin, the accuracy radius in meters, and an arrival timestamp. Per-check-in, never always-on. Workers can always decline.
PRO feature · consent required at every check-in · for arrival confirmation & dispatch — never covert, always-on employee tracking
What this is: per-check-in
- The worker shares location only when they tap a check-in link
- One arrival = one location, with timestamp and accuracy radius
- Between check-ins, nothing is collected — no movement trail
- No app to install; opens in the worker's mobile browser
What this is not: an always-on leash
- No background daemon silently reporting position all shift
- No breadcrumb map of where someone went between jobs
- No hidden tracking the worker can't see or refuse
- No way to pull a location the worker didn't agree to share
Field-team check-ins are about confirming arrivals your workers know they're confirming — not surveilling people who don't. The consent screen makes that explicit every single time.
The part that makes it honest
How a check-in works
Two affirmative taps stand between your link and any GPS coordinate. There is no silent path to a worker's precise location — by design, and by the laws of the browser.
1. Worker sees the notice
Opening the check-in link shows a plain-language screen: this link is requesting your location for your dispatch team. No coordinates have left their phone yet.
2. They tap "Share my location"
Only if they agree. This triggers the browser's own native "Allow location access" prompt — controlled by the OS, not by us. Or they tap "Continue without sharing".
3. Dispatch sees the arrival
After they approve, the device returns precise lat/lng + accuracy radius. We reverse-geocode the site and drop a Maps pin with a timestamp. If they declined, dispatch gets approximate IP location instead.
Declining is a real option. "Continue without sharing", dismissing the prompt, or a pre-blocked browser all redirect the worker normally — dispatch simply falls back to approximate IP location (~50 km). No dark patterns, no forcing.
This is exactly what your field worker sees
Before any coordinate is captured, the worker sees this consent screen. It names your dispatch team, explains that precise location will be shared to confirm arrival, and offers a clear way to decline. The browser's own Allow prompt only fires after they tap Share. This is the screen every visitor sees — nothing is hidden, and nothing happens behind their back.
- Our consent notice fires first — before the browser prompt
- The browser's native Allow prompt is OS-controlled and unfakeable
- A report button sits on the notice for any worker to use
- Every consented check-in stores a timestamped consent record
This link is asking for your location
The person who created this link wants your precise location. Created by Northgate HVAC dispatch to confirm your arrival at the job site.
Visual mock-up of the consent screen every visitor sees before the browser's own Allow prompt. Nothing is hidden.
Pinpoint check-in links are a PRO feature. Start free and upgrade when dispatch needs meter-accurate, consent-gated arrival confirmation.
Create a check-in linkWhat dispatch gets per check-in
When a worker shares on arrival, this is the full record — precise, mapped, timestamped, and exportable to your invoicing or scheduling system.
Precise lat / lng
Device-reported coordinates, typically accurate to 5–50 m outdoors at a site.
Accuracy radius (meters)
The confidence radius the device reports — know a tight on-site fix from a loose one.
Job-site address
Reverse-geocoded city / region / country from the precise coordinates.
Arrival timestamp
When the check-in happened — reconcile against the scheduled job window.
Google Maps pin
An embedded pin you can click through to maps.google.com for directions.
Device, browser, OS
Mobile/desktop, Chrome/Safari, iOS/Android — alongside referrer and UTM tags.
{
"consent": "granted",
"source": "gps",
"checkin": "arrival",
"tech": "J. Alvarez",
"timestamp": "2026-05-31T08:47:11Z",
"lat": 34.052235,
"lng": -118.243683,
"accuracy_m": 9,
"site": "Los Angeles, CA",
"maps": "https://maps.google.com/?q=34.052235,-118.243683",
"device": "mobile",
"browser": "Safari 18",
"os": "iOS 18"
}Declined check-ins return "source": "ip" with an approximate city and no precise coordinates.
Where dispatch teams use it
Pinpoint check-in links work wherever a field worker expects to confirm they arrived — service, logistics, and crews on the move. If the worker wouldn't agree knowing what it does, it's the wrong use.
Field-service arrival confirmation
HVAC, plumbing, electrical, and appliance techs tap the link when they reach the customer's address. Dispatch gets proof-of-arrival with a pin and timestamp — no "I was there at 9" disputes.
Driver & courier check-ins
Drivers confirm they reached a stop on a multi-drop route with one tap. Dispatch sees the exact Maps pin per stop — faster than radioing in cross streets.
Construction & subcontractor crews
Subs and day crews who'd never install a company app still tap a browser link to confirm they reached the right site or gate. One link, one check-in, no onboarding.
Asset & equipment hand-off
Crews log where gear was dropped or picked up by sharing location at the moment of hand-off. Pinpoint the exact yard, dock, or bay for each asset.
Event & venue load-in
Vendors and staff confirm they reached the right gate of a large venue. Coordinate dozens of arrivals on one map without a flurry of phone calls.
Inspections & site audits
Inspectors and auditors confirm they physically visited each location by sharing position at check-in — a clean, timestamped, mapped audit trail.
Consent check-in vs always-on tracking vs "exact location" grabbers
The honest comparison search engines bury. We're the consensual, brandable option for dispatch.
| Feature | Pinpoint check-in (this) | Always-on app tracker | Grabify / IPLogger "exact" |
|---|---|---|---|
| When location is captured | Only at a check-in | Continuously, all shift | On any link open |
| Worker consent | Required, every check-in | One-time install consent | None — covert by design |
| Location accuracy | 5–50 m (GPS) | 5–50 m (GPS) | Claims exact, delivers IP (~50 km) |
| Movement trail between jobs | None collected | Full breadcrumb trail | n/a |
| App install required | No (browser link) | Yes (company app) | No |
| Honest about what it does | Yes | Depends on policy | No — false 'exact GPS' claims |
| Reportable by the worker | Yes (button on notice) | Rarely | No |
| Allowed on this platform | Yes (consensual) | n/a | Banned / disabled on report |
Always-on fleet trackers have their place — but they're a different, heavier tool. If all dispatch needs is "confirm this person arrived here, with their agreement", a per-check-in link is lighter, cheaper, and more respectful. And no "exact location" grabber gives you precise GPS covertly — that path doesn't exist.
Platform-wide, Track Link has served ~2,560 users and ~232,000 tracked clicks across 96 countries. Pinpoint check-in links are the consent-first way to bring precise location into that toolkit for field teams.
The honest part: covert worker tracking is not a feature
If you came here to pinpoint a worker's location without them knowing, read this carefully — then leave.
- It's prohibited. Using Track Link to capture anyone's location without their knowing, affirmative consent violates our Terms of Service and applicable law — including a worker's.
- It's reportable. Every Pinpoint check-in link shows the worker a notice with a Report this link button. One tap flags it to us.
- It gets the link disabled. Reported or detected covert-use links are disabled and the account is reviewed. We cooperate with lawful requests.
- It doesn't exist anyway. No legitimate tool can return precise GPS without the browser's OS-level permission prompt firing. Any service promising silent "exact location" is either lying or delivering mere IP geo.
- Consensual check-ins are welcome. Arrival confirmation, driver and courier stops, subcontractor site check-ins, asset hand-off, and inspections — where the worker expects and agrees — are exactly what these links are for.
FAQ
Straight answers about consent-based check-ins, what dispatch sees, and what's allowed.
How does a field-team check-in link confirm where a worker is?
You generate a Pinpoint Link in Track Link and send it to a technician or driver — by SMS, in a job ticket, in your scheduling tool, or in a group chat. When they open it on arrival, they first see a plain-language notice that the link is requesting their location and that it's for your dispatch team. If they tap 'Share my location', their browser fires its own native 'Allow location access' prompt. Only after they approve does the device return precise coordinates from its GPS chip. Dispatch then sees the exact latitude/longitude, an accuracy radius in meters, a reverse-geocoded job-site address, a Google Maps pin, and the arrival timestamp. No approval, no coordinates.
Is this the same as tracking my employees all day?
No — and that distinction is the whole point. This is per-check-in, not always-on. There is no background daemon, no mobile app silently reporting position, no breadcrumb trail of someone's movements between jobs. A worker only shares location at the moment they choose to tap a specific check-in link, and they see exactly what's being shared and with whom before they do. Between check-ins, Track Link knows nothing about where anyone is. If you want a covert always-on GPS leash on staff, this is deliberately the wrong tool.
Can dispatch see a worker's location without them agreeing?
No. Not on Track Link, and not through any legitimate tool. The browser physically will not hand over GPS coordinates without the worker approving an OS-controlled permission prompt — we can't suppress it, fake it, or pre-approve it. On top of that OS prompt, we show our own visible consent notice first, naming your team as the requester, and put a report button right on it. A link built to pinpoint a worker covertly is prohibited here, gets disabled on report, and simply does not work technically. Consent is the feature, not an obstacle to it.
What happens if a technician declines to share location?
Nothing breaks. If they tap 'Continue without sharing', dismiss the browser prompt, or have location blocked for that site, the link still works and still redirects to whatever destination you set (a job ticket, a confirmation page, a form). Dispatch simply gets the approximate IP-based location for that check-in (~50 km, city-level) instead of precise GPS, clearly labelled 'IP (approximate)' versus 'GPS (consented)' in the dashboard. Build your policy around that: precise sharing is requested, never forced.
What does dispatch actually see for each check-in?
For a consented check-in: precise latitude and longitude, the accuracy radius in meters, the reverse-geocoded site address (city / region / country), an embedded Google Maps pin that clicks through to maps.google.com for directions, the arrival timestamp, plus device type, browser, and OS. For a declined or IP-only check-in: the approximate city and the same metadata, flagged as approximate. Every record exports to CSV so you can attach proof-of-arrival to invoices or reconcile against scheduled job times.
Do field workers need to install an app?
No. A Pinpoint check-in link opens in whatever mobile browser the worker already has — Safari, Chrome, Samsung Internet. There is no app to install, no account for them to create, and no login. That's a big deal for subcontractors, day labor, and rotating crews who'd never install your company app: the link works once, for one check-in, and asks for nothing beyond a one-tap location share they can decline.
Is consent-based field check-in legal?
When it's consensual and for a legitimate business purpose, yes — it's the same consent model that delivery, ride-share, and roadside-assistance apps use every day. The lawful part is the consent: the worker sees what's requested, by whom, and affirmatively agrees before any coordinates are sent. What's not legal — and is banned under our Terms — is using a link to extract a worker's location through deception or to surveil someone who hasn't knowingly agreed. In the EU/UK, employee location is sensitive personal data: disclose it in your privacy notice, collect it only for the stated check-in purpose, and don't track between jobs. Use it for arrival confirmation. Never as a covert leash.
Can I send the same link to a whole crew, or one per person?
Both patterns work. A single shift link can confirm that someone from the crew reached the site, with each open recorded separately. Or generate a per-technician link so each arrival is attributed to a named worker — handy for proof-of-service on multi-stop routes. Each open is its own check-in event with its own timestamp, pin, and accuracy radius, and you can name and group links however your dispatch board is organized.
Why is this a PRO feature?
Precise GPS capture carries reverse-geocoding costs, the Maps embed, stricter abuse monitoring, and consent-record retention, so it lives on the PRO plan. Our free IP-based location link stays free forever. You can start free, try the IP-based location-tracker link for rough city-level arrival, and upgrade to PRO when dispatch needs meter-accurate, consent-gated check-ins.
Related
GPS location tracking link
The precise, consent-gated GPS capture behind check-ins.
Request location by link
Ask someone to share where they are — the consent-first way.
Exact location tracker link
What "exact location" really means — and what it can't mean.
IP location tracker link
The free, passive, ~50 km counterpart to precise GPS.
Confirm who arrived where — the consensual way.
Pinpoint check-in links are a PRO feature: meter-accurate lat/lng, accuracy radius, a Maps pin, an arrival timestamp, and a consent record on every shared check-in. Per-check-in, never always-on. The worker always sees the notice first and can always decline. Start free, upgrade when dispatch needs precision.