Chapter 15: Rules and Favors
Bettina arrived at the policy workshop with a burrito wrapped in foil and a document containing forty-seven tracked changes.
“I was told lunch would be provided,” she said.
Gareth looked at the empty table. “It was supposed to be.”
“I brought this as a contingency. I don’t intend to share it.”
Anneke moved her laptop away from the patch of sunlight Bettina had chosen. Pree came in behind her, followed by Nikhil from Field Services and Marisol from Records. I had invited Marisol because she had asked to see how the coverage issue would be handled. I had not yet found a good place for it in the rules.
Gareth opened the draft on the screen.
“We want people to understand what they can do,” he said.
“And what they can’t,” Bettina said.
“And whether they can still get a meeting on the calendar,” Pree said.
The first rule was straightforward enough: a slot permitted one specified internal meeting on a protected Thursday. It did not require anyone to attend, and it did not grant personal leave.
Nikhil read it twice. “If the meeting moves from ten to eleven, do we need another approval?”
“Not if the same people can attend and the purpose hasn’t changed,” I said.
Pree raised a hand. “What if one person can’t attend?”
“You’d need to find another time or proceed without them.”
“So the rule is that we can have a meeting if we can have a meeting.”
“The permission removes one obstacle,” I said.
“There are others,” Marisol said.
I added a note about checking attendance before requesting a transfer. Pree asked me to remove it.
“We know to check attendance, Delia. We’re not livestock.”
The second rule required the affected team leads to approve a transfer in the Ledger. The third set the prospective limit: a unit could newly commit no more than half its next-quarter allocation. Existing excess commitments and documented exceptions remained in the review record; the rule did not cancel them.
Anneke pointed at the wording. “Half of thirteen is six and a half. The Ledger won’t record half a slot.”
“Six whole slots,” I said. “We’ll show the calculation.”
“And the old promises?”
“Still visible. Still need reconciliation.”
“Could you make the warning bigger?”
Simon, who had joined by video to advise on the interface, leaned towards his camera. “The warning is already red.”
“Make it redder,” Anneke said.
Pree scrolled through the list of exceptions. “My team has two claims to Finance from the January arrangement. Those stay?”
“Yes,” I said. “With the conditions you approved.”
She nodded, but did not look pleased. She had agreed to them when I needed them. Neither of us had found an occasion on which to discuss the cost without also discussing my gratitude.
Bettina unwrapped her burrito, read the fourth rule and folded the foil back over it.
“Slots expire at the end of their quarter,” she said. “We need a separate sentence about promises.”
I typed one: Expiry cancels all associated commitments.
“No,” she said.
I deleted it.
“If someone promises a future transfer and doesn’t deliver, the permission may expire. That doesn’t tell us what happened to their agreement.”
“Can we tell them what happens?” Gareth asked.
“We can ask them to bring disputed agreements to us. We can’t make every agreement disappear by adding a sentence to a procedure.”
Simon put his hand up on the screen, then lowered it. “People will want a simpler answer.”
“So would I,” Bettina said.
Her proposed sentence said an expired slot could no longer be used as permission for a meeting; any separate dispute about an agreement should be referred for review. It was longer than mine and had the disadvantage of being accurate.
We moved to non-slot exchanges. I had drafted: Slots may only be exchanged for other slots.
“May only be transferred as recorded under this procedure,” Bettina said. “The Ledger doesn’t convert them into parking, shifts, money or anything else.”
Nikhil sat forward. “Femi and Tomas swapped on-call weekends. Is that forbidden now?”
“I’m not proposing to prohibit all shift swaps,” Bettina said. “I’m saying the Ledger won’t recognise a shift as the consideration for a slot.”
“What if both people want the swap?”
“Then their managers still need to assess the rota on its own terms.”
Anneke turned to me. “And if the transfer happens on Monday and the swap happens on Tuesday?”
“We can ask whether they’re connected,” I said.
“You can. Will they answer?”
Bettina took a bite of burrito. She had postponed it so long that the tortilla had begun to stiffen. While she chewed, Marisol lifted the printed draft.
“Where does it say who covers our desk?”
“It doesn’t,” I said. “This is the transfer procedure.”
“I know what it is. I’m asking where the answer goes.”
Gareth leaned forward. “I’ve asked the relevant managers to look at coverage.”
“Mine has looked,” Marisol said. “She’d like Reception to help. Reception would like us to pick a day when they have someone spare.”
Pree closed her laptop. “That’s my problem too. I can get a permission and still spend two days finding people for the briefing.”
“We’re recording those examples,” I said.
Marisol put the paper down. “All right. I just wanted everyone to hear that I asked.”
The room was quiet except for Bettina carefully refolding the foil.
Gareth thanked Marisol and suggested we finish the rules before lunch got any later. There was no lunch, but the phrase did its work. We agreed the four rules, with Bettina’s revisions. I promised an accompanying page explaining the cap, the outstanding exceptions and the review process.
After the workshop, I sent Marisol the coverage paragraph from my programme again, with the names of the managers Gareth had asked to respond. She replied with a date on which she and Glen could meet them. I forwarded it to Gareth.
The rules went out that afternoon. The subject line read CLEARER THURSDAYS. I had proposed LEDGER PROCEDURE, but Communications said people might not open it.
Within ten minutes someone asked whether a birthday cake counted as a non-slot conversion. Bettina replied that a birthday cake was a birthday cake. She copied me, which meant I would now receive every reply.
Two days later I went upstairs to Engineering to see whether the new rules had made the transfer process easier. Anneke was at a whiteboard with Tomas, who erased a diagram when he saw me.
“That looked useful,” I said.
“It was wrong,” he said.
Anneke studied the pale marks left by the eraser. “It was a fish.”
Tomas put the marker down. “Femi’s coming over. We’re sorting out March cover.”
“For the weekend you agreed to take?”
“Yes. He’s checking a date.”
He glanced at Anneke. She took the hint and went to fetch coffee. I stayed where I was, which was less perceptive.
“I’m not here to examine your rota,” I said.
“Good.” He uncapped the marker again. “Because the fish had nothing to do with it.”
Femi arrived carrying his phone. Tomas showed him the date on the board, and they settled the weekend in under a minute. Then Femi hesitated.
“There’s also that Thursday request,” he said.
Tomas looked at me. “The meeting’s still needed?”
“Nikhil says so.”
“We have a permission available. I’ll ask Anneke.”
“Thanks. And I’ll bring the—”
Femi stopped.
“The what?” Tomas said.
“Nothing. I’ll put the request in.”
After he left, Tomas stared at the marker in his hand. “He was going to bring me a coffee.”
“Was he?”
“He might have been. He knows what I drink.”
Anneke returned with two mugs. She handed one to Tomas and kept the other.
“Your coffee arrangement appears to have collapsed,” she said.
“It was a thank-you.”
“For what?” I asked.
Tomas gave me a tired look. “That’s the bit we’ve all become very interested in.”
I followed Anneke to her desk. She opened the Ledger and showed me a new offer from Engineering. It listed an available permission and a date, with no terms beyond the meeting details.
“Clean entry,” she said.
“Is there an associated arrangement?”
“I don’t know. I haven’t asked Tomas yet.”
“Will you?”
“Yes. I have to approve it.”
A message arrived while we were looking at the screen. A lead from a small team wanted to know whether an offer she had seen that morning was still available. It had disappeared before she could contact the other team.
Anneke checked its history. “Withdrawn.”
“Can we see why?”
“The user entered ‘no longer available.’”
I called the lead who had withdrawn it. He said his team might need the permission after all. When I asked whether he had discussed it with another unit, he said he had spoken to several people but had made no agreement. I thanked him and passed that answer to the woman who had asked.
She called me back.
“I used to be able to see what people wanted,” she said. “Now the offers are up for five minutes.”
“Some may be reconsidering after the rules.”
“Fine. But the people who hear about them in the kitchen are still hearing about them.”
I wrote that down. She asked whether I could tell her when another permission became available. I showed her how to set a Ledger alert, though I could not promise it would reach her before a private conversation did.
Anneke waited until I put the phone down.
“You think they’ve stopped making arrangements?” she asked.
“No.”
“Do you think the rules caused all of them to hide?”
“No. Some weren’t in the Book before.”
I looked at the withdrawn offer again. It told us when it had appeared, when it had gone and who had removed it. The history was excellent.
“We may have given people a reason to leave less of the conversation where anyone else can see it,” I said.
Anneke nodded. “That’s what I was asking.”
“I know. I heard you at the workshop.”
“You answered a different question.”
I added the withdrawn offer and the lead’s concern to my notes, without inventing an exchange I could not establish. Then I opened the coverage section and added her other point: a team that missed a short-lived offer still needed a way to get its work done.
At the next desk, Tomas drew the fish again. This time he gave it a briefcase.