COMPANY
Software for the businesses that work in other people’s buildings.
Most operations software is written for a factory, an office or a warehouse: one place, one workforce, one clock. Facility-service businesses are the opposite shape. The work is spread across dozens of buildings somebody else owns, done by people who never come into an office, and it has to be proved before it can be billed.
Four principles, and the product is checkable against them.
These are the constraints the system is actually built under, not a values statement. Each one rules something out.
Operations first
Onvoro is not HR software. It covers workforce and site operations, attendance, proof of work, timesheets and billing. Payroll and accounting are somebody else’s job: Onvoro hands over to them, and if you use Xero, invoices and approved hours go straight there.
Site-centric
The site is the entity everything hangs off: the client, the team, the supervisor, the geofence, the schedule, the tasks, the attendance, the rate. Ask a question about a building and the answer is on one page.
Proof of work
Evidence that the work happened, and evidence of what it was judged against. A verified sign-in, a completed task, a photo, a note, an approval, and the history of who changed what.
Exceptions handled, not prevented
Real operations are messy. Detect, flag, explain, allow an authorised correction, and audit it. Never strand somebody standing at a site who needs to work.
The hard part of this work is not scheduling. It is that by the end of the month nobody can say what actually happened, so the invoice is assembled from memory and defended from memory too.
What we decided differently.
Every one of these costs us something. They are here because the alternative costs an operator more.
The record only flows one way
Attendance becomes a timesheet, an approved timesheet becomes a billable entry, and that becomes an invoice line. Each step reads the one before it and writes something new. Nothing edits upstream, which is why an approved week cannot quietly change after it is billed.
We stop at the invoice on purpose
Onvoro is not trying to become your ledger or your payroll. It takes the work to an issued invoice with the evidence attached and hands it to the systems that are already good at the rest.
What Onvoro does not store.
A field workforce is asked to hand over more than most. Each of these is a deliberate absence rather than a feature we have not got to.
No continuous location
A position is captured at sign-in and at sign-out. There is no background tracking and no GPS trail, because nothing is collecting one. A worker who wants to know whether the app watches them all day can be told no.
No tax file numbers
A TFN brings the Privacy (Tax File Number) Rule 2015 over the whole database and buys nothing operational. Your payroll system already holds it and is the system of record.
No employee bank details and no superannuation
Same reasoning. These are personal data with real handling obligations and no operational use here. The only bank details Onvoro holds are your own, because they print on your invoices.
No sensitive data we cannot justify
Work rights and licences are held, because letting somebody work in breach of a visa is a criminal offence and an expired ticket is a real reason not to roster them. That is the test each field has to pass.
Where it runs, and what state it is in.
Onvoro is in early access. The chain from a quote to an invoice paid in Xero is built and working.
Built
Quotes, clients, sites and regions, workforce and credentials, contracts and service plans, rostering, attendance, jobs, site tasks, issues, timesheets, billing, invoices, Xero for invoices, payments and payroll hours, reports, notifications, a live map of every site and the audit log. A worker app on iOS.
Not built
Accounting systems other than Xero, such as MYOB; bills and purchases; credit notes; and Xero Payroll calendars that run twice a month. They are named here rather than implied, because a page that describes a feature nobody can open is worse than a short page.
Where the data sits
We are based in Australia and handle personal information under the Privacy Act 1988 and the Australian Privacy Principles. The database, the files uploaded to it and our backups are held in Singapore; the web application is served from the United States; and our technical logs are held in the United States for thirty days. The privacy policy names each provider and where it operates, and it is the version that governs.