One company. Two products. One source of truth.
Your people, customers, sites and assets are the same in both products, because they are the same in your business. Everything else stays in the product it belongs to.
Operations
- Work Orders
- Dispatch
- Scheduling & Capacity
- Crews
- Customers
- Sites
- Assets
- Service Agreements
- Field Service
- Labour & Materials
- Quotes & Invoices
Shared foundation
- People & Workers
- Roles & Permissions
- Divisions, Branches, Departments
- Customers & Sites
- Assets & Equipment
- Documents
- Custom Fields
- Notifications
- Approvals
- Reporting
- Audit Trail
Safety & Compliance
- Safety Programs
- Hazards & Controls
- Inspections & Forms
- Incidents & Investigations
- Corrective Actions
- Training
- Competencies
- Contractor Management
- Audit Readiness
What “separate” actually means
This is not a safety module bolted onto a field service product, and it is not work orders bolted onto safety software. Each product stands alone.
A construction company with no service work
Runs Safety & Compliance on its own. No dispatch board, no work orders, no invoicing — none of it appears anywhere in the product.
A service contractor with no COR program
Runs Operations on its own. No safety navigation, no program documents, no requirements — the product does not ask about any of it.
A company running both
Gets one set of people, customers, sites and assets, and a connection between the work and the risk that neither product could provide alone.
A product you do not run is absent, not empty. If a company runs Operations only, Orientra does not report that they scored zero on safety documentation — it reports nothing at all, because “this company has no safety findings” and “this company does not run Safety” are different claims and only one of them is true.
The foundation both products stand on
People and access
A worker is a person with competencies and history. A user is an account. They are linked, never collapsed — a subcontractor can be tracked without being given a login.
Roles and permissions
Permissions describe capabilities, never screens. Rename every role in your company and the same people keep the same authority.
Organisation structure
Division, branch, department — three levels, because that is what a contractor actually has. Branch is the primary access boundary.
Custom fields
Add a field to work orders, customers, sites, assets, people, incidents or hazards. It appears on the record immediately. Configuration, not development.
Notifications
Rules you configure, delivered to the person who holds the relevant capability — not to a company inbox nobody reads.
Approvals
Put a specific action behind a workflow when your business needs it. An entity with no workflow is not gated at all.
Reporting
Every number opens the records behind it. A figure that cannot be drilled into is removed rather than displayed.
Audit trail
Who did what, when, and what the record said at the time. Historical evidence does not change when configuration does.
Mobile ready
The field experience is designed for a phone from the start, not a desktop layout squeezed down later.
See both products working together.
Start a 45-day free trial with your own company — no card required — or book a demonstration focused on the workflows that matter to you.