Skip to main content

Location & Geofencing

If your work happens in places — client sites, job sites, campuses, an office you split time with — TimeCampus can tie time to place: record where work happened, define geofences around the locations that matter, and log when you enter and leave them.

Get started

TimeCampus is generally available — create an account at app.timecampus.com.

Location capture is opt-in — always

Location tracking is off until you turn it on, and it's controlled entirely by you from Location Tracking → Privacy Settings — what's captured, how long it's kept, and when it stops. There are no screenshots, no keystroke logging, and no surveillance anywhere in TimeCampus; location is no exception. This feature exists so you can attribute your own time to places, not so anyone can watch where you are.

Who it's for​

Field and mobile professionals get the most from it: a consultant splitting the week across client sites, a technician moving between jobs, anyone whose "what was I working on?" is best answered by "where was I?".

Where it lives​

PageWhat it's for
Location TrackingYour location entries and stats
Location Tracking → Privacy SettingsOpt in or out, and control retention
GeofencingDefine geofences and view enter/exit events
Geofencing → SettingsConfigure geofence behaviour

Location entries​

A location entry records a place and a stay: coordinates, a human-readable address, when you arrived and left, and the duration — optionally linked to a project and a geofence. Over time, Location Tracking shows your stats: totals and your most-frequent locations, useful for splitting time across sites at billing time.

Location entries complement time entries — time answers what and how long; location answers where.

Geofences​

A geofence is a named circle on the map — a centre point and a radius — around a place that matters:

Geofence settingWhat it does
Name"Acme HQ", "Site B", "Downtown office"
Centre + radiusThe area the fence covers
TriggerWhether it fires on entry, on exit, or both
Linked projectThe project this place's time belongs to
Active togglePause a fence without deleting it

Setting one up​

  1. Go to Geofencing and create a geofence around the site.
  2. Set the trigger and link it to the client's project.
  3. Leave it active. When your device crosses the fence, an enter or exit event is recorded with the time and location.

The event log on Geofencing gives you a factual record of arrivals and departures per site — exactly what you need to reconstruct or verify on-site time. Tune behaviour under Geofencing → Settings.

Pausing and stopping​

Control is always one toggle away:

  • Pause one fence — flip its active toggle off; events stop for that fence
  • Stop location capture entirely — turn it off in Location Tracking → Privacy Settings; nothing is captured, and your existing data is handled according to your retention settings
Roadmap

Automatic time tracking on geofence entry — arriving on site starts the right project's timer for you, end-to-end from the mobile app — is on the roadmap, alongside the native mobile capture channel it depends on. Today, geofences record enter/exit events and link places to projects; starting the timer is still your tap. See Channels and the roadmap.

A typical field workflow​

  1. Opt in under Location Tracking → Privacy Settings.
  2. Create a geofence for each client site, linked to that client's project.
  3. Work your week. Enter/exit events accumulate per site.
  4. Record or verify visits as location entries with durations, linked to the project.
  5. At billing time, use location stats plus per-project time entries to produce site-accurate, client-ready numbers via Reports.

Privacy, in plain terms​

  • Opt-in, per user. Nobody can silently turn location capture on for you.
  • You control retention. How long location data is kept is your setting, not a default you can't see.
  • Scoped like everything else. Location data is workspace-scoped and permission-guarded like all TimeCampus data — see the privacy model and data controls.
  • Aggregate team views. Team-level insights stay aggregate by design; location tracking doesn't create an individual-surveillance backdoor.

Next steps​