Why Sending a PDF Is Costing You More Than You Think
Not long ago, I needed to confirm some standard business details for a routine compliance check. The request arrived as a PDF. It wasn't form-fillable. I didn't have a printer to hand. What followed was twenty minutes of frustration — downloading the file, trying conversion tools, giving up, starting again — for something that should have taken five minutes and two clicks.
It's a small thing. But small things, repeated thousands of times across an organisation, add up to something significant.
The PDF has become the default document of bureaucracy. It looks official. It feels secure. And for preserving a finished document — a signed contract, a published report — it's entirely appropriate. The problem is that somewhere along the way, organisations started using PDFs to collect information, which is almost exactly the wrong tool for the job.
When you send someone a static PDF to fill in, you're asking them to print it, write on it, scan it, and email it back. That assumes they have a printer. It assumes they have a scanner, or know how to use their phone as one. It assumes they can read your handwriting when it comes back. And it assumes none of this will put them off completing the task at all — which, increasingly, it does.
The organisations still doing this aren't doing it because they've thought it through and decided it's the best approach. They're doing it because it's how it's always been done, and nobody has stopped to ask whether it still makes sense.
The alternative isn't complicated. For most routine information-gathering — KYC checks, onboarding details, annual confirmation updates, contact changes — a simple digital form does the job in a fraction of the time. Microsoft Forms, a SharePoint list, a short Power Apps form: these are all tools that most organisations already have access to through Microsoft 365.
Better still, rather than sending a blank form and asking someone to fill everything in from scratch, send them what you already know and ask them to confirm or correct it. The cognitive load drops. The time it takes drops. The quality of the data you get back improves because people aren't transcribing the same details for the fifth time — they're just checking that what you have is right.
The information comes back clean and structured, ready to use, rather than as a scanned image of someone's handwriting that needs to be retyped into a system anyway.
This is what Lean thinking applied to everyday admin looks like in practice. Not a transformation programme. Not a system replacement. Just a clear-eyed look at a small, repeated process and a decision to do it in a way that respects everyone's time — including the people on the receiving end.
If your organisation is still sending PDFs for routine information gathering, the question worth asking isn't "how do we make the PDF better?" It's "why are we still using a PDF at all?"
The answer, in most cases, is that nobody has got around to changing it yet. That's a very easy thing to fix.
