Create & refine
Define checks and data collection fields
Make each checkpoint ask for the information your process actually needs.
What you’ll achieve
Each relevant step has clear, purposeful field definitions.
Before you begin
- An editable step.
On this page
Choose what needs to be recorded
Fields describe the information to collect alongside a step, such as a checked condition, a measured value, or a serial number. Define them for a concrete purpose: verification, traceability, or a later decision.
The Steps editor is an authoring surface. Defining a field here is not the same as recording an operator’s completed execution. Check the delivery or execution system you use for how results are collected.
Choose a field type
| Type | Typical use |
|---|---|
| Checkbox | Confirm a named condition was checked. |
| Text | Record a kit ID, observation, or serial number. |
| Number | Collect a measurement; state the unit in the label. |
| Radio / Dropdown | Choose from explicit, meaningful options. |
| File Upload | Request supporting evidence such as a photo. |
| GPS Location | Define a location-recording requirement where appropriate. |
| Date | Record a relevant date. |
Add and review field definitions
- 1
Expand the step and open its Fields section.
- 2
Add a field and choose its type. Give it a clear label that states the expected answer.
- 3
Configure the options and other controls exposed for that type. For example, a selection field needs useful choices.
- 4
Review AI-generated fields with the same care as manually created ones, then check the saved instruction and the intended export.
Keep the collection useful
- Prefer “Kit identifier” to “Value.” For measurements, include the unit.
- Avoid collecting the same result in multiple steps unless it serves a defined purpose.
- Distinguish a required source-backed check from an optional AI suggestion.
- Verify format support in the destination; an editable Word document is not an interactive execution form.