Employee Directory: What It Is and How to Build One for Your Small Business
What is an employee directory and how do you build one? Fields to include, tools to use, and when to upgrade from spreadsheets for teams of 5-50.
Employee Directory
How to build one that actually gets used
At 5 employees, everyone knows everyone. You know who to email, who to Slack, and who handles what. The directory is in your head.
At 12 employees, that breaks. A new hire asks you who handles accounts payable. You answer from memory. Two days later, a different new hire asks you the same question. A week after that, someone needs the phone number for a coworker they have only emailed. You dig through your contacts, find it, and forward it. That is your job now: human phone book.
I built a Google Sheet with everyone's name, title, email, and phone number. It helped for about three months. Then someone changed their number and did not tell me. Someone else moved to a different department and the sheet still showed the old one. A new hire looked at it on their first day and found two people who no longer worked at the company. The spreadsheet was worse than nothing because it was wrong and people trusted it.
That is when I realized an employee directory is not a spreadsheet. It is a system: something that stays current, that employees can update themselves, and that connects to the rest of your HR data so you are not maintaining the same information in three places. That system is now a core feature of FirstHR: a searchable directory with profiles, an org chart, and self-service updates built into the same platform that handles onboarding and documents.
What Is an Employee Directory?
An employee directory is a centralized, searchable list of everyone who works at your company. It contains contact information (email, phone, location), organizational information (title, department, manager), and optionally personal details (photo, bio, preferred name). It is the internal equivalent of a phone book, except it should also show where each person fits in the organization.
The distinction between a directory and a database matters. A directory is employee-facing: anyone in the company can search it to find a coworker's contact information or understand the org structure. A database is HR-facing: it stores sensitive information (salary, SSN, performance records) that only HR and management should access. Good HR software provides both: a public-facing directory for the team and a restricted database for administration.
What to Include in an Employee Directory
The right fields depend on your company size and whether the directory is a standalone tool or part of your HR system. At minimum, every directory needs name, title, department, and contact information. Beyond that, the fields you add should serve a specific purpose: organizational fields help people understand the structure, communication fields help remote teams coordinate, and compliance fields help HR track legal requirements.
Two rules for deciding what to include: if someone might need to look up the information to do their job, include it. If the information is sensitive and does not help daily work (salary, SSN, disciplinary records), restrict it to HR access only.
Who Belongs in the Directory and Who Does Not
"Everyone who works here" sounds like a simple rule until you try to apply it. A 14-person company usually has more than 14 people who show up to meetings: a fractional bookkeeper, a contract designer, a summer intern, someone on parental leave, and a former employee whose Google account nobody has disabled. Each of these gets a different answer.
| Person | In the directory? | Why |
|---|---|---|
| W-2 employee, full-time or part-time | Yes | The default case. Part-time employees belong in the directory on the same terms as everyone else. |
| Employee on FMLA, parental, or medical leave | Yes, with a status flag | They are still employed and still count toward headcount thresholds. Do not remove them. A neutral 'On leave, returning [month]' status stops coworkers from asking why nobody is answering, without disclosing the reason for the leave. |
| 1099 independent contractor | Yes, but visibly labeled as a contractor | People need to reach them. But do not list them with a manager, a department seat, and a hire date exactly as if they were staff. Directory presentation is not what decides worker classification, but it is one more fact showing integration into the business, and it is trivially easy to get right. |
| Staffing agency or temp worker | Yes, labeled with the agency | Joint-employment questions turn on who controls the work, so make the employer of record visible rather than implied. |
| Paid intern | Yes | A paid intern is generally an employee and counts toward headcount like anyone else. |
| Unpaid intern | Case by case | Whether an unpaid intern is an employee at all turns on the DOL primary beneficiary test. If you are treating them as a non-employee, do not list them as staff. |
| Board member or advisor | Usually no | They are not employees and do not need to appear in an internal contact list. Keep them in a separate list. |
| Departed employee | No, removed on the last day | Directory removal belongs on the offboarding checklist next to account deactivation. Their record stays in your HR files; their entry leaves the directory. |
| Accepted candidate who has not started | Yes, from preboarding | Give them a profile a week before Day 1 so they can browse the team, and hide them from company-wide search until their start date if your tool supports it. |
The one field that resolves most of this is employment type: W-2 full-time, W-2 part-time, contractor, temp, intern. Once it exists, the directory can show everyone while your headcount reports count only the right people, and nobody has to remember which of the 19 names on the list are actually on payroll.
The Work Location Field Does More Than You Think
In a single-office company, "location" is decoration: it tells people which floor to walk to. The moment one employee moves to another state, it becomes the field that determines which laws apply to that person, and it stops being safe to leave blank or fill in with "Remote."
An employee's work state (where they physically perform the work, not where your company is incorporated and usually not where the manager sits) generally drives:
| What it drives | Why the work state matters |
|---|---|
| State income tax withholding and unemployment insurance | You typically have to register with the tax and unemployment agencies in the state where the work is performed, often after the first employee there. Reciprocity agreements and a handful of convenience-of-the-employer rules complicate this, so confirm with your payroll provider rather than assuming. |
| Paid sick leave and paid family leave | These are state and sometimes city programs with their own accrual rules, and several run as payroll-deducted insurance programs. An employee in a city with a local ordinance may be covered even when your headquarters state has nothing. |
| Minimum wage and overtime rules | Federal FLSA sets the floor. State and city minimums are often higher, and a few states use daily overtime or different exempt salary thresholds than the federal one. |
| Final paycheck timing at termination | Deadlines vary from immediately on the last day to the next regular payday depending on the state and on whether the employee quit or was fired. |
| Required labor law postings | Remote employees still have to receive the state and federal notices, usually by email or an intranet page rather than a break room poster. |
| Harassment prevention training mandates | Several states require it, at different headcounts and intervals. California, for example, requires it for employers with five or more employees. |
Practically, this means the directory should carry two distinct fields that founders often collapse into one: work location (the state and city where the work happens, visible to the team as a time zone and office) and home address (needed for W-2 delivery and benefits, restricted to HR). An employee can live in one state and work in another, and if you store only one address you will eventually withhold in the wrong place.
Add a policy alongside the field: employees must notify HR before a permanent move to a different state. A relocation an employee mentions casually in Slack three months after the fact is a payroll registration you were supposed to complete before their first paycheck from that state.
Why an Employee Directory Matters
| Problem | Without a Directory | With a Directory |
|---|---|---|
| New hire needs to contact the right person | Asks the founder, who may be busy; waits hours or days for a response | Searches by name, department, or role; finds contact info in seconds |
| Employee changes their phone number | Tells the founder, who updates a spreadsheet if they remember | Employee updates their own profile; change is instant and permanent |
| Someone needs to know the reporting structure | Asks around until they piece it together | Views the org chart, which auto-generates from directory data |
| New hire on Day 1 needs to learn the team | Gets a verbal tour and forgets most names by Day 2 | Browses the directory with photos, titles, and departments before Day 1 |
| Remote employee needs to find a coworker in a different time zone | Guesses based on Slack activity | Checks the directory for location, time zone, and working hours |
Research from the Work Institute shows that 20% of turnover happens within the first 45 days. Information friction during onboarding (not knowing who to ask, not finding basic contact details, not understanding the team structure) contributes directly to that early departure. A directory eliminates this friction from Day 1.
5 Ways to Build an Employee Directory
| Approach | Best For | Cost | Limitations |
|---|---|---|---|
| Google Sheets or Excel | 1-8 employees | Free | No search, no photos, no org chart, no self-service, goes stale quickly |
| Notion or Airtable | 5-15 employees (tech-savvy team) | $0-$10/user/month | Flexible but requires setup; no HRIS integration, no e-signatures, no onboarding workflows |
| Dedicated directory tool (Pingboard, OneDirectory) | 20-200 employees with IT support | $3-$8/user/month | Good directory features but separate from HR data; creates duplicate records |
| HR software with built-in directory | 5-50 employees without HR/IT staff | $98-$200/month flat | Directory, org chart, self-service, onboarding, and documents in one system |
| SharePoint or Microsoft 365 add-on | Companies already on M365 with IT admin | $0-$5/user/month on top of M365 | Powerful but complex; requires IT to configure and maintain |
For small businesses with 5 to 50 employees, the HR software approach wins on total cost and maintenance. A dedicated directory tool costs $3 to $8 per employee per month and only gives you a directory. HR software at a flat fee gives you the directory plus onboarding, document management, e-signatures, and an org chart. You maintain one system instead of two or three, and the data stays in sync because it is all in the same place.
How to Create an Employee Directory
The entire process takes 2 to 4 hours for a team of 20, including data collection time. If you are using HR software, most of the data you need (names, titles, departments, hire dates) already exists from onboarding. The directory is built from data you have already collected rather than requiring a separate data-entry project.
When to Upgrade From a Spreadsheet
Spreadsheet directories work at small scale and fail predictably as you grow. Knowing the failure signals helps you upgrade before the spreadsheet causes real problems.
| Signal | What It Means | When It Typically Happens |
|---|---|---|
| Someone's info is wrong and nobody noticed | The spreadsheet is not being maintained consistently | 8-12 employees |
| A new hire cannot find basic contact information on Day 1 | The directory is not accessible or not updated with new hires | 10-15 employees |
| You are maintaining employee data in multiple places | Spreadsheet, payroll, benefits, documents all have separate records | 10-15 employees |
| You cannot remember the reporting structure without checking | The team is too large for informal org knowledge | 15-20 employees |
| Someone asks 'do we have a current employee list?' and you are not sure | The spreadsheet is outdated enough that you do not trust it | Any size, but typically 12+ |
The upgrade path is straightforward: move from the spreadsheet to HR software that includes a directory as a built-in feature. This eliminates the maintenance problem because the directory updates happen as part of your existing HR workflows (onboarding, role changes, departures) rather than as a separate task.
Migrating Off the Spreadsheet Without Importing the Mess
The failure mode of a directory migration is importing the spreadsheet as-is. You end up with the same wrong phone numbers and the same two ghost employees, except now they look official because they live in a real system. A clean cutover for a team of 20 takes about half a day.
One decision to make deliberately during the cutover: what happens to records for people who have already left. They should not appear in the directory, but you still have retention obligations for their underlying employment records. Import them as inactive rather than deleting them, so the historical data survives while the directory shows only current staff.
Privacy and Access Controls
Not every field in the directory should be visible to every employee. Sensitive information needs access controls that match the principle of least privilege: people see what they need to do their job, and nothing more.
| Visibility Level | What It Includes | Who Can See It |
|---|---|---|
| Public (all employees) | Name, title, department, work email, work phone, manager, photo, location, hire date | Everyone in the company |
| Manager-only | Direct reports list, team performance notes, compensation band (if transparent) | The employee's direct manager and above |
| HR-only | Personal email, home address, SSN, salary, emergency contacts, I-9 status, benefits elections, disciplinary records | Founder, HR, and authorized payroll staff |
| Employee-controlled | Personal phone, birthday, pronouns, bio, skills/certifications | Employee decides whether to share publicly |
The employee-controlled tier matters more than most founders realize. Giving employees control over their personal information (whether to share their birthday, their pronouns, or a personal bio) signals respect for their autonomy. It also produces a better directory because people voluntarily share useful information when they feel in control of what is visible.
For US-specific compliance considerations around employee data, SHRM recommends keeping I-9 records separate from general personnel files. This applies to your directory as well: I-9 and immigration data should never appear in the employee-facing directory, only in restricted HR records.
Can an employee refuse to appear in the directory?
This comes up more often than founders expect, and the answer splits along the same line as the visibility tiers. An employee's name, title, department, and work email are business records; the company assigned them and needs them to be usable internally, so appearing in an internal contact list is not opt-out territory. A photo, a personal cell number, a birthday, a bio, and pronouns are the employee's own information, and asking for them is a request, not an instruction. Treat a refusal on those fields as a complete answer and do not follow up.
There is one situation where the general rule bends. An employee with a documented safety concern, most often a domestic violence or stalking situation, may need their location, photo, and any contact detail suppressed company-wide. Several states have address confidentiality programs for exactly this. Handle it quietly with the smallest number of people who need to know, and do not create a directory entry with a visible gap that invites questions.
Employee data privacy statutes are worth a sentence of realism. California's CCPA/CPRA extended consumer-style rights to employee and applicant data, but the law only reaches businesses that meet its coverage thresholds, which are set by revenue and by the volume of personal information handled; most companies in the 5-to-50 range fall under them. That does not make the question moot, because a handful of states have their own rules on things like biometric data and personnel file access, and because employees increasingly ask what you store regardless of what the law requires. Being able to show someone their own profile in thirty seconds is the cheapest possible answer.
Exports are the real leak
Most directory data escapes through the export button, not a breach. A departing salesperson who downloads the directory leaves with every colleague's work contact details, and if you allowed personal phone numbers into the public tier, those go too. Restrict full-directory export to administrators, keep personal contact details out of the tier that everyone can see, and if your tool logs exports, glance at that log during offboarding.
What Your Headcount Triggers
The most underrated use of an accurate directory is that it tells you how many employees you have, and in US employment law the answer to that question decides which statutes apply to you. Growing from 14 to 15 people, or from 19 to 20, changes your legal obligations on a specific date, and the change is not announced by anyone. If your headcount lives in a stale spreadsheet, you find out you crossed a threshold when a claim arrives.
| Threshold | What starts applying | How the count works |
|---|---|---|
| 1+ employees | FLSA minimum wage and overtime, I-9 verification, workers' compensation in most states, and many state anti-discrimination and paid sick leave laws | There is no small-employer exemption from the core federal wage and hour rules. State discrimination laws frequently start at 1 to 5 employees, well below the federal thresholds below. |
| 15+ employees | Title VII (race, color, religion, sex, national origin), the ADA, and GINA | 15 or more employees for each working day in each of 20 or more calendar weeks in the current or preceding calendar year. Part-time employees on the payroll count. |
| 20+ employees | The ADEA (age 40 and over) and federal COBRA continuation coverage | The ADEA uses the same 20-calendar-week test as Title VII. COBRA asks whether you had 20 or more employees on more than 50% of typical business days in the previous calendar year, counting part-timers as fractions. Most states have a mini-COBRA law covering smaller employers. |
| 50+ full-time and full-time-equivalent employees | The ACA employer mandate: offer compliant coverage to full-time employees or face a penalty, plus 1094-C and 1095-C filing | Averaged over the prior calendar year. Full-time means 30 hours a week or 130 hours a month; part-time hours are converted to equivalents. This is the only threshold on this list that uses equivalents rather than a headcount. |
| 50+ employees | FMLA: up to 12 weeks of job-protected unpaid leave | 50 or more employees for each working day during each of 20 or more calendar workweeks in the current or preceding calendar year. Separately, an individual employee is only eligible if they have 12 months of service, 1,250 hours worked in the prior 12 months, and work at a site with 50 employees within 75 miles. Several states run their own paid or unpaid leave programs at much lower employer sizes. |
| 100+ employees | EEO-1 Component 1 reporting to the EEOC, and the federal WARN Act | EEO-1 also applies to federal contractors with 50 or more employees and a contract of $50,000 or more. WARN excludes part-time employees from the count in a specific way, and several states have their own mini-WARN acts with lower thresholds, so check your state before relying on the federal number. |
None of this requires HR software to get right, but it does require a list you trust. The practical move is to run a headcount report from the directory at the end of each quarter, note which of these numbers you are within two employees of, and check the ones you have crossed against your state's equivalents. Contractors and unpaid interns are excluded from these counts, which is the other reason the employment-type field earns its keep.
Employee Directory Best Practices
| Practice | Why It Matters |
|---|---|
| Make it self-service from Day 1 | If employees can update their own contact info, photo, and preferences, the data stays current without the founder maintaining it |
| Include photos for every entry | Photos make the directory useful for new hires who are matching names to faces, and for remote teams who rarely meet in person |
| Link it to onboarding | New hires get directory access during preboarding and are required to complete their profile before Day 1 |
| Keep it to one source of truth | If your directory is in HR software, do not also maintain a spreadsheet. Duplicate systems always diverge. |
| Add the directory to your onboarding checklist | Step 1 of Week 1: browse the directory, learn who does what, update your profile |
| Review quarterly for accuracy | Even with self-service, do a 15-minute quarterly check: are departed employees removed? Are titles current? Are new hires added? |
Common Employee Directory Mistakes
| Mistake | Why It Happens | The Fix |
|---|---|---|
| Using a spreadsheet past 10 employees | It worked before, seems unnecessary to change | Switch to HR software with a built-in directory. The maintenance burden of a spreadsheet at 15+ employees is not worth the savings. |
| Not including photos | Feels optional or privacy-invasive | Photos make the directory usable. Without them, new hires cannot match names to faces. Make photo upload part of onboarding. |
| Maintaining duplicate records | Directory in one system, HR data in another, payroll in a third | Use one system where the directory is built from the same data used for onboarding and HR administration. |
| No self-service for employees | Founder controls all data updates | Let employees update their own contact info. Founder-maintained directories always go stale. |
| Not removing departed employees | Nobody owns the process | Build directory removal into your offboarding checklist so it happens automatically when someone leaves. |
| Sharing sensitive data in the directory | Unclear access controls | Define visibility levels before launch: public, manager-only, HR-only, employee-controlled. |
| Not connecting it to onboarding | Directory is treated as an admin tool, not an onboarding tool | Add directory browsing to Day 1 orientation. It is one of the fastest ways to help new hires learn the team. |
The root cause behind most of these mistakes is treating the employee directory as a standalone admin task rather than as part of your HR infrastructure. When the directory lives inside your HR system and updates happen through your existing employee lifecycle workflows (onboarding adds people, offboarding removes people, role changes update titles), the directory maintains itself.
Frequently Asked Questions
What is an employee directory?
An employee directory is a searchable list of everyone in a company with their contact information, job title, department, reporting relationship, and other relevant details. It serves as the internal phone book for the organization. At small businesses, it can be as simple as a shared spreadsheet or as sophisticated as a searchable database within HR software that includes photos, org chart visualization, and self-service profile management.
What should an employee directory include?
At minimum, an employee directory should include: full name, job title, department, work email, and phone number. Beyond the basics, useful fields include: manager name (for org chart clarity), hire date, office location or time zone (for remote teams), preferred contact method, profile photo, and emergency contact. Administrative fields like FLSA classification, employment status, and I-9 completion are important for HR but should be restricted to management access.
How do you create an employee directory?
Start by choosing your tool (spreadsheet for under 10 employees, HR software for 10 or more), define the fields you need, collect information from each employee, organize by department, set access permissions, and share it with the team. The entire process takes 2-4 hours for a team of 20. The most important step is making it self-service: employees should be able to update their own contact information, photo, and preferences without asking the founder.
When should a small business switch from a spreadsheet directory to software?
Switch when you reach 10-15 employees or when any of these pain points appear: someone's information is outdated and nobody noticed, you cannot remember who reports to whom without checking, new hires take more than a day to find basic contact information, or you are maintaining the same employee data in multiple places. At that point, a spreadsheet creates more problems than it solves, and HR software with a built-in directory eliminates the maintenance burden.
Is an employee directory the same as an org chart?
No. An employee directory is a searchable list of people with their contact information. An org chart is a visual representation of reporting relationships and organizational structure. They complement each other: the directory tells you how to reach someone, the org chart tells you where they sit in the organization. Most HR software combines both into one system where the directory data automatically generates the org chart based on manager-report relationships.
What employee information should be private vs public?
Public to all employees: name, title, department, work email, work phone, manager, profile photo, and office location. Restricted to HR and management: personal email, home address, salary, SSN, emergency contacts, I-9 status, disciplinary records, and medical information. Employee-controlled: personal phone number, birthday, pronouns, and bio. The principle is that work-related contact information is visible to everyone while personal and sensitive information is restricted.
How do you keep an employee directory up to date?
The most effective approach is self-service: employees update their own information through an employee portal. This eliminates the bottleneck of one person maintaining everyone's data. For changes that require HR action (title changes, department transfers, new hires, departures), build directory updates into your existing HR processes so the directory is updated as part of the workflow, not as a separate task someone remembers to do later.
Should independent contractors be listed in the employee directory?
Yes, list them so people can reach them, but label them clearly as contractors rather than presenting them exactly like staff with a manager, a department seat, and a hire date. Directory presentation does not decide worker classification on its own, but it is one more fact that shows integration into the business, and it is easy to get right. The practical fix is an employment-type field (W-2 full-time, W-2 part-time, contractor, temp, intern) so the directory can show everyone while your headcount reports count only employees.
Does my employee count change which employment laws apply?
Yes, and this is why an accurate headcount matters. Title VII, the ADA, and GINA generally apply at 15 or more employees; the ADEA and federal COBRA at 20; the ACA employer mandate at 50 full-time and full-time-equivalent employees; FMLA at 50; EEO-1 reporting and the federal WARN Act at 100. Most of these tests look backward across 20 calendar weeks or the previous calendar year rather than at today's number, and part-time employees on the payroll count for all of them except the ACA calculation, which converts part-time hours into equivalents. State laws often start much lower, sometimes at one employee, so check your state alongside the federal thresholds.
Do small businesses need an employee directory?
Any business with more than 8-10 employees benefits from a directory. Below that, everyone knows everyone. Above that, new hires struggle to learn who does what, people waste time looking up contact information, and the founder fields basic questions that a directory would answer. The directory does not need to be sophisticated. Even a well-organized spreadsheet shared with the team is better than nothing.