New Starters Cannot Find Policies and Procedures: The Productivity Cost

Week one, and nobody can find the leave form

A new bookkeeper starts on a Monday at a Cape Town firm. By ten o'clock she has her laptop and her login. By eleven she needs the expense policy, the supplier onboarding checklist and the template used for month-end journals. She asks the colleague at the next desk. He thinks the expense policy is in the shared drive, perhaps under "HR", perhaps under "Old". The checklist, he says, is in an email from last year. The template he will forward, once he finds it.

By Friday she has asked eleven questions, interrupted four people, and still uses a journal template that was replaced in March. Nobody has done anything wrong. The business simply has no obvious answer to a basic question: where does this kind of information live, and how does a newcomer find it?

This article is about that specific gap, where new employees cannot tell where policies, procedures and working information are kept, and what it costs in productivity. It is related to the same internal questions being asked repeatedly, but narrower. The knowledge may exist and may even be well written. The problem is that it cannot be found.

Why newcomers feel it most

Long-serving staff navigate by memory. They know that the pricing sheet is in a folder named after a colleague who left, that the safety procedure sits in a Teams channel nobody uses any more, and that the approved version of a contract template is the one with "FINAL_v3" in the name. This is knowledge about the filing system, not about the work, and none of it is written down.

A new employee has no such map. Every search is a guess, and every wrong guess costs minutes. Worse, a newcomer cannot judge whether the document they found is current, so they either trust something outdated or interrupt a colleague to check. Both are expensive.

Where the time and money go

• Slow ramp-up. The period between starting and working independently stretches when a large share of each day goes to hunting for the basics. The salary has been running since day one, and the output has not.
• Interruptions to experienced staff. Each question breaks a colleague's concentration. The cost is the interrupted task plus the time to regain focus, and the newcomer feels guilty for asking, so asks less.
• Errors from outdated versions. Using an old template, rate sheet or procedure produces rework, customer corrections or compliance problems.
• Inconsistent practice. When each person finds a different version, the business ends up with several ways of doing the same thing.
• Early resignations. A new employee who feels lost and unwelcome may leave before the business has recovered its recruitment cost.
• Managers become the search engine. Team leaders spend onboarding week answering location questions that could have been answered by a map.

You can estimate the cost without precise measurement. Ask the last three recruits how many times in their first fortnight they could not find something and had to ask. Multiply by a modest five minutes for the newcomer and the same for the colleague asked, and then by the hourly cost of both. The result is usually large enough to justify an afternoon of tidying.

Why the problem persists

1. Information grows by accident. Files are saved where the author happened to be working. Nobody decides the structure, so the structure is whatever accumulated.
2. Several homes for the same thing. Email, a shared drive, a chat tool, a paper file and someone's desktop each hold part of the truth. This pattern is described in when business knowledge lives in inbox history.
3. No owner for each document. Without a named owner, nobody retires the old version or checks that the new one is findable.
4. Onboarding relies on goodwill. The first-week plan is a conversation with a manager, which varies with how busy the manager is. See onboarding that depends on a manager's memory.
5. Search is poor. Inconsistent file names and permissions that hide documents from people who need them make even good search tools unhelpful.

What a findable home looks like

The aim is not to buy a new system. It is to make one place the first place to look. Most small and mid-sized businesses already own the tools. Microsoft's documentation introducing SharePoint describes sites for sharing information with a team or across an organisation, with navigation, search and permissions in one place. Teams documents the idea of channels organised around a topic, with files attached to each. Google Workspace and other suites offer equivalents. The tool matters less than three design choices.

1. A single front page

Create one start page titled something like "How we work here". It should have no more than a dozen links, grouped by the questions a newcomer asks: people and leave, money and expenses, customers and sales, systems and access, safety and compliance. Pin it in the chat tool and put the link in the welcome email.

2. A named owner and review date for each document

Every policy or procedure on that page carries an owner's name and the date it was last confirmed as current. When a document is replaced, the old version is archived and removed from the visible list. This single habit removes most outdated-version errors.

3. A first-week path

List, for each role, the ten documents the new person needs in the first week and the order to read them in. This turns a vague promise of support into a concrete plan, and it exposes any document that does not yet exist.

The compliance reason to know where things are

Some of what new staff must find is a legal matter. The Protection of Personal Information Act places duties on responsible parties for how personal information is processed and secured. A new employee who cannot find the data-handling procedure, or who does not know who the information officer is, is more likely to guess. Making these documents easy to locate, and recording that each person has read them, supports good practice. The mechanics of that record are covered in why policy acknowledgements need a reliable system record.

Practical next actions

1. Ask your last two or three recruits to list every item they struggled to find in their first month, and use that list as the starting contents of your start page.
2. Choose one place as the home for policies and procedures, create a single front page with no more than twelve links, and add its address to your welcome email.
3. Give every document on the page a named owner and a last-confirmed date, and archive any superseded version so it no longer appears in search.
4. Write a first-week reading path for each role, ten documents at most, and check that each of them exists and is current.
5. After each new hire's first month, ask what they still could not find, fix it, and repeat the exercise with the next recruit.

A business does not need a large knowledge programme to make new staff productive sooner. It needs one obvious place to look, a person responsible for keeping it accurate, and a short path for the first week. For a broader view of getting knowledge out of individual heads, read how to move operational knowledge out of people's heads.

Sources and further reading

• Introduction to SharePoint and OneDrive in Microsoft 365 for administrators - SharePoint in Microsoft 365
• Overview of teams and channels in Microsoft Teams - Microsoft Teams

Related Mellorca reading

• Recreating Documents Nobody Can Find: The Cost of Duplicated Work
• Too Many Apps to Learn: The Hidden Training and Productivity Cost of Software Overload
• Too Many Project Meetings Because Nothing Else Shows Status: The Payroll Cost