Someone disputes their hours, or a shift's times look wrong and you want to know who moved them. Every shift keeps its own history, from the moment it was created.
Open a shift's history
- Go to Team → Shifts → All Shifts.
- Find the shift and click the list icon at the end of its row. Its tooltip reads Check logs.
- A window opens, titled with the agent's name and the shift type.
This lives only on All Shifts, so it needs the All Shifts right. An agent looking at My Shifts cannot open their own shift's history.
What the window shows
At the top, four cards for Shift Type, Start Time, End Time and Comments. Each one shows the Current value, and above it the Original value if it has ever been changed. If nothing was touched, the card says No changes made — which is the quickest possible answer to "was this shift edited?".
Under them, the Activity card shows which devices the agent was active on during the shift, and when. It fills in only if your workspace records activity — see Record which device agents are active on during shifts.
Below that is the Shift Logs table, one row per event:
| Column | What it holds |
|---|---|
| Event | What happened — see the list below |
| Old Value | The value before the change |
| New Value | The value after it |
| User | Who made the change |
| Device | The kind of device the change came from, such as Windows · Chrome or Yaplet app · Android |
| IP Address | The address the change came from |
| Continent, Country, City | Where that address is, as best we can tell |
| Created At | When it happened |
You can filter the Event, Old Value, New Value, IP Address, Continent, Country and City columns, so on a long-running shift you can pull out just the pay-rate changes by filtering Event for update_pay_rate. The activity notes themselves are not listed as rows; the Activity card sums them up.
The events you will see
- start — the shift was created by someone clocking in.
- end — an end time was set for the first time, by clocking out or by clicking End shift.
- update_start — the start time was changed afterwards.
- update_end — the end time was changed afterwards.
- update_shift_type — the shift's type was changed afterwards. The old and new values hold the names of the two types.
- update_pay_rate — the pay rate for this one shift was changed on All Shifts.
- update_comments — a comment was added or edited.
- finalize — the shift was locked, or unlocked again. Both directions are recorded under this name, so read the old and new values to tell which way it went.
- manually_created — an administrator added the shift by hand with Add shift rather than an agent clocking in.
Why it matters
When someone believes their pay is wrong, this is the record that settles it: every change to the shift, who made it, and when. Note the one gap — deleting a shift removes its history too, so the log answers "what happened to this shift", not "did a shift ever exist here".
What's next
The organization-wide equivalent for everything outside shifts is the audit log.