Job Manager
From first quote to final payment.
2026
Development recorded in the project repository. Earlier work may predate this history; this is not a confirmed launch date.Business systems
Inside Job Manager
The current Job Manager interface running from the project repository.
The problem
A contractor's work moves from enquiry and estimate to sites, crews, field changes, customer decisions, invoices and collections. When the office and the job site manage those stages in different tools, the current scope, completed work and financial position stop matching.
The operating system also has to handle real contracting exceptions: offline crews, additions after billing, invoices covering several jobs, payments covering several invoices and different access for staff and customers.
The solution
Job Manager brings CRM, sites, jobs, crew assignments, quoting, customer access, field updates, billing and payments into one job lifecycle. Office and field staff work from the same operational record while customer and project permissions expose only the relevant view.
Offline edits queue for synchronisation and already-billed line items retain their history. Later changes can become supplemental billing or a controlled void-and-rebill; payment allocation and bank matching connect the job record to what has actually been collected.
The decisions behind it
- Changing work, stable history
- A new job price and an issued invoice are not the same record. Adjustments need an explicit route instead of overwriting what was previously billed.
- Offline access still has boundaries
- Queued changes must be checked when they reach the server; having a local copy does not grant permission to update every project.
- Many jobs, many payments
- Billing and payment allocation must handle relationships that are more complex than one job, one invoice and one payment.
- Job lifecycle and crew assignments
- Offline field updates
- Quotes, invoices and customer access