Support Audit Log

Overview

The Audit Trail in Astalty allows you to view recent activity and track changes made across the platform, including updates to Participant profiles and scheduled supports.

For each change, the Audit Trail records:

• Time and Date the change was made
• User who made the change
• Details of what was changed
• Reason for the change (when there are changes made to supports)

Viewing an Audit Trail on a Shift

• Go to the Schedule.
• Click on the support you wish to review.
• In the top left-hand side menu, open Actions.
• Click the three dots and select Audit Trail.

• The Audit Trail will display all changes made to that support, along with timestamps, the user who made each change, and any associated reasons.
• When looking at changes to start and end times of supports, it's important to note that the time of the change may differ from the expected time if the support is being performed in a different timezone than what your timezone is.
• Automated SMS Reminders sent for the support are recorded too. They appear on the Reminders tab of the Audit Trail rather than alongside the other changes — see Reminders sent for a support.

Recording a Reason for a Change on a Shift

If you need to record a reason for a change:

• Click into the shift you want to update.
• Select Update Details.

• Make the necessary changes to the relevant fields.
• Scroll to the bottom of the form and enter the Reason for Change in the provided field.

• Click Update.

The shift will be updated with the new details, and the reason you entered will be saved. This reason will then appear in the Audit Trail for that shift, along with the date, time, and user who made the change.

Reason for Unassigning Staff

Any changes made to the attached Support Workers in a published shift will require a Reason for Unassign.

Example of the Audit detail of a Support Worker being unassigned from their shift, as viewed in the Audit Trail of a support.

Travel Removed From a Support

Every time travel is removed from a support or group support, the Audit Trail records it. The entry names the travel type and the driver, lists what the Support Worker had recorded against it, and says who actioned the removal:

Travel From Support for Amy Worker was removed. It had recorded odometer readings 500 to 530 and odometer photos attached. Removal actioned by Jane Admin

The "It had..." sentence only appears when there was something to report, and covers odometer readings, whether odometer photos were attached, and the approved distance. Travel removed with none of these recorded produces the shorter entry: Travel To Support for Amy Worker was removed. Removal actioned by Jane Admin.

Because the entry is written for every removal, the Audit Trail is also where to look for the removals that don't ask you to confirm first — including travel removed across a series of shifts, and travel dropped when a Participant is de-selected from a group travel row. See Confirming Removal of Recorded Travel.

Location Tracking

You can view location tracking details recorded during a shift in the Audit Trail. To access this information, open the Audit Trail and select the Location Events tab.

Reminders sent for a support

If your organisation uses SMS Reminders, the Audit Trail has a Reminders tab listing every reminder sent for that support. For each one you'll see the reminder window (for example 24 hours before), when it was sent, the Participant it went to, the delivery status (for example Sent, Delivered, or Failed), and the message body. If none have gone out yet, it shows "No reminders have been sent yet."