Loading
A personnel record on its own is filing. It matters at the moments it changes something: a plan, a payslip, a promise to a client.
These three are those moments. Each crosses from HR into somewhere that does not think of itself as HR.
Software fails at boundaries. A feature list cannot show you one; a journey has to.
Hire to onboard, leave to capacity and time to payroll all start in Nest and end somewhere else entirely — in IT, in a delivery plan, in the ledger.
That is the point. HR software judged only on its own screens is judged on the wrong thing; what matters is whether the consequences reach the systems that act on them.
Leave to capacity is the clearest case. Leave approved in an HR system and a plan that still shows full availability is not a data problem, it is two systems and no join.
Not because anyone was careless — because the record stopped at the edge of the tool, and somebody had to carry it across by hand.
Who runs Nest →If your capacity plans are wrong, read leave to capacity. It is the shortest chain and the most immediately visible.
If you are onboarding regularly, hire to onboard is the one that removes the most administrative failure.
No. It runs end to end in Nest and hands a file to whatever pays people. Books joins when you want the posting to happen without an export.
About a week, and most of that is agreeing the reporting line. Once that is right, approvals and onboarding follow it automatically.
The chain starts later, at accepted offer. Everything downstream is unchanged, because the personnel file is what the rest reads.
Between offer and payroll. The same bank details and tax codes get collected twice, by two teams, from a person who has started.
Yes, with a different contract type on the same record. What changes is what payroll does with it, not where the person lives.
We will run it end to end on your own numbers in half an hour, and tell you honestly which parts Treepie does not improve.