Skip to main content

See who edited and published a schedule

How to view a history of schedule changes, including who made the change and when it was done

Workforce stores a history of changes made to schedules, including:

  • The history of edits to a schedule

  • Who performed each action (edit, publish, delete)

  • When the action was performed

Managers, General Managers, and Admins can view these histories. Team managers can view snapshots for rosters they published.


Where to find the schedule history

Both of the tools detailed in this article can be found on your schedule by navigating to Tools found in the sidebar on the left hand side of your schedule.


Schedule Edit History

The edit history shows a list of changes made to shifts, including the action taken (create, update, delete) and the time it was performed. Changes are grouped by who made them and when - this could be a manager, another user, or an automated system action.

To filter the edit history to a single employee's shifts, use Filter By Employees and select the relevant person.


Schedule Snapshots

A schedule snapshot is a record of shifts that were sent to employees via notification — this occurs when a roster is printed, emailed, or sent by SMS.

Each snapshot records which shifts were included in that notification and when it was sent. When re-publishing a roster, only the shifts that have changed since the last publish are included by default, though this can be changed to include all shifts.

To view published snapshots:

  1. Select Published Snapshots from the date section beneath Tools for each roster in the sidebar.

  2. Find the snapshot you want to view.

  3. Select Download beneath the Published Roster column heading to open the snapshot as a PDF.


FAQ

How long is the edit history stored?

The edit history is tied to the roster week. It shows all changes made to shifts in that roster period and does not have a fixed expiry date.

How long are snapshots stored?

Snapshots are stored for as long as the roster they belong to exists. They are not automatically deleted on a set schedule.

Did this answer your question?