Marcus said yes on Tuesday, in the kitchen, between two other things. The Hallett file goes over to the surveyor. He meant it then and he means it now. It’s Thursday afternoon, and you still don’t know whether it went.
There’s nothing to open. The handoff happened out loud, so it left no thread, no subject line, no sent message filed under the morning you typed it. What you have is a memory of a conversation. You also have a feeling that’s been getting worse since Wednesday. The one instrument you own for settling it is to walk eight feet and ask. However you word the question, it’ll sound like you doubted he’d do it.
The chapter before this one was about a loop that went quiet at the far end of a thread you can still open. This one is about the loop that stayed spoken: work you handed to somebody, off your desk and still entirely your problem.
- Handing work over makes two loops out of one. There’s the one you owe the client, and the one they owe you, which sits inside it with less time in it.
- The doing moves to them. What you answer for stays with you, and in regulated work somebody has written that down.
- Everything the tracking needs is in the room while the two of you are still talking. Reconstructing it afterward costs a phone call.
- The cost of checking on people has been measured twice, with different answers. Both point the same way, and most people guess the other way.
Off your desk is not off your list
The relief you feel when somebody takes a job off you is real. It’s also the whole problem. Something did leave, and it was the doing. The knowing stayed with you. Those two travel together often enough that you stop noticing they come apart.
Three things make this different from a client who has stopped replying.
All you have is a memory. A quiet thread is at least a thing. It has a date, a subject line, your own words at the bottom of it. A handoff made in a corridor lives in two memories that have already started to differ. Catching something that arrived as speech is its own small skill, and adding a task in five seconds is where it’s worked through.
The date stayed behind. You told the client the surveyor would have it by Friday. Marcus heard something closer to this week. Both of you were honest, and both of you missed it. The date lived in your message to the client. The handoff happened in the kitchen. When Friday comes, it’s your name on the promise.
Two loops now, and the inner one is shorter. The client’s loop closes on Friday. Marcus’s loop has to close before that, with room left over for whatever comes back wrong. How much room is a number you can estimate. Most people leave it to feel, which is why the wrong surveyor turns up at 4:30 on the Friday.
So the sentence worth keeping is short. The work left your desk. It stayed on your list. The only question is whether your list knows that.
The doing moves but the answering stays
If your work is regulated, this part is written down. It’s worth reading once, because it tells you what the tracking is for.
Take audit, where the drafting is most explicit. The PCAOB’s supervision standard, AS 1201, opens by putting the whole engagement on one person: “The engagement partner is responsible for the engagement and its performance. Accordingly, the engagement partner is responsible for proper supervision of the work of engagement team members (including engagement team members outside the engagement partner’s firm).” Hold on to the parenthesis. It reaches the person who works in another building and reports to somebody else, and it holds you responsible all the same.
That governs audits performed under PCAOB standards, so most readers of this series sit outside it. The tax side reaches much further. Treasury Department Circular No. 230 gets there at section 10.36, applicable beginning June 12, 2014. It names anyone with “principal authority and responsibility for overseeing a firm’s practice”. That person must “take reasonable steps to ensure that the firm has adequate procedures in effect for all members, associates, and employees” for complying with the rules.
The discipline provision underneath it is the sentence to notice, because of what it does with ignorance. An individual is exposed where they “know or should know” that people in the firm have engaged in a pattern or practice that does not comply. The exposure lands when they then, “through willfulness, recklessness, or gross incompetence”, fail to take prompt action to correct it.
Be careful how far you stretch that. Section 10.36 is about the firm’s procedures rather than about your Thursday. The bar it sets is high, and a late surveyor sits a long way below it. What it settles is the direction of travel. The obligation sits with the person overseeing the practice. Handing work to somebody moves the work, and leaves the obligation where it was. And “should know” is doing real work in a sentence about a person who did not know.
Consultants and advisors reach the same place by a different road, with no regulator in the picture. There’s a client who hired you, an engagement that names you, and an invoice with your firm on it. Whatever you subcontract, those three documents stay exactly as they are.
So the tracking is the residue of an obligation that stayed behind when the work went. If keeping a list of what other people owe you feels distasteful, sit with that for a moment. The alternative isn’t trusting people more. It’s answering for work you decided not to look at.
What to record before they walk away
The first chapter set out what any open loop has to carry: which way it points, when it’s due, what counts as done, and the words it came from. All four apply here. A handoff needs five more. Every one of them is free while the conversation is still happening, and costs a phone call afterward.
A name, and one name. One person, said out loud. A job given to a room stays in the room, and the reason that chapter gave for it is a measured finding rather than a slogan. If you genuinely don’t mind who does it, somebody still has to pick, and that pick is the handoff. The handoff starts when the name does.
Your date, not the client’s date. Work out how long you’d need to fix the thing yourself if what came back was wrong. Set the return date that far ahead of the real deadline. That gap is the only protection the arrangement has, and it’s an honest measure of your exposure. A handoff with a zero-day gap is a bet.
What has to be true for it to be finished. Write it as “the surveyor has it and has acknowledged it”, rather than “send the Hallett file to the surveyor”. The difference sounds like pedantry for about as long as it takes for a file to sit in somebody’s outbox over a weekend. The finish line for handed-off work is nearly always a fact about a third party. The person doing the work will reasonably assume their part ended when they pressed send.
Where you will see it without asking. A copy on the outgoing message, the shared folder, the portal status, the reply that lands in both your mailboxes. Decide this at the handoff and checking costs you ten seconds of reading. Skip it and checking costs you a conversation, which is why it stops happening. What you’re asking for is a place in the path of the thing itself. That’s a smaller request than a progress report, and a better one.
What happens if it misses the date. Agreed in the kitchen, this is one cheerful sentence: if the surveyor hasn’t confirmed by Thursday, tell me and I’ll call them. Left to the Friday, when it matters, it’s a hard conversation held at speed by somebody who’s already annoyed.
Five lines, thirty seconds. What makes them worth writing is the timing. The awkward parts of the arrangement get settled while both of you are relaxed, at the one moment when raising them is normal.
There’s a second version of this question for two people who share a practice, where the handoff has to be a repeatable form rather than a note you keep on your own side. That has its own treatment in when an email falls through the cracks between you. What follows here is the tracking rather than the transfer.
The return leg nobody agrees on
Go back to AS 1201 for a moment, because it does something ordinary delegation rarely does. Among the supervisory activities in paragraph .05 is an instruction to “direct engagement team members to bring significant accounting and auditing issues arising during the audit to the attention of the engagement partner or other engagement team members performing supervisory activities.”
Notice where the burden falls. The supervisor gives the direction, in advance, about what comes back up. The junior person is spared the judgment call about whether this is the kind of thing the partner would want to hear.
“Keep me posted” does the opposite. It hands the hardest judgment in the whole arrangement, when do I need to know, to the person with the least information about why the date matters. That’s also the person with the strongest reason to keep their hand down. Reporting a problem looks like reporting a failure, and it looks most like one to the people newest in the job. So what you get is silence. Silence from a colleague is exactly as ambiguous as silence from a client, with the added complication that you see them at lunch.
Two things fix it, and both are said at the handoff.
Name the trigger rather than the frequency. Tell me if the surveyor hasn’t acknowledged by Thursday. Tell me if the drawings turn out to be the old set. Tell me if this is going to need more than an hour. Each of those is a condition somebody can check on its own terms, with no guessing about what you’d want to hear.
Make the report scheduled rather than exceptional. A note on Thursday, news or no news, costs almost nothing. It also takes the confession out of sending one. A routine message is easy to write.
Then agree the day on which their silence starts to mean something. That’s the same idea the last chapter applied to a quiet thread, moved to the front where it’s cheap.
Why you keep deciding not to ask
You’ve talked yourself out of asking four times now, and the fourth took longer than the first. That reluctance is well founded. Checking really does have a price, and there’s a good experiment about it and a better one about how large the price actually is.
Armin Falk and Michael Kosfeld set up a principal and an agent. The principal could leave the agent to choose freely how much to produce, or impose a minimum first. In The Hidden Costs of Control, published in the American Economic Review in December 2006, they reported that imposing the minimum backfired: “control entails hidden costs since most agents reduce their performance as a response to the principal’s controlling decision.” Asked why, the agents talked about the signal rather than the money. “Most agents who react negatively say that they perceive the controlling decision as a signal of distrust and a limitation of their choice autonomy.”
That’s the finding everybody quotes, usually as though it meant don’t check. The follow-up work says something more useful. Anthony Ziegelmeyer, Katrin Schmelz and Matteo Ploner ran the original treatments again with 476 subjects. They published the result in Experimental Economics in 2012 as Hidden costs of control: four repetitions and an extension. Their summary: “We largely confirm the existence of hidden costs of control but, contrary to the original study, hidden costs of control are usually not substantial enough to significantly undermine the effectiveness of economic incentives.”
These are laboratory games with cash payoffs between people who had never met, and control in them meant taking options away rather than asking a colleague where a file stands. Take the direction and leave the size. The cost of checking is real, it’s paid in the other person’s motivation, and it’s usually smaller than the thing it buys. So spend that cost deliberately, on purpose, at a moment you chose. Spend it by accident at 4:30 on a Friday and your tone does the damage rather than the question.
Three things make a check cheap.
It was agreed in advance. This is most of it. A question the two of you set on Tuesday is Thursday arriving on schedule. The whole asymmetry is in who appears to have decided, and that’s why every field in the previous section gets set at the handoff rather than when you need it.
It is about the work, not the person. Where does the Hallett file stand, rather than did you do the Hallett file. The first asks about an object, and either of you might answer it. The second grades somebody. They feel the difference before the sentence ends, and so do you, which is why the second one takes four attempts to say.
It’s the same for everybody. Selective checking is the checking that reads as suspicion, because that’s what it is. Check the new hire’s work and leave the senior’s, and you’ve told both of them something about themselves. The file has nothing to do with it.
There’s a cost on the other side that nobody counts, and it belongs in this section rather than as a consolation at the end of it. The question on Thursday is the kindness. The person you skipped is the one who finds out on Friday, in front of a client, that the thing they thought was fine is broken, with no time to fix it. Ask anybody who has had both done to them. Being asked on Thursday wins.
The eight feet is its own factor and worth naming. You’ve chased the client’s controller three times this month without a second thought, and Marcus not once, and the difference is the room. Marcus can react in front of you, and the controller can’t. Proximity turns an administrative question into a social act. It’s the same question either way.
The people who will never see your list
Most of what you’re waiting on sits with somebody you can only ask. The client’s bookkeeper, the attorney, the surveyor, the payroll provider, another firm you split a job with, or the client themselves. AS 1201’s parenthesis about people outside the firm is the regulated version of a fact you already live with. The work belongs to them. The outcome is still yours.
What changes across those relationships is the escalation. With your own staff you can direct. With a vendor you have a contract and a service level, so the second conversation is a different one and usually a shorter one. With a client you ask. Asking a client for something they owe you has its own machinery, most of it about why the thing is still sitting on their side, which managing client document requests without the chasing works through properly.
The register stays the same throughout. Name, date, what finished looks like, where you’ll see it, what happens if it misses the date. A handoff to a partner at another firm needs the same five lines as a handoff to your junior. It needs them more, because the building has nobody in it to notice.
One case behaves differently enough to separate out. Sometimes what you handed over is a decision: the partner who has to sign, the client who has to choose between two accounting treatments, the committee that meets monthly. A decision sits either made or pending, with nothing in between to supervise or report on. What you have is a wait, a known return date, and a single fact you need. The only useful question is whether the decision has been made yet. Most people file those as tasks, and the list fills with rows that sit still and can’t be worked on. A list like that stops being read within a month.
In a firm where two people hand work to each other all day, there’s a further question about whether you both see the same picture of who’s holding what. That’s a different subject with a different answer, and it’s when you stop having to ask who has it.
The five ways a handoff ends
The first chapter made the point that every way a loop ends is something somebody does. Time alone closes nothing. Handed-off work has five endings, and everybody plans for one of them.
It comes back done. This still takes an act from you, which is agreeing that it’s done. Delegated work has a particular way of staying open forever. It arrives, you glance at it, you mean to look properly, and the row outlives the thing it was tracking by three weeks.
It comes back partly done. The normal case, and the one that needs a decision rather than a sigh. The remainder is a new handoff with its own date, or it’s yours now. Leave it unnamed and it becomes yours anyway, at nine in the evening, and nobody learns anything.
You take it back. People avoid this ending because it feels like a verdict on a colleague, so instead they do the work quietly, which is the worst available version. Your colleague stays in the dark, you teach yourself that handing off fails, and you add a job to a week that was already the reason you handed it off. Say it plainly and early: I’m going to take the Hallett file back, I need it today, nothing has gone wrong. That’s an ending. Silence leaves the row open.
It stops being needed. Scopes change, clients decide differently, the meeting moves. A handoff still standing after the need went is somebody’s Saturday, and the cancellation takes eight words.
It escalates. Where the obstacle is authority rather than effort, the same person can be asked forever and the thing stays put. That’s a different message to a different person, and it needs its own date.
Whichever it is, close the row deliberately, because the closing is where the only useful information in this whole system gets made. After a quarter of doing it you’ll know who returns things two days early, who returns them on the afternoon of the date, and who has to be asked twice. That’s knowledge about your own week. It’s the input to the one decision that actually reduces the amount of chasing you do, which is who you hand the next thing to, and how much room you leave when you do.
What Point holds after the work leaves
Point is the mail client itself, and your team’s chat sits in the same feed as the mail. A handoff typed to a colleague at 9:20 sits in the same place as the client message that caused it. One surface, one app, nothing to copy across.
Ask somebody for something in that feed and Point lifts the commitment out of the sentence with its date attached. The ask joins the same list as the work you owe, marked as something you’re waiting on rather than something to do, with the conversation it came from one step away. You asked a colleague for something, in the words you were going to use anyway. The tracking happened while you typed.
The same holds for an ask you send by mail, to the surveyor or the client’s bookkeeper or the firm you split the job with. Point holds work you’ve handed out as a wait, and you’re prompted to chase it at the point where chasing still leaves room. Where that point falls is the subject of the next chapter rather than this one.
Where the finish line is an event rather than a reply, say so in plain words and it becomes a watch. Tell me when the surveyor acknowledges. Tell me when the portal shows it filed. The watch speaks once, when it fires, and stays quiet the rest of the time. Setting your first watch in plain words is the how of that.
Everything gathers into a single list, whatever the conversation and whichever of your businesses it belongs to. That matters here more than anywhere else in the series, because handed-off work is precisely what ends up in the second list nobody reads.
Every type of action has a level you set for it yourself, running from suggest and stop, through prepare it and leave it out, to get on with it. All of them start at the middle level, so moving one up is something you go and do. Point’s work leaves a record in ordinary sentences you can read straight through, and reversing something starts from the line that logged it. One standing exception: a message already delivered is sitting on somebody else’s server, and it’s past reach. The wider inventory is on the benefits page.
Point holds your half: the ask, the date, the wait, the prompt. Managing Marcus stays with you. Whether the file reaches the surveyor is still between the two of you, and some Thursdays still end with a walk across the office.
The list is right, and the week is long
Say you do all of it. Every handoff gets its name and its date and its finish line while the conversation is still warm. The rows are accurate. The list is complete.
It’s now the fourteenth of the month, you have forty-one open rows, eleven of them are things other people owe you, and four of those are due this week. Every one of those facts is correct and sitting in a list. The list has stayed quiet all morning, because a list has no voice. It waits to be opened.
Which is the assumption everything above quietly rests on. You have to remember to look, on a day you picked weeks ago, in the week that was busy enough to make the delegation necessary in the first place. And looking is the wrong unit anyway. The useful moment to act on one of those rows sits earlier than the day it’s due, at the point where a question still leaves room for an answer. That point falls in one place for a colleague eight feet away, and another for a surveyor who takes four days to reply.
Knowing when to chase is one thing. Being told when to chase is another, and it’s the one that survives a bad week. That is the next chapter.