Loading
Because it starts as documents. Contracts on a drive, salary changes in an email thread, the org chart in a slide deck, right-to-work checks in a folder. Each one made sense when it was created.
Then somebody asks who reported to whom in March, or when a policy was signed, and the answer takes an afternoon and arrives with a caveat.
One personnel file per person: contract and terms, documents with expiry dates, salary and role history, reporting line, and every lifecycle event from offer to alumni. Each change is dated.
Field-level permissions mean the file can be complete without being open — a manager approving leave does not see what that leave costs.
It will not chase a missing document beyond flagging that it expired, and it will not resolve who somebody actually reports to when the chart and reality disagree.
It records the answer you give it, thoroughly and with a date. That is the whole claim.
Because access derives from the reporting line, a reorganisation moving forty people takes effect the same afternoon rather than becoming a quarter-long review.
Loop reads availability, Books reads approved time, Desk reads team membership. None of them keeps a second copy of an employee.
Products, not integrations. Each one reads the same record, so a join is a permission rather than a sync job with a mapping screen behind it.
Yes. Reporting lines are dated, so historical structure resolves correctly.
Yes, at field level, with every access to a restricted field recorded.
Access follows the reporting line, so it is a same-day change rather than an access review.
Half an hour on your own numbers is usually enough to say whether Nest is the right place to start.