Authorization with specifics
A work order that says \"fix the AC\" invites a different job than the one you meant. The effective WO specifies: the scope in tasks, the location precisely, materials responsibility, the completion date, and the agreed price or rate basis.
The WO in the field
Facility teams issue WOs to contractors; contractors log them as jobs; completion gets confirmed against the order's scope. The numbered WO is also what the contractor's invoice will cite — closing the authorization-to-payment loop.
Recurring work, saved details
Sites, contractors and common job types save for reuse — the fifth AC service takes a minute to order. Region sets currency; records keep the maintenance history.
Features
- Task-level scope definition
- Site and schedule fields
- Price or rate-basis terms
- Free for signed-in users
- Job history saved
Supported formats
How it works
- 1
Specify the work
Tasks, site, schedule, price basis.
- 2
Generate the numbered WO
Clear authorization the contractor executes.
- 3
Confirm completion against it
Invoice matches the order.
No general cloud storage — uploaded and processed files are temporary and deleted automatically.