We've been busy making Trail even better for you and your teams. Here's a roundup of our latest updates - from smarter Corrective Actions to new ways to verify task completion.
​

You can now see which corrective actions were raised from which tasks, directly in Task Reports - with links to open each action on the Trail for full context.
​
Learn more here.

Your exported PDF reports now include photos - so the record you share is the full picture. Images from comments, inline comments, and Record Log fields are included automatically, each shown in context alongside the relevant task content.
​

Learn more here.
​

The ability to raise an Access Maintain callout can now be built directly into your task workflow, allowing teams to place a callout without having to switch systems or disrupt their workflow.

Learn more here.

Trail has a fresh new look!
​
We've recently released updates to our colour palette to align more closely with other modules within our ecosystem. Bringing our users a more consistent visual experience when navigating between modules.
​
Though not to worry, as this was just a visual update, there have been no changes to functionality.
​

Who can use this: This can be set up by Standard Plan admins, Managers can add their locations to site settings and all users can complete location verification tasks.

You can now add a location verification check to individual tasks. Think of it like a digital "I was here" stamp - when a team member marks a task as complete, Trail records whether they were on-site, off-site, or if their location couldn't be determined.
​

This is especially useful for compliance-heavy environments where you need proof that critical tasks were carried out in the right place.
​

How to set it up:

💡 Note: If you enable location verification on a task but haven't set a location in your Site Settings, the feature won't work. Make sure the site location is configured first!
​
Learn more here.

Who can use this: Standard Plan users who can raise, complete, or review actions
​

Previously, when a Corrective Action was raised from a task, it could be tricky to remember exactly which section or question it came from. Now, Trail automatically adds source context to every raised action.

Each Corrective Action will display:

This context is visible in the following places:

This means less time spent cross-referencing tasks and more time getting things done.
​
Learn more here.
​

Who can use this: Admins & Custom Roles who can create tasks
​

If you've added custom exception messaging to a field in your task templates, you'll be pleased to know it now appears even when a Corrective Action is set to required (mandatory).
​

Previously, this messaging only showed when actions were requested — which meant your helpful guidance disappeared the moment you made the action mandatory. That's now been fixed.
​

This is particularly useful if you use exception messages to explain why an action is needed or to guide team members on what to do next.
​

No setup changes are needed - if you've already added custom exception messaging, it will now display automatically on required actions.
​

If you have any questions about these updates or need help getting set up, contact our support team.
​