Skip to content
English
  • There are no suggestions because the search field is empty.

Field Ticket Form Configuration

 What are Field Tickets?

Field Tickets are a form type inside the Jobs module for capturing billable field work. Each Field Ticket represents a discrete visit, day, or event of work performed against a Job, with:

  • Line-item cost tracking (through Misc Items and an optional Other Expenses form question).
  • Automatic subtotals and Field Ticket total.
  • File attachments (photos, PDFs, other documents — up to 20 files at 20 MB each).
  • All standard form-engine capabilities: custom questions, workflows, calculations, departments.

Architecture note (for admins doing setup): Field Tickets are not a separate database entity. Every Field Ticket is a form log (like any HSE, Custom, or Inspection submission) with its form_type set to Field Ticket and attached to a parent Job. This means the same Form Config, Reports, workflows, and PDF-export machinery you already use for other form types applies here — you're configuring a form type, not learning a new module.

Key point: Field Tickets are designed for service companies and OFS operators who need to invoice clients for on-site work. E&P operators can use them too, but the invoicing-readiness features carry the most value for organizations that bill hours and materials externally.

Why Field Tickets Matter
  • One place for billable work. All labour, equipment, chemicals, and inventory used on a Job land on Field Tickets under that Job — no side-of-desk spreadsheets to reconcile at month-end.
  • Automatic cost calculation. Line-item subtotals and Field Ticket totals compute from rate × quantity, eliminating a common source of billing errors.
  • Feeds Invoicing. Field Tickets are the source data for the Invoicing module — their line items build invoices automatically.
  • Cross-Job visibility. The Job Dashboard aggregates Field Ticket totals per Job. Note this is a Field-Ticket-only figure — Job Form budget-category spend is the notable omission, while job asset daily cost and task cost are not counted as cost anywhere.
  • Filters that match how the work happens. Assigned-to-Me, Company, and Job Status filters let field techs see only their tickets and back-office see only what's ready to invoice.
Prerequisites

Configure these before creating Field Ticket forms:

  1. Enable the Jobs module. Turn on the Job/Project Forms setting (the project_page key) under Org Configuration → Other → Org Settings.
  2. Assign the Jobs role permission to the roles that will create and edit Field Tickets, under Org Configuration → Users & Roles → Roles. This is the same permission that gates Jobs — there is no separate "Field Tickets" permission.
  3. Set up Companies (the customers you bill) under Org Configuration → Organization → Companies.
  4. Configure Misc Types and Misc Items under Org Configuration → Other → Misc Items. These are the line-item catalog for the "Inventory Used" table on Field Tickets. Per Misc Item, set:
    • Unit of Measure — a short label describing what one "usage" means. Common values are hrs for hourly billing such as labour and equipment time, each for per-piece billing such as parts and supplies, L for per-litre items such as chemicals and fuel, or any other unit your work needs. The unit of measure only labels the row; it does not set the price.
    • Consumable — check this for items that decrement inventory stock (chemicals, one-time parts). Leave unchecked for equipment/rentals that don't decrement.
    • A default rate (optional) — set up through an extra info column whose Internal Column is rate, then filled in per item. It pre-fills the Rate box when an operator picks that item on a ticket. The exact steps are in "How to set a default rate" below — the naming is not obvious and getting it wrong produces a column that looks right and prices nothing.
  5. Users with location access. Standard EZ Ops location assignments apply — users need access to the Job's location to see the Field Ticket.
Where Field Tickets Live

Field Tickets are accessed through Jobs. There is no top-nav "Field Tickets" menu item.

  • Reports → Operations → Job Dashboard — every Job with a Total Cost column aggregating all Field Ticket totals on that Job. Expand a Job to reach its Field Tickets section, and use New Field Ticket to create one.
  • Location Dashboard — the Field Tickets widget lists Field Tickets filed at that location, filterable by Job name.
  • Reports → Forms — filter by form type Field Ticket for a table with a Total Cost column plus PDF and ZIP export per ticket.
Setting Up a Field Ticket Form

Step 1 — Create the form

Navigate to Admin → Forms and click Add New Form.

  • Select Type: Field Ticket. This option only appears when project_page is enabled.
  • Enter a name — this is the form name operators will see when creating a new ticket.
  • Assign a department (optional) — the department's supervisors become default email recipients for workflows.

