Logic Jumps allow your team to bypass or redirect to different fields based on responses to questions within a Record Log. With Logic Jumps, you can prevent your team from answering irrelevant questions and avoid creating bespoke tasks for site-specific differences. To learn more about setting up Logic Jumps, click here.

Logic Jumps streamline tasks by requiring only relevant fields to be completed, saving time and effort. This flexibility allows tasks to adapt based on the team's responses while ensuring all necessary fields are completed. Logic Jumps are especially useful for time-poor teams working on lengthy or difficult tasks that require more structure. This functionality makes Trail feel more intuitive and encourages engagement by guiding team members through tasks logically and efficiently.
​

There are lots of examples where using Logic Jumps might be useful! Below, we'll outline a few of the most common scenarios.

Each of your sites is different, and it's important to take these differences into account when assigning tasks. But creating individualised tasks can be time consuming, and separate tasks for each site wont do you any favours when it comes to reviewing completion down the line.

Consider the current auditing system you have in place. It's possible that you have bespoke audits for each site, even if those audits only vary in small ways. For example, maybe only a handful of your sites have an outdoor area. Logic Jumps allow you to ask questions regarding this outdoor space to the sites that need it, while allowing the others to easily skip this section of the report.

If your team confirms that they do have an outdoor area, they'll be asked to continue answering questions around this space:

However, if they answer 'No,' this Record Log will skip right to the next section of the audit.

Consider Delivery checks, for instance. While some sites may receive deliveries daily, others only receive them a few times a week. Adding an initial Logic Jump to the task, asking if the team is expecting a delivery, allows those who aren't to close the task without entering additional records.

In this example, if the team select 'No' - the Logic Jump previously configured in the Task Editor skips all fields which ask the user to record details of their delivery and instead moves straight to completing the task:

If the team select 'Yes' however, the fields relevant to recording a delivery will appear:

In this case, Logic Jumps (coupled with mandatory fields) ensure that any deliveries are properly logged, without leaving the team left to choose between not completing the task or leaving it blank on those days it doesn't apply. When reviewing records, you'll feel confident that all deliveries have been recorded appropriately.

There are times when a particular answer suggests that further information or follow-up is needed. Consider a common task, the equipment check. In this example, teams are asked to sign off to say whether a specific piece of equipment has been checked. If they encounter a fault or issue with the equipment, they'll need to take further action. Logic Jumps help to guide the team through the next steps.

If the team selects 'No,' confirming that there are no equipment issues, Logic configured in the Task Editor allows teams to complete the 'Sign Off' field and the task as a whole:

If 'Yes' has been selected, teams can add additional context and information to their records:

💡 Note: This is the perfect opportunity to enlist Corrective Actions, prompting the team to initiate the appropriate follow-up!

To make things easier for the team, you may choose to have the most common responses to a prompt listed in an options field. For example, on a delivery check you you would list regular suppliers in an options field to save the team time when taking a delivery. But what if a new supplier comes along? Simply add a field for 'Other' available to your teams, backed up with a Logic Jump enabling them to add further details.

Here a Logic Jump configured on the 'Options' selection jumps to a field where the team can provide the new suppliers name:

Otherwise, the user selects a standard supplier and simply moves on the the following questions:

Remember, these are just a few examples of where Logic Jumps might come in handy. If you're wondering whether a task you've created might benefit from a Logic Jump, or are struggling to implement them yourself, just reach out to our Support Team!