How to keep client information organized

Organized isn't really the goal. Findable at the moment you need it is. Here's a structure you can adopt this week — and the honest part most advice skips, where organizing quietly stops paying for itself.

Nobody notices whether your client information is organized. What gets noticed is the four seconds on a Tuesday call when the client says "we did agree you'd cover the travel, right?" — and you either answer, or you say "let me pull that up" and email them Thursday.

That's the actual test, and it's worth naming up front because it changes what you should build. A system judged by how neat it looks produces elaborate folder trees nobody maintains past week three. A system judged by that four-second moment produces something much plainer. Below is the plain version: the one structural decision that matters, what belongs in a client record, when to capture it, an honest answer on whether you need a CRM — and then the part where organizing runs out of road.

1. Split by client, not by document type

Almost every organizing decision downstream is determined by one choice: what sits at the top level. Most people split by kind of thing — contracts in one place, meeting notes in another, correspondence in the mail app, invoices in the accounting tool. It looks orderly. It fails in use, because you almost never ask a question shaped like a document type.

You do not wake up wanting to see all your contracts. You wake up wanting to know where things stand with one client. So make the top-level split match the question you ask most:

• One home per client, whatever the material. The contract, the notes, the deck they sent, the photo of the whiteboard — same client, same place, regardless of the form it arrived in.
• The same internal shape in every client's home. Not because uniformity is virtuous, but because it removes the decision. You stop asking "where does this go" and start knowing, and a decision you don't have to make is a decision you can't skip on a bad day.
• Everything about a client is in one place, or the place is a lie. A home that holds 70% of the client's material is worse than no system, because you'll trust it and it will be wrong at the moment it matters.

This is the whole structural decision. Folder taxonomies, naming conventions and the search operators that find an old file fast are worth getting right too — we cover those in detail in the guide to organizing client emails and documents — but they're refinements on top of this one split.

2. Know what actually counts as client information

"Client information" is treated as one undifferentiated pile, which is why people either keep too little or hoard everything. It's really four layers, and they behave completely differently — different refresh rates, different consequences when missing.

Two practical consequences fall out of the table. First, the standing facts deserve a single short page per client that you can read in thirty seconds before a call — they change rarely enough that keeping one current costs almost nothing, and they're the facts whose absence is most visible to the client. Second, the four layers want different treatment: the running history wants a chronological note (see how to keep notes on clients for what to record), while the open loops want their own single list across all clients, because "who's gone quiet on me?" is a question you ask across the whole book at once, not client by client (the follow-up guide covers that list).

And a note on what doesn't belong: the presentation you already delivered, the agenda restated in a note, the fourth copy of a deck. Anything you'll never ask a question about is weight, not information. A client record earns its keep by what you can get out of it, not by what went in.

3. Capture at arrival — the weekly tidy-up is a myth

The most common piece of advice on this subject is to book a recurring slot to sort out your client records. It sounds responsible. It doesn't survive a real quarter, because that slot sits on Friday afternoon and Friday afternoon is where fires go to be fought.

The alternative is the one-touch rule: a thing goes to its home the moment it arrives, not later. The email you'd have filed on Friday takes five seconds to file now, when it's already open in front of you and you already know what it is. Later, it costs you the five seconds plus the reconstruction of what it was and why you kept it.

• Handle it once. If you're setting something aside to deal with properly later, you've created two jobs out of one and postponed the easier of them.
• Capture in whatever form is fastest right then. Three lines typed in the corridor, a voice memo dictated on the walk to the car, a photo of a marked-up printout. A rough capture made in the moment beats a polished one reconstructed tomorrow — and reconstructed tomorrow is usually reconstructed never.
• Write the standing facts down the first time you learn them. The signing authority, the invoicing address, the procurement quirk. You will not remember which of your clients had which constraint by month four.

Then the monthly pass becomes an audit instead of a cleanup: ten minutes per active engagement, checking the standing facts are still true, nothing open has gone stale, and finished work has been archived so the active set stays short. Audits take minutes precisely because the filing already happened.

4. Do you need a CRM for this? An honest answer

Most advice on this topic ends by recommending software, which is a good reason to be explicit about when that's right and when it isn't. There's a genuine dividing line, and it isn't about company size.

