Attendance proof
Under Dashboard → Evidence → Service level → Attendance you see every single visit of your team per property and period: start, end, duration against the minimum duration, gap to the previous visit, time window and flags. The same view is available to your customer in the customer portal once you enable the module there — pseudonymised or, if you choose, with names.
What is this view for?
The customer's question is: Was someone there, for how long, and how often? The service level answers it as a rate. This view provides the evidence behind it: one visit after another, measured against the property's targets, with a note on whether a visit was recorded later, edited, deleted or approved. As the operator you check here what the customer will see before you enable the module in the customer access.
Features at a glance
| Column | Content |
|---|---|
| Date, start – end | When the visit started and ended. A visit still running carries the flag Running. |
| Duration | Working time without breaks, judged against the minimum duration per visit (series → property → tenant). |
| Gap to previous | Time since the end of the previous visit at the same property; overlapping visits are flagged Parallel. |
| Time window | Did the visit fall into a planned shift of this property? Without planned shifts the column reads No time window. |
| Employee | Always the real name for the operator. |
| Flags | Recorded later, via API, automatic, edited, deleted, approved, running. |
Above the list you find the period's figures: visits in total, below minimum duration, gap violated, outside time window, corrected, and the average duration. The switch Findings only hides unremarkable visits.
The row action Changes to this visit opens the change log: who changed which time field when, and why.
Good to know
- Period at most 92 days, default is the last 14 days.
- Targets (minimum duration, minimum gap) are maintained on the property or in the company defaults; without a target the column reads No target.
- What the customer sees is governed by the module switch Attendance proof and the names switch in the customer access.
Permissions
Visible with View time tracking of others (or edit time tracking), the same boundary as the target/actual comparison. Customer accounts use their own module in the customer portal instead.