Client Document Collection: A System That Actually Works

Why document chasing eats the season

Document chasing consumes capacity because every outstanding item spawns its own thread: an email, a reply, a forwarded photo of a receipt, a follow-up. Multiply a dozen items by a hundred clients and the firm is running an unpaid correspondence department during its busiest weeks.

The cost is not only time. Files sit open waiting on one slip, which is how work-in-progress accumulates and how deadline buffers quietly disappear.

Pick one channel and defend it

Every document request and every submission should move through one channel, and the firm has to defend that rule kindly but without exceptions. A client who emails attachments in week one will email attachments forever unless the first request itself arrives through the chosen channel.

The channel matters less than the singularity. One place means one thing to check, one place to search during a review, and no reconciling an inbox against a drive folder against a text thread in April.

Build a standing request list per engagement type

Write the request list once per engagement type — T1, corporate year-end, monthly bookkeeping, payroll — and reuse it every period. A standing list means no one composes a request from memory, and the client receives the same structure every year, which trains them to keep the same folder.

Group items by where the client finds them: slips from employers and institutions, receipts they accumulate, statements they download, and prior-year CRA correspondence. A list organised around the client's reality comes back faster than one organised around the firm's working paper index.

Time requests to the client's calendar, not the firm's

Send the year-end request about a month before the client's fiscal year-end, not when the firm is ready to start the file. The client is already thinking about year-end; the documents exist; nothing has been shredded or lost to a laptop change yet.

This is a place where cadence-aware tooling helps. SpidNums raises a year-end reminder one month before each client's fiscal year-end, which is exactly the moment the standing request list should go out.

Escalate on dates, not on frustration

Decide the follow-up schedule before the first request goes out: a nudge at day seven, a phone call at day fourteen, and at day twenty-one a short note stating plainly what cannot be filed without the outstanding items and what that means for the client's deadline.

Written this way, escalation is a system rather than a mood. No one has to decide whether today is the day to chase; the calendar already decided.

• Day 7 — friendly nudge listing only the outstanding items
• Day 14 — phone call, log the outcome
• Day 21 — written note tying the missing items to the filing deadline

Track received against requested, per engagement

Every engagement needs a visible received-versus-outstanding position, or the firm rediscovers what is missing by reopening the file. A checklist item per requested document, ticked as items arrive, turns 'are we waiting on them or on us?' into a glance instead of an archaeology dig.

Run the request list as tasks on the engagement's project and the answer lives where the work lives — in SpidNums that is the project's task list, filterable to show exactly which files are stalled on the client.

Give clients one signed-in place

Clients cooperate with systems that reduce their own effort. A branded client portal gives them one signed-in place where their services, deadlines, documents and engagement letters live — so a request is not another email to lose but an item in a place they already know.

In SpidNums the portal carries the firm's own branding, and invites go out by magic link with a temporary password, so the client's first experience is one click rather than an account-creation chore.

Set the pattern in the client's first week

Whatever pattern the first exchange follows becomes the permanent pattern, so the very first document request a new client receives should already run through the system: the standing list, the single channel, the portal invite. Onboarding is the only moment the habit is free.

Retraining an existing book is slower but the same move: pick the next natural request each client will receive and send it through the system, rather than announcing a policy change in the abstract.