Step 2 — What gets auto-populated (no admin work needed)

The Field Ticket form dialog automatically includes:

Field Source
Job Name, Start/End Date Parent Job (visible in the header banner)
Job Location Parent Job
Select Job Editable dropdown; defaults to the current Job
Type of Location: Field Location / Plant / Custom Built-in toggle. Custom lets the operator enter a location that isn't modeled in EZ Ops (e.g. a client site)
Select Location Dropdown of Field Locations or Plants; text input if Custom
Total Cost display Auto-calculated from all line items + Other Expenses
Attach Files / Take Picture Built-in; 20 files max, 20 MB per file (constants, not per-org configurable)
logged_by, logged_at, unique display ID Auto-set on save

You do not need to add form questions for Job number, ticket date, technician name, or location — those are part of the built-in dialog chrome.

Step 3 — Add line items to the ticket

Field Tickets have two independent line-item mechanisms, both feeding the same Total Cost displayed at the top and bottom of the ticket. They are configured differently and used for different kinds of billable items — most orgs will want both enabled.

A. Misc Items Used — the catalog-driven line-item table

This is the "Inventory Used" table shown on the ticket. It appears whenever the Misc Items setting (the misc_items_widget key) is on for the form.

How it works:

  • Types and Items are admin-configured in the Misc Items catalog under Org Configuration → Other → Misc Items. You decide what categories exist — Labour, Equipment, Chemicals, Inventory, Consumables, whatever fits your billing — and what individual items live under each.
  • Each Misc Item has a unit of measure such as hrs, each, L, kg, or m, which determines what "one usage" means.

Columns on the ticket row:

Column Notes
Type Chosen from the Misc Types configured in your catalog
Description The specific Misc Item within that Type
Quantity / Usage Entered per row (freeform decimal)
Rate ($/usage) Entered by the operator per row
Line Item Cost ($) Auto-calculated = Rate × Quantity

Stock behavior: consumable Misc Items decrement stock in the Inventory module when the ticket is saved. Non-consumables (rental equipment, tools) do not decrement.

A ticket line is not a job asset. Adding a Misc Item to a Field Ticket records a priced usage on that ticket. Adding a Misc Item to the Job itself reserves the item — it marks it Assigned for a date range and carries no cost. The two are separate records, and only the ticket line produces money. A Misc Item on a ticket does not mark the item Assigned.

Use Misc Items for anything you bill regularly and want in a reusable catalog — labour classes, standard rentals, common chemicals, part numbers you stock.

Where a rate comes from

Three different fields can look like "the rate", and only one of them prices the ticket line:

Field Where it lives What it does
Default rate An extra info column on the Misc Type whose Internal Column is set to rate, with a value filled in per Misc Item Pre-fills the Rate box when an operator picks that item on a ticket. Nothing more — it is a starting value
Rate The row on the Field Ticket This is the one that counts. Line Item Cost is this rate × quantity, and it is what the ticket total and the Job Dashboard use
Daily cost A job asset on the Job itself A planning reference only. It prices nothing — not the asset, not the Job, and never a ticket total
How to set a default rate

There is no price field on a Misc Item. Pricing is carried by an extra info column, and the column only prices anything when its Internal Column is set to rate. The visible label is separate and can say whatever you like.

Once per Misc Type:

  1. Go to Org Configuration → Other → Misc Items (labelled Inventory in organizations that renamed it) and open the Misc Types tab.
  2. Select the arrow beside the Type to open Edit {type} extra info interface.
  3. Select Add extra info column.
  4. Set Alias to whatever operators should see — Rate, Unit Price, $/hr. This is only a label.
  5. Set Internal Column to rate from the dropdown. This is the step that does the work. A column with the alias "Rate" but no Internal Column set will display and store a number that never reaches a ticket.
  6. Save.

Then per Misc Item, on the Misc Items tab, create or edit the item and type the number into the field labelled with the alias you chose.

In bulk, the Misc Items import template carries one column per extra info alias, so the pricing column's header is your alias — not rate. Every configured alias is a required column on every row.

