Key takeaways
- Send one list with one deadline, not a new email for every document.
- Make the request finishable on a phone, without a password or an app.
- Put the reminder schedule in the same system as the request, so it stops when everything is in.
- Review what arrives, send back only what is wrong, and file the accepted documents in a place the next person can find.
Why the email thread fails
An email thread is a conversation, not a record. The request is in one message, the client's question is in another, the file is in a third, and the answer to the question is in a fourth. Nobody can tell which items are still open without reading the whole thread.
The thread also puts the follow-up on the person who sent it. If the bookkeeper is out, or the client replies to a different address, the request stalls. The firm has no shared view of who owes what, so the same document gets requested twice and the client gets annoyed.
A collection process replaces the thread with one list, one status per item and one place for the files. The client sees the same list every time, and the firm sees which items are still open without reading a conversation.
Make one list, not a new request for every document
Start with the checklist for the job: a monthly close list, an individual tax organizer, a business organizer or a year-end 1099 list. Group the items in the order the client will find them, such as statements first, payroll second and questions last.
Each item should ask for one thing. "Send your bank statements and payroll reports" is two items, and a client who sends one of them will mark the whole line done. Split it. Add a short note on what to send, for which period and in what form.
Mark the items that only apply to some clients. A client with no payroll should not have to read a payroll item to know it does not apply. A yes or no question at the top can hide the items that do not fit, but the list still needs to be readable if the client skips the question.
Make the request easy to finish on a phone
Most clients will open the request on a phone, often at night, often with one hand. A PDF attachment and a request to print, sign and scan is a request to do it later. A link that opens a list, saves as the client goes and accepts a photo is a request that can be finished now.
Do not require a password or an app for a client who opens a link from an email. If the firm wants a second factor, use a one-time code by email. The client should be able to stop, close the browser and come back without losing the answers.
Ask for the document, not the number. A client should never type a full Social Security number, EIN or bank account number into a text answer. Ask for a photo or a PDF of the document, and let the firm's secure storage handle the rest.
Put the deadline and the reminder in the same place
A due date in an email is a suggestion. A due date on the list, with a reminder that sends itself, is a commitment. Set the due date when the request goes out, and tell the client what happens after it.
The reminder schedule should match the client and the work. A monthly close may need a reminder three days before the due date and another on the due date. A tax organizer may need a reminder at two weeks, one week and two days. A 1099 request in January may need a reminder every few days until the W-9s arrive.
The most important rule is that reminders stop when everything is in. A client who sends the last document and still receives a reminder learns that the reminders are noise. A reminder that stops teaches the client that the list is accurate.
Review what arrives
A collection process is not finished when the client uploads a file. Someone has to look at it. Accept the item if it is right, send back the one file that is wrong with a short note if it is not, and leave the rest of the request alone.
Sending back the whole request because one file is wrong is the fastest way to lose the client's attention. Send back the item. The client sees one thing to fix, not a list to redo.
Keep the review visible. The client should be able to see which items are accepted, which are waiting and which were sent back. The firm should be able to see the same status without asking the person who sent the request.
File it where the next person can find it
The accepted file should land in a folder that matches the client and the year, not in a downloads folder named after the person who reviewed it. A consistent folder structure is the difference between a five-minute handoff and a day of searching.
Name the folders after the client and the period, and keep the source documents separate from the workpapers. If the firm uses a document management system, the collection tool should file into it or export to it in the same structure.
Keep the request record with the file. The list, the date each item arrived, the review decision and the reminder history are the evidence that the firm asked, followed up and received the document.
What to measure
Measure the request, not the inbox. The useful numbers are how long it takes a client to send the first item, how many items are still open at the due date, and how many requests are completed without a manual follow-up.
A firm that tracks those numbers can see whether the problem is the list, the client or the reminder schedule. A firm that only counts emails sent is measuring effort, not results.
Start with one service and one client. Run the process for a month, compare it to the email thread, and then move the next client. A process that is rolled out to the whole book at once is hard to debug.