Loading
Because the answer lives somewhere the employee cannot see. How much leave is left, when was the last payslip, who covers this while somebody is away.
Each is a two-minute question that becomes an email, a delay and an interruption. Multiply by headcount and it is a meaningful part of an HR team's week.
The employee sees their own record: balance, payslips, documents, and the team calendar showing who else is off before they request rather than after.
A request routes to the right approver with the context to decide it, and the employee can see where it is without asking.
It does not let people change what they should not. Contact details usually; role and reporting line never, because those are decisions rather than preferences.
And it shows nothing about colleagues beyond the directory and the shared team calendar.
The volume of routine questions falls, and what remains is the work that actually needs a person.
And because the directory is a view of the personnel record rather than a second list, it is current — leavers disappear when their record closes rather than in September.
Yes, with the team calendar, before requesting.
The fields you permit — usually contact details, never reporting line.
No. The directory is public; the file is permissioned per field.
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.