Attend

Who came, when, and where they clocked in.

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.

Clay-style illustration of attendance check-in: a worker tapping a badge on a teal time clock by the warehouse entrance, a shift board and shelves behindClay-style illustration of attendance check-in: a worker tapping a badge on a teal time clock by the warehouse entrance, a shift board and shelves behind

About this product

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.

What it is for

Who it is for:For warehouse supervisors, HR and admins who need to know exactly who showed up — and for every employee who clocks in.

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.

HR and payroll admins

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.

Multi-site operators

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.

Every employee who clocks in

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.

Core workflow

  1. Define shifts and groups
  2. Draw the geofences
  3. Employees clock in
  4. Approve exceptions
  5. Close the month and export

Key features

Clay illustration: a warehouse gate with a round GPS fence ring around it and a worker tapping a phone to clock inClay illustration: a warehouse gate with a round GPS fence ring around it and a worker tapping a phone to clock in

GPS-fenced clock-ins

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.

Clay illustration: one worker card linked by lines to three small site fences — warehouse, yard and officeClay illustration: one worker card linked by lines to three small site fences — warehouse, yard and office

One employee, several fences

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.

Clay illustration: a phone punch screen with a zone picker marked optional beside a green checkmarkClay illustration: a phone punch screen with a zone picker marked optional beside a green checkmark

Zone choice is optional

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.

Clay illustration: a weekly roster board with shift cards in teal and orange being dragged into placeClay illustration: a weekly roster board with shift cards in teal and orange being dragged into place

Shifts, groups and rosters

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.

Clay illustration: a leave balance card with a small calendar and an overtime slip turning into a rest day tokenClay illustration: a leave balance card with a small calendar and an overtime slip turning into a rest day token

Leave balances and overtime

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.

Clay illustration: an approvals inbox with stamped request cards and a batch approve buttonClay illustration: an approvals inbox with stamped request cards and a batch approve button

One inbox for every exception

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.

Clay illustration: a monthly attendance report with a small bar chart and a CSV export buttonClay illustration: a monthly attendance report with a small bar chart and a CSV export button

Monthly close, payroll-ready

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.

The everyday essentials

Shift definitions

Start and end, lunch break, late grace minutes, and the weekdays the shift runs.

Attendance groups

People tied to a shift, with the group's own late grace on top.

Geofences

One fence per site, with its own radius — plus personal bindings per employee.

Leave types and balances

Annual, sick and the rest, each with its own balance and rules.

Holiday calendar

The days nobody works, marked once and respected by every rule.

Makeup punches

A missed punch is fixed through approval, and the fix lands back in the record.

Overtime and time off in lieu

Overtime is requested and approved, and approved hours convert to rest.

Payroll-ready export

CSV and API handoff with employee number, date, hours and leave type.

Ecosystem support

Labor reads the same people

Attend records the facts and Labor measures the work. The employee master record is maintained in Attend and read by Labor, so the people on the efficiency board are the same people on the attendance record — one roster, two lenses. Attendance hours feed Labor as the reference for what the team was present for, while speed and output stay Labor's own measures. The boundary is deliberate: facts here, performance there, and neither app rewrites the other's numbers.

People holds the record

Every employee Attend tracks is a person in People, with the same job title, the same department and the same record. Attend maintains the attendance side of that record — shifts, groups, fences, balances — and People carries the rest: skills, badges and the employment record. Change a job title in one place and the attendance rules that key off it follow, because both apps read the same employee, not two copies of one.

AI Assistant — Rollie

Ask about attendance in plain words. Rollie, Docklify's AI assistant, answers over live Attend data — who is late today, who is on leave this week, which team is short — through read-only tools, and looking at the data never becomes write access. A supervisor asks for the morning picture before the shift starts; HR asks for the month's exceptions without opening a report. The answers come from the same records the dashboard shows, so the assistant and the screen never disagree.

How it connects:Attend records attendance facts; Labor measures efficiency on the same people; People holds the employee record Attend maintains. Payroll systems receive the monthly export — Attend never calculates pay. A punch, a leave request and a shift all live in Attend; what the team did with the hours is Labor's question.

Ready to put it to work?

Explore the other apps