Jobs vs job records
Maintenance in Tero.Ops uses two terms that refer to the same thing at different stages:
- A Job is a unit of planned or required work that is still open. “Service main engine — 500-hour service.”
- A Job record is that job once it’s finished — Completed or Cancelled — together with what actually happened: the completion report, parts used, who carried it out, and how long it took.
When you complete a job (see Recording job completion), it moves from Jobs to Job records. Completed work requests become records the same way.
Where to find them
| Jobs | Job records | |
|---|---|---|
| Sidebar | Operations → Jobs | Operations → Job records |
| On an asset | Jobs tab | Records tab |
| Statuses | Pending, Started, Paused, Overdue | Completed, Cancelled |
Why the distinction matters
Real maintenance never matches the plan exactly. A 500-hour service might be done early, with different parts, by someone other than the assigned technician, taking longer than estimated. The job describes the plan; the record captures what really happened.
This matters for:
- History — “How many engine services have we actually done this year?” is answered from records, not jobs.
- Audits — each record keeps its report, parts, people, and time, and can be exported to PDF.
- Recurring schedules — a schedule creates a separate job for each occurrence. Each completed occurrence becomes its own record, and a recurring job shows the earlier occurrences in its History section.
In practice
You usually work with jobs when planning and doing the work, and with records when looking at history or exporting reports.