For an office team, attendance is a gate and a register. For field teams — salespeople, delivery staff, technicians, merchandisers — there is no gate. Attendance becomes a WhatsApp "good morning" with a selfie, a call to the manager, or nothing at all. Payroll then depends on what someone remembers at month end.
What field attendance should capture
- Shift start and end, with time and place.
- Breaks if they matter to your policy.
- The work in between — visits, orders, deliveries — which is the real evidence of a working day.
- Leave and absence, requested and approved.
Using location fairly
Location helps — it shows the shift started at the first outlet, not at home. It also needs care:
- Record location during working time only.
- Explain what is recorded, when and why.
- Ask for consent where required.
- Use it to support people — confirm work, plan routes, help when something goes wrong — not to punish every detour.
- Set the rules centrally, not per phone.
Leave without paperwork
| Step | Who |
|---|---|
| Request leave in the app | Employee |
| Approve or decline | Manager |
| Balance updated | Automatic |
| Attendance reflects it | Automatic |
How Zaqnet handles field attendance
- Shifts are started and ended in GroundLink, and managers can see who is on duty.
- Location tracking follows the tracking rules your admin sets, with consent asked in the app — see tracking vehicles with phones.
- Leave requests and balances, reviewed by managers.
- Expense claims for field costs — see field staff expenses.
- Team members and attendance are managed in ControlRoom.
The best proof of a field day's work is the work itself, recorded where it happened.