Two constraints worth knowing before you design the catalogue:

  • One Internal Column value per Type. A Type cannot have two columns both set to rate.
  • rate is a fixed option, alongside description, make, model, and serial_number. You cannot invent a second pricing key.

Whether an operator can overwrite a pre-filled rate depends on which screen they are using. On the Job Dashboard the default rate is only a starting value and the operator can type over it. On the location or plant Field Tickets panel — the path field crews use, and the only one that works offline — the Rate box is disabled whenever the Misc Item carries a default rate, so the ticket can only be billed at the catalogue price. Plan for this when you set default rates: an item whose price genuinely varies by job is better left without one, so crews can enter the real figure rather than routing it through Other Expenses.

Once the ticket is saved, the row's own rate is authoritative — later edits to the Misc Item's default rate do not change tickets already recorded.

B. Other Expenses — the freeform on-ticket table

This is a form question type you add to the Field Ticket form. Add a question with answer type Other Expenses in Form Config. It appears on the ticket as a small table that the operator can add rows to freely.

How it works:

  • No catalog. The operator types Description, Rate, and Quantity for each row from scratch.
  • Capped at 25 rows per ticket. A counter beside the table reads {n}/25 line items, and Maximum line items reached appears at the limit. This is a constant, not a per-org setting.
  • Each row's contribution to the ticket total is Rate × Quantity, summed with the Misc Items totals.

A row is only counted if both Rate and Quantity are filled in with numbers. Rows left partly blank are ignored, on the ticket total and on any invoice the ticket feeds.

Use Other Expenses for one-offs that don't warrant a catalog entry: permits, mileage reimbursement, meals, third-party services, single-use consumables purchased on the way to site.

Both together

The Total Cost aggregates across both sources. Most service-company Field Ticket forms enable both — Misc Items for the recurring items, Other Expenses for the miscellany. Both sources also flow through to invoicing: each Misc Item row and each Other Expenses row becomes its own invoice line.

Step 4 — Add custom questions

Field Tickets support the full form-question library available in Form Config (radio, select, text, numbers, attachments, Item in List, Other Expenses, and the rest).

Recommended baseline questions for a standard service-company Field Ticket:

Time on site:

  • Arrival date & time (date + time input)
  • Departure date & time (date + time input)
  • Total hours on site (calculation on the two above)
  • Delays / non-productive time? (Radio: Yes/No; conditional textarea when Yes)

Crew:

  • Lead technician (Select, from user list)
  • Additional crew members (Checkboxes or item-in-list, from user list — see Assignments below)

Work performed:

  • Scope of work performed (Textarea, required)
  • Weather / site conditions (Select or Textarea)
  • Safety / JSA completed? (Checkbox, required)
  • PPE compliant? (Checkbox)

Office / invoicing routing:

  • Notes for office (Textarea)
  • Customer contact met on site (Text)

Skip anything the built-in dialog already captures (Job info, location, date).

Do not use "Category budget question" on a Field Ticket form. The checkbox appears on any money or number question regardless of form type, so it is offered here — but it only produces cost on a Job form attached to a Job. Ticked on a Field Ticket, the answer saves and contributes nothing to Job cost, and the Job Category picker beside it will be empty because that list is only loaded for Job forms. Capture Field Ticket cost through Misc Items or Other Expenses instead.

Step 5 — Capabilities and limits (form-type matrix)

Capability Field Ticket Notes
Sections ❌ No Ticket is completed in one continuous session.
Workflows (email, corrective actions) ✅ Yes Full workflow tab available.
Calculations ✅ Yes Basic, time-based, chained.
Departments ✅ Yes Sets default supervisor recipients.
Form Process / Investigation ❌ No HSE-Dashboard review flow does not apply.
Pass values ✅ Yes On select/radio questions.
Attachments / photos ✅ Yes 20 files, 20 MB each, S3-stored.
Reference files / external IDs ✅ Yes Standard.
Import ✅ Yes Standard. Note: Import is unavailable for the Machine Schedule form type.

Step 6 — Set up assignments (optional)

Field Tickets support two independent assignment paths that both feed the "Assigned to Me" filter on the Jobs page:

  • Job-level assignments — users assigned directly to the parent Job. Configured on the Job itself.
  • Field-Ticket-level assignments — users assigned to a specific ticket. Configured via a form question on the Field Ticket form (see below).

