Engineering · · 4 min read
Why the assistant reads one record, not five systems
An assistant is only as trustworthy as the data it reads. Ours reads one employee record, respects its permissions and shows its sources.
There is a tempting way to build an HR assistant: connect it to everything, let it read spreadsheets and email and whatever HR system a customer happens to have, and hope the model sorts it out. We chose the opposite. roothr.ai keeps people, payroll, compliance and hiring in one application, and the assistant reads that one employee record through the same permissions a person would have.
One source of truth
When you ask who is on leave on Friday, there is exactly one place that answer lives. That means the assistant does not have to reconcile three versions of a rota, and it means you can check its answer in the same place it looked.
Permissions are not optional
A line manager asking about pay should see their team, not the company. Permissions sit on the record itself, and the assistant runs as the person asking, so it can never reveal more than they could open themselves.
Every answer shows its working
Figures link to the records they came from. A compliance flag names the worker, the document and the date. If the assistant is not sure, it says so and asks rather than filling the gap with a plausible guess. In payroll and immigration, a confident wrong answer is worse than no answer.
One boundary, one set of controls
roothr.ai is UK hosted and UK processed, under ISO 27001 controls, ICO registration and GDPR arrangements. Prompts and answers stay within that boundary and are not used to train third-party models. Where a partner platform such as Root HR holds the records, the connection runs on permissions you grant and can withdraw.
None of this is glamorous. It is the difference between an assistant you can use for a demo and one you can hand your payroll to.
Run your own month on roothr.ai
HR, payroll, UKVI compliance and hiring in one application. Plans from £39.99 a month.
