What attachment sprawl looks like
Most small law offices do not have a document problem. They have a document location problem. The signed engagement letter is in one paralegal's inbox, the client's driver's license photo came in by text, the bank statements arrived as three separate replies with "here you go" in the subject line, and the one page the attorney actually needs is a blurry scan that nobody noticed until the day before a filing deadline.
A client portal with a per-matter document checklist fixes the location problem. It gives the client one place to see what is still needed, gives staff one place to see what came in, and gives the attorney a clear answer to "are we ready?" Here is how to design that checklist before anyone picks software. TwoQM develops custom software, client portals, CRM workflows, automation, AI integrations, and connected systems for small firms when off-the-shelf tools do not match how the office actually works.
Here is an original example, not a TwoQM client and not a measured result. A two-attorney family law office opens a new matter. The intake call goes well. Staff email the client a list of twelve documents. Over the next three weeks the client replies seven times, forwards two items from a spouse's account, texts photos of a pay stub to the front desk cell phone, and drops off a USB drive. Nobody did anything wrong. But when the attorney asks what is missing, a paralegal spends an hour searching inboxes and still is not sure the tax return is the right year.
Design the checklist per matter type, not per firm
A probate matter, an uncontested divorce, and a business formation each need different documents in a different order. Start with the matters you open most often.
For each matter type, write down:
Required items. The documents the attorney needs before the next step, such as identification, signed engagement letter, prior orders, policy declarations, or entity paperwork.
Conditional items. Documents needed only in some cases. "If there is real property, upload the deed." The portal should show these only when the condition applies.
Who reviews each item. A paralegal can confirm a document is legible and the right year. Only an attorney decides whether it is legally sufficient.
Item statuses clients understand. Needed, uploaded, under review, accepted, and needs a new copy, with a short reason when something is sent back.
A due date tied to the matter. Not a generic reminder, but "we need this by the 14th so we can prepare your filing."
Write it on paper with your staff first. The software should follow the checklist, not the other way around.
What the client should see
Keep the client side simple. A client who opens the portal on a phone should see their matter name, a short list of what is still needed, an upload button next to each item, and a plain message when something is accepted or needs to be redone. They should never see internal notes or other clients.
Offer the portal in the language the client is most comfortable reading. In South Texas that often means English and Spanish side by side, with the same checklist and the same statuses.
What staff should see
Staff need a board, not a pile. A useful internal view shows every open matter with its percentage complete, the oldest outstanding item, and which items are waiting on internal review rather than on the client. A matter stalled on the client is different from one stalled on three unreviewed uploads.
Use plain business automation for the predictable steps: a confirmation when an upload arrives, a reminder to the client a few days before an item is due, an alert to the assigned paralegal when an upload sits unreviewed past your own deadline, and a note on the matter record when the checklist reaches 100 percent. None of that needs a language model.
AI can help where documents are messy and a person still decides. A model can suggest which checklist item an uploaded file probably belongs to, flag a statement that appears to be from the wrong year, or draft a polite request for a clearer copy. A staff member confirms before anything is filed or sent. Keep its access limited to what that task needs.
Confidentiality is a design requirement
The American Bar Association's Formal Opinion 477R (2017) discusses a lawyer's duty to make reasonable efforts to protect client information sent over the internet, and notes that more sensitive information may call for stronger safeguards. Your state bar's rules and your own risk judgment set the standard for your firm. This article is a workflow guide, not legal or ethics advice.
In practice, ask any portal project to cover the basics: individual staff logins with multi-factor authentication, client access limited to their own matters, an activity log of who uploaded, viewed, or downloaded each file, encrypted connections, a clear retention and closing process, and a way to remove a former staff member's access the same day they leave.
Connect it to the systems you already use
A portal that lives alone becomes one more inbox. The matter record in your CRM or practice tool should show checklist status. Accepted documents should land in the matter's folder with a consistent name. Your website's intake form can create the matter and the first checklist automatically. That is the work TwoQM describes as connected systems: fewer copy-paste steps between tools your staff already open every day. See how TwoQM works with law firms.
Where to start this week
Pick your two most common matter types. Write the required and conditional document list for each, mark who reviews each item, and decide the client-facing statuses. Then count how many hours your team spent last month searching for attachments.
If your firm wants a client portal shaped around your matter types, your review steps, and your existing tools, TwoQM can scope it with you.