Your HR team is spending 20% of their time on document requests. Here's the proof.

Think about the last time someone on your team needed an employment confirmation letter.

They emailed HR. HR pulled up a template -- if there was one. Edited the name, the title, the start date. Chased the manager for a signature. Sent it back. The employee asked for a PDF. HR sent the Word doc by mistake. Three emails later, the right document arrived.

Total time: somewhere between 25 and 45 minutes. For a letter that contains four facts the company already knows.

Now multiply that by the number of requests your People Team processes every week.

The volume problem nobody talks about

Employment confirmation letters. Salary confirmations. Visa support letters. Reference requests. Policy acknowledgements. Right to work verification.

These are not unusual requests. They are the backbone of employment administration -- the things employees need when they're applying for a mortgage, renewing a visa, renting a flat or starting a new job elsewhere. They arrive in the People Team inbox every single week, at every company, regardless of size.

A People Team supporting 200 employees will typically process between 15 and 30 document requests per month. At 20 minutes per request on the low end, that is 5 to 10 hours of People Team time per month spent on requests that are, in terms of cognitive content, close to zero.

The information already exists. The template already exists. The approval chain already exists. The only thing that doesn't exist is a system that connects them.

Why this keeps happening

The reason HR document requests are still manual at most companies isn't that nobody has noticed the problem. It's that the solution has always seemed smaller than it is.

A shared Google Doc template feels like a fix. A folder of PDFs on the intranet feels like a fix. An email alias that goes to the HR team feels like a fix.

None of them are fixes. They're workarounds that reduce the friction slightly while preserving the fundamental problem: every request still requires a human to find the template, populate it with the right data, route it for approval, and send it back.

The data the document needs -- name, title, salary, start date, manager -- already exists in the company's HR system. The template already exists. The approver is already known. The only manual step is the assembly.

What automation actually looks like

A well-designed document automation system does four things.

First, it gives employees a self-service portal where they can request the documents they need without emailing anyone. The request takes 90 seconds. The form is pre-filled with everything the system already knows about them.

Second, it routes the request to the right approver automatically -- manager approval for standard requests, HR approval for salary confirmations, dual approval for contract amendments.

Third, it generates the document from a verified template, populating every variable from the company's HR records. No copy-pasting. No mail-merge. No version control problems.

Fourth, it creates an immutable audit trail. Every request, every approval, every download is logged. The company has a complete record for every document ever generated.

The employee gets their document in under 10 minutes. The People Team didn't touch it. The audit trail is complete.

The number that matters

The ROI on document automation is one of the clearest in the HR technology stack, because the cost is so concrete.

A People Team of 8 spending 6 hours per month on manual document requests is spending 72 hours per year -- nearly two full working weeks -- on tasks that could be automated. At a loaded cost of £40 per hour, that's £2,880 per year on a problem that costs less than £200 per month to eliminate.

That's before you count the requests that go wrong -- the letter with the wrong salary figure, the reference that arrived three days late, the policy acknowledgement that was never signed and created a compliance gap.

The document request problem is not a technology problem. It's a systems problem. And it has a straightforward solution.

The People Teams who automate document requests get that time back. They spend it on the things that actually require human judgement -- conversations, decisions, strategy.

That's what People Teams should be for.