If you're in the left column, get a CRM and keep it fed — nothing in this guide substitutes for it. If you're in the right column, the honest read is that a CRM converts your client information problem into a data-entry problem, and the data entry is a job you'll quietly stop doing by month two. The pile of half-maintained client software in the world is mostly made of right-column people who bought a left-column tool.

Where "organized" quietly runs out

Now the part that most guides on this subject leave out. Everything above optimizes filing — and filing has a lopsided cost profile. You pay it many times a day, every day. You collect on it a couple of times a week, when you actually need to retrieve something. You are paying a daily tax for an occasional benefit, which is exactly the kind of arrangement that erodes the first week you're genuinely busy.

Worse, even a perfectly maintained system leaves the hardest job with you. You are still the index. To retrieve anything you have to know which client, which layer, roughly which month, and the words you happened to use at the time. A filing system rewards you for remembering where you put things — which is a strange thing to optimize for, since not remembering is the problem you started with.

And it only ever holds what you remembered to capture. The procurement lead time they mentioned once and nobody wrote down. The reasoning behind a decision — the decision survived, the why didn't. The commitment made out loud on a call that never became a task on anyone's list. None of it is missing because your folders are bad. It's missing because it was never a file.

So the four-second test from the top of this page rarely comes down to organization at all. What you need in that moment isn't a location — it's a fact plus the evidence for it: did we agree to cover the travel, and where does it say so? A folder tree can't answer that. It answers a different, easier question you weren't asking.

A different answer: organize for retrieval instead

This is the problem Equerry is built for. Rather than filing client information more diligently so you can find it later, you hand what matters to a personal assistant that remembers it — and then you ask, in plain words, when the moment comes.

What that looks like against the four layers above:

• Put your assistant on the thread once. CC your Equerry address (something like mark@mail.getequerry.app) when you send the engagement email — every later reply on that thread lands automatically, and the first time a new person writes in you get a single tap to approve them. Forwarding works too for a thread you didn't start, but it captures that one snapshot rather than what follows.
• Hand over the documents the way you already share things. Send a PDF or a contract through the share sheet, photograph a marked-up printout or a whiteboard, save a screenshot. No folder to choose, no name to invent.
• Capture the loose material in the corridor. Dictate a voice memo after the call, or type a three-line note — the rate they floated, the constraint they mentioned, the thing you just promised by Friday. The parts that were never going to become a file.
• Then ask instead of hunting. "Did we agree to cover travel for the Acme engagement?" comes back with the answer and a source chip — tap it to see the exact passage it drew on and open the note it came from, so you can check the answer rather than take it on trust.
• Be handed the record before the call, not after. Equerry can brief you from what you've shared about that client — the decision from October, what's still open, the reply that landed at 3:42 on Thursday while you were in another session — so the standing facts and the running history arrive together, before you need them.
• Audit what it holds like it's your own notebook. You can see every fact it has remembered from the things you shared, and delete anything it shouldn't keep. Client information you can't inspect isn't organized, whoever is holding it.

Two boundaries matter here, and both are deliberate. Equerry knows only what you hand it — the threads you CC or forward, the files you share, the notes and memos you save, and the calendar you let it read so it can brief you before a meeting. It isn't signed into your mailbox, and it doesn't sit on your calls: it doesn't record meetings or transcribe live conversations. And it isn't a CRM. There are no deal stages, no pipeline, no fields to keep current. It's a personal assistant that helps you get things done — which, for client work, mostly means knowing what was said and being able to show you where.

The shift is smaller than it sounds. You keep one home per client, because separation is still worth having. What you drop is the belief that your filing has to be good enough to find things by placement — because retrieval no longer depends on where you put it, only on your having handed it over.

Start here

• Pick the split and commit. One home per client, same shape inside each. If you currently split by document type, converting two active clients this week is enough to feel the difference.
• Write one standing-facts page per active client. Fifteen minutes each, most of it already in your head, and it pays back the first time you don't have to ask.
• Adopt the one-touch rule for a fortnight and cancel the recurring tidy-up slot. Replace it with a ten-minute monthly audit per engagement.
• Stop filing the things that were never files. The lead time mentioned once, the reasoning behind an old decision, the promise made out loud — hand those to an assistant that can give them back when you ask instead of trying to file them perfectly now.

Organized is a means. Being able to answer the question in the four seconds you have is the end — and the shortest route there isn't a better filing habit, it's not needing one. See how the briefing before a call works, or the wider system for keeping track of multiple clients.

Last updated 2026-08-29.