Eleven minutes on the Tuesday told you what eight weeks of Thursdays hadn’t. The night shift question and the remediation phase are one item. They’re one person who hasn’t decided anything since October. It arrived under two subject lines, so you read it as two scheduling problems.
So the list has done its job and handed you a conclusion. Reminding is the wrong instrument here. Everybody remembers. Ray has read the line eight times.
That number is where this part starts. It’s the one fact in the situation you’ve never counted, and you had a fair reason to skip it. Sitting down to write a chase, worrying over the wording, sending it on purpose: you have done that zero times. The ask has gone out eight.
The count you never made
Work it back through the Thursdays. The night shift question went into the update on October 15, in “what I need,” with a name on it and a date. On October 22 it dropped into “open.” That’s what the edit does with an unanswered ask. Then October 29. Then November 5, 12, 19, 26, and December 3. One request, eight deliveries of it. The remediation phase has been through the same machinery four times since November 12.
The edit is what hides this from you. Carrying a line forward is free, which is most of why the method works and all of why it fails here. You see eight weeks as one line you kept. Ray sees the eighth week running in which a supplier has noted that Ray still owes something. That message goes to Dana and Alex as well.
Which is what nagging actually is. Nagging is a property of the sequence, and each of those eight lines was short, dated, factual and entirely polite. A ninth wording leaves what the first eight built exactly where it is. That’s why “how do I word this without sounding pushy” is the wrong question. People ask it because the wording is the only part of the sequence they can see.
Two tests are worth running before you send anything else.
Has anything happened since the last time you asked? Time passing is a different thing from an event. Look for something that could have changed the answer. A meeting. Somebody back from leave. A piece of your own work landing. If the newest fact is that it’s Thursday again, the message repeats, however you write it.
Could they answer it in exactly the words they’d have used four weeks ago? If yes, it’s the same question, whatever the sentence looks like.
Out of that comes the one cadence rule that holds in a delivery engagement, and it runs on events rather than on Thursdays. One ask per event. The engagement makes its own events, which is the useful part. Interim findings landing is an event. A site visit finishing is an event. A decision raised alongside work the client is actually reading gets an answer. The same decision raised in a quiet week waits. That’s also why the pass runs before a milestone rather than after it.
And a rule for the standing update itself. Three appearances is the limit. By the fourth week, an unanswered ask reads as a public score, kept by you, of one person’s silence in front of their colleagues. Take it out of the open block on the fourth week. It stays on your own list, where it belongs. What happens to it there is the rest of this page.
When several items are one item
Sort the open list by who owes it rather than by what it is. Items arrive sorted by subject, and they stay in that order until somebody re-sorts them. Which is why this view is a rare one.
Sorted by person, a delivery engagement shows one of two shapes. A spread, where four people each owe you something small. That’s a busy client, and patience covers it. Or a spike, where one name holds everything open and every other name is clear.
A spike is a finding in itself, and it says more than that one person runs slower than the rest. When one name holds every open item and every other name is clear, you don’t have several items. You have one obstacle with several subject lines attached to it.
Three tells confirm it.
They stopped moving at about the same time, even though they were raised weeks apart.
They’re all the same kind of thing. Kind, rather than topic. Everything that needs a signature. Everything that costs money. Everything that would have to be explained to somebody else.
And the person answers you normally about everything else. Ray came back on the badge question in four hours, and on the December site access in one day. Somebody who answers logistics inside a day and goes quiet on anything with a number in it is stuck, rather than busy. They’re stuck on one kind of question, and the kind is the information.
This changes the arithmetic of what you do next. Eight weeks of two problems gives you two attempts. One problem gives you one. One attempt spent well beats the four half-attempts you were about to make.
A question they can answer today
Here’s what being inside the work gives you, and what somebody chasing a proposal is still outside of. There’s a document with a date on it, and the date lives in the agreement rather than in your head.
“Have you had a chance to think about the remediation phase?” asks Ray to report on Ray. There’s one honest answer. Ray has given it twice already, and a third time costs a little more.
“Do you want the night shift in the report, or out of it?” asks about a thing that exists, one Ray can picture, on a date Ray already agreed to. Same decision underneath. Completely different to receive.
Three properties make the second one work. Name them and you can build the same question for a different engagement.
The date belongs to the work rather than to you. The report goes on December 18 because the statement of work says so. That leaves the question carrying the agreement’s deadline, which is one anybody can live with.
Both answers are usable. Out means section 6 is finished as it stands, and you write it on Friday. In means two nights on site, a price, and a different section 6. Either answer lets you do something on the Monday. You’re asking for an instruction rather than for news.
And the delay stays out of it. Every version of the answer lets Ray skip explaining eight weeks, which takes away the most expensive part of replying late.
The general point holds beyond this engagement. A quiet decision moves when you ask about the work it’s holding up rather than about the decision itself. You can both see the work. The decision is invisible to you both.
Somebody in the building already knows
You’ve been on the floor with Alex for eight weeks. Alex has coffee with the people who sit near Ray, and sits in meetings you’re outside. Alex knows things about the shape of December at Northgate. Inside the building those things are the weather, so nobody has thought to tell you.
So ask about the weather, and leave Ray out of it.
Is there a budget round going on at the moment? Does anything get decided in December, or does it all wait until January? When something like this gets approved here, does it go through Ray or past Ray? What comes back is usually a fact rather than an opinion. A capital budget that runs on a different calendar from the operating one. A freeze from the first of December. A committee that sits monthly. A reorganization. Somebody on leave until the eleventh.
There’s a line here, and it’s worth being exact about, because crossing it costs you the relationship that produces next year’s work. You can ask a client’s employee how their employer’s calendar works. Their sponsor’s private position stays off the table, and so does chasing on your behalf. The test is whether you’d be comfortable hearing Ray repeat the question back word for word. “Does anything get signed off in December?” passes that. “Do you know why Ray has not come back to me?” fails it.
The same applies to the phone, which tells you in fifteen minutes what eight weeks of email missed. Everything on the list above is the kind of thing people say out loud and leave out of writing. Give the call a subject other than the decision. “I am writing section 6 on Friday and I want to make sure I write it the right way round” is a call about your work. “I wanted to check in on where we are” is a chase with a dial tone, and it gets the same answer the emails got.
Writing it into the document
This is the move that does the most, and being in delivery is what makes it available. The unanswered decision goes into the report as a stated assumption, with its consequence visible.
Scope note. This review covers the day and late shifts. The night shift was raised on October 15 and has not been added to the scope, so the exception rates in section 4 and the routing recommendation in section 6 are calculated on two shifts of the three. If the night shift is brought into the review, both figures change, and the recommendation in section 6 may reverse.
Three things happen, and the report is the only place they can.
It reaches past the people your update reaches. A report gets read, forwarded and quoted by whoever is actually deciding. That includes the person above Ray, who has never seen your thread, and who may well be the reason this has sat still.
It moves the open item from your side to theirs. An unanswered email is your problem. A caveat in a document somebody is paying for has to be resolved before the document is usable for anything. And it’s sitting in front of the people who need to use it.
And it holds in March. When somebody asks why the night shift was left out, the answer is on page two of the document they accepted. Dated, in the copy they hold.
Two cautions. Write it as a boundary of the work, never as a complaint about the client. “was raised on October 15 and has not been added to the scope” is a fact. “we asked repeatedly and received no response” is a grievance, and it will be read as one for years. And show it to your contact before it goes in, in plain words, on the thread. That’s the same ordering the statement of work phase runs on, for the same reason. Everybody should meet a sentence about themselves on the thread first, ahead of the formal document.
The date you did not invent
Independents spend a lot of effort manufacturing deadlines, because a contract is what creates the real ones. In delivery you have two real ones, and you’ve probably said neither out loud.
The first is the report date. December 18, in the agreement, agreed in September by people who are still there.
The second matters more, and it’s the one almost everybody leaves unsaid. Putting the night shift in the report takes two nights on site and three days to work them up. So the last date on which a yes is still buildable is Friday December 11, rather than the 18th. A decision that arrives on the 15th is a no wearing a yes.
Say the second one once, as a fact about how the work gets made rather than as a demand on anybody’s calendar. “If it goes in, I need two nights on site and the week of the fourteenth entire, so the eleventh is the last day I can still build it into the report.” That’s arithmetic about your own hands, and arithmetic is a hard thing to push back on.
Then say the other half of it, which is the most useful thing you know and the thing Ray is missing entirely. After the eleventh, the night shift becomes a separate piece of work, with its own scope, its own approval and its own start date. That’s a larger thing to get agreed than the one currently sitting unanswered. People assume delay makes a decision cheaper. It almost always makes it more expensive. Say so plainly, with no edge on it, and it lands as a kindness.
And say it once. A date restated in three consecutive updates is a countdown, and a countdown is the exact thing this whole page is written to avoid.
Three that no message will move
Sometimes the wrong tool is the whole problem, and better writing leaves it exactly where it is.
It is money moving rather than a decision being made. A purchase order, an invoice release, a supplier record. That runs in a queue at the queue’s own speed, owned by somebody other than your sponsor, and everybody in it is indifferent to your work. Ask your contact for the name of the person who administers it. Then write to that person about a reference number. Every message to Ray about it is wasted.
It changes what was agreed. An approval that alters the scope, the price or the dates is a change to the agreement. It belongs on the thread where the agreement lives, rather than in the open block of a status email. Chasing it in the wrong file is how the record comes apart later.
Nothing has been raised anywhere. Ask your contact to name the meeting at which this would be decided. A name means a decision is pending in that building. Silence means asking will keep producing silence. The scoping call had a test for this, and it applies unchanged in week nine. Ask when the conversation is likely to happen. A date back means you’re waiting for an answer. Otherwise you’re waiting for something to be scheduled, which is a different problem with a different first move.
Parking it before the last day
You have two Thursdays left. Then the report goes, the engagement closes, and the standing channel you’ve been using for all of this stops existing.
So parking here is handover. It’s the last thing this method does.
Every open item gets an ending in the final update: done, dropped, or handed back. The three endings are the same ones as always. The one new rule is that you say each ending out loud, because after the 18th there’s a week missing in which anything would get tidied up.
The ones handed back go into the report as recommendations, with a number and a start date on each. Two nights of observation on the night shift and four days of analysis, priced, best done before the Q1 count. An open question in a final report dies with the report. A recommendation with a price is a thing somebody picks up in February with all of it already written down. An open question is a thing somebody has to reopen a conversation about, and February is when conversations stay closed.
Then tell your contact once that you’re taking it off your own list, and what it would take to put it back. Say it flat, with no edge on it and no closing gambit in it. Say it as an accurate statement of what you’re still holding and what you’ve let go, which is the last professional courtesy of the engagement and the one people remember.
All of this leaves the deciding to them. What it does is make the decision cheap to make later, possibly by somebody other than Ray, in a month when you’re somewhere else.
The counting Point can do
Everything above is judgment. Whether eight weeks of quiet is a busy client or a dead engagement. Whether the caveat goes in the report. Whether Alex is the right person to ask. That’s the work, and it’s why the client hired a person.
The count is the mechanical part, and the count is what this whole page turned on. An ask you sent stays on the books under whatever date you gave it, with its conversation attached. It comes back once the silence has run past what you allowed for, rather than on whichever morning you next reread last Thursday’s message. The mechanics of a thread that returns are worth reading once. The part that matters here is smaller. How many times you’ve asked, and since when, is something you look at, rather than something you reconstruct on a Tuesday in December.
Each item still carries its conversation, so the regrouping in the second section of this page is a thing you do by looking rather than by remembering. Whose name is on every open line is a question about a list. It’s a hard question while the list lives in eleven threads, and an easy one once the list is in front of you.
For the waiting itself, the plainer instrument is the standing request. Tell me when Ray replies on the remediation note. Tell me when anything arrives from their finance side. You hear once, on the day it happens, and every other day stays quiet, which is the whole of what setting a watch amounts to over an ordinary week. The checking stops being something you do. And when you want the message where Ray mentioned the capital budget, describing it in your own words is enough to find it.
One boundary works differently on this page than elsewhere in the series, and it’s worth stating rather than assuming. Point’s autonomy is a level you set separately per type of action, and every type starts at review. Everything above sits outside those levels entirely. Writing a scope note into a report, telephoning Alex, deciding that two items are one item: that stays yours at any setting. What Point holds is the record. What was asked, on what date, and what came back is logged with a time against it, and this method depends on the count being right. The activity log is the same idea pointed at Point’s own work.
And one limit decides this engagement. Point cannot see inside Northgate. Who can approve what and at what level, when their committees sit, whether the money you’re waiting on is capital or operating: those facts live in one place, which is inside people, and they arrive by asking. The benefits page is the flat list of what Point does do. Point for consultants is the same argument across a practice rather than one stuck decision. And Point is the whole of it.
What eight weeks of silence was worth
Some of it turns into an answer before the 18th and some of it stays quiet. The engagement ends either way.
What you’ve gained since October is a description of how Northgate decides things. That anything with a number on it goes past Ray to somebody you have never met. That the number in question is a capital one, which puts it in a different queue from the one your fee came out of. That the queue has a calendar, and the calendar restarts in January. That Alex knew all four of those in week two, and would have said so at any point for the asking.
All of that lives in the note you started keeping for yourself on the afternoon of the scoping call, rather than in your mailbox. It’s the most valuable page in the engagement now. It’s the only written account anywhere of how the next decision at this client will actually get made.
Which is the thing worth carrying out of the building. For eight weeks you read the silence as a delivery problem. Here is what it was. Ray was declining to answer, in December, a question that this organization answers in January, about money that is still to be allocated, for work that would start after your last day.
That’s next year’s engagement, arriving early and wearing the wrong subject line. Your inbox will stay quiet on the morning it turns into a live conversation, because it opens somewhere other than a message addressed to you.