Clocking In & Location

How employees clock in and out, the project/task/description and location requirements, breaks, offline capture, rounding, manual entry, and editing time entries.

What this covers

Clocking in and out is the core of time tracking: it records when work starts, when it stops, how long breaks lasted, and — when enabled — where the clock event happened. This page explains what an employee sees and supplies when they clock in, which settings administrators control, and how worked time is calculated.

Where settings live. The behaviors below are controlled by your organization's Time Tracking settings, edited by an Administrator. Defaults listed here are the values a brand-new organization starts with — your admin may have changed them.

Clocking in and out

From the Time Tracking screen (web or mobile) an employee can:

ActionWhat it does
Clock InStarts a new worked period
Clock OutEnds the current period and finalizes the entry
Start BreakBegins an unpaid break within the current period
End BreakEnds the break and adds its minutes to your cumulative break time

Your worked duration for an entry is calculated as:

worked = clock-out time − clock-in time − total break time

So a 9:00–17:00 shift with a 30-minute break records 7h 30m of worked time, not 8 hours.


What you supply when clocking in

When you clock in, the app validates your request in this order. If a required item is missing you'll see a specific error and the clock-in is rejected.

RequirementDefaultError if missingNotes
Not already clocked inalways—You can't open a second entry while one is open
Project selectionOnPROJECT_REQUIREDThe project must belong to your organization
Task selectionOnTASK_REQUIREDThe task must belong to the project you chose (otherwise INVALID_TASK, "Invalid task for this project")
DescriptionOnDESCRIPTION_REQUIREDWhat you're working on; capped at 500 characters
Location allowedOnLOCATION_REQUIREDYou must permit location access (see below)

The description and the captured address are each capped at 500 characters. If location is required, your coordinates are also range-validated (a plausible latitude/longitude).

Why require a project, task, and description? It makes every minute traceable to real work, which is what powers accurate project costing, billing, and reports. Admins who don't need this granularity can turn any of these off.

Location capture

When location is required (or simply allowed), each clock-in and clock-out stores:

  • Latitude and longitude
  • A reverse-geocoded address
  • The GPS accuracy (in metres)
  • A location-confidence level derived from that accuracy
  • With geofencing enabled, which fence applied and whether you were inside it

Confidence is grouped by how precise the GPS reading was:

ConfidenceGPS accuracy
High≤ 20 m
Medium20–100 m
Low100–500 m
Unverified> 500 m

Who sees a clock-in location

Everyone who can see the team's time can see who is clocked in and their hours. The recorded location (coordinates and address) is shown only to:

  • the person themselves, for their own entries;
  • a department head, for people in their department;
  • administrators and executives, for everyone.

Employees looking at colleagues see their status and hours without a location.

Why store accuracy and confidence? A clock-in from a 5-metre-accurate reading is far more trustworthy than one from a 600-metre reading. Recording both lets approvers and geofencing judge a location fairly instead of treating every GPS fix as equal.

Breaks

ActionRule
Start BreakRecords the break start. Errors if you're already on a break.
End BreakAdds the elapsed minutes to your cumulative break total for the entry.

A "minimum break" setting exists (for example, at least a 30-minute break after 5 hours).

Break enforcement is configurable, not yet enforced. The "enforce breaks", minimum-break-after, and minimum-break-duration settings can be set today, but the app does not currently block or auto-insert breaks based on them. Treat them as a stated policy, not an automatic guardrail.

Offline capture (mobile)

The mobile app can record a clock event while offline and submit it when connectivity returns. The submitted timestamp is accepted within these tolerances:

DirectionAllowed drift
Futureup to ~15 minutes
Pastup to 24 hours

Anything outside that window is rejected with TIMESTAMP_OUT_OF_RANGE — for older corrections you must use a manual time entry instead (subject to the manual-entry permission below).


Rounding (optional)

Rounding is off by default. When an admin enables it, clock-in and clock-out times are rounded to an interval before the entry is finalized.

OptionValues
Interval1–60 minutes (default 15)
DirectionRound up, round down, or round to nearest

The worked duration is calculated from the rounded times, so the hours shown on screen, in reports, and on invoices all agree.


Manual time entry

A manual entry lets someone record worked time without a live clock-in (for example, to log a forgotten shift).

WhoAllowed?
Administrator / ExecutiveAlways
Department Head / EmployeeOnly if "allow manual time entry" is on (default off)

Manual entries also respect pay-period lockdown — an entry whose date falls in a locked window can't be created by employees.

Whose timezone the times are in

The start and end times you type are read in the employee's own timezone (the timezone on their profile, or the organization's timezone when they have not set one). When that differs from the organization's timezone, the form shows a note such as "Times are in America/Toronto" under the time fields, so a manager entering 09:00 for someone in another zone knows whose 09:00 it is. When several people with different timezones are selected, it reads "Times are in each person's own timezone".

The mobile app works the same way: a manual entry uses your own timezone (or your organization's), so hours entered on a phone set to another zone land on the right day and time.


Editing time entries

WhoAllowed?
Administrator / ExecutiveAlways
Department Head / EmployeeOnly if "allow editing clock in/out" is on (default off)

Editing is also blocked when the entry falls inside a locked pay period — see Overtime & Pay-Period Lockdown.

When you edit an entry:

  • Times stay in the employee's own timezone, as for a manual entry, and saving without changing the start or end time leaves them exactly as they were.
  • The employee cannot be changed. The form shows whose entry it is instead of a picker. An entry stays with the person who logged it; to log time for someone else, add a new entry.

Projects and tasks on an entry

A time entry's task must belong to its project, whether the entry comes from clocking in, a manual entry, an edit or a bulk update. A task from another project is refused with "Invalid task for this project", and a task without a project is refused. Changing an entry's project without choosing a task clears the old task, so the hours never stay on a task from the previous project.

Finalized timesheets

Once a timesheet period is finalized or signed, its entries are part of the payroll record:

  • Nobody, whatever their role, can change an entry's times, break, project, task, rate or billing, or add or move an entry into that period. The description, notes and tags can still be edited.
  • Its entries cannot be deleted, one at a time or in bulk.
  • Its entries cannot be approved or rejected, and any still pending leave the time approvals queue and every pending count.

See Timesheets.


Troubleshooting

SymptomCauseFix
PROJECT_REQUIRED / TASK_REQUIRED / DESCRIPTION_REQUIREDA required field was emptySelect a project/task and add a description before clocking in
LOCATION_REQUIREDLocation is required but not grantedEnable location services / grant the app permission, then retry
"Already clocked in"An open entry existsClock out (or end the open entry) before clocking in again
TIMESTAMP_OUT_OF_RANGEOffline timestamp is too far in the past/futureUse a manual time entry for older corrections
Can't add a manual entry"Allow manual time entry" is off for your roleAsk an administrator to enable it or to add the entry for you
Can't edit your entry"Allow editing clock in/out" is off, or the entry is in a locked pay periodAsk an administrator
Description rejectedOver 500 charactersShorten the description (and address, if applicable)
"Invalid task for this project"The task belongs to a different projectChoose a task from the entry's project, or change the project first
No location shown for a colleagueLocations are for department heads (their people), administrators and executivesExpected for employees