Software shopping in the trades means wading through vocabulary: one product manages work orders, another schedules jobs, a third resolves tickets, and somewhere a consultant says service request with a straight face. They overlap heavily but are not synonyms, and the word a product leads with tells you which industry it grew up in, which predicts how it will fit a trade business better than any feature list.
The five terms, untangled
A work order is a formal authorisation for specific work, usually with a number, an asset, and a paper ancestry in maintenance departments and facilities management (work order overview). A job is the trades word for the same round trip described from the doer's side: a customer, a site, a crew, a date, and evidence coming back. A ticket comes from IT helpdesks: a numbered record of a reported problem queued for resolution, born digital and measured in response times. A service request is the customer-facing act of asking, which may become a ticket, then a work order, then someone's Tuesday. A task is the smallest unit: one step inside any of the above.
The practical translation: facilities and property software says work order, trade software says job, IT and internal-maintenance software says ticket. All of them mean a unit of work with a lifecycle from raised to done.
Why the origin story matters when buying
Products inherit assumptions from their birth industry. Work-order systems assume assets are the centre of the world: they are superb at maintenance history per air-conditioning unit and clumsy at quoting a homeowner. Ticket systems assume a desk-bound resolver and measure response time, not travel time; they rarely understand a van, a multi-day install or a signature on a doorstep. Job-centred systems assume a customer, a site visit and an invoice at the end, which is the actual shape of trade work.
None of this appears on pricing pages, but it leaks through everywhere: whether the mobile app works offline, whether a job can span three days, whether the record ends in an invoice or a resolution code. Asking which word a vendor's own staff use in demos is a surprisingly reliable fit test.
The lifecycle is the same everywhere
Strip the vocabulary and every system runs the same arc: raised, triaged, scheduled, dispatched, done, evidenced, billed or closed. What differs is which stages the software takes seriously. Trade businesses live or die in the middle stages, scheduling and dispatch and evidence, because that is where crews wait, customers cool and paperwork leaks. An IT ticket can sit in a queue harmlessly; a job with a customer standing in a cold house cannot.
That is why our own vocabulary at SKEDS is unapologetically job: the record starts with a customer and a site, carries H&S forms, photos, hours and a signature through the middle, and ends as a draft invoice. The field service management explainer maps where these lifecycles fit the wider software landscape.
A working glossary for mixed company
When your commercial clients send work orders and your software speaks jobs, the mapping is mechanical: their work order number goes in your job reference field, their asset ID goes in the site or notes, and your completion evidence returns as their close-out documentation. Crews need never learn the client's dialect; the office translates at the edges. The one term worth adopting internally regardless of software is task, for the checklist steps inside a job, because it gives the crew a shared word for the difference between the job is done and every step of the job is done, and that difference is where callbacks are born. Our job sheet template shows this structure on one page of paper if you want the concept before the software.
Frequently asked questions
Is a purchase order the same as a work order?
No. A purchase order authorises buying something from a supplier; a work order authorises doing something. Confusing them upsets exactly one person: your accountant.
What is a job card?
Another regional synonym, common in the UK, South Africa and Australia, for the printed job record a technician carries, the same artefact as a job sheet. Our free job sheet template is a job card by any name.
Do I need software that supports all these terms?
No, you need software whose native term matches your work's shape. For customer-site-invoice work that is a job system; renaming labels does not change a product's assumptions.
Found this useful? Share it
Someone in your trade group chat is asking this exact question.
Key takeaways
- Work order, job and ticket are the same lifecycle described by different industries.
- A vendor's native vocabulary predicts its assumptions better than its feature list.
- Trade work lives in the middle stages: scheduling, dispatch and evidence.
- Translate client dialects at the office edge; crews only ever need one word.
Stop running the job from a spreadsheet
Schedule your crew, run jobs from the van, and invoice the moment they are done. Free for one user, forever.
Start free trial
