Tasks, check-in/out, and cycle attribution

A task is a piece of assigned field work — visit this outlet, complete this form — dispatched to a specific worker (or left open for anyone).

The task lifecycle

1. Dispatched — created and (optionally) assigned to a worker.
2. Checked in — the worker has arrived and started the work.
3. Checked out — the worker has finished; this is what marks a task completed.

Open a task from Tasks to see its full history: who was assigned, when they checked in/out, and — if your account uses location verification — whether their location matched the expected site.

"Requires geofence review"

If a task shows this flag, the worker's device location at check-out didn't match the expected site closely enough (or the location reading looked spoofed). This never blocks or discards the work — it just flags it for a manager to glance at.

Cycle attribution and re-attribution

If your account runs on recurring cycles (e.g. a weekly or monthly reporting period), each completed task is automatically attributed to whichever cycle was open when the worker checked out. This determines which reporting period the task counts toward.

Occasionally a task needs to be re-attributed — for example, a visit happened just after a cycle closed but should still count for the prior period by agreement with the client. An Owner or Admin can do this from the task's detail page: pick the correct cycle, give a reason (required, and kept as a permanent record), and save. Re-attribution never changes the task's actual check-in/check-out times — only which reporting cycle it's counted against.