Skip to content

The chasing emails, and the list behind them

Part 03 of 8

On this page

Most of those four minutes went on the sentence that came before the ask.

The Framptons owed two things. What Corinne wrote first was the receipt: the two brokerage statements and the mortgage interest arrived on the twenty-fourth of January and they’re in the file. Then the two still to come. A 1099-INT, named the way the credit union names it on the envelope rather than the way a return names it. And a K-1 from a partnership Alan Frampton owns a ninth of. Then a line saying the return starts once both are in. Then one more, about the K-1 only, asking whether it had reached them yet, and if it hasn’t, roughly when they expect it.

Three of the four minutes went somewhere other than writing. She had last year’s return open on one side of the screen and January’s thread open on the other. So she could see in one moment what ought to exist and what had actually turned up. That’s the whole of why the Framptons were the easy one.

What follows is the part underneath the wording. The craft of the message itself is settled and written down. A document runs late for about six reasons, and forgetting covers only one. A first ask has things it should contain. A second attempt has to change something in order to be a second attempt at all. That craft has a guide of its own, and Corinne wrote a good first chase because she’d read the same things every practitioner has read. What February taught her sits below the wording. A round of chasing is a reconciliation, performed once per client, and the thing it reconciles against has to be kept somewhere.

Where the four minutes went

Every chase carries three facts, and only one of them is the ask.

What’s still outstanding. What’s already arrived. And whether the outstanding thing exists yet, which decides whether the message is a chase or a calendar entry.

Those three live in three different places. The second is in the mailbox, spread across however many threads a client happened to start. Past one person, it’s spread across mailboxes too. The first was in the count Corinne had done over the last weekend of January, which by the second of February was one spreadsheet on one laptop. The third sits outside everybody’s records, and usually the way to get it is to ask.

So the writing is the last step and the cheapest one. What the four minutes mostly bought was the assembly of a small, temporary, client-shaped view of the job. She held it together long enough to write six sentences, then dismantled it.

The eighty-six went out between the second and the eleventh of February. She went by feel rather than a time sheet, and the shape was clear enough by the end of the first evening. Where a client had sent everything in one thread, to her, a chase ran four or five minutes. Where deliveries had come in over eleven days in eleven fresh threads, each beginning hi again, it ran nearer twenty. Most of that time went on establishing what she already had. Two of the eighty-six waited past the day she meant to write them. The organizer had gone out over Idris’s signature in January and the deliveries had followed it, so what those two clients had sent was his to tell her.

Call it eleven hours across nine days. That sounds survivable, and it is, in the way a cost is survivable when it comes out of the only month that matters. Eleven hours in February weighs differently from eleven hours in October. It’s eleven hours taken out of the two weeks in which preparation starts, spent by the person whose desk the finished returns come back to.

Ten days of replies

By the fourteenth, sixty-two of the eighty-six had answered something. Almost none of them had answered the question.

Most of what came back were deliveries, and most of the deliveries were partial. Two things asked for. One thing sent. The other simply went unmentioned. That’s the ordinary result of working down a request in whatever order the paperwork proves findable, and by the middle of February Corinne could have predicted it for individual clients with reasonable accuracy.

Three replies said some version of we sent that already, and two of them were correct. One had gone to Marguerite in a January thread about something else entirely. The other rode in as an attachment on a message whose subject line was about a rental property, which is where it stayed.

Eleven replies came with a date in place of a document. The partnership expects to issue at the end of March. The brokerage says the consolidated statement is due out on the fifteenth. Those were the most valuable replies in the whole batch, and every one of them felt like nothing when it landed, because a date reads as less than progress. They were valuable because they took eleven files off the list of things Corinne had to think about and put them onto a calendar. That’s the one conversion in this month that reduces work rather than moving it.

Some replies were about something else. A chase is a message from the firm, and a message from the firm is an opportunity to ask the thing they’ve been meaning to ask since June. So a document request that also invites a question gets a reply about the question. Those arrived at a rate that surprised her, and they go where they always go, which is the pile of client questions.

And twenty-four clients said nothing whatever.

Every one of those outcomes changes the list. A partial delivery changes two lines. A date turns one line into a calendar entry. A question leaves the list alone and adds an hour to the week. Silence leaves it alone too, and means four different things.

The list, meanwhile, was a spreadsheet built on one Saturday in January, and by the fourteenth of February it described the first of February. It had drifted for an ordinary reason. Sixty-two clients had written to four mailboxes over ten days while the person holding the spreadsheet was preparing returns. Whose mailbox counts as the record, once there’s more than one of them, is a question a practice has to answer deliberately, and running the firm inbox is where that gets settled. Corinne had left it open. In December she’d noticed the question and set it down.

The morning she nearly asked twice

On the seventeenth she started the second round, and the fourth message she wrote was to a client who had sent four of their six items on the eighth.

She caught it because something in the client’s name felt recently handled, and she went looking before she sent. The four had come in a single reply to a January thread, addressed to Marguerite, who’d acknowledged them properly and filed them. To Marguerite, a delivery going exactly as it should was a thing already handled.

The message she’d drafted asked for all six.

It’s worth sitting with what that message does. A client who spent a Sunday evening finding four documents opens a note nine days later asking for all six. What they take from it is either that their evening didn’t register or that the documents never arrived. Either way, the remaining two arrive on the same schedule as before. The receipt that prevents it, and why acknowledging a delivery by name is the cheapest chase a practice ever sends, belongs to the guide on document requests. This week is about something else.

What belongs to this week is an asymmetry that surprised her. A first ask is always right about what already arrived, because at that point everything is still outstanding. Every ask after the first can be wrong about it. So the risk in a chasing round sits in the rounds that follow it. It grows with every day and every delivery in between. And it grows fastest in the firm that’s busiest, which is the firm least able to check.

Why a second round costs more than a first

The first round’s cost per client is bounded by the size of the request. Six items, a paragraph, four minutes.

The second round’s cost per client is bounded by everything that’s happened since. By the seventeenth, that was fifteen days of traffic across four mailboxes, belonging to people who were all doing their jobs correctly. Every safe version of that message costs the same reading: the client’s mail since the second, which takes about as long as reading the client’s mail since the second.

Which is exactly why most second rounds in most practices get written from the list instead. It’s faster, and it’s faster because it skips the checking, and the checking is the part that keeps it right.

Corinne wrote her second round from the threads. Thirty-one clients, most of a Sunday. She moved nine of them to the telephone, on the reasoning that a call settles in ninety seconds what an email settles in four days, and that some of the nine were people whose silence she already understood. Which lever to pull on a third attempt, and why an identical message sent twice is a message sent once, is the other half of the document request guide, and it reads the same in February as it does in any other month.

What does change in February is the date. When to ask again is arithmetic rather than manners. Take the filing deadline, subtract whatever your own side still has to do after the thing lands, then subtract the queue already on the desks. That sum returns a much earlier answer in the third week of February than the same sum returns in July, and inbox zero during busy season sets out why. Corinne’s answer, for the eighty-six, was nine days for the first round and seven for the second. It was going to keep shortening, because the deadline is the only term in that sum that moves on its own.

The part that had stopped needing her

Some of February was cheaper than it would have been. It’s worth being exact about which parts, because the parts that stayed expensive are the point of this chapter.

Point had been reading her mailbox since the first week of December. By February there were four ordinary things Point did that a chasing month rewards. Mail arrives ranked on what it costs to leave rather than on when it was sent, so a client with a date against them comes up ahead of a software renewal, and the weighing behind that has a guide of its own. Every thread carries a line saying what’s in it before she opens it, which on a thread carrying documents is nearly the whole question, since all she wants to know is whether something came and whether it was what she asked for. Attachments come out of the threads that carried them and gather into one dated list against a client’s name, with the message each of them rode in on still attached. And the acknowledgments go out drafted in her own words, so a receipt naming what has just landed is an edit rather than a composition, which is why she raised that one action to run without her back in January.

Then a fifth, which is the one that matters most in a month like this. A request she sends is held as something she’s owed rather than filed into sent items. It comes back to her on the date she set rather than the day it occurs to her. When the answer arrives, the follow-up stands down. Point marks it as looking finished, with the reason in plain sight, and waits for her to agree. That’s the seventeenth of February, handled before she opens the draft. It’s also the only reason an automatic reminder is safe to point at a client at all, because a reminder that doesn’t know what already arrived is worse than no reminder.

The dial holds a separate place for each type of action. Review is where they all begin, so a thing gets readied and then held until she looks at it. Corinne raised the acknowledgments and left the rest where they were. She keeps anything that names a consequence to a client at review, and she plans to keep it there. Point sits on the mailbox the practice already had, so everything stayed where it was, and everything Point does is listed on benefits.

Now the honest part.

The follow-up stands down when the answer arrives in her mailbox. Two of the eighty-six were requests that went out over Idris’s signature, into Idris’s threads, and those are Idris’s open loops in Idris’s account. The ask lives in his mailbox, and so does anything waiting on it.

And underneath that sits the larger boundary, the one good mail handling leaves exactly where it is. Point knows what’s come through the mailbox. Point doesn’t know that the Framptons owe two things and the Ashbrooks owed four, because that number was never in an email. It came out of last year’s return and a short conversation about what changed during the year, and it lives wherever the firm decided to put it, which in this firm was a spreadsheet. The copying step between a message and a list is the step that fails first, and email task management is about removing it for the obligations that arrive as sentences in other people’s mail. A register of what each client owes you works the other way round. It’s built before anybody writes to you at all, and a mailbox is the wrong shape to hold it.

So February split cleanly in two. The arriving half had gotten cheaper in January and stayed cheaper through February. The other half says what ought to have arrived and hasn’t, and it cost exactly what it had always cost, and it all came out of one person.

The only copy of the list

Idris caught her by the printer on the twenty-third and asked whether Vardy still owed the mileage log.

She said yes, and the van insurance, and that the mileage was likely to come as a photograph of a notebook. She was right about all three. It took her about six seconds, and it stayed unremarkable until she was halfway back to her desk.

Marguerite had asked her something of the same shape on the Friday. Idris asked again on the Monday, about a different client. Everyone was doing the reasonable thing. They were asking the only person in the building who could answer. She could answer because she’d spent a weekend in January building the list and eleven hours in February keeping it. Both of those had happened inside her own head and one spreadsheet.

By the first of March the practice had a register of what four hundred clients still owed it. The register was Corinne. She had eleven returns of her own waiting on the desk behind her, and the business engagements had not started yet.

Ready for a calmer inbox?

Join the private beta

We're onboarding a few teams at a time. Leave your email, confirm it once, and we'll send an invitation the moment a place opens.

By joining you agree to our privacy policy.

Private beta

What you're joining

It runs on the mail you have

Point sits on top of Gmail or Outlook. Your address, your history and your contacts stay exactly as they are, so there is nothing to migrate.

You set how much Point does

Out of the box everything waits for your review, replies included. You hand over only what you trust, one kind of work at a time.

Join the private beta

We're onboarding a few teams at a time. Leave your email, confirm it once, and we'll send an invitation the moment a place opens.

By joining you agree to our privacy policy.