The Jobs list "Assigned to Me" toggle shows a Job if the current user is a member of either list.

How to configure Field-Ticket-level assignment:

Field Tickets don't have their own "assignee" field — assignment is captured by a specific form question. To wire this up:

  1. Open the Field Ticket form in Admin → Forms.
  2. Add a new question with Answer Type = Item in List.
  3. In the Select list to use dropdown, choose users. This is a virtual list that resolves to your org's active users at runtime — it is not a Dropdown List you have to create at /admin/dropDownLists. The users option is the only list currently supported for assignments.
  4. Check the box labeled "Assign selected users to the form log." This is the critical step — without this checkbox, users picked in the question are recorded as a plain answer only and no assignment is written. The in-app tooltip reads:

    "When on, the users selected for this question are assigned to the form log. Only one question per form can create assignments."

    The screenshot above also demonstrates the assignment question as a conditional child of an "Assign to Other" Yes/No parent — that pattern is optional, but if you use it, note the assignment is only written when the parent evaluates to "Yes" at save time. See "Constraints and gotchas" below.
  5. Save the question.

Constraints and gotchas:

  • Only one assignment-creating question per form. Form Config rejects a second question with the checkbox enabled.
  • The list must be users. A regular Dropdown List containing user names as plain text won't work — assignments need the real user records that the virtual users list provides.
  • Multiple assignees per ticket require the Multiple User Tasks setting (the multiple_user_tasks key) to be on. Without it, one assignee per ticket.
  • Assignments are recorded on every save, including Save Progress. You don't have to Save and Submit.
  • The assignment question can't be a conditional child whose visibility depends on other answers. If the question is hidden at the moment the ticket is saved, its answer is dropped and no assignment is created. Put the assignment question at the top level of the form, always visible.
  • The Assigned to Me filter on the Job Dashboard shows a Job if the current user is assigned to the Job itself or to any Field Ticket under it.

Step 7 — Configure workflows (optional)

Same workflow builder as Health & Safety / Custom forms. Common patterns for Field Tickets:

  • Notify the dispatcher when a Field Ticket is completed — send an email with the total cost and key line items.
  • Auto-create a Task for the office to review and invoice the ticket.
  • Notify the customer contact on completion (if the form captures their email).

Workflows fire on Save and Submit. Save Progress does not fire workflows.

Lifecycle and Statuses

Field Tickets do not have a dedicated status field. Lifecycle is expressed through the standard form states plus one invoicing state:

State How it happens What it means
In progress (draft) Operator clicks Save Progress Retrievable and editable. Workflows do not fire.
Complete Operator clicks Save and Submit Total is finalized and workflows fire.
Deleted Admin deletes the ticket Disappears from lists but is retained and recoverable.
Attached to an invoice Someone selects the ticket in the invoice editor The ticket no longer appears in the Field Ticket picker on any other invoice.

There is no "Submitted" or "Approved" state, and no approval or review step of any kind. The Form Process tab that drives the Health & Safety review flow is deliberately unavailable on the Field Ticket form type, and Field Tickets never appear in the HSE review dashboard. Nobody signs off a ticket before it can be billed.

One thing to be aware of if you export form data: a completed Field Ticket picks up a workflow status of Reviewed automatically on completion. That is a side effect of the shared form engine, not a record of a review — no reviewer name and no review timestamp are stored, and nobody looked at the ticket. Do not treat that value as an audit trail.

Completion and invoicing are independent. The invoice editor lists every Field Ticket on the Job that isn't already attached to another invoice, whether it is complete or still a draft. If your process requires tickets to be finished before they're billed, that has to be a team convention — the app does not enforce it.

Attaching a ticket to an invoice is what consumes it, not completing the invoice. Attaching to a brand-new, unfinished invoice removes the ticket from every other invoice's picker immediately. Unlinking it in the invoice editor returns it to the pool.

Deleting an invoice does not release its Field Tickets. They stay attached to the deleted invoice and stay out of the picker. If you need them back, restore the invoice from the Deleted tab, unlink the tickets, save, then delete the invoice again.

