Conditional Logic in Gearbelt lets you build dynamic forms that respond to user input. When a user selects a value in a Dropdown field, Conditional Logic can show or hide other fields in real time — reducing clutter and surfacing only the information that’s relevant. It applies across all Gearbelt form types: inspection, schedule, and repair forms.
Definition
Conditional Logic is a Gearbelt feature that shows or hides fields in a form template based on the option a user selects in a Dropdown field.
What it’s used for
Show follow-up questions only when specific conditions are met
Hide fields that are not relevant to the current situation
Create cleaner, more focused forms without removing fields entirely
Rule structure
One rule can match more than one Dropdown value — meaning the same group of fields is shown for multiple selections.
A single Dropdown field can have more than one rule — each rule can show a different set of fields for different values.
When to use it
Use Conditional Logic when some fields are only relevant under certain conditions — for example, when an inspection outcome, asset state, or repair type requires additional detail that wouldn’t apply in every case.
Constraints and limitations
Single logic layer only
Conditional Logic operates on a single layer. Fields shown by a rule cannot themselves trigger additional logic rules. Nested or chained logic is not supported.
Dropdown is the only trigger field type
Only Dropdown fields can trigger conditional logic. Other field types cannot be used as triggers.
Behaviour when editing a submitted record
When a user edits a previously submitted record, Conditional Logic re-applies based on the current Dropdown selections. Fields that are hidden under the current logic state will not appear as edited or deleted in the revision history — changes to hidden fields are not recorded.
Issues raised from a field that is subsequently hidden
If a field that had an issue raised against it is subsequently hidden by a conditional logic rule, the issue is detached from the form — it is not deleted. The issue remains accessible in Gearbelt’s issue management area.