A PBC list is the one document in an engagement both sides are meant to be reading at the same time. That’s the thing email is worst at. Attach it and you’ve issued copies. The work is keeping one of them true while the answers come back in fifty separate messages.
- A document request is one ask to one person, and then it’s finished. A PBC list is a standing register. Two organizations hold it, and it stays alive for the length of the job.
- Every line has two states, theirs and yours. Most lists carry one column for both. Provided and accepted can be two weeks apart.
- The item number is the one part of a list that email carries intact. Everything else gets paraphrased on the way.
- The list grows while you work it. So a percentage measured against the list you issued reports against a denominator that stopped existing in week two.
A register, not a request
Inside your office the list is a work plan. It’s everything the job needs before anybody can start it. The moment it leaves, it turns into something else. It becomes an instrument addressed to people who didn’t write it, don’t share your vocabulary, and have no idea which of its forty lines is the one holding everything up.
Four things separate it from an ordinary request for documents, and the rest of this follows from them.
It’s standing. A request gets answered and closes. A list stays open for weeks and changes state every few days while nobody has it open.
It’s shared. Two organizations are supposed to be looking at the same object, which is true of nothing else in the engagement. The workpapers are yours. The ledger is theirs. The list is meant to be one thing in two places.
It has several owners at both ends. A manager, a senior and whoever is doing the fieldwork on your side. On theirs, an owner, a controller, an outside bookkeeper, and a payroll bureau nobody mentioned at planning.
And it’s the record of what was asked and when. If the engagement runs late, the conversation is conducted against the list. So its dates have to be as accurate as its items.
The same object turns up under different names. An audit or a review calls it the PBC list. Due diligence calls it a request list. A tax practice calls it the organizer, plus the dozen things it turns out you also need once the organizer comes back. What’s on it varies enormously. How it behaves in a mailbox is the same every time.
The ask itself is a separate craft with a guide of its own. Naming a document the way the client’s own paperwork names it. Keeping a request small enough to be an errand. Asking for a date where the thing has yet to be issued. All of that is managing client document requests, and it works the same way on a numbered line. What changes is everything around the ask. One copy, two states, and a count that means something.
Who each line is addressed to
A list sent to the client arrives at a company, and a company can always assume somebody else has it.
The client is four people. An owner who signed the engagement and reads mail on a phone. A controller who has the ledger. A bookkeeper who works two days a week and holds the bank feeds. A payroll provider with no relationship to you whatsoever. Send forty lines to all of them and each one can reasonably assume one of the others is dealing with it.
A real fraction of any list also sits somewhere else entirely. The broker statement, the legal letter, the actuarial report, the bank confirmation, the last two years of a scheme the client has never logged into. Those lines are requests your client has to make of somebody else. The chain is one link longer than the list shows. A line like that wants two things written next to it on the day it’s issued: who has to be asked, and the fact that it’s a forwarded request rather than a search of a filing cabinet. Otherwise it looks like a bank statement on the page, and it’s a much bigger job than one.
So every line carries a name at issue, rather than at the first chase. Two things come out of that, and the second is the valuable one. Lines go to somebody who can act on them. And the lines you can name nobody for become visible in week one, while they’re still cheap, rather than in week six.
It also means the list should come apart. The bookkeeper wants their twelve lines rather than all forty. Four short lists, each sent to the person who can actually produce what’s on it, move faster than one long list sent to four people. The reason has nothing to do with reading speed. A list addressed to one named person is a task. The same list addressed to a company is a notice.
The argument for keeping any single ask short enough to be acted on that morning is made in managing client document requests. What’s different here is that the list stays long, because the list is the whole job. So the cut is by owner rather than by count.
The copy that forks
This one catches careful firms, and it costs more than every chase in the engagement put together.
You send the list out on the fourth. The controller works through it on Sunday evening. They tick eight rows and write useful notes in the last column: two don’t apply, one is with the bank, one was sent to a partner in March. Meanwhile your senior has added four rows discovered during planning, and sends the new version out on the eleventh. That version goes out without the controller’s notes, because those notes were in a file sitting in somebody’s sent items and nobody merged them.
Two weeks on, the client says they filled it in, which is true. The firm says it never arrived, which is also true. Both of them are looking at a spreadsheet with their own name on it.
Nobody was careless. A file sent by mail is a copy by definition, and a list with two copies has opinions where it should have a state.
There are two arrangements that hold, and they’re opposites.
The list lives somewhere both sides can open, and the mail carries only pointers to it and news about it. That costs a decision about access and a small amount of client patience in week one. It removes the fork completely.
Or the list stays yours, the client reads it rather than edits it, and answers come back as messages against item numbers. That costs you a transcription and removes the fork just as completely. It has a side effect worth more than the transcription: the client’s reasoning arrives as prose. “We sold the van in March” is information a tick in a cell can never give you, and it’s the sentence that closes three lines at once.
What fails is the arrangement in the middle, which is the one most firms are running. Send an editable copy, receive an edited copy back, merge the two by eye. That merge is a manual reconciliation between two spreadsheets. It’s usually done by whoever is least busy, usually at the end of a day, and it’s the most error-prone act in the whole engagement.
One rule sits on top of whichever you pick. Whatever the client has to read in order to act should be readable the moment it opens. A status message of twelve numbered lines in the body is read on a train. A workbook with a frozen header row and conditional formatting is opened on Thursday, if at all.
The only thing email carries intact
Prose about documents is ambiguous, and everybody involved is fluent enough to miss it. “Sent the bank stuff.” “The other statement.” “That one you asked about last week.” Each of those needs interpreting, and the interpreting is done from memory by whoever opens the message, with the list somewhere else.
A number means one thing. Two rules make it work, and neither is interesting.
Numbers are permanent. Item 14 is item 14 in the first version, the fourth version and next February’s rollforward. A new line takes the next unused number, and rows keep their numbers however untidy that looks. The version of this that costs real money is a renumber between two issues of the list. After it, the client’s “we have sent 12 and 14” names two different documents on each side, and both sides believe the reconciliation has been done.
Numbers travel. Ask for them in replies, put one in the subject line when an item earns a thread of its own, and use them at the front of file names. Clients do this once asked, because quoting a number is less work than describing a document.
What it buys is that reconciliation becomes mechanical. A reply reading “3, 7 and 12 attached, 9 does not apply, we sold the van in March” updates four lines in fifteen seconds. Anyone who opens the message can do it, rather than only the person who wrote the list. That last part is what carries the engagement through somebody being away for a week.
The number is your handle on a line and the description is theirs, and a line wants both. The number survives a phone call, a forward and a photograph of a document taken at a kitchen table. The description lets somebody recognize the thing in front of them as the thing you meant.
Follow-up items hang off the line that produced them. The three purchase invoices the fixed asset register turned up are 22.1, 22.2 and 22.3. It costs nothing to write them that way, and it makes the next section countable.
Provided is not accepted
Most lists carry one status column, and the words in it belong to one side. Outstanding and received are your words. Sent it and not yet are theirs. They look like the same two states, and they describe different ones.
Between them sits a third state, and it’s the one every engagement spends weeks inside: it arrived, and nobody has looked at it. Your status column has nowhere to put that.
Plenty can be waiting in there. It’s the wrong period. It’s the right period, unsigned. It’s a summary where you needed the detail behind it. It’s exactly right and raises three new questions. In every one of those the client is entitled to believe they have provided the item, and you’re entitled to say you’re still waiting on it, and both are true, because received is being asked to carry two meanings.
Two things follow.
A line closes when somebody has opened the file and it’s usable. Until then it has landed, which is a different word and deserves to look different on the page. Closing on arrival is what produces the conversation where a firm tells a client they’re all done on Tuesday and reopens four items on Thursday, and the second time that happens the list stops being believed.
And keep their state where they can see it, alongside yours. A line reading “sent March 9, with us, not yet reviewed” is honest, it tells a client their Sunday counted, and it stops a document being sent twice. It also shows you something your own column hides. How much of what’s outstanding is sitting with them, and how much is sitting with you. On a slow engagement that split is usually the entire answer, and it’s usually a surprise to the firm.
Why an acknowledgment is worth writing at all, and what it does to the chasing you’d otherwise have to do, belongs to managing client document requests. What belongs here is narrower. A list with one status column has nowhere to put the difference between a document being sent and a document being any use.
The list grows while you work it
Every document you receive makes more items. The bank statement raises a transfer nobody can explain. The fixed asset register raises three purchase invoices. The trial balance raises two reconciliations and a question about a director’s loan. On an audit that is most of fieldwork. On a compilation it’s most of the questions. On a tax return it’s the follow-up that only exists once the client has answered, which is why January could never have held it.
So the list you’re working is a different list from the one you issued. A percentage computed against the original reports on a denominator that stopped existing in week two, which is why the status number reads sixty, then seventy, then sixty-eight. A figure that goes backwards is a figure a client stops reading.
Two numbers answer what one number can’t, and they answer different questions.
How many items are open now, and whether that fell this week. That’s progress, and it’s the only honest form of it.
How many of the open items are ones you added rather than ones you issued. That’s scope, and it’s the number worth watching internally from the first week.
The second one has a conversation attached, and the timing of that conversation is most of its value. A list that has doubled means a job larger than the one that was priced, rather than a slow client. Saying so in week three is a conversation. Saying so in week nine is an argument. The list is the evidence either way, which is the practical reason its dates have to be right.
There’s a smaller reason to keep the two kinds apart. The items you added are your questions, so they’re yours to word properly and yours to send in batches. Released one at a time as they occur to you, they read to the client as being nibbled at, and a client who feels nibbled at answers more slowly than one who gets four questions on a Tuesday.
At the end of the job, those added items are the part worth keeping. They’re the questions this client’s records raise every year, and next year they belong on the list as issued rather than being rediscovered in week four. That’s what a rollforward is actually for. The rows are already in the template. The value is in the annotations: the lines that never apply to this client, the ones that always come from the bookkeeper rather than the owner, the one that took six weeks because it comes from a bank. Rebuilding from a clean template each year gets you a list where six of the forty lines are irrelevant, and a list carrying six irrelevant lines has taught the client, correctly, that it can be skimmed.
Which client takes six weeks and two phone calls is a fact about the client, and where to write that down is managing client document requests. What belongs on the list is narrower and easier to keep: which of its own lines this client’s books always turn into three more. What all of it feels like from inside a practice in the middle of March, as a week rather than as a method, is told in tax season without the inbox spiral.
Where does Point fit?
All of the above runs on a spreadsheet and a telephone, and it has done for as long as there have been engagements. The careful firms run it well. What a tool changes is which half a person is carrying. The noticing, the matching and the first draft of the words move. The deciding stays with you.
Point reads the mailbox ahead of you and weighs everything in it by how much it matters and how soon. So a controller’s reply naming three items sits above the renewal notice on the morning both arrive. That weighing is explained properly in how triage decides what needs you. Every thread carries its summary in a line, which on a delivery thread answers the only question you have: whether something came, and whether it was for the period you asked about.
Three things fit a list in particular. Attachments gather into a single list instead of scattering through threads, each one still linked to the message that delivered it, which is the raw material of any reconciliation against numbered lines. Put a question to a document, and the answer arrives showing the place in the file it was read from, which shortens the walk from landed to accepted more than anything else here. And a standing request in plain words covers the item you’re genuinely waiting on. Ask to hear when the signed representation letter arrives, and you hear once, on the day it does, rather than going to look.
The waiting is handled the same way. A request buried three paragraphs into a client’s message turns into a dated item, and nobody retypes it. Every request you send stays visible as an open loop with your own date attached, and it surfaces again on that date rather than whenever the client next crosses your mind. Where the answer has already landed, the reminder flags itself as probably settled and waits for you to agree. So nobody chases item 14 the morning after item 14 arrived.
Replies come back drafted in the way you write, so the status message naming what’s in and what’s still open starts as something you correct rather than something you compose. On the day a list conversation turns into asking the controller for twenty minutes, Point handles that scheduling back-and-forth itself. How far Point goes on its own is a separate setting per kind of action, and every one of them arrives set to review. The work is prepared, then it waits. The dial covers that setting in full. The first kind worth raising is acknowledging a delivery. The message telling a client their list has doubled wants somebody’s eyes on it first. What was done is written down in order with times against it and can be reversed from there, apart from the exception every mail tool shares: a message already sitting on somebody else’s server has been sent.
Connecting is a sign-in to the mail account the practice already uses, on Google or on Microsoft, so the address on the engagement letter stays exactly as it is.
The list itself stays with you. Point holds no item 14, no status column, and no view on whether the fixed asset register was for the right year. The numbering, the owner against each line, the two states and the count of what you added are yours, and they’re the parts of this that are the actual work. The benefits page is the whole inventory, and Point for accountants works through it in the setting of a practice. Whether a tool ought to be reading engagement mail in the first place is a prior question, answered at length in what AI may safely be pointed at in a practice.
Common questions
Should the PBC list go out as a spreadsheet attachment?
Sent as something to read, it’s fine. Sent as something to fill in, it has already forked. The distinction is whether the copy the client is holding can drift away from yours while you both work, rather than anything about the file type. If the client is going to write in it, the copy needs to be one you both open rather than one each of you keeps. Where that’s out of reach, hold the list yourself and take answers as numbered replies in the body of a message. It costs a few minutes of transcription per round. It buys a single state, plus the client’s reasons in their own words, which a tick in a cell never gives you.
How often should we reissue the list?
On a change of state, rather than on a calendar. A weekly reissue that looks the same as last week’s teaches a client that the list is a mailing rather than a record, and by the fourth one it’s being skimmed on the way to the next thing. What earns a reissue is news: the lines closed since last time, the lines added and what raised them, and the count of what’s open now with the direction it moved. If a week has genuinely changed nothing, that’s still worth saying, and it’s one sentence rather than an attachment.
Who should own the list inside the firm?
One named person, chosen for something other than seniority. The list’s accuracy is a function of how fast an arrival reaches it, so the owner is whoever is reliably reading the mail every day. What the senior person owns is different in kind: deciding that a line doesn’t apply, and having the conversation when the items you added start to outnumber the items you issued. Splitting it that way also answers the time-off question, because a list kept by number can be updated by anyone who can read a reply. If arrivals are currently landing in four mailboxes rather than one, that’s the prior problem, and running the firm inbox is where it gets settled.
The client says they have sent everything and our list says otherwise.
Both statements are usually true, which is why arguing about it never resolves anything. Answer with numbers instead of with a position:
- what you hold against 3, 7 and 12
- what’s still open
- the group you do have and can’t yet use, with the reason for each
That last group is what the disagreement is almost always about, and naming it is the only version of the sentence that lets both sides be right. If it happens twice with the same client, the fault is in the list rather than in them. A single status column has been asked to hold two people’s meaning of the word received.
Would a portal or a request tracker fix this?
It fixes one of the five problems above, and it’s the one with the highest cost, so that’s worth something. A shared register with a status against each line removes the fork outright and gives both sides one place to look. The rest stays with you: who each line is addressed to, whether an item closes on arrival, and whether the list can tell an item you issued from an item your own review created. That last count is the one that tells you whether the job has grown. Those are decisions about how the list is run, and any tool inherits them rather than supplying them. Whether the chasing itself gets easier is a different question, and it’s answered in managing client document requests.
The short version
A PBC list is a register two organizations share, and email is the one channel that can’t share anything. So the jobs are these. Address each line to a person at the moment you issue it, and mark the lines the client has to obtain from somebody else, because those are a longer chain than they look. Keep exactly one copy authoritative. Either it lives somewhere you both open, or you hold it yourself and take answers as numbered replies. Leave the merge in the middle alone. Number every line permanently and ask for numbers back, because a number is the only thing that travels through a mailbox intact. Keep their state as well as yours. Close a line once somebody has opened the file and it works. Then count what’s open now, and how much of it you added yourself. The second number is the one that tells you the job has grown while the first was standing still. This collection carries a guide for each of the other recurring jobs, and the buying question gets settled in AI email for accountants.