Reporting

Three surfaces cover Field Tickets:

Reports → Forms

  • Form-type filter: Field Ticket
  • Total Cost column
  • Full form details on drill-down, with PDF and ZIP export per ticket. The ZIP includes attachments.

Reports → Operations → Job Dashboard

  • Total Cost ($) column — the sum of every Field Ticket total on the Job, explained by a tooltip on the column header. It is Field Tickets only. A Job that also carries Job Form budget-category spend has a real total higher than this column shows, and a Job with no Field Tickets reads $0 here no matter what has been spent on it. Job asset daily cost and task cost are not so much missing from this column as not counted as cost anywhere.

Reports → Operations → Invoices

  • The Field Ticket picker inside an invoice doubles as a list of work on that Job that hasn't been billed yet.

The Field Ticket PDF

Field Ticket PDFs are generated on demand and contain:

  1. Header — the EZ Ops logo.
  2. Job block — Job name, start date, end date.
  3. Ticket metadata — who logged it, when, and the ticket's display ID.
  4. Answers — every custom question and its answer.
  5. Other Expenses table, if present — Description, Rate, Qty, Total.
  6. Attachments — photos and files.

Field Tickets use the shared form PDF template. There is no Field-Ticket-specific layout and no per-org branding on the ticket PDF beyond the EZ Ops logo.

The invoice PDF is a different document with a different layout — it carries your organization's address and the customer's, and it shows no EZ Ops logo.

What Field Tickets Do Not Do

Commonly-expected features that are not available:

  • Signatures. No signature capture, for the customer or the technician.
  • Cloning or templating. There is no "duplicate this ticket" action. Each ticket is created fresh.
  • A Field-Ticket-specific PDF template. Tickets use the shared form PDF template, with no per-org branding beyond the EZ Ops logo.
  • An approval or review step. No sign-off exists between a completed ticket and an invoice.
  • Role-based cost hiding. Rates and totals are visible to every user who can open the ticket. If your organization needs rates hidden from field technicians, contact EZ Ops Support at 888-378-4602 ext. 1 or EzopsSupport@Detechtion.com.
  • Direct accounting-system export. There is no QuickBooks, SAP, or Sage integration. Invoicing produces a PDF.
  • A completion requirement before billing. A draft ticket can be attached to an invoice just as easily as a completed one.
Common Issues

"I don't see the Field Ticket form type in Admin → Forms."

  • Confirm the Job/Project Forms setting is enabled under Org Configuration → Other → Org Settings.
  • Confirm your role has the Jobs permission under Org Configuration → Users & Roles → Roles.

"The Total Cost on the ticket doesn't match what I entered."

  • Line items compute rate × quantity per row. Double-check both fields.
  • Other Expenses adds to the total separately — check the Other Expenses table.
  • The ticket total is stored on the ticket when it is saved, not recalculated every time it is displayed. Any change to line items after the ticket was completed requires re-saving it to refresh the stored total.

"An operator can't see a Field Ticket someone else created on the same Job."

  • Field Ticket assignment is on the ticket, not inherited from the Job.
  • If your list is filtered to "Assigned to Me," you'll only see tickets where you're on the assignment list (or the parent Job's assignment list).
  • Location access still applies — the operator needs access to the Job's location.

"A Misc Item's stock decremented but the operator only recorded it in the form."

  • Consumable Misc Items decrement stock automatically when the ticket is saved. This is intentional. If the item shouldn't decrement, mark it as non-consumable under Org Configuration → Other → Misc Items.

"The Save and Submit button is disabled."

  • A parent Job must be selected. If the ticket was drafted without a Job, Save Progress works but completing requires a Job.
  • Any required custom questions must be answered.

"A Field Ticket doesn't appear in the invoice editor's picker."

  • It is already attached to another invoice. Open that invoice and unlink it, or check the Deleted invoices tab — a deleted invoice still holds on to its tickets.
  • It has to be on the same Job as the invoice.
  • It does not need to be complete.

"A ticket was attached to an invoice but contributed fewer lines than expected."

  • Other Expenses rows are skipped when either Rate or Quantity is blank or non-numeric. Fill those rows in, then unlink and re-attach the ticket.