DirectoryThe person’s record
A file that remembers. Every role somebody has held, under the team as it was named then; the fields your organization actually needs; and the documents that belong to them.
Every title, in order. With the team as it was named then.
A position carries a title, a team and a reason it changed, with only the current one left open-ended.
- Every title somebody has held, in order
- The team named as it was named at the time
- Hired, promoted, transferred, retitled: told apart
- A note on the ones that need explaining
- Only one has no end date: the job they hold today
Including the last day. Recorded properly, once.
The two can never disagree, because closing the role and recording the departure happen at the same moment.
- Six reasons, so “left” isn’t the only thing on file
- A last day, and a note if there is one
- Who recorded it, because somebody did
- Their current role is closed off on that same last day
- Nobody leaves the organization still reading “Present”
The fields you actually need. Grouped the way your record is.
A base set ships with the product; everything your organization genuinely tracks you define yourself, in your own sections. Values remember whether they came from onboarding or from a manager.
- A base set ships; the rest is yours to define
- Grouped into the sections your record actually has
- Filled in once at onboarding, then kept
- A manager’s edit stays put: onboarding never writes over it
- Every value knows where it came from
What the record doesn’t do. Named, so you find out here.
No leave of absence
Time off covers vacation, sick, personal and unpaid. A longer leave has no flow of its own today. The status is defined but not yet wired up, which is not the same as working.
Documents are not signed here
A document on somebody’s file is stored, titled, and shown to them or not. Signing is a different thing with different obligations, and it lives in Offers.
No payroll
Cadre holds the record, the history and the time off. What somebody is paid, and paying them, stays wherever it lives today.
One person, one file
Their history, their fields, their documents and their time off, with each document shown to them or kept internal, one flag at a time.
Where the record starts. Most of it arrives on day one.
Nothing moves. Each position stores the team as it was at the time, so a role held in “Production” in 2023 still reads Production after the team becomes “Operations”. Reorganizing the present should not rewrite the past.
Yes. A base set ships with the product, and you add whatever your organization actually needs on top: grouped into your own sections and ordered how you like. One limit worth knowing: fields hold text in this version. You can set up a field meant to hold a file, but uploading to it does not work yet.
The manager’s edit, permanently. Onboarding answers fill the standing fields once; after that a manager’s edit stays put, and onboarding never writes over it. Every value also records which of the two it came from.
The ones you mark visible to them. Each document carries that flag individually, so a signed contract and an internal note can sit on the same file without the same audience.
You cannot, not as its own thing. That is a gap rather than a design choice, and we would rather name it here than let you find it on the day somebody needs it.