Chapter 14: Director, Time Allocation
The invitation arrived with a title I had not seen before.
Leadership call: Time Allocation — Director appointment
I checked the recipients, then checked whether there was another Delia Fung at Halbrook. There was a D. Fung in Field Services, but his name was Daniel and he had recently sent an all-staff message asking whoever had taken his lunch container to return the lid as well.
Gareth called before I could write to him.
“Have you seen the invitation?”
“Yes.”
“I wanted to speak to you first.”
“You sent the invitation first.”
“I did. Corinne’s assistant needed the title for the calendar.”
“What title?”
He was quiet for just long enough.
“Come upstairs,” he said.
Gareth had put a folder on the chair opposite his desk. He moved it when I came in, although there was room for both of us.
“We’d like you to take a director role,” he said. “Time Allocation. You’d report to me, and Corinne would have a dotted-line interest because of the operating system.”
“What does a dotted-line interest involve?”
“Regular updates. She’ll have input into the priorities.”
“Can she change them?”
“We’d discuss that.”
I sat down. “Who is we?”
He smiled, then saw that I was waiting.
“You and I would set the work programme. If Corinne wanted a change, she’d raise it with us. If we disagreed, I’d make the decision, subject to the usual executive process.”
That was a better answer than the first one. It also contained the usual executive process.
He handed me a sheet with the proposed salary. I read the figure twice, then folded the sheet along a line that was already there.
“You’d have a systems analyst assigned from Operational Insight,” he said. “Engineering would provide a development lead for the Ledger. You wouldn’t manage the engineers, but their work on it would be part of the agreed programme.”
“Would I still do the client-reporting analysis?”
“Your current supervisor is arranging a handover.”
“She hasn’t mentioned it.”
“We wanted to make sure you were interested.”
“You’ve named the meeting.”
Gareth took off his glasses. “That was premature.”
I looked at the salary again. I had spent eleven years at Halbrook becoming the person called when a figure looked wrong. It was satisfying work, but the call often came after someone else had presented the figure.
“What authority would I have over transfers?” I asked.
“You’d own the procedure and the register. Changes to policy would come through me, with Bettina’s advice.”
“And the promises already in it?”
“We need a reliable account of them.”
“That won’t make them reliable promises.”
“No.” He rubbed one lens with his thumb. “But we ought to know what we’re dealing with.”
I thought of Marisol’s soup and Glen’s retention review. Their coverage request was in my proposal, beneath the system requirements. I had put it there myself.
“I want the coverage work included,” I said. “Records has permissions it may not be able to use. A better register won’t cover its desk.”
“I’ve read that section. We’ll ask the relevant managers to look at it.”
“Will it be part of my programme?”
“Yes. You can bring me the findings.”
I wanted him to promise more. I also wanted the job, and I was aware that those two wishes made me an unreliable judge of the answer.
“Can I have the afternoon to think?”
“Of course. The call isn’t until tomorrow.”
At my desk, I opened the proposal and read the paragraph about ownership. I had recommended a named owner with authority to maintain the register and report on its effects. I had not specified that the owner should be paid more. It was encouraging to discover that leadership had found something to add.
I called Sal, who would inherit part of my handover.
“Congratulations,” she said.
“I haven’t accepted.”
“Oh. Then I withdraw it.”
“Did you know?”
“Your supervisor asked me what would need covering if you moved. She told me not to assume anything.”
“What did you tell her?”
“That we’d need someone who knows the reporting exceptions. And that you should document them before you become too important.”
I turned towards the empty chair beside my desk. “I’m already too important.”
“Then document them today.”
I called Gareth back before lunch and accepted.
Eleven faces appeared on the leadership call the next morning. I counted them while Gareth introduced the role, partly because counting was familiar and partly because my own face kept moving when I tried to drag it out of the way.
Corinne spoke about support, accountability and the risk of relying on a single spreadsheet. She also said the transfer activity showed an appetite for cross-functional cooperation.
I unmuted myself.
“It shows that the named representatives have made transfers,” I said. “We’re still looking at who can use the permissions and what happens around them.”
A small silence followed. Then Corinne nodded.
“That’s part of why Delia will lead it.”
Gareth displayed a slide with my name and the title beneath it. The letters were large enough that there was no room for my surname on one line. He had chosen to put Fung beneath Delia, which made me look like two directors sharing the post.
Afterwards, messages arrived from people I knew and several I did not. Anneke wrote: Congratulations. Can a director still approve the server maintenance window?
I replied that she could now ask my office.
She came downstairs and asked me in person.
The following week, Anneke’s development area smelled faintly of hot plastic. Someone had brought a space heater for the morning and been told by Facilities to turn it off. It stood under a desk with a label on it: NOT A PAPERWEIGHT.
On Anneke’s screen, the new Ledger showed a row of green boxes.
“Those are test approvals,” she said. “Nobody has actually transferred anything.”
Simon leaned over the back of my chair. “The green is reassuring.”
“It’s also the same green whether the underlying promise can be delivered or not,” I said.
“That’s why it says approval received and not everything is fine.”
“Could it say everything is fine?” Anneke asked. “It would save us a great deal of work.”
Simon had brought a list of features people used in the Book. It included search by quarter, a way to see the stated terms and a button labelled Ask, which opened a message to the person who had posted an offer.
“The button stays,” he said. “Otherwise everyone comes to Delia.”
“I’m trying to become less available,” I said.
“You’ll need a better calendar for that.”
Anneke opened the migration checklist. Engineering had matched the current balances against my register; I had checked the approvals attached to each transfer. Future promises were harder. Some had been amended in email, some were awaiting lead confirmation, and several entries appeared to concern the same expected permissions.
I pointed to one flagged row. “These two both say they’re receiving the same future slot.”
“They both entered it,” Simon said. “I asked each of them. Each thinks the other arrangement was cancelled.”
“Was it?”
“Neither has the cancellation.”
“Then leave both visible and mark the conflict.”
Simon made a note. “They won’t like that.”
“Which one would you prefer us to delete?”
He looked at the screen. “I’d prefer them to tell us.”
We imported the claim with the conflicting entry attached and a warning that neither had been verified for delivery. Other unresolved rows received their own flags. The Ledger would record whole permissions; where the Book described a fractional promise, we retained the original text in the review notes rather than manufacturing a whole slot.
Anneke showed me the approval screen. Both team leads had to sign in under their company accounts. The Ledger recorded the time, the terms they had approved and any subsequent amendment. If someone changed the terms, the approvals cleared and had to be given again.
“Can you alter a balance?” I asked.
“As an administrator, with a reason recorded. So can the other authorised administrators. Every change stays in the history.”
“And Simon?”
“Ordinary user.”
Simon put a hand to his chest. “After everything I’ve done.”
“You can still post an offer,” Anneke said.
“I’ve always wanted to be ordinary.”
We checked the six Q2 claims to Finance against the approvals from Sal, Anneke and Pree. They were entered separately, with the relevant units and conditions. Doug’s current permission had already been used for the rearranged handover. Seeing the rows again, I remembered Pree saying her team would have to find room for its two.
At three, Anneke made the Book read-only. Simon opened it on his own screen and tried to post an offer. A notice appeared: THIS BOOK IS CLOSED FOR NEW ENTRIES.
“I could have written something warmer,” he said.
“People can still read their old entries?” I asked.
“Yes. The links take them to the Ledger for anything new.”
Anneke ran the final check. A test request passed from one account to another, gathered its approvals and appeared in the audit history. She removed the test entry using an administrator account; its removal appeared in the history too.
“All right,” she said. “It’s live.”
Simon refreshed his page. Two actual offers appeared within a minute.
I opened the first. Its terms were clear, the permission was available, and both leads would be asked to approve it. The second contained a reference to an earlier promise with a flag beside it.
“Do we hold that one?” Simon asked.
“We ask them to resolve the flag before it can transfer.”
He sent the message. I watched the new audit trail record the request, my decision and the time. For once, someone else could find out what had happened without searching my inbox.
Then another notification appeared: a lead wanted to know why her old agreement was marked unresolved. She had a signed email, she said, and expected the transfer to go through.
I opened the attachment. It was a signed email. The other party’s later amendment was in the register, unanswered.
“Call her,” Anneke said.
“I will.”
“You can also put the reason in the Ledger.”
“I know.”
I entered the reason first, carefully enough that she could see which amendment needed an answer. Then I picked up the phone.