What is a Form?
Forms are the foundation of Tickets, allowing you to define the fields and attributes displayed on a ticket. This flexibility ensures that Tickets can be tailored to meet your specific needs and existing processes.
A form is a customizable template that determines what information is captured on a ticket. Because forms are fully flexible, they can be adapted to a wide range of use cases, including:
Defect Tracking: Manage and track defects and their resolution.
Quality Inspections: Perform comprehensive quality inspections during commissioning.
Photo Documentation: Keep a visual record of progress and issues.
Handovers: Facilitate smooth handovers with well-organized information.
Recurring Tasks Management: Handle regular tasks, such as maintenance, efficiently.
ℹ️ Also read Introduction to Tickets to learn more about what a ticket is and how you can fulfill different use cases with them.
Company-Level vs. Site-Level Forms
Forms can be created at two levels, depending on how broadly you need them to be available.
Level | Scope | Best For |
Company-Level | Available across all sites in your company | Standardized processes, company-wide templates |
Site-Level | Available only on a specific site | Site-specific workflows, unique requirements |
Company-level forms are ideal when you want to maintain consistency across multiple sites — create the form once and assign it to any site that needs it.
Site-level forms are best when a site has unique requirements that don't apply elsewhere.
Creating a Form
Creating a Site-Level Form
Navigate to your site.
Go to the Forms tab in the site navigation.
Click + Create Form and Start from Scratch.
The form builder will open.
Creating a Company-Level Form
Go to Company Settings.
Navigate to the Forms section.
Click + Create Form.
The form builder will open.
To use a company-level form for a site,
Navigate to your site.
Go to the Forms tab in the site navigation.
Click + Create Form and Assign company-level form.
Building Your Form
Once inside the form builder:
Give your form a clear, descriptive name. This will be used to identify it, e.g. when Creating Tickets later.
Drag and drop fields from the left sidebar onto the canvas.
Configure the properties as needed.
Click Save when you're done.
Available Field Types
Text: A free-form text input for capturing written information.
Number: A numeric input that accepts decimal values. Ensures only numbers are entered, keeping data clean for reporting or calculations.
Select: A dropdown menu where users choose exactly one option from a predefined list. Each option can be assigned a color, which can be used to color-code ticket pins on the map.
Multi-Select: Similar to Select, but allows users to choose more than one option at a time. Each option can also be assigned a color but cannot be used to show colors on the map.
Date: A date picker for selecting a specific date. Optionally, you can enable time selection to capture both date and time.
Checkbox: A simple toggle representing a yes/no or true/false value.
Pass/Fail: A specialized field for quality control with two clear states: Pass or Fail. Provides a visual, easy-to-tap interface optimized for inspection workflows. This option also allows you to create follow-up tickets and link attachments if a property fails.
File Upload: Allows users to attach one or more files — including images and documents — directly to a ticket. Particularly useful for photo documentation in the field.
Signature: A digital signature capture field where users can draw their signature using touch or mouse input. Creates a verifiable record of who signed and when.
URL: A dedicated input for web links. Validates that the entered value is a properly formatted URL.
User: A dropdown listing all team members in your company, allowing you to select one or more users.
Info: A read-only text block that displays static information. Users cannot edit this field — it shows exactly the text you define when building the form. This field will not be included in PDF reports unless the 'Include All Properties' option is checked.
Subcomponent Form: Links a ticket to another form, creating a parent-child relationship. This allows nested tickets to be created and connected to the main ticket.
Section: A structural element that lets you group related fields together under a named heading. Sections help organize longer forms into logical parts, making them easier to navigate and fill out. Sections are also reflected as distinct parts in exported PDF reports, giving your documentation a clear, professional structure.
Tips and Tricks
Reuse Forms Across Sites
If you've built a site-level form that would be useful elsewhere, you can copy it to another site — look for the option to import from an existing form when creating a new one. For forms needed across many sites, consider creating them at the company level from the start.
Control Map Visibility
When creating a form, you can choose whether tickets using it appear in your operations view by default. This is helpful when you have multiple forms on a site and want to keep the map view clean and uncluttered.
By default, ticket pins are colored by their status. You can change this to color pins based on any Select or Multi-Select field instead. Go to the dataset settings, change the Color Based On option, and make sure your dropdown options have colors assigned.
Restrict Forms to Specific Component Types
When setting up a form, you can limit it to only be available for certain component types. This ensures users always pick the right form for the asset they're working on, reducing mistakes and keeping your data consistent. For example, a Panel Inspection form can be restricted so it only appears when creating a ticket on a panel component.
