Work order form
A work order exists to get a job dispatched, not merely logged — someone has to know where to go and how urgent it is before they can act. A location or asset field and a priority level are what make a request routable the moment it arrives, rather than a paragraph a dispatcher has to read and re-type into their own system. This form collects the request; it doesn't assign anyone to it or track the job through to completion. Routing the ticket and closing it out are still steps you take afterward, the same way a webhook only tells you a request arrived.
The form beside this text is live. Fill it in and submit it — it validates exactly as it would for a real respondent, and saves nothing.
Location is a field of its own, not folded into the description
A dedicated location or asset field means a work order can be sorted or filtered by where the job is before anyone reads what it's about — a maintenance queue grouped by building looks nothing like one grouped by request time. Support-request-form, built for software issues, has no equivalent field, because a software bug has no physical location to record.
Priority is routine/urgent/emergency, not a budget or a timeline
The priority field here asks how soon the work needs doing, scaled for dispatch — routine, urgent, emergency — which is a different question from quote-request-form's timeline field (ASAP, within a month, exploring) that scopes when a project starts, or its budget field that scopes what it costs. A work order isn't being priced; it's being routed.
No card required.
Work order form
Live previewHow to build this form
5 steps in the editor. Nothing here needs a paid plan.
- Add text and email fields for the requester's name and contact details.
- Add a text field for the location or asset — a building, room or equipment ID — so the job is placed before anyone reads the description.
- Add a select field for priority (routine, urgent, emergency) and a select field for the type of work (plumbing, electrical, HVAC, general).
- Add a required long text field describing what needs doing, and an optional date field for a preferred time.
- In Settings, add a webhook so each work order reaches your dispatch system or on-call channel the moment it's submitted.
Fields in this form
8 fields, using 6 of the 19 field types available.
| Question | Field type | Required |
|---|---|---|
| Full name | Short text | Yes |
| Yes | ||
| Phone | Phone | Optional |
| Location or asset | Short text | Yes |
| Priority | Select | Yes |
| Type of work | Select | Yes |
| Describe what needs doing | Long text | Yes |
| Preferred date | Date | Optional |
What goes wrong with this form
Specific to a work order form, not general advice about forms.
No location field, so the request has to be read to be placed
Without a dedicated location or asset field, "where" lives inside the description text, and a dispatcher has to open every row to find it. A location field is what lets a queue be sorted by building or equipment before anyone reads a word of what's wrong. Quote-request-form has no equivalent field, because a project quote has nowhere to dispatch to.
Priority left as free text
A text field for urgency produces "ASAP", "whenever", and "ASAP!!" — none of which sort. A select field with a fixed scale (routine, urgent, emergency) is what lets an emergency request be found ahead of ten routine ones.
No work-type field to split the queue by trade
Without a select field for the kind of work — plumbing, electrical, HVAC, general — every ticket lands in one undifferentiated queue regardless of which contractor or in-house team should see it. Sorting a mixed queue by trade means opening each ticket rather than filtering a column.
Questions about this form
What does a work order form need that a general request form doesn't?
A location or asset field, at minimum — a building, room or piece of equipment — so the job can be dispatched without anyone reading the description first. Priority (routine, urgent, emergency) and a work-type select round out the six fields this form uses.
Can I route work orders by priority automatically?
Not automatically inside the form — priority is a required select field (routine, urgent, emergency) so every order carries a value you can sort or filter by in the CSV export or in your own system via webhook, but assigning it to someone is still a step you take after it arrives.
How many work orders can this form collect?
Up to 100 on the free plan, 2,000 on Basic, 5,000 on Advanced — the same platform-wide response cap every form has. A busy facility can set a closing date or response cap in Settings once a queue is more than anyone can act on in a day.
Does a work order form track a job through to completion?
No — it collects the request: who reported it, where, how urgent, and what needs doing. Assigning a technician and marking it closed both happen outside the form, in whatever system the webhook forwards the order to.