Chapter 9: Planning Season
The pastries had been cut into quarters, which was ambitious given how long they had been in the planning room.
Pree took a piece of croissant and used it to point at the calendar on the wall.
“I need Field Services for twenty minutes,” she said. “Engineering for fifteen. Client Support for all of it.”
Nikhil examined the grid. “You have Field Services for twenty minutes on Tuesday.”
“I have you on Tuesday. I need the person who’s actually been to the site.”
“He’s at the site.”
“Could he call?”
“He could. He’d be calling from a room full of equipment your client has asked him to fix.”
Kirstie nudged a plate away from her papers. “Could we put it Thursday after the external call? We’ve got the campaign review then, and I need the same product people.”
“The campaign review is already on Thursday,” I said. “It has a permission.”
“I know. I’m proposing we add Pree’s discussion to it.”
Pree looked at her. “For twenty minutes?”
“Possibly thirty. Once everyone’s there.”
“And then Marketing gets my client team for thirty minutes?”
“They could stay.”
“They could. They also have clients.”
We were meant to be identifying essential planning sessions for the rest of December. Gareth had asked the leads to bring the meetings they could not move, together with the people required for each. This had produced a wall of calendars and a smaller wall of people explaining why someone else’s calendar was wrong.
Anneke circled a Wednesday morning. “My deputy can attend either the migration review or the campaign preparation. She can’t attend both.”
“Could you attend one?” Kirstie asked.
“I’m on the release call.”
“Could the release call move?”
“It could. We’d have to ask the customer.”
Kirstie put down her pen. “I can hear how that sounded.”
“It sounded like planning,” Anneke said.
Doug arrived late with a folder against his chest. He had been on the bank-file call, which had run over because the bank had sent a file Finance had not expected and Finance had sent a question the bank had not expected. Neither side, apparently, had found the surprise refreshing.
“There’s a Thursday preparation session for the close,” he said. “It’s on the grid.”
“We’ve seen it,” Pree said. “Does it need everyone?”
“No. It needs the six people on the invitation.”
“Could any of them send notes?”
“They could send me notes. I would still need to discuss them.”
I held up my hand before we acquired a seventh person to discuss the notes. “Does Finance have a slot for it?”
“We do.”
“Then we’re trying to fit the other meetings around the people, not the permission.”
Doug looked at the grid. “That sounds easier.”
It did not sound easier to anyone else.
Pree’s briefing was the immediate problem. Gareth had spoken to her, as promised, but they had not agreed on a standing arrangement.
“He asked me to identify which briefings were genuinely necessary,” she said.
“And?” I asked.
“I identified them. He said we should take another look after planning.”
She tore the croissant quarter in two. A flake landed on Thursday.
“I can move part of it to Wednesday,” she said. “But I need a decision from Field Services before the external call. If we wait until after, we’re telling the client what we should have done.”
Nikhil leaned over the calendar. “My site lead could call at one-fifteen Thursday. I can make sure he has a quiet room.”
“Engineering?” Pree asked.
“My deputy can make one-fifteen,” Anneke said. “If Kirstie’s review starts later.”
Kirstie considered it. “I can start at two. Product will complain.”
“Product can complain to me,” Pree said.
“That’s tempting. But you still need a slot.”
Pree turned to her laptop. The Book had three current-quarter offers that morning, two marked discuss terms. One was from Legal; Bettina had posted it herself. Pree sent her a message, then called when the message remained unanswered.
We listened to Pree’s side.
“Bettina? Sorry, we’re in the planning room. Do you still have the December permission?”
A pause.
“Yes. The client briefing. Nikhil’s site lead and Anneke’s deputy can attend.”
Another pause. Pree looked at me. “One next quarter?”
She muted the call. “She has a review that might move to January. She wants one of ours then.”
“You have six expected,” I said. “And the other briefings.”
“I know how many I have.”
She unmuted. “One next quarter, if we receive the allocation. I’ll transfer it for the review you specify.”
She listened, then smiled without showing much pleasure. “Thank you. I’ll send the details.”
She wrote the terms while we were still at the table. Bettina replied with approval; Pree signed off for Client Support. I entered Legal’s current transfer and recorded Client Support’s future promise separately.
“One for one,” Doug said.
“For that one,” Pree said.
Kirstie was looking at another offer. “Records says it may be able to spare its remaining permission.”
“May,” I said.
“I can read, Delia.”
She sent a message to the Records lead, Farah, who joined us by phone. Farah explained that her team had a document retention meeting pencilled in for December but could hold it on a Tuesday if the people collecting boxes arrived when they had promised.
“And if they don’t?” Kirstie asked.
“We’ll have a great many boxes on Tuesday.”
Kirstie offered one next-quarter slot for the current permission. Farah asked for two.
“Marketing only gets two in the whole quarter,” Kirstie said.
“We get one,” Farah replied.
“Which you might not need.”
“Which I might.”
Kirstie looked at her campaign calendar. She had given Engineering a current slot in November and was expecting two future permissions in return, but those would not help her hold another review before Christmas.
“Two, then,” she said. “Subject to our allocation.”
Farah asked for the proposed meeting and dates before she approved anything. Kirstie sent them from the table. Farah called back ten minutes later to say she could move the retention meeting and would agree, provided Kirstie gave her notice of when the two future transfers would be needed.
“They’re for you,” Kirstie said.
“I know. I’d like notice before I use them.”
When the written approvals arrived, I entered the current transfer and the two-slot promise. Records’ current balance fell by one; Marketing’s rose by one. No January balance moved.
By the time we left, Pree had her briefing and Kirstie had her review. Nikhil had found a room at the site. Anneke’s deputy had two meetings on Thursday but could attend both.
The Book showed the new terms before I had finished clearing the pastry plates. Someone from Field Services had already asked whether Records had anything else available.
It did not.
In the second week of December, Gareth came downstairs for the Book review carrying a notebook and a mince pie wrapped in a napkin.
“I brought you one,” he said.
“Is it in the notebook?”
“I ate yours on the stairs. This is mine.”
We sat at Ferg’s desk. Simon joined us on a call from Sales, and Anneke came over when I asked about the server.
The Book had produced introductions, not transfers. We checked a sample of its entries against the register: some proposals had led to approved agreements; others had expired, been withdrawn or remained unanswered. Simon showed us the access log. His account could read the allocation sheet; it had not edited it. Anneke confirmed that Engineering still controlled the retired server and could shut the trial down if necessary.
“Any unapproved transfers?” Gareth asked.
“Two invitations went out before the leads agreed,” I said. “Both were withdrawn. One person posted on behalf of a team without asking its lead; Simon labelled the offer unapproved, and the lead removed it.”
Simon’s voice came through the speaker. “I can make the warning appear before someone posts.”
“Please do,” I said.
Gareth made a note. “And the terms?”
I opened the future-promises sheet. Engineering owed Marketing two slots under the November agreement. Client Support had promised Legal one. Marketing had since promised Records two, and other leads had made arrangements of their own.
“What am I looking at?” Gareth asked.
“Promises against allocations that haven’t been issued.”
“The allocation is expected to stay the same.”
“Yes. That’s why people are making them.”
I sorted the rows by the team promising delivery. A few had committed more than half their expected January allocation. One had promised away more than it expected to receive.
Gareth leaned closer. “How?”
“Different agreements, different recipients. The Book shows proposals; my register shows the promises once the leads approve them. Nobody asked me to prevent the total.”
Anneke stood behind us with her arms folded. “Can they deliver?”
“Not all of them as written, if the allocation stays at forty-two.”
Gareth turned a page in his notebook. “Then tell them.”
“I will. But another agreement could come in this afternoon.”
Simon said, “I can put a total beside each team’s offers.”
“That would help people see it,” I said. “It wouldn’t stop a lead approving another promise by email.”
There was a brief scrape on the line. Simon had put down his phone, or perhaps picked up a pen.
Gareth checked his watch. “I have to go upstairs. Send me what you recommend.”
“Today?”
“As soon as you can.”
He left the mince pie. I ate it while the spreadsheet recalculated.
By four, the light outside had gone the colour of the windows opposite. My inbox contained six messages marked urgent, three of which concerned the wording of an invitation. I drafted a note to the leads: from now on, a unit could make new commitments against no more than half its expected next-quarter allocation. Existing promises above that level remained recorded; the leads involved should review them with their counterparties and tell me whether they could agree on changes.
I read it twice.
For Records, half of one slot was half a slot. The register could record a promise in words, but it could transfer only a whole permission when one was issued. I added that distinction and asked leads to contact me before offering a fraction.
Anneke came back for her mug.
“What are you sending?”
I showed her.
She read the first paragraph. “Who authorised you to cap it?”
“Gareth asked what I recommended.”
“That isn’t quite the same.”
“No.”
“Have you asked the teams with old promises how they’re supposed to reduce them?”
“I’m asking them to reconcile voluntarily. I can’t cancel an agreement because I dislike the total.”
“What happens if the other side says no?”
“Then the promise stays on the sheet, and we have to deal with it.”
Anneke rested her mug on Ferg’s desk. “Engineering has already promised Marketing two. Are you telling Kirstie she can’t have them?”
“No. The cap applies to new commitments. You still owe Kirstie what you agreed, subject to the allocation.”
“Good. She’s already planned around them.”
That was precisely why the old rows could not simply disappear. It was also why I wanted to stop adding new ones.
I sent Gareth the draft and marked it for a decision. Then I called him. His assistant said he was with Corinne; I left a message and returned to the rows.
At five-fifteen, another proposal arrived: a team offering three January slots for one in December. Its lead had approved it. The recipient had not yet replied.
I forwarded the proposal to Gareth with my draft. He called back three minutes later.
“Send the cap,” he said. “Make clear it’s interim, and that it applies from now. I’ll endorse it to the leads.”
“And the existing excess?”
“Ask them to review it together. We can’t pretend those promises weren’t made.”
I added interim to the subject line and sent the note. Gareth’s endorsement followed shortly afterwards.
The recipient of the three-slot offer replied before six. She would accept one future slot, she wrote, if the other lead still wanted to proceed.
He did. Both approved the revised terms.
I entered the agreement, then went back to the earlier rows. None had changed. I sent each pair of leads a separate message with the promises they had made and asked when they could discuss them.
The first reply came from Kirstie.
Anneke and I have discussed ours. We’d like to keep it, please. x
I marked it reviewed; unchanged and opened the next row.