Work order tracking sounds like warehouse software until you have three crews out on a Tuesday and the office cannot answer "which job is Mark on?" without calling Mark. AV is not generic field service. You are tracking programming hours, client walkthroughs, rack builds, and sign-off photos on jobs that started as a proposal six weeks ago.
This is the tracking model we built into work orders in Specifi. One database from signed proposal to invoice, with a native mobile app for the van.
Start from the signed proposal, not a blank form
When the client signs, line items, labour, and room scope should flow into a work order without re-keying. If the office rebuilds the job in a second tool, tracking will always lag reality. Convert to Project is the whole point: the proposal is the job record.
Dispatch: one calendar, every crew
The office view is a dispatch calendar: who is where, which phase is active, what slipped. Change the schedule once and the mobile app updates on the tech's phone. No screenshot of a spreadsheet in the group chat.
Field: capture on site, not at 6 PM
GPS clock-in, before-and-after photos, voice notes, on-site customer e-signature, change requests logged against the job. The tech should not be typing project names from memory on a ladder. The app already knows which work order they opened from the schedule.
Sign-off: close the loop back to invoice
When the client signs on site, the job status updates in the office immediately. Milestones tie to invoicing so you are not chasing "is it done?" before you bill. Email threads about punch-list items land on the job via email integration, not in a inbox parallel universe.
If the work order does not match the proposal, someone is re-typing. Re-typing is where tracking breaks.
Matthew, Founder / Ex-Installer
The report we read this week called out work order tracking as the largest untapped query cluster still without a dedicated page. The feature tour lives on /work-orders. If you want to see dispatch and field sign-off on your job types, book a demo.