Field types

When building a report template, you can choose from the following field types. Each serves a different purpose, and the AI assistant knows how to fill every one from conversation.

​

Short text

A single line of free text. Use this for names, reference numbers, short descriptions, and anything else that needs a brief, open-ended answer. Example uses: employee name, asset tag, job reference, site address.

​

Long text

A multi-line text box for longer answers. Use this when the field worker might need to write several sentences, for example a summary of work carried out, or a description of damage found.

​

Section header

A visual divider with a heading. Section headers do not collect data. They are purely for organising the form into labelled groups, making it easier to read and navigate. Example uses: “Device details”, “Condition assessment”, “Sign-off”.

​

Checkbox

A yes/no tick box. Use this for binary questions where the answer is either true or false. Example uses: “Was PPE worn?”, “Has the area been made safe?”, “Customer signature obtained.”

​

Combo box

A dropdown that lets the field worker choose one option from a predefined list. Use this when you want controlled, consistent answers rather than free text. Example uses: device condition (Good / Fair / Damaged), job outcome (Complete / Incomplete / Follow-up required). When setting up a combo box, define the list of options in the field editor.

​

Radio group

Similar to a combo box, but the options are displayed as a visible list of radio buttons rather than a dropdown. Useful when there are only a few options and you want them all visible at once without opening a menu.

​

RAG (Red / Amber / Green)

A colour-coded status rating. The field worker selects one of three colours — Red, Amber, or Green — to indicate condition or risk level at a glance. The AI assistant can set this from natural language: saying “driveability is amber” is enough to fill in the field. RAG values appear as a coloured badge in submitted reports and in any PDF export. Example uses: vehicle driveability, site safety status, equipment condition rating.

​

Image upload

Allows the field worker to take a photo or choose one from their device gallery. The photo is attached to the specific field in the report. Example uses: photo of device condition, site photo, signature capture.

​

PDF upload

Allows the field worker to attach a PDF document from their device storage. The file is uploaded directly to the report and available for download from the dashboard. Example uses: attaching a signed delivery note, uploading a completed paper form, sending a manual alongside the job record.

​

Audio upload

Allows the field worker to attach an existing audio file from their device, or record a new voice note on the spot. The audio plays back directly in the dashboard report viewer — no download needed. Example uses: verbal condition description, spoken instruction, recorded observation where typing is impractical.

​

Scan (QR / barcode / OCR)

Lets the field worker point their camera at a QR code, barcode, or piece of printed text to fill the field, instead of typing it in. Choose which of the three the field should look for when you add it — QR code, Barcode, or OCR. The field stores both the decoded text and the photo FieldPal captured when it scanned, so the original code is always available as evidence alongside the value. Example uses: asset tag on equipment, vehicle VIN plate, delivery note barcode, a serial number printed on a label.

​

Repeatable section

A group of fields that can be added multiple times, one set per item. Use this when the job involves inspecting or recording multiple instances of the same thing. Example uses: one set of fields per window inspected, per item collected, per defect found. The AI assistant adds a new row each time the field worker describes another item. Rows can also be added manually.

​

Conditional section

A group of fields that only appears when a specific condition is met on another field. The condition is set when you create the section, for example “show these fields only if Device condition equals Damaged”. Data in a conditional section is preserved but hidden when the condition is false. Example uses: damage description fields that appear only when condition is “Damaged”, follow-up fields that appear only when job outcome is “Incomplete”. See Conditional sections for a full walkthrough of setting the trigger field, matching values, and inner fields.

​

Making a field searchable

Short text, long text, combo box, radio group, RAG, checkbox and scan fields can be linked to a facet, so reports can be found by that field’s value in the Reports register, even across different templates. Set this with Searchable by in the field editor. See Facets.