Chapter 4: Something Reasonable
Gareth had approved the first forty-one requests.
He told me this on Monday morning, before I had opened the file.
“The first forty-one by urgency?” I asked.
“By arrival.”
He stood beside Ferg’s empty chair with his glasses in one hand and a paper cup in the other. The cup had softened at the rim.
“I thought I should get back to people promptly,” he said.
“You did.”
“Then the forty-second needed more information, and I realised I hadn’t looked at the forty-third.”
“How many have you looked at now?”
“All of them. Some twice. I’ve approved three more urgent ones since Friday, but I haven’t sent the answers yet.”
I opened his spreadsheet. The first forty-one rows were green. After that, the colours became less certain: yellow for questions, orange for possible conflicts, and a blue that Gareth had used when he could not remember what yellow meant.
“Can we undo the first approvals?” I asked.
His expression changed.
“Not easily,” he said. “People have arranged their work around them. Two meetings have already happened.”
That was fair. I removed my hand from the mouse.
“I’m not suggesting we cancel everything. I need to know what’s available for the rest.”
Gareth put down his cup and leaned over the screen. Several approvals were for recurring meetings. One had no end date.
“That one was only meant to cover October,” he said.
“Does the organiser know?”
“I’ll ask.”
He took out his phone. I watched him type, then erase a sentence.
“Would you like me to do it?” I said.
“No. I approved it.”
He sent the message and retrieved his cup. “Can you find a way to make this manageable?”
“I can classify the requests. Whether that makes them manageable depends on what you want to approve.”
“I’d like to approve the ones people need.”
“That’s what the form asked them for.”
He looked at the screen again. “You see the difficulty.”
After he left, I moved to Ferg’s desk. Mine had two reports open, a mug with a skin on the coffee and a stack of files I did not want to confuse with Gareth’s. Ferg’s desk held a monitor, a keyboard and a pale rectangle where the plant had been.
I started with the recurring requests. Pree’s briefing appeared thirteen times in one quarter if the client call continued weekly. Doug had asked for meetings only when the bank file produced a discrepancy, but he had also requested a standing reservation so the right people would keep the time free. The Cambridge plant wanted a short meeting whenever Friday’s collection changed. Marketing wanted its six-year-old planning session back on Thursday because Wednesday had proved inconvenient for two people.
I called the Marketing organiser.
“What happened to Wednesday?” I asked.
“Kirstie has another meeting.”
“Can Kirstie’s other meeting move?”
A pause. “It’s with your team.”
I checked. It was a monthly report review I attended, and I had declined a proposed change the previous week because the new time was close to lunch.
“I’ll move it,” I said.
“That would help.”
I changed the invitation before I could discover another reason not to.
By mid-afternoon I had sorted the requests into deadlines, recurring dependencies, preparation and preference. Several belonged in more than one category. The labels helped me see the work, but they did not tell me who should get a Thursday meeting when two teams wanted the same people.
I pulled the corrected calendar query and looked at how often each part of Halbrook had scheduled internal meetings before the ban. Engineering had the largest share. Client Support and Finance followed. The smaller units had fewer meetings, though that did not mean a missed meeting mattered less to them.
At four, Anneke came looking for the person who usually sat at my desk.
“You’ve moved,” she said.
“Temporarily.”
She looked at Ferg’s chair. “Has anyone told him?”
“He left.”
“That hasn’t stopped half his meetings.”
I showed her the spreadsheet. She studied the requests without touching the keyboard, which was unusual enough to make me suspicious.
“Are those the approved ones?” she asked.
“Mostly.”
“Engineering submitted six.”
“You have two approvals and four questions.”
“Which two?”
I pointed. One was for a migration rehearsal. The other was a meeting whose organiser had described its purpose as alignment.
Anneke frowned. “The rehearsal matters.”
“And the alignment?”
“I’ll find out what it is.”
She left, then came back with the answer three minutes later.
“We don’t need it.”
“Did you speak to the organiser?”
“I am the organiser.”
I deleted the row from my working copy. It was an unexpectedly satisfying keystroke.
By the time the light moved off the window and lay across Ferg’s keyboard, I had stopped trying to rank every meeting. Gareth could spend the quarter deciding whether Doug’s possible bank discrepancy mattered more than a plant collection. He would also have to predict when each would occur.
I made a second sheet and gave each unit a quarterly allowance of meeting permissions. The total would limit the number of exceptions; the teams would decide which meetings to use them for.
The first calculation gave Engineering most of the permissions and several small units none. That was a faithful reflection of the old calendars. It was not a useful way to protect people who might need one meeting and had never scheduled many.
I set a floor of one per unit and a ceiling for the largest. Product and Operational Insight shared a unit because our requests involved many of the same people. Finance included Accounts Receivable. After several adjustments, the sheet read:
| Allocation unit | Quarterly slots |
|---|---|
| Engineering | 13 |
| Client Support | 6 |
| Finance, including Accounts Receivable | 5 |
| Sales | 4 |
| Field Services | 3 |
| Marketing | 2 |
| Legal | 2 |
| People & Culture | 2 |
| Product and Operational Insight | 2 |
| Facilities | 1 |
| Reception | 1 |
| Records | 1 |
| Total | 42 |
I checked the sum twice. Then I checked that I had included every unit once.
A slot would permit one specified internal meeting on a protected Thursday. It would not excuse anyone from attending work, grant an afternoon off or require an invited person to attend. Teams would still have to arrange the meeting and its participants. Existing approvals would count against the relevant allocations; Gareth would need to correct the open-ended approval and tell the teams what remained.
I sat back. The model had sharp edges. Pree’s thirteen briefings would not fit into six slots, and Client Support had asked for other meetings too. A floor of one helped Records hold a necessary discussion; it did nothing to put somebody on its desk while the staff met. I added both points beneath the table.
Then I saved the file as Thursday proposal and went upstairs before I could improve it into another classification exercise.
Gareth’s office door was open. He was reading a message on his phone and mouthing part of it to himself.
“The open-ended approval was a mistake,” he said when he saw me. “The organiser says October is fine.”
“One down.”
“Come in.”
He cleared a space on his desk by moving three folders onto a fourth. I put my laptop there and turned the screen towards him.
He read the table, then went back to the top.
“Forty-two?”
“Across twelve allocation units, per quarter. I used the old meeting pattern as a starting point, then gave every unit at least one and limited the largest share.”
“Why forty-two?”
“It leaves room for exceptions without returning every Thursday to its previous condition. It’s a proposed budget, not a number I found in the data.”
He nodded at that. “And the teams decide how to spend it?”
“Which meetings to hold. A slot permits a meeting; it doesn’t give anybody leave.”
He smiled. “You’ve already had that question.”
“I’m trying to avoid having it.”
Gareth ran his finger down the table. “Pree will need more than six.”
“Yes.”
“Could we give her thirteen?”
“We could. Then we need to decide whether to increase the total or take seven from somewhere else.”
“Engineering has thirteen.”
“Engineering has more people and a larger share of the requests. Anneke would have a view.”
“She usually does.”
“She also cancelled one of hers today.”
“That is encouraging.” He looked at Client Support again. “Pree’s need is real.”
“I know. This doesn’t settle the standing briefing. It gives her six permissions to choose from, and she’ll need a decision about the other weeks.”
“From me.”
“Probably.”
Gareth took off his glasses and wiped them with the end of his tie. “I was hoping the budget would make those decisions unnecessary.”
“It makes fewer of them yours. That’s still an improvement.”
He put the glasses back on and read the notes below the table. I had expected him to stop at the numbers. Instead he asked me how the floor affected Reception and whether the ceiling would prevent Engineering from doing work it could not move. I showed him the requests I had used and the assumptions I had made where the forms were incomplete.
He opened his calendar.
“Corinne has half an hour now. Will you come?”
I glanced at the time. My supervisor had asked for a draft by morning. It was possible to say no, send Gareth the file and let him present it. It was also possible that he would present my floor and ceiling without explaining why they were there.
“Yes,” I said. “Let me send one message.”
Corinne Vance’s office faced another office building. A man in the opposite window was watering a plant with a bottle. Corinne watched him for a moment while Gareth explained the backlog.
“Two hundred and six?” she said.
“In nine days.”
“And forty-four approvals?”
“Forty-one in order, then three urgent requests awaiting confirmation.”
She gave him a level look. “That’s clear. Delia?”
I showed her the table. She asked who would enforce the limits and what would happen to the approvals already issued.
“Gareth’s team can maintain a register for the trial,” I said. “Each lead needs to see what has already been approved against their allocation. Anything beyond it comes back for a decision.”
“Does the register need to come to me?”
“Not each meeting,” Gareth said quickly. “I can handle decisions that exceed the budget.”
Corinne tapped the row for Client Support. “Pree will call me about this.”
“She may,” Gareth said.
“She should. Her client won’t care which internal rule caused a poor briefing.”
“I’ll speak with her before the announcement.”
Corinne considered the table again. “Try it from the middle of the month. Run the existing approvals against the allocations first, and bring me the result at the end of the quarter.”
Gareth looked at me. I nodded, though she had already made the decision.
Outside her office, he exhaled.
“She liked it.”
“She approved a trial.”
“That is how Corinne likes things.”
He asked me to send the sheet and offered to draft the announcement. I said I would add a note explaining that the allocations covered meeting permissions, not leave, and another flagging the unresolved recurring requests.
“Thank you,” he said. “You’ve made this feel possible.”
I returned to Ferg’s desk to retrieve my bag. An email from Pree was waiting.
Any news on a standing arrangement? The transit authority has sent dates through December.
I opened the calendar she had attached. The Thursday calls ran down the screen in a neat column. I counted the briefings she would need before the end of the quarter, then opened Gareth’s draft announcement and began writing the note he would have to give her.