Employee directory: the internal list people actually use

An employee directory is the internal list of who works here, what they do, and how to reach them. It sounds too simple to get wrong, and almost every company gets it wrong the same way: the list is created enthusiastically, nobody owns it, and within a year it contains three people who left and a phone number that rings at a desk nobody sits at.

The directory that survives is boringly small. Enough fields to answer the question somebody actually had — who does this, who do I ask, what team is this person on — and no more, because every extra field is another thing that will be wrong.

What belongs in an employee directory

• Name, and the name they go by if it differs. The second one is what people search for.
• Role, in words a colleague would use, not the title on the contract.
• Team and manager. These two turn a list into a map of the organisation, which is the main reason anyone opens it.
• Work contact details — email, and a phone number only where a person genuinely takes calls on it.
• Location and working hours where the team spans time zones. Nothing wastes more time than a message sent to somebody who logged off four hours ago.
• Start date, which quietly answers who to ask about how things used to work.

What does not belong

Home addresses, personal phone numbers, dates of birth, emergency contacts, photographs where nobody consented, salary bands, and anything about health or family circumstances. These belong in a personnel record with restricted access, not in a list everyone can browse. Under privacy regimes such as the GDPR, an internal directory is still processing of personal data: keep it to what the job requires, tell people what is published, and give them a way to correct it. What exactly is lawful depends on your jurisdiction and is worth checking properly rather than assuming.

Keeping it true

1. Give it one owner. A directory maintained by everyone is maintained by nobody.
2. Tie updates to the two events that change it: joining and leaving. If your onboarding checklist and your offboarding process each include a directory line, drift mostly stops.
3. Let people edit their own row for the soft fields — preferred name, pronunciation, working hours — while role, team and manager stay with the owner.
4. Review quarterly against payroll or the HR record. Ten minutes, and it catches the leavers nobody remembered.
5. Publish it in exactly one place and link everything else to it. Two directories means one of them is lying and no way to tell which.

The field that earns its place more than any other is manager. Contact details answer how to reach one person; the reporting line answers who to ask when you do not know who to ask, which is the question new joiners actually have and the one a flat list of names cannot answer.

Where to keep it

Ettex Contacts holds the directory as structured records you can filter by team, role or location, and the same store carries external contacts — the difference is a field, not a separate system, which is covered in contact list template. New joiners and leavers are the two moments that matter, and tying the update to employee onboarding checklist keeps it honest.

What it is not: Ettex Contacts is not an HR system of record. There is no payroll, no personnel file with restricted access, no org-chart rendering and no automatic provisioning of accounts from a directory entry. Sensitive personnel data should live in a system built to restrict it, and the directory should hold the work-facing subset only.