Last updated:

What are logic fields?

Learn more about logic fields and how to use them.

What are logic fields?

When building your template, you can add questions with different response types so users can conduct inspections effectively and efficiently. Take your template to the next level by adding logic fields to trigger follow-up questions, require actions, require evidence, and send notifications depending on users' answers.

Available logic fields

Ask questions

You can add as many questions as you want in your template, but what if there are times you want to ask follow-up questions? With SafetyCulture, you can add logic fields to ask follow-up questions based on a user's selected response.

You can set up linked responses within a logic flow to automatically carry the same answer across multiple follow-up questions.

Notify team members

Notifications are a great way to inform your team members of essential details. With SafetyCulture, you can automatically notify specific users, groups, or site member when a particular question response is selected. You can choose to send notifications immediately or on inspection completion. If you select the inspection completion option, marking an inspection as incomplete and then complete again will send the notification again.

Please note that inspection response notifications are subject to the recipients' notification settings.

Only up to 500 users can be notified at a time. If an organization or group exceeds this limit, 500 users are randomly selected to receive the notification.

Require note

There are times when you need additional context behind a response. With SafetyCulture, you can require users to leave a note when they select a particular answer, helping capture important details, explanations, or observations that provide better clarity on the response.

Require media

Photos and videos help validate responses and provide clearer evidence during inspections. You can require users to attach media when a specific answer is selected, ensuring accurate documentation and giving you a clearer view of what’s happening on site.

Require action

Don't just find things; fix them! The Actions feature allows you to identify, track, and complete tasks created from inspections. By marking specific questions as requiring actions, users will need to create or link open actions as follow-up tasks to mark an inspection as complete.

Examples

Ask different sets of questions based on the response to a question

When conducting a field safety assessment, you may want to ask follow-up questions based on the response. For example, if you answer "Yes" to the question "Was a hazard observed?" the response can trigger additional hazard-related questions, ensuring a more focused and thorough inspection.

Notify a team member when a response is selected

You can set up automatic notifications to alert team members when their input is needed based on a specific response during an inspection. For example, if not all corrective actions in an inspection have been added as "Actions", a notification can be automatically sent to Area managers, informing them of the issue. This ensures key team members are alerted in real-time or after inspection completion for quick resolution of critical issues.

A notification that a user receives when the "Notify" logic field gets triggered while conducting the inspection.

Require notes based on a response

Capture essential context by requiring a note when certain responses are selected. For example, if the question "Is the room clean and ready for guests?" is answered "No," the inspector must provide a note explaining which parts of the room are not ready and which areas still need cleaning. This helps document reasoning and ensures there is a clear justification before completing the inspection.

Require notes when a specific response is selected in an inspection.

Require media evidence based on a response

Improve accuracy by requiring photos or videos when a specific response indicates an issue or needs confirmation. For example, if the question "Is the room clean and ready for guests?" is answered "Yes," the inspector must attach a photo showing the room's condition at the time of inspection. This ensures the reasoning behind the response is properly documented and provides clear justification before the inspection can be completed.

Require media when a specific response is selected in an inspection.

Require action based on a response

Use actions to ensure problems are followed up on and resolved. For example, during an inspection, if the answer to "Is the coffee machine working in order?" is "No," the inspector can be required to create an action to have the coffee machine fixed. This ensures failed checks lead to actionable tasks, helping teams track, assign, and complete necessary follow-up work before closing out the inspection.

Require action appearing while conducting the inspection via the web app.

Logic conditions

  • If answer is <response>

  • If answer is not <response>

  • If answer is selected <response>

  • If answer is not selected <response>

  • If answer is one of <response>

  • If answer is is not one of<response>

  • If answer is <text>

  • If answer is not <text>

  • If answer is <text>

  • If answer is not <text>

  • If answer is <text>

  • If answer is not <text>

  • If answer is less than <number>

  • If answer is less than or equal to <number>

  • If answer is equal to <number>

  • If answer is not equal to <number>

  • If answer is greater than or equal to <number>

  • If answer is greater than <number>

  • If answer is between <number> and <number>

  • If answer is not between <number> and <number>

  • If temperature fails

  • If temperature passes

  • If answer is less than <number>

  • If answer is less than or equal to <number>

  • If answer is equal to <number>

  • If answer is not equal to <number>

  • If answer is greater than or equal to <number>

  • If answer is greater than <number>

  • If answer is between <number> and <number>

  • If answer is not between <number> and <number>

  • If checkbox is checked

  • If checkbox is not checked

  • If slider value less than <value>

  • If slider value less than or equal to <value>

  • If slider value equal to <value>

  • If slider value not equal to <value>

  • If slider value greater than or equal to <value>

  • If slider value greater than <value>

  • If slider value is between <value> and <value>

  • If slider value is not between <value> and <value>

  • If signature name is <text>

  • If signature name is not <text>

  • If signature exists

  • If signature does not exist

Need more help?
In this article