The first PBC email of the year went out on the second of March, about six weeks later than it should have, and the six weeks are itemized in February.
It went to Ostrander Millwork, an S corporation with nine people on the payroll, and it carried twenty-two items. Idris sent forty-one more over that week and the next, which is most of the firm’s sixty business engagements. Behind all of them was a fifteenth of March that fell on a Sunday, which bought the practice one extra day and nothing else.
Read Ostrander’s twenty-two and the list splits down the middle, though nothing on the page marks the split.
Eleven of the items already existed. December bank statements, the payoff figure on the equipment note, the payroll bureau’s year-end reports, twelve months of card transactions. Somebody else produced every one of those, they are sitting behind a login, and the only open question is whether a human being goes and fetches them. That is January’s work in a different month, and by March Corinne’s practice was good at it.
The other eleven did not exist yet. A schedule of what the shop bought during the year and what it scrapped. A count of what was on the racks on the thirty-first of December. A reconciliation of what Pete Ostrander had put into the company and taken out of it, which is not a document at all. It is an argument, and its answer is a number somebody has to arrive at and then be willing to stand behind.
Two different asks, and the mailbox does not distinguish them. Neither, on the page, does the list. How a prepared-by-client list should be built and why a practice ends up running five copies of the same one is a job with a guide of its own, and Corinne’s list was a good list. What March taught her was about the eleven items on it that nobody had made yet.
The eleven that somebody has to make
An item you retrieve fails in one way. Nobody went and got it.
An item somebody has to build fails in four. They may not get to it. They may not know how. They may do it against the wrong definition of what you asked for. Or they may do part of it, decide that part is the whole, and send it.
That last one is the whole of this chapter, and it takes three weeks to become visible.
There is also a fact about business engagements that individual work never prepares a practice for, which is that the request and the labour and the reply belong to three different people. Corinne wrote to Pete Ostrander, because Pete signs the engagement letter and Pete is the client. Pete does not keep the books. Lena Rusk keeps them, two days a week, from her own house, with four other companies on the same rota. And the reply came back from Dee Aldridge in the Ostrander office, because Dee is the person who reads the address the firm actually writes to.
So the email lands on the one person who will do none of the work, gets forwarded to somebody outside the company who never saw the original ask, and is answered by a third party who is relaying. Every business engagement runs some version of that chain, and the version varies per client, and none of it is written down anywhere in the mailbox. The December habit of building the list of names from the engagement list rather than from memory, and of adding whoever writes on a client’s behalf, is what that fortnight was for, and it is worth more in March than it is in January, because in March the person who answers is almost never the person who was asked.
The second thing about the eleven is the dates, and Corinne’s list had one date on it. The sixteenth of March, which was the deadline, and which is a date for the return rather than for any item on the list. Twenty-two items sharing one date is twenty-two items with no order, and a client working a list with no order works it in the order the paperwork proves easy. The bank statements come first because the bank statements take four minutes. The inventory count comes last because the inventory count is a Saturday.
Which is exactly backwards from the firm’s side, where the count gates the return and the bank statements gate nothing.
What Lena had already built
Dee’s message arrived at twenty to five on Tuesday the tenth. Subject line, re: Ostrander Millwork 2025. Body, one sentence: Lena’s done the asset one, attached, she’s working through the rest.
The attachment was a spreadsheet. Eight rows, a date column, a description column, a cost column, and a total. It was titled fixed assets 2025. Idris opened it, saw a fixed asset schedule, saw eight additions that looked like the sort of thing a millwork shop buys in a year, and marked the item as in.
He was not being careless. It was a fixed asset schedule. It was the fixed asset schedule Lena had built in October, for the bank, because the equipment note carries a covenant and the bank wanted a picture of the collateral. She had it on her desktop, it was accurate as far as it went, and when an accountant asked her for a schedule of additions she sent the schedule of additions she had.
The last date on it was the nineteenth of September. There were no disposals on it at all, because a bank does not care what you scrapped, only what you still own.
Nobody found that out on the tenth of March. It was found on the second of April, by Marguerite, at preparation, with last year’s depreciation schedule open beside it.
Here is the debt February left, and here is what March does to it. In February the pattern was that a partial delivery is normal: two things asked for, one thing sent, no mention of the other. That is painful and it is not hidden. You can count it. Two minus one is one, and the one that did not come is still sitting on the list saying so.
On the business side the pattern is the same and the visibility is not. Half the items are built rather than fetched, so partial delivery is more common, not less. But a partial build does not arrive looking partial. It arrives as an attachment with the right name, in a thread that says here you go, from a person who believes they have answered you. It occupies exactly the same line in the mailbox as a complete one. It ticks exactly the same box on the list.
An absent document is a shape in the record. You can point at the gap. A schedule that stops in September is not a gap. It is a presence, and the only thing that distinguishes it from the real one is what a preparer finds when they read it against something else.
Between the tick and the reading
The gap between the tenth of March and the second of April is where the cost sits, and it is worth being precise about why it is not just three weeks of delay.
On the tenth, Lena Rusk had the file open. The question of what happened to the old panel saw was a question she could have answered from the room she was sitting in. On the second of April she is doing quarterly payroll for somebody else, she has closed that job out in her own head, and being asked to revisit a schedule she considered finished three weeks ago means reconstructing not only the numbers but her own reasoning about them. She will do it. It will take her four times as long, and there is a real chance the answer is worse.
On Marguerite’s side the arithmetic is different and no better. A return that has not been started is a return that has not been started. A return that is eighty per cent built and stops on a missing disposal is worse than that, because picking it back up costs an hour of rereading before any new work happens, and because it now occupies a slot on a desk while it waits. Corinne’s practice has seven people and every one of them was carrying something in that condition by the second week of April.
None of which is fixed by the calendar moving. Ostrander went on extension on the thirteenth of March, along with thirty-one of the firm’s sixty businesses, which is neither a failure nor a plan and is a season in its own right; what extension season does to a mailbox is the job version of it, and this arc reaches it later. What an extension buys is time on the filing. It does not buy time on the discovery. The schedule that stopped in September stopped in September on the tenth of March, and the only thing an extension changes is the date on which somebody finally reads it.
So the question underneath the whole month is not how fast a firm chases. It is how early a delivery gets read by somebody able to tell whether it is the thing. That is a preparer’s job, done on a file that is not yet the preparer’s, on the day it lands rather than on the day the file comes up. Corinne could see the shape of the answer by the middle of March. She could not see where the hours were.
The line above the attachment
Some of March cost less than it would have, and as in the two months before it, the parts that got cheaper and the parts that did not fall on a clean line.
Point had been on the practice’s mailboxes since the first week of December. Three things it does mattered more in March than they had in either month before.
The first is that the firm is on one surface rather than four. Three January deliveries had gone to Idris, for the ordinary reason that his name was at the bottom of the organizer those clients received, and Corinne neither saw them nor had cause to know she had not. In February that cost her two chases she could not write on the day she meant to. In March, with the business engagements running mostly through Idris and the follow-up work landing on whoever was free, the ordinary state of a client is that two people have touched it. What ends the question of who has a thing is not both of them seeing the same message, and that distinction has a guide of its own.
The second is that a question about a client can be asked rather than searched for. What has Ostrander sent since the second is a sentence, and it is answered out of the mail the firm actually holds, across the accounts it came into, without Corinne opening four folders and reconstructing a fortnight. Attachments are already gathered against the client they arrived for, each one still tied to the message that carried it, so the answer to what came is a list rather than an excavation.
The third is that a request goes out as something the firm is owed rather than as a message in sent items, and comes back on the date it was given rather than the day somebody remembers. When the reply arrives, the follow-up is marked as looking answered and waits for a human to agree, which is the only arrangement under which pointing an automatic reminder at a client is safe at all. Why a quiet thread has to be the mailbox’s problem rather than yours is what that whole subject is about.
Every kind of action carries its own place on the dial, and every one of them begins at review. Corinne had raised acknowledgements back in January and had moved nothing since. Nothing that tells a client what will be filed for them is going to be raised at all, this year or next. The dial is where that setting gets explained properly, and everything Point does is listed on benefits. None of it required the practice to move addresses, since Point signs in to the accounts already in use.
Now the boundary, and in March it is a sharper one than it was in either January or February.
Point read Dee’s message and put a line above it saying that a fixed asset schedule for 2025 was attached. That line was correct. It was correct in the way the message was correct, which is that both of them describe what the file says about itself. Whether eight rows is the right number of rows is not a question about the message. It is a comparison between this spreadsheet and last year’s depreciation schedule and a conversation about a panel saw, and two of those three things have never been in an email at all.
That is a useful test to carry, and it is more useful than asking whether a tool is an email client. Ask instead whether the thing holding your list can answer a question nobody has written to you about. A mailbox, however well it reads, answers questions about mail. A register of what sixty businesses owe you, item by item, with a state against each item, is answering a question that exists whether or not anybody sends anything, and a practice that needs one should buy one deliberately rather than hope a good inbox turns into it. What a good inbox genuinely removes is the reconstruction: the fortnight of threads you would otherwise read before you could write four sentences.
Which list is right
Dee got two chasing emails from the practice inside twenty-four hours.
Corinne’s went on the Thursday, for the inventory count and the shareholder reconciliation. Idris’s went on the Friday morning, for the inventory count and the disposals and a bank statement that had in fact arrived on the sixth. They had both been diligent. They had been diligent against two different spreadsheets, because Corinne’s register covered the individual work and had grown a business tab in early March, and Idris had built his own for his sixty when he sent the lists out, and neither of them had ever discussed it, because neither of them knew there was anything to discuss.
Dee replied to both of them on the Friday afternoon, and the whole message was four words.
Which list is right.
By the end of that week the practice had one, and it was not in anybody’s head and not on anybody’s laptop. That question, at least, the firm can now answer, and the answer took a decision rather than a weekend.
What it did not settle is the other one, the one the second of April asked and nobody had an hour for. A list can tell you that the fixed asset schedule arrived on the tenth of March. It cannot tell you that it is the wrong fixed asset schedule. Only a person reading it can, and only if they read it while the client can still remember why they built it that way.
On the second of April Corinne’s preparers had three hundred and nine individual returns between them, thirty-one business files that had moved into the month rather than out of it, and ten working days.