Warehouse supervisors
The shift starts and the supervisor already knows who is in the building, who is late, and which posts are short — before the first pick is assigned.
Attendance facts for the whole operation: GPS-fenced clock-ins, shifts and rosters, leave balances, overtime, and a monthly record that payroll can use as-is.


Attend is the attendance app for the whole operation. It answers four plain questions: who came, when they came, where they clocked in, and why someone did not come. Employees clock in on the phone inside a GPS fence drawn around each site; the shift and the attendance group decide what on time means; leave balances, makeup punches and overtime all pass through one approval inbox; and the month closes with a summary the payroll system takes as-is. Attend keeps the employee master record that Labor reads, and it stops where payroll starts: it never calculates pay, it hands payroll clean, complete hours. A company with several sites binds each employee to the fences they work at, so a punch at any approved site counts and a punch anywhere else is flagged with a note.
The shift starts and the supervisor already knows who is in the building, who is late, and which posts are short — before the first pick is assigned.
Leave balances, approvals and the monthly record live in one place, and the month-end export carries employee number, date, attendance hours, overtime hours and leave type — ready for the payroll system.
One company, several sites: each employee is bound to the fences they actually work at, so a punch at any approved site counts and the rules stay the same everywhere.
Clock in on the phone, see your own record, request leave, fix a missed punch — no paper form, no trip to the office, no guessing whether it went through.


Every site gets a fence: a center point and a radius drawn around the building, the yard or the gate. An employee clocks in on the phone, and the phone checks the GPS position against the fence before the punch lands — inside the fence it counts, outside the fence it is marked abnormal and a note is required before the record is accepted. A punch with no coordinates at all is kept as unknown rather than guessed either way, so the record never claims a location it did not measure. The fence is the proof: the punch carries where it happened, not just when.


A company with several sites binds each fence straight to the employee who works there. The binding only widens the set of fences that count for that person — it never switches the check off. At punch time the phone still tests every bound fence by its own radius, and landing inside any one of them counts as in-fence. An employee with no personal binding behaves exactly as before: the group fence applies. And a punch outside every bound fence is handled exactly as before too: marked out-of-fence, note required, nothing relaxed. The binding itself is a small record — employee, fence, nothing else — and removing it returns the employee to the group fence at once.


Not every punch needs a zone. The zone picker on the punch screen is marked optional in all six languages, and an employee clocks in fine without picking one — the punch is never blocked for a missing zone. The zone is there for teams that sort attendance by area: pick it when it helps, skip it when it does not, and the record stays complete either way. The rule is simple on purpose: the fence decides whether the punch counts, the zone only adds context when the employee offers it. Supervisors see the zone on the record when it is given, and the monthly report reads the same way: zones present where offered, blank where skipped, and the attendance itself never in doubt.


A shift is a definition: start and end, lunch break, a grace period for late arrival, and the weekdays it runs. An attendance group ties people to a shift and carries its own late grace, so one building runs early, mid and late shifts side by side without separate rulebooks. Supervisors build the week on a drag-and-drop roster, rotate the shifts, and reuse templates for the patterns that repeat. The roster is what the punch is judged against: on time, late or absent is read off the shift the employee was actually rostered for, not off a company-wide clock.


Leave is a balance, not a favor. Each leave type carries its own balance and rules, the holiday calendar marks the days nobody works, and every request shows the balance before it is approved — nobody approves leave the employee does not have. Overtime is requested the same way, and an approved overtime request links to time off in lieu, so extra hours turn into rest instead of vanishing from the record. The balance moves only through approved requests: the number an employee sees is the number the approver sees, and the month-end report reads off the same balance.


Missed punches and leave requests land in the same inbox, so nothing waits in two places. Pending, mine and done tabs keep the queue readable, and batch approval clears a morning of routine requests in one pass — the approver sees the punch, the reason and the balance together before deciding. A makeup punch approved here writes straight back into the attendance record, so the report and the record never disagree. The inbox is the only place approvals happen: no side chats, no paper slips, no approval the system cannot show later. Approvers work the queue oldest first, and a request that waits too long is visible to the supervisor before it becomes a payroll problem.


The month closes on one summary: attendance, late, early-leave, absent, leave and overtime hours for every employee, with the exception detail behind every number. Department filters cut the same summary by team, and the CSV export carries employee number, date, attendance hours, overtime hours and leave type in the shape payroll systems expect — no retyping, no spreadsheet surgery. Attend never calculates pay, tax or contributions: it hands payroll hours that are already clean, already approved and already complete, and the export is the handoff.
Start and end, lunch break, late grace minutes, and the weekdays the shift runs.
People tied to a shift, with the group's own late grace on top.
One fence per site, with its own radius — plus personal bindings per employee.
Annual, sick and the rest, each with its own balance and rules.
The days nobody works, marked once and respected by every rule.
A missed punch is fixed through approval, and the fix lands back in the record.
Overtime is requested and approved, and approved hours convert to rest.
CSV and API handoff with employee number, date, hours and leave type.