Employee Directory: Why Every Canadian Team Over 15 People Needs One

At ten people, everyone knows everyone. You know what each person does because you've probably worked with all of them directly. Need to ask about the sales pipeline? You know it's Jamie. Have a question about the product roadmap? That's Priya. The organizational knowledge lives in people's heads, and that works because the number of connections is small enough to manage.

Then you hire your fifteenth person. Then your twentieth. And somewhere in that range, a shift happens that's so gradual you almost miss it. Someone new joins and asks, "Who handles vendor contracts?" and three people give three different answers. A customer sends an email to the wrong person, and it sits in an inbox for four days because nobody realized it needed to be forwarded. A manager introduces two people who have actually been on the same team for six weeks.

This is the "who does what?" problem, and it hits every growing team at roughly the same inflection point. In our experience working with growing Canadian teams, this friction tends to surface around 15–20 people. It is not a crisis — it is a slow accumulation of small inefficiencies that compound as the team grows.

The real cost of not knowing who does what

The "who does what?" problem manifests in a few predictable ways, none of which show up in any dashboard or report:

Message routing delays. Someone has a question, doesn't know who to ask, so they post it in a general Slack channel. Three people respond with partial answers. Two more people redirect them to someone else. The actual subject matter expert doesn't see the message until the next day because they don't follow that channel. Total elapsed time to get a simple answer: 18 hours. In an office, it would have taken 30 seconds.

Duplicate work. Without clear visibility into who owns what, teams occasionally solve the same problem independently. Two engineers build similar internal tools. Two salespeople reach out to the same prospect. These collisions are invisible until someone notices, and by then, the duplicate effort is already spent.

Onboarding friction. New hires suffer the most. They don't have the institutional knowledge that long-tenured employees have built up. Every question about "who should I talk to about X?" requires them to interrupt someone, which they're reluctant to do in their first weeks. A directory gives new hires a map of the organization from day one. If you're building out your onboarding process, see our Canadian onboarding checklist.

Manager confusion. As teams restructure and people move between groups, reporting lines get fuzzy. "Who reports to whom?" sounds like a question with an obvious answer, but in a fast-growing company with dotted-line relationships, project-based teams, and recent reorganizations, the answer is often unclear — even to the managers themselves.

What a good employee directory includes

A spreadsheet with names and email addresses is a contact list, not a directory. A real employee directory is a structured, searchable map of your organization that answers questions people actually ask.

The essentials

Every directory should include these fields for each employee:

• Full name and preferred name. Not everyone goes by their legal name. The directory should reflect what people actually call each other.
• Photo. Faces matter, especially in remote teams. Being able to put a face to a name before a meeting reduces the social friction of cross-team interactions.
• Job title and department. This is the most-searched information in any directory. People want to know what someone does and which team they're on.
• Manager / reporting chain. Who does this person report to? This is critical for understanding decision-making authority and escalation paths.
• Location and timezone. For remote and distributed teams, knowing someone's province and timezone is as important as knowing their role. It determines when you can realistically expect a response — and the province of work also has compliance implications (statutory holidays, provincial ESA rules).
• Contact information. Work email, Slack handle, and any other channels the team uses. The goal is to make it easy to reach anyone through the right channel.
• Start date. Useful for context. Knowing that someone has been at the company for three years versus three months changes how you interact with them.

Nice-to-haves that add real value

Beyond the essentials, some directory fields improve team cohesion and cross-functional collaboration:

• Skills and expertise. Who on the team speaks French? Who has experience with CRA payroll integrations? Who has a background in compliance? This turns the directory from a contact lookup into a knowledge-finding tool.
• Working hours. Particularly useful for distributed teams with flexible schedules. If someone works 7 AM to 3 PM Eastern while the rest of the team works 9 to 5, the directory should make that visible.
• Pronunciation guide. A small field that makes a big difference. Nobody wants to mispronounce a colleague's name in a meeting. A simple phonetic guide or audio clip eliminates the awkwardness.
• Short bio or "about me." A sentence or two about the person's background or interests. This gives people a starting point for conversation, which matters more than you'd think when building relationships across a distributed team.

Privacy: PIPEDA, provincial laws, and what should be visible to whom

This is where many Canadian teams get the directory wrong. The instinct is either full transparency — everyone sees everything — or full restriction — only HR has access. Neither extreme works, and full transparency creates real PIPEDA exposure.

A well-designed directory uses role-based visibility to show the right information to the right people:

Visible to everyone: Name, photo, title, department, manager, work email, Slack handle, general location (city/province), timezone, start date, bio, skills, working hours.

Visible to managers only: Direct reports' emergency contact information, performance notes, disciplinary records.

Visible to HR and payroll only: Compensation, compensation history, home address, personal phone number, Social Insurance Number (which is treated as sensitive personal information under PIPEDA and federal SIN guidance), banking details, benefits elections, T4 information.

The principle is simple: people should see what they need to do their jobs, and nothing more. An engineer doesn't need to see a colleague's salary. A manager doesn't need to see an employee's SIN. HR needs access to everything for administrative purposes, but that access should be auditable.

The safest approach is to default to minimal visibility and expand based on a documented justification.

The self-service advantage

Here's a reality that every Canadian HR team knows: employee data goes stale fast. People move. They change their phone numbers. They get promoted and their title doesn't update for three months. They get married and their emergency contact information is wrong for six months because nobody told HR.

In a centralized HR-managed directory, every change requires someone in HR to process it. That means every change competes for HR's time with a hundred other tasks, and updates that aren't urgent get deprioritized. The result is a directory that's accurate when first created and increasingly wrong over time.

Self-service solves this. When employees can update their own profiles — photo, preferred name, bio, working hours, contact information — the data stays current because the person with the most motivation to keep it accurate is the one doing the updating.

Self-service also reduces the back-and-forth that slows down simple changes. Instead of emailing HR, waiting for confirmation, and then checking a week later to see if the update went through, the employee makes the change themselves and it's immediately visible. Sensitive fields — like compensation, SIN, or employment status — remain locked to HR, but everything an employee should reasonably control about their own profile is editable.

WalnutsHR's employee management features include self-service profiles with configurable privacy controls, so employees stay in control of their information while HR maintains oversight of sensitive data.

The directory as a living org chart

One of the most valuable side effects of a well-maintained employee directory is that it becomes your org chart — not a static diagram someone made in PowerPoint six months ago, but a live representation of how your organization is actually structured right now.

When reporting relationships are part of the directory, you can generate an org chart automatically. When someone gets promoted, changes teams, or gets a new manager, the org chart updates immediately. No one has to remember to update a separate document.

This matters for several practical reasons:

Decision routing. When a decision needs approval, people can follow the reporting chain upward without guessing. When someone needs to escalate an issue, they can see exactly who to go to.

Cross-team collaboration. When you need to work with another department, the org chart tells you who leads that team, who the key people are, and how the team is structured. This prevents the common problem of reaching out to the wrong person because you assumed a title implied a role it doesn't.

Board and investor reporting. When your board asks for a current org chart, you export it from the directory in seconds instead of spending an afternoon rebuilding it from memory.

When to invest in a directory

If you're under ten people, a Notion page or shared doc with everyone's info probably works fine. But the threshold is lower than you think, and the transition is easier than you expect.

Here are the signs that it's time:

• A new hire has asked "who should I talk to about X?" more than twice in their first week
• Someone sent an important email or message to the wrong person because they didn't know who owned a particular area
• Your org chart hasn't been updated in more than three months
• You have employees in more than one province or timezone
• A manager couldn't immediately answer "who reports to you?" with a complete list
• HR has spent time this month manually updating employee information that the employees could have updated themselves

If any of these sound familiar, you've crossed the threshold. The good news is that setting up a directory in a modern HR platform takes hours, not weeks. WalnutsHR's pricing starts free for small teams, so the barrier to entry is essentially zero — you can have a functioning directory before the end of the day.

Getting started

The process is straightforward. Gather your current employee data — most of it already exists in a spreadsheet, your payroll system, or your email directory. Import it into a centralized platform. Set up the privacy controls aligned with PIPEDA principles. Invite employees to claim their profiles and fill in the optional fields. And then watch as a tool that took an afternoon to set up saves your team hours every week.

The companies that scale smoothly share a common trait: they build organizational infrastructure slightly ahead of when they need it. An employee directory is one of those foundational investments. It's simple, it's low-cost, and once it's in place, you'll wonder how you operated without it.

Build your team's directory today. Check our pricing or get started free with WalnutsHR.