Operandio Response Types to Use in Jobs

Response Types Guide

The platform offers a variety of response types to help you capture the right information for each step in a checklist or job. Choosing the right response type ensures your team records data accurately and efficiently, whether it’s a simple note, a yes/no answer, a numeric value, or a reading from a connected device.

This guide covers:

What do the icons mean? Some response types have icons next to them. Learn what each icon represents and how it affects your workflow.
What response types are available? Get definitions and examples of each response type and see how they can be used in your checklists and jobs.
Optional conditions for each question. Discover how you can use conditional logic depending on the response type to make your workflows smarter and more dynamic.

What do the icons mean?

Icons in the platform indicate which response type is selected and which features, such as scoring or conditional logic, are compatible. Use this guide to understand what each icon means and how to choose the right response type for your workflow.

Icons	Definition
	Conditional Logic Conditional logic lets Operandio change what happens next based on responses or data already entered. This helps ensure the right questions, actions, or requirements appear at the right time. Please use this guide for more: How to Use Conditional Logic in Jobs
	Bluetooth Bluetooth support allows Operandio to connect to Bluetooth-enabled devices and capture data directly from them, reducing manual entry and errors. Example Operandio connects to a Bluetooth temperature probe and records the reading automatically during a food safety check.
	Scoring Scoring allows Operandio to calculate results for audits or inspections based on predefined scoring rules, making performance easy to measure and compare. Example An audit assigns point values to each question, and Operandio calculates a total score and overall rating.

Choosing the right response type

The response types you can select are fully customizable, depending on the content in your lists. Each type is designed to capture information in the way that makes the most sense for your workflow. Whether it’s a simple yes/no check, a detailed note, or a reading from a connected device, Operandio gives you the flexibility to design checklists and jobs that work for your team.

Below is a summary of the available response types, what they do, and examples of how they can be used.

Response Type	Purpose & Example
Checkbox	Tick once the task is completed. Example: Tick when the fryer has been cleaned and turned off at close.
Photo submission	Forces a real-time photo to prove the task was completed. Example: Take a photo of the clean kitchen bench or arcade floor after cleaning.
File submission	Upload supporting documents. Example: Upload the amusement ride safety certificate or food supplier invoice.

Inputs

Response Type	Purpose & Example
Short text entry	Brief written response. Example: Menu item prepared.
Long text entry	Detailed explanation or notes. Example: Describe a customer injury near the climbing structure.
Number entry	Numerical data only. Example: Record fridge temperature or number of guests in a party room
Selection	Select from users, suppliers, assets, or custom items. Example: Select the pizza oven, arcade machine, or food supplier from a list.
Date & time entry	Numerical data only. Example: Record fridge temperature or number of guests in a party room
Scan NFC touchpoint	Confirms the user is physically at a location or asset. Example: Scan NFC tag on the freezer door or at the entrance to the trampoline zone. Please use this guide: https://help.operandio.com/article/118-how-to-use-an-nfc-tag-in-a-job
Signature	Record when something occurred. Example: Time the kitchen closed or when a ride inspection was completed.

Buttons

Response Type	Purpose & Example
Number rating (1 to 5)	Simple quality rating. Example: Rate kitchen cleanliness or party room setup quality.
Number rating (1 to 10)	More detailed rating scale. Example: Rate customer experience for a birthday party.
Number rating (1 to 20)	Detailed scoring or audits. Example: Safety audit score for an attraction.
Yes, No	Simple confirmation. Example: Was the allergen checklist completed?
Yes, No, N/A	Confirmation with non-applicable option. Example: Was the climbing wall used today?
Pass, Fail	Compliance outcome. Example: Daily ride safety inspection result.
Complaint, Not Compliant	Used when identifying issues. Example: Food safety issue or unsafe play equipment identified.
Satisfaction	Measures guest or staff satisfaction. Example: Parent satisfaction after a birthday party.

More

Response Type	Purpose & Example
Section	Groups related tasks together. Example: “Kitchen Close Checklist” or “Arcade Opening Checks”.
Instruction	Provides guidance, no response required. Example: “Wash hands before handling food” or “Ensure ride is powered off before inspection.”
Nest an existing process	Reuses an existing checklist or process. Example: Include the daily cleaning checklist inside the closing process.
Randomizer	Randomly selects checks or questions. Example: Random food safety or ride safety spot checks.

Optional conditions to use

When adding steps and creating your lists, you’ll notice optional conditions underneath each step. These allow you to add extra functionality to make your workflows smarter and more dynamic. Some conditions are available for all response types, while others apply only to certain types, such as button responses.

Conditions available for all response types

Condition	Purpose & Example
Required	Users will not be able to skip this step. Example: A food safety check step is marked as required to ensure it is always completed.
Exclude Locations	Remove this step at certain locations. Example: A task that only applies to stores with a specific kitchen layout can be excluded from other locations.

Conditions available for button response types only

Condition	Purpose & Example
Required	Users will not be able to skip this step. Example: A button step confirming a prep task must be completed before moving on.
No Score	Prevent this step from affecting the overall score. Example: A non-critical step that tracks completion but shouldn’t impact audit scoring
Custom Scoring	Assign specific points to this step for scoring purposes. Example: A quality check step that contributes 5 points to an overall audit score.
Exclude Locations	Prevent this step from affecting the overall score. Example: A non-critical step that tracks completion but shouldn’t impact audit scoring.
Add logic	Use conditional logic to determine what happens next based on the response. Example: Show a follow-up question only if a “No” answer is selected. For more information, see How to use conditional logic in jobs.

Choosing the right response type ensures your checklists and jobs capture the information you need in the most efficient and accurate way. Operandio’s flexible options - whether text, numbers, checkboxes, Bluetooth readings, or conditional logic - allow you to tailor your workflows to match your team’s needs.

Take the time to explore each response type and experiment with how they can work together. The right setup not only makes data collection easier but also helps your team stay consistent, reduce errors, and make better decisions based on the information you capture.

Remember, the platform is designed to work for you - customize, test, and refine your checklists so they fit your workflow perfectly.