Document collection for law firms: how to get client documents in securely, without the chase
Most small law firms collect client documents by email: a list in a letter, attachments in reply, then follow-up after follow-up for what's missing. Typically a paralegal or secretary spends several hours a week chasing and filing, and matters stall while they wait, especially on high-volume work like conveyancing, probate and family.
Email is also the least secure way to do it. Attachments land in personal inboxes, get forwarded, and end up filed against the wrong matter or not at all. This guide is for law firms of 10-60 people - a people business, meaning a business that sells its people's expertise and time, like lawyers, accountants, agencies and consultants. It covers how to fix document collection with what you already have, the signs you've outgrown it, and what a custom build adds.
Why it happens
Clients don't hold back documents on purpose. They're unsure exactly what you need, the request is buried in a long letter, or the upload route is awkward on a phone. On your side, the request, the documents and the status live in different places:
The request
goes out as a letter or email from the practice management system - Clio, PracticePanther or MyCase - or from Word.
Documents come back
by email, post, the PMS portal or a file-sharing link.
Filing
happens in the PMS or a document management system such as NetDocuments, usually by hand.
The status
of what's outstanding lives in a checklist, a spreadsheet or someone's memory.
So nobody can see at a glance what's missing across all matters, and the only way to chase is for someone to work through files one by one.
The fix with what you already have
Most firms can halve the chasing with tools they already pay for.
- 01
Move collection into your PMS portal
Clio for Clients lets clients securely send messages and documents from a browser or phone, organised by case. MyCase and PracticePanther have client portals too. A simple trick that works in most portals: share one folder per matter specifically for client uploads, so everything arrives in one place.
- 02
Write standard request lists per matter type
A probate list, a purchase list, a divorce financial disclosure list. Short, specific, in plain English, with a sentence on why each item matters. Clients send things faster when they understand the reason.
- 03
Tell clients how, not just what
"Take a photo of each page with your phone and upload it here" gets better results than "please provide copies".
- 04
Set a chasing rhythm
A reminder after five working days, another after ten, then a phone call from a named person. Put the reminders in the PMS as tasks so they don't depend on memory.
- 05
Stop accepting documents by email, gently
When a client emails something, file it, thank them, and point them to the portal for next time.
- 06
File as it arrives
Agree naming rules for documents and a single place they live, whether that's the PMS or NetDocuments. Our free client portal requirements checklist helps you decide what your firm needs from any upload route before you choose one.
Setting it up, step by step
The exact menus differ by product and plan, so check your vendor's help pages as you go. The order of work is the same in every system.
- Pick one matter type to start. Choose the one with the most documents and the most chasing, often residential purchases, probate or financial disclosure. Don't try to fix every practice area in the first month.
- Write the request list. Sit with the paralegal who chases most and list every document that matter type needs, in the order you usually need them. For each item, write one plain-English line on what it is, why you need it and what a good copy looks like.
- Turn the list into a template in your PMS. In Clio, PracticePanther or MyCase, save it as a document template or an email template so the request goes out the same way every time, with the client's name and matter details filled in.
- Turn the list into a task checklist too. Most practice management systems let you save a set of tasks against a matter type. Create one task per document, assigned to the person who chases, so "what's outstanding" becomes a filtered task list rather than a memory test.
- Set up the client portal. Switch on the portal in your PMS, decide which folder clients can upload to, and write a two-line welcome message explaining what it's for. Test it yourself from a phone, signed in as a test client, before any real client sees it.
- Agree where documents end up. If you use NetDocuments or another document management system alongside the PMS, decide which one holds the final copy, and set up a standard folder structure per matter type so filing is the same on every file.
- Agree the naming rule. For example: matter number, document type, date. Write it on one page and pin it where support staff can see it.
- Add the chasing rhythm. Create reminder tasks at five and ten working days after the request goes out, and a call task after that, each assigned to a named person.
- Link payment where it belongs. If the same request also asks for money on account, use the payment link from LawPay or your PMS's own payments feature in the same message, so the client does both in one sitting.
- Try it on five live matters, then fix what didn't work before rolling it out to the rest of the team.
Common mistakes
Request lists written for lawyers, not clients.
"Please provide your AML documentation" means nothing to most people. "A photo of your passport photo page and a bank statement from the last three months" does.
One giant list on day one.
Asking for everything at once overwhelms clients. Ask for what you need now, and send the next batch when the matter reaches that stage.
A portal nobody mentions.
If the engagement letter, the first email and the email signature don't all point to the portal, clients won't find it.
Keeping email open as a quiet back door.
If fee-earners still say "just email it over", the portal never becomes the habit.
Filing later.
Documents left in an inbox "to file on Friday" are the ones that go missing.
Chasing with no owner.
A reminder sent by the system with no named person behind it is easy to ignore. Clients respond to people.
What good looks like
When document collection is working, a client can see on one screen what's still needed and upload it from their phone in a couple of minutes. Every document lands in the right matter, named the same way, the day it arrives. Your paralegal can open one list and see every outstanding item across their matters, oldest first. Chasers go out on time without anyone remembering to send them, and stop when the item arrives. And a supervising partner can ask "what's holding up this matter?" and get an answer in seconds.
When that stops working
These steps carry most small firms a long way. Watch for these signs:
Clients still email documents
, because the portal needs a login they forget.
Requests don't tick themselves off.
Someone opens every upload to work out which item it is.
You can't see what's missing across all matters
, only matter by matter.
Your PMS and document system disagree
about where a document lives, and filing takes longer than receiving.
Third parties send documents too
lenders, banks, medical providers, the other side - and each arrives a different way.
Big or sensitive files
(medical records, bank statements going back years) don't fit comfortably through email or the portal.
Matters stall
at the same stage every time, and the reason is always a missing document.
What a custom build looks like
A custom document collection build gives each client one simple, secure link for their matter, and gives your team one view of what's missing across every matter. It's a build we're often asked about by law firms.
For a typical firm:
- One link per matter. The client sees exactly what's still needed, why, and how to provide it, and uploads from a phone or laptop. Sign-in is simple enough that clients actually use it.
- Uploads filed automatically to the right matter and folder in your PMS or NetDocuments, named by your rules, and ticked off against the request list. A person confirms anything the build isn't sure about.
- Chasers that stop when they should. Reminders follow your rhythm, stop the moment an item arrives, and hand over to a named person when a phone call is the right next step.
- One view across matters of what's outstanding, sorted by how long it's been waiting and how close the matter's next key date is.
- Third-party requests tracked the same way as client ones.
It uses the same building blocks as the client portal we built for a podcast agency, shaped to legal work and confidentiality. We work in four steps - scope, build, roll out, improve - and roll-out includes training support staff and making the client side simple enough that clients don't fall back to email.
On the open market, a client portal or document system typically costs $8,000-18,000 to build, plus ongoing support; our guide to software costs for accounting and law firms puts this in context. Forge's prices are on the pricing page: a two-week ops audit at $2,500 (£2,000), credited to your first month, then a monthly plan at $2,000, $3,500 or $7,500 a month (£1,600, £2,800 or £6,000), with your first build included. The software runs on your own accounts, so you own it and pay those tool costs directly; we keep it monitored and fixed.
Clients who can see their documents are in also want to see what happens next. Our guide to matter status updates for clients covers that.
Who gets time back, and what they do with it
Document chasing lands mostly on paralegals and legal secretaries, and the delays land on fee-earners.
When chasing and filing run themselves, your paralegal spends the time on substantive work - for example, reviewing a bundle of bank statements for the disclosure schedule instead of chasing the last three. Your secretary spends less time renaming attachments and more time on the clients who need help, such as a bereaved family working through an estate for the first time. Your fee-earners see matters move without having to ask what's holding them up.
For example: a month at a 20-person firm
Take, for example, a 20-person firm with a residential property team, a private client team handling wills and probate, and a family team. Between them they might open 40 matters a month, most of which need documents from clients.
Before the change, requests go out as attachments to a long letter. Clients reply by email to whoever wrote to them, so documents land in six different inboxes. Priya, the property paralegal, keeps a spreadsheet of what's outstanding and updates it by hand. A probate file stalls for three weeks because the bank statements were emailed to a secretary who was on holiday. Nobody can say how many matters are waiting on a client document without asking around.
After, the same month runs differently. Each matter type has a short request list, sent from a template on the day the matter opens, with a portal link and a sentence on why each item matters. Clients upload from their phones. Priya opens her task list each morning and sees exactly what's missing, sorted by age. Reminders go out at five and ten days, and on day twelve Priya phones the two clients who haven't replied, both of whom were simply unsure which bank statement was wanted. The family team's financial disclosure lists arrive more complete, because each item now says what period it should cover.
Nothing in that example needs a custom build. It needs the PMS set up properly and one person in each team who owns the outstanding list.
Rolling it out and training the team
Start with one team.
Pick the one with the heaviest chasing load. They'll feel the difference first and make the case to everyone else.
Train support staff first.
Paralegals and secretaries send most requests and receive most documents. Walk through a real matter from request to filed document.
Brief fee-earners in ten minutes.
They need to know where documents now arrive, how to check what's outstanding, and to stop saying "just email it".
Change the client-facing words at the same time.
Update the engagement letter, the first email and signatures so they all point to the portal.
Run the old route alongside for two weeks
, then close it gently. Thank clients who still email, file their documents, and point them to the portal.
Ask for feedback after week one
, from staff and from a few clients, and change the request lists. The first version is never right.
Be honest about the worry.
Some support staff will wonder what a smoother process means for them. It means less chasing and renaming, and more time on the parts of a file that need a person.
How to know it worked
Measure the same things for a month before and a month after:
Days to complete:
how long from the first request until every document is in.
Chasers per matter:
how many reminders and calls it took.
Documents by email:
what share still arrived by email instead of the portal.
Filing time:
how long from arrival to correctly filed.
Stalled matters:
how many matters sat waiting on a client document for more than two weeks.
If days to complete falls and the email share keeps dropping, it's working. If clients have drifted back to email, find out why, usually a login problem or a request they didn't understand, before adding anything new.
Supervision
Document collection carries real risk: a misfiled document can reach the wrong client, and a missing one can delay a completion or a court deadline. A named person in each team owns the outstanding list and reviews it weekly. Supervising lawyers check that key documents are in before relying on them, rather than assuming. Anything the system files automatically should be easy to check and correct, and anything it isn't sure about should go to a person, never be guessed.
Confidentiality and data protection
Client documents are often the most sensitive data a firm holds, so the collection route has to be secure by design. This section is general information, not legal advice; check your own obligations with your regulator and advisers.
Where data lives
Uploads go straight into your PMS or document management system, running on your firm's own accounts. Nothing is held on Forge accounts.
Who can see it
Each client sees only their own matter. Inside the firm, access follows your existing roles and matter permissions.
Why email isn't enough
Attachments in personal inboxes are hard to control and easy to misdirect. A secure upload route is a practical step towards the duties below.
UK firms
The SRA's guidance on confidentiality of client information explains that paragraph 6.3 of the Codes of Conduct requires you to keep the affairs of current and former clients confidential. The ICO's guide to data security explains the UK GDPR duty to process personal data with appropriate technical and organisational measures.
US firms
ABA Model Rule 1.6(c) requires a lawyer to make reasonable efforts to prevent the inadvertent or unauthorised disclosure of, or unauthorised access to, information relating to a client's representation. Check your state's version of the rule.
Questions, answered plainly
What is the best way for a law firm to collect documents from clients?
A secure portal with a short, plain-English request list per matter type, simple phone uploads, reminders on a set rhythm, and a named person who calls after the second miss. Avoid relying on email attachments.
Is email secure enough for client documents?
It's the hardest route to control: attachments sit in inboxes, get forwarded and are easy to misdirect. Most firms move to a portal or secure upload link and stop accepting documents by email except when necessary.
Can clients upload documents through Clio?
Yes. Clio for Clients lets clients securely send messages and documents to the firm from a browser or the mobile app, organised by case.
How do we stop chasing clients for the same documents?
Use standard request lists per matter type, explain why each item is needed, set automatic reminders that stop when items arrive, and track outstanding items across all matters in one view.
How much does a custom document collection build cost?
Typically $8,000-18,000 on the open market for a portal or document system, plus ongoing support. With Forge, a two-week ops audit is $2,500 (£2,000), credited to your first month, then $2,000, $3,500 or $7,500 a month (£1,600, £2,800 or £6,000) with your first build included.