Audit trail
The Audit Trail is the change log for your organisation or agency: one row per event, with the old and new value of every field that moved, who did it and when. It covers requests, shifts and pay, agency officers and their documents, user accounts, and every time sensitive documents or payroll files are opened or exported. You can filter it, export it as CSV and check nothing has been altered.
What do I need before I start?
A management account. The trail is open to Admin, Manager, Control, Agency Admin and Agency Coordinator (and ShiftTracker's own Super Admins). Employees, officers and clients get a flat refusal. There is no separate "view audit" permission to grant — it is the role that decides. An organisation's staff see their organisation's events; an agency's staff see their agency's.
Something to look at. The trail records what the platform's own routes write to it, and nothing back-fills it. An organisation whose data was imported or seeded directly into the database has an empty Audit Trail and there is no way to reconstruct one.
An understanding of what is in scope. This matters more than it sounds, so it has its own section below.
How do I find a change?
- Open More → Audit Trail in the top navigation, or go to
/audit. - Set the filters you need. Five are available: Entity, Source, Action, Actor name, and a date range. The filters except Actor name are kept in the page's address, so a filtered view survives a refresh and can be shared; a name stays out of the address.
- Click Apply. Reset clears everything and reloads.
- Read the list. Each row shows the entity as a badge, a one-line summary, the actor with their role, and the time in your organisation's timezone.
- Click a row to expand it. You get a Property / Old / New grid of every field that changed, the reason if one was recorded, and the raw entity, id and action at the bottom.
- The list loads 50 at a time, newest first. Load more fetches the next 50.

The filters behave differently from each other, which is easy to trip over:
| Filter | Behaviour |
|---|---|
| Entity | A fixed menu: All entities, Shift, Request, Arbitration, Officer, Officer screening, Officer document, Employee, Employee document, Roster shift, User account, Client, Site, Import, Agency details, External site, Site managers, Check-call alarm, Check-call pattern, Check-call settings, Organisation settings, Client portal settings, Client report download, Client monthly scorecard, Form client portal setting, Report export, Payroll export, Check-call report, Right to Work report, Schedule e-mail, Roster publish, Workforce template, Form report correction, Blog image |
| Source | All sources, User, System |
| Action | Free text, matched exactly — status finds nothing if the stored action is arbitration_manual |
| Actor name | Free text, partial match, case-insensitive |
| Date range | From and to dates, read in your organisation's timezone, with the end date including the whole of that day |
Arbitration is not a stored entity. Pay events are anchored to the shift they belong to, so they are stored as shifts and the filter picks them out by their action — anything beginning arbitration, plus mark_paid and mark_invoiced. The list badges those rows as ARBITRATION so the two agree.
What is actually recorded?
Only what the platform's own screens and routes write. Today that is:
| Area | Recorded |
|---|---|
| Requests | Created, edited, shared and unshared with agencies; proposals made, changed, withdrawn or deleted; officers assigned and unassigned |
| Roster shifts | Created, edited and moved between statuses; the slot-linking when a request claims or creates a shift; agency roster shifts |
| Pay | Every arbitration action, including the Mark Paid and Mark Invoiced locks |
| Agency officers | Activation and deactivation, PIN reissue, changes to their compliance flags and emergency or medical details (field names only, never the values), and their BS 7858 screening overrides |
| Officer documents | An agency uploading, verifying or archiving a document; anyone — agency or organisation — opening the list or a file |
| Your own employees' documents | Uploading, verifying, archiving or editing one; somebody opening one (View) |
| Accounts | A login created, its role changed, switched on or off; employee login-email and password-link events |
| Sites and settings | Sites and who manages them; check-call patterns and settings; organisation details and roster-publish settings; client-portal settings; shift-pattern edits |
| Clients | Client records created; client report downloads and monthly scorecards |
| Check calls | A control-room acknowledgement of an alarm, a manual escalation, and a book-on or book-off logged by hand |
| Other | Roster publishes, bulk imports, workforce template imports, schedule e-mails sent, and corrections to a form report |
| Agency settings | The agency's profile, and its own external sites |
| Files leaving the system | Payroll Export downloads, check-call compliance and agency report exports, and the Right to Work report — viewing it and exporting it |
Opening a document and exporting a payroll or Right to Work file are written before the data is handed over, and the request is refused if the record cannot be written — an unrecorded look at someone's right-to-work evidence is treated as worse than a failed one.
What is not in the Audit Trail:
- Logins, password changes and session activity.
- Other edits to an employee's record.
- Leave decisions.
Several of those do write a record — to an older employee history table that has no screen in the product. If you need evidence of a leave approval, the Audit Trail will not give it to you.
Each row's badge uses the same name as the Entity menu.
Field values are diffed automatically, and a fixed list of field names is excluded from that diff whatever happens: anything matching password, token, secret, hash, salt, National Insurance number, sort code, account number, bank, PIN or API key. Those never enter the trail, so an export is safe to hand over.
How do I export it for an evidence pack?
Click Export CSV in the header. The export applies the filters currently in the boxes — not the ones you last clicked Apply on, and not the page you have scrolled to — so set the filters, then export.
| Property | Value |
|---|---|
| Columns | ID, Timestamp, Entity, Entity ID, Action, Source, Actor, Actor Role, Summary, Changes, Reason, IP Address (organisation exports only) |
| Row cap | 10,000, newest first |
| Timestamps | Formatted in the organisation's timezone |
| Filename | audit-trail-YYYY-MM-DD.csv |
| Encoding | UTF-8 with a byte-order mark, so Excel opens it correctly |
Two things differ from the screen. An organisation's export carries the IP address of the actor, which the list does not show; an agency's export leaves the column out, because some of its rows were written by another party — an organisation's staff opening the agency's officer documents. And it is capped: at the cap you get the 10,000 most recent matching rows with no warning, so narrow the date range rather than exporting the lot.
How do I prove nothing has been tampered with?
Click Verify integrity. The answer appears beside the button as either Chain intact · N digests or Tampering detected · digest #N.
Underneath, the trail is protected twice over. The database refuses to update or delete a row in either the event table or the digest table — the attempt raises an error rather than succeeding quietly. On top of that, a scheduled job periodically seals the events written so far into a digest: a hash of those rows, chained to the previous digest. Altering, inserting or removing any past event changes its window's hash and breaks every digest after it, which is what Verify integrity re-derives and checks.
Two results are easy to misread:
- Chain intact · 0 digests means nothing has been sealed yet, not that nothing has happened. Freshly written events are not eligible until they are more than an hour old, and the sealing job has to have run at least once.
- A broken chain is reported as a successful check that found a problem, not as an error. The message names the first digest that failed and says whether the break was an altered row or a missing earlier digest.
The chain is kept per organisation. An agency's events are sealed under the organisation that owns each request, so an agency login that is not linked to an organisation gets Verification is per-organization; no organization on session instead of a result.
Where else does the same trail appear?
Two screens show the trail for a single record rather than the whole organisation: the request detail page, and the shift details dialog on the roster. Both read the same events and render them the same way — collapsed to a summary, expandable to the old-and-new grid. If you know which record you care about, that is usually faster than filtering the explorer.
If it goes wrong
| What you see | What it means |
|---|---|
| You don't have permission to view the audit trail. | Your role is not one of the management roles above. |
| Verification is per-organization; no organization on session | You are signed in to an agency that is not linked to an organisation. The trail itself still works; only the integrity check needs an organisation. |
| No audit events match these filters. on an unfiltered view | Nothing has been recorded for your organisation. Data written straight into the database never produces audit rows. |
| An Action filter returns nothing | It is an exact match. Expand a row you care about and copy the action from the line at the bottom. |
| An agency user sees fewer rows than you do | Correct. Agency roles are scoped to their own agency, organisation roles to their own organisation. |
| Verify integrity says 0 digests | The sealing job has not run yet, or has nothing older than an hour to seal. |
| A change you know happened is missing | Check the scope list above — settings, logins and leave decisions are not in this trail. |
Related
Last updated 2026-11-17