Wealth advisors: track open files and chase missing documents

An open file is not a file that is moving

Short answer: for a wealth advisor, tracking open files means keeping one view that says, for each client, which documents have arrived, which are missing and since when. Reminders can then go out on fixed dates without you having to think about them. What stays with you: judging a doubtful document, deciding a file is complete, and everything that counts as advice.

An advisory practice typically carries around thirty open files at once, each at a different stage: information form in progress, tax notice awaited, bank statements incomplete, proof of a life insurance contract outstanding. Each one depends on a client who answers when they remember. The advisor has to remember who owes what, since when, and whether a reminder has already gone out.

This article covers only how to organise the follow-up. It says nothing about what your activity must collect or keep: that list belongs to your compliance function and your advisers. Our general approach is described on the studio’s home page.

Where the time actually goes

The time is not lost writing a reminder. It is lost in four less visible places.

• Memory. Knowing that one client has not sent their latest statement means finding an email among hundreds.
• Reconstruction. Before each reminder, you check what has already arrived, under what name, in which folder.
• Bad timing. A reminder sent after the client has already replied is irritating. A forgotten one lets the file sleep.
• Slipping follow-up. When the advisor is busy with meetings, waiting files drop behind the urgent. Scheduled reviews slip for the same reason.

The real cost of an incomplete file is therefore the total delay between the first request and completeness, not the minutes spent writing a message. That delay is what you should measure.

The tracking table, the centrepiece

Definition: a file tracking table is a single view that lists, per client, each expected document with its status (not received, received, to check, validated), the date of the last reminder and the person holding the file. It, far more than any AI, removes the mental load: it replaces memory and email threads.

Once it exists, everything attaches to it: the acknowledgement updates a row, the reminder fires on rows still marked "not received" after a delay you set, filing names each document after the row it fills. Your morning view shrinks to the files that are stuck, the kind of daily summary listed among the processes the studio automates.

The document names above are examples. Your master list, per client type, remains yours.

Chasing missing documents: a cadence, not a single nudge

An effective reminder rests on three parts: a document list specific to each client profile, a check that a received file matches the document expected, and a cadence that stops on receipt. Without them, automation boils down to the same email repeated at fixed intervals, often sent after the client has already dealt with it.

These delays are a working base, not a standard. Tune them to your clients: a busy private client and a company director do not move at the same pace. Test the tone on three files before rolling out, and read the first messages before they leave.

Each reminder names only what is still missing. That detail changes how it lands: "I still need your latest statement" reads as a service, "documents are missing from your file" reads as a reproach. The principle is the same as for collecting documents in an accounting firm, with documents that are more personal.

Check the document, not just its presence

Receiving a file does not mean having the document. Four defects recur: the scan is unreadable, a page is missing, the date has expired, or the document belongs to someone else. The AI reads the file, proposes what it is and which folder it belongs to, and flags anything it is unsure about. You review only the flagged cases.

Some documents also deserve a closer look than others, and you decide which. Those that carry a financial stake, or that you will rely on for a recommendation, are better reviewed by a person every time, whatever the AI says about them. The tool sorts the pile so that your attention goes where it is needed.

The most serious risk in the circuit is filing a document in another client’s folder. For that reason each client is processed separately, the name is checked at every step, and a document whose owner is uncertain is not filed: it comes back to you.

What runs alone, what stays with you

The last row is deliberate. A tool can state a fact: every document on the list has arrived. Deciding that the file is usable is a judgement that binds you. No message and no write-back should leave without a person’s approval.

A worked example, to replace with your own numbers

We do not publish an average gain: it depends on your clients and habits. Here is how to compute yours, with purely illustrative figures.

Suppose 30 open files, 10 of them waiting for documents each month. If, once timed, tracking one waiting file (finding what is missing, chasing, checking, filing) takes you 40 minutes a month, that is 10 × 40 = 400 minutes, about 6 hours 40. If the circuit brings this down to 10 minutes of review and decisions per file, the total drops to 100 minutes. The theoretical gain is 300 minutes a month, 5 hours. These are your assumptions, not a promise: replace 30, 10 and 40 with your measurements.

The most visible gain is sometimes not time but how long files stay open. A file chased on fixed dates usually completes faster than one chased when the advisor happens to think of it. Measure the average delay between first request and completeness, before and after.

When this is not the right choice

• You follow fewer than ten files at a time. A spreadsheet and a calendar reminder are enough. The calculation above will tell you.
• Every file is unique. If no document list repeats, there is little routine to prepare. The tool will mostly help with filing.
• Your clients only communicate by phone. You first need a way to record what was agreed. Automation comes after.
• Your master list does not exist. Reminders sent from a vague list will be vague. Write the list first.

A tool like this is also no substitute for advice on what your professional obligations require you to collect or retain. That question is outside its scope.

Pitfalls

• Chasing too hard. A badly tuned sequence makes the practice look pushy. Read the first messages.
• Chasing after receipt. If the table is not updated when a document lands, the reminder goes out for nothing.
• Letting the tool conclude. "Everything received" does not mean "the file is sound".
• Neglecting confidentiality. These files hold personal financial data. Ask where it is hosted, who can access it and whether each action is logged. Hosting in Switzerland is possible.

Where to start this week

Take your last five files that waited for documents. For each, note the date of the first request, the number of reminders and the completion date. Compute the average delay. If most waited more than three weeks, the topic deserves a project, and the first thing to write is the master list per client profile. For the stage before this one, see from first meeting to a complete client file.