Work Orders

The work order is the unit of work in Prova. A request becomes a job, the job is assigned to a person or a contractor, it is approved, and it is closed. Each job links to the asset it concerns, to the maintenance routine or inspection that raised it, and to the safety certificate it supports. Costs, labour hours, photos and comments attach to the job itself, and every approval and status change lands on one chronological timeline. Boards then give you kanban views over that work, organisation-wide, per team or scoped to a single region, with columns carrying your own labels while still mapping onto Prova’s canonical statuses. Saved views do the same for registers, where each person keeps their own filter, sort and column layout.

The paper trail is the point. When an inspector asks what you did about a defect found in March, the answer is a single record: what was found, who was assigned, what it cost, what evidence was filed, and when it closed. Teams running this through email can usually produce the request or the invoice, but rarely both. And because head office and a site engineer get different views rather than different systems, both are looking at the same work orders, so there is nothing to reconcile at month end and no critical report living in one person’s spreadsheet.