I sent the chronology before Fallon could reach across the table, and the message reached all three client teams with the roster attached.
For a few seconds, nothing happened, so I closed my laptop halfway and rubbed the ridge the keyboard had pressed into my wrist.
Fallon stayed beside me.
I stayed seated.
Her husband moved back into the hallway, still carrying the customer dashboard on his screen, and I chose not to follow him when the first status icon changed from gray to amber.
Eli spoke first.
“I have it,” he said.
I waited.
He asked Fallon whether the roster represented the operating structure she intended clients to rely on after the transition, and I watched her pull a chair toward the speaker instead of answering immediately.
“It’s a working document,” she said. “We’re making sure nobody carries more than they should during a sensitive period.”
I put both hands under the table because my fingers had started shaking from hunger.
Eli asked again.
I let Fallon answer again.
“Yes,” she said. “It reflects the structure we’re moving toward.”
I opened the version history.
That answer mattered because the roster had not been labeled draft, temporary, or pending; it had been distributed as the contact map for active accounts.
Fallon glanced at my screen.
I turned it toward her.
Eli asked who could authorize exceptions on the commitments already in motion, and I chose not to rescue the silence that followed.
Fallon named herself.
I wrote that down.
Then Eli asked her to describe the exception path for his account when a delivery window changed after a carrier handoff but before the receiving warehouse posted availability.
Fallon looked at me.
I looked at the white card beside my keyboard.
“You’ve always handled those details,” she said gently. “There’s no reason we can’t keep leaning on you while everything settles.”
I moved the card an inch away from the speaker.
“Am I handling them,” I asked, “or am I available during the transition?”
She stopped smiling.
Eli did not fill the gap.
I did.
“The exception goes through the account commitment log first, then the receiving-window record, then the client contact named for that shipment. If the window changes twice, it comes back to the continuity owner before anyone promises a new date.”
Eli said, “Correct.”
I heard Fallon breathe through her nose.
I chose not to look at her.
A little later, the second client changed its review status from requested to active, and the third asked for the current delegation map before it would release any pending renewal action.
I opened the Mercer contract.
I opened the second account file.
I opened the third and found the same requirement buried under different language: the person controlling an open commitment had to be identifiable before the client treated a transition as operationally complete.
The office had grown cold enough that I pulled my sleeves over my hands, and somebody outside the room peeled a shipping label off a box, stuck it to his palm, and forgot it there.
Fallon leaned closer.
“You’re exhausted,” she said. “I don’t want you making this harder on yourself because you’re hurt.”
I closed one contract and left the other two open.
“Then tell them who owns the commitments.”
“I do.”
I nodded toward the files.
“Show them.”
She tried.
For nearly half an hour, Fallon walked through account names, regional contacts, and project summaries while I kept my mouth shut unless a client addressed me directly.
She knew the presentations.
She knew the forecasts.
She did not know which client had prohibited split-routing after a winter delay, which one required a verbal confirmation before a revised commitment could be posted, or which warehouse treated an early arrival as a failed window.
I answered only when asked.
That made it worse.
Eli finally said, “This isn’t about whether Fallon can learn it. We need to know who had this authority yesterday and who has it today.”
I pulled up the old roster.
My name appeared beside every active line.
I pulled up the new one.
Fallon’s did.
Then I put both versions on the screen at once.
Nobody spoke for several seconds.
Fallon reached for the white card, perhaps just to move it out of the way, and I put my notebook over it before her fingers got there.
“Let’s not turn internal formatting into a crisis,” she said.
I asked Eli whether the clients needed anything beyond the documents already distributed.
“Yes,” he said.
One word.
He wanted a written delegation for the open commitments, not another title chart.
I asked whether a temporary delegation would satisfy the review.
He said it could, if all three clients accepted the same structure and if the authority attached to it was real.
Fallon sat back.
I could see the calculation without pretending I knew what was in her head: she looked at the frozen renewal screen, then at the roster, then at me.
“Fine,” she said. “We’ll restore your transition authority until this is resolved.”
I did not thank her.
I asked what authority meant.
She listed shipment exceptions, renewal preparation, and client escalation calls, and I typed each item into a clean document while her husband stood in the doorway reading over my shoulder.
Before sending it, I added one sentence stating that I could not be held responsible for commitments I could not view or approve.
Fallon objected.
I left it in.
Her husband said, “That seems fair.”
I sent the draft to the three clients for confirmation rather than presenting it as finished.
For the first time that morning, the dashboard moved in our direction.
One account marked the structure acceptable pending system access.
Another reopened its renewal workspace.
Eli asked for fifteen minutes to check the language with his team.
I stood up.
My knees hurt.
In the kitchenette, I opened a cabinet, stared at three packets of instant oatmeal, and shut it without taking one because the smell of somebody’s reheated tomato soup had killed what little appetite I had.
I rinsed a clean spoon anyway.
It accomplished nothing.
When I returned, Fallon had moved into the larger conference room and placed herself at the head of the table.
I chose the seat nearest the wall.
Mara Bell came in carrying a legal pad and apologized for being wrong about the ownership update clearing the freeze automatically.
I told her I knew.
I did not ask her to fix it.
She had already given Fallon the wrong answer once, and by then there was no value in replaying it.
Instead, I asked Mara to pull the live commitment queue so we could test whether the authority Fallon had just offered me actually existed inside the operating system.
Mara logged in.
My name was missing there too.
I checked my own account.
Read only.
Fallon stared at the screen.
“That must have happened when the roster changed,” she said.
I clicked an open shipment.
I could see it.
I could not alter it.
I clicked the renewal preparation queue.
Same thing.
I clicked the escalation register and found the button I had used for years grayed out beneath my name.
That was when the small recovery we had just made disappeared.
I had authority on a document Fallon was willing to sign and no authority in the system where the work happened.
Eli called back before anyone could repair it.
I answered.
“Can you act under the delegation now?”
“No.”
Fallon closed her eyes for a second.
I told Eli exactly what I could access and exactly what I could not, then I asked him not to release anything on my verbal assurance.
He agreed.
The second client reversed its earlier status a few minutes later and put the renewal workspace back under review.
Nobody raised a voice.
That made the room feel smaller.
Fallon pushed her chair away from the table and said, “I am trying to put you back in place. You don’t have to punish the company while I do it.”
I chose my words carefully.
“I’m not asking them to trust authority I don’t have.”
“You know what I mean.”
“I do.”
I stopped there.
Sometime before lunch, Mara found the reason my permissions had changed: the operating roster had been connected to the account-access groups during the transition setup, so removing my active-account assignments had stripped the corresponding approval rights automatically.
I asked her not to undo anything yet.
Fallon looked surprised.
I wanted the clients to see one consistent record of what had happened before we changed it again.
That choice cost us time.
It also stopped the morning from becoming a sequence of edits nobody could later explain.
Mara exported the access history, and I sent only the portion covering my account to the client teams after Fallon reviewed the same copy.
I included no accusation.
I included no guess about why my name had been removed.
I included the timestamps.
Then the problem changed shape.
One of the open commitments hit its decision window.
A shipment already moving toward a distribution point needed a receiving adjustment, the kind of ordinary problem I had handled hundreds of times, and nobody in the room currently had both the client context and active authority to approve the change cleanly.
I could have told Fallon what to click.
I did not.
Instead, I asked Mara to display the commitment notes and told Fallon where the relevant restriction appeared.
Fallon read it twice.
“So I move the window forward?”
I shook my head.
“Read the last client note.”
She read it.
The account prohibited a second window move without direct continuity approval.
“Which is you,” she said.
“It was.”
I let that sit.
This was not a bigger threat than the frozen renewals; it was simply the first time the abstract change in authority had landed on a truck already moving through the world.
Fallon asked the client for a one-time exception under her own name.
I listened.
The client granted it.
Nothing collapsed.
Nobody won.
A truck got a new window.
For a while, that was all.
I ate half a sleeve of crackers Mara left beside my laptop and brushed salt from the touchpad with the side of my hand.
The room warmed as the afternoon sun reached the windows, and I moved my chair two inches away from the glass.
Fallon spent that quieter stretch rebuilding my permissions with Mara.
I checked each account only after the change posted.
Shipment exceptions returned first.
Then the escalation register.
Then the renewal preparation queue.
I tested one inactive record and one live one before I told anyone the access was working.
Eli’s team accepted the temporary delegation shortly afterward.
The second client did too.
The third followed sometime that afternoon, but it left the executive review open until its own continuity lead could speak with us.
For the first time since the dashboard had changed color, people outside the conference room stopped walking so fast.
I noticed the bent cardboard box from earlier had finally been flattened and pushed against the recycling bin.
Fallon’s husband came in with four paper cups of coffee and handed me one without asking.
I took it.
It was terrible.
I drank it anyway.
By late afternoon, the renewal freezes had begun to loosen, and Fallon asked Mara to circulate a corrected roster with my name restored beside the active accounts.
I stopped Mara before she sent it.
“Mark the effective time.”
Mara added it.
I read the document once.
Then I let her send it.
The new roster looked almost exactly like the old one.
My name was back where it had been.
Fallon’s title remained above mine.
The temporary delegation matched the system access.
Two clients closed their executive reviews.
People started talking as though the day had survived itself.
Fallon came to my side of the table and set her palm flat beside my notebook.
“We fixed it,” she said.
I looked at the dashboard.
Two green indicators.
One amber.
“Two of them,” I said.
She exhaled.
“The third will follow.”
I did not argue.
For nearly twenty minutes, nothing happened.
I opened a blank email, deleted it, and opened the weather app instead even though I had no intention of going anywhere.
Then Eli called again.
The third client had asked him to stay on the joint review because the accounts shared enough operating exposure that they wanted one answer to a question none of us had addressed yet.
I put the call on speaker.
Fallon sat down beside me.
Eli asked whether restoring my name meant the previous roster had been an error.
Fallon answered before I did.
“It was part of a transition process that moved too quickly. We’ve corrected the operating effect.”
I looked at the old roster on my screen.
Eli asked a narrower question.
“Was her removal accidental?”
Fallon did not speak.
I did not speak for her.
The room stayed quiet long enough for the ventilation fan to click off above us.
Finally Fallon said, “No.”
I wrote the word on my legal pad.
Eli continued.
If the removal had been intentional, the clients needed to know whether restoring me was merely a temporary repair or whether Sutton Arowave was prepared to keep a defined continuity function in place for the open commitments covered by their agreements.
That was different from putting my name back.
A roster could be changed tomorrow.
A defined operating function would have to survive whoever sat at the head of the table.
I pulled the contracts closer.
Earlier, while everyone had been focused on the freeze itself, I had noticed that each agreement described continuity responsibilities by function before naming the employee then holding them.
I had not treated that language as leverage.
Now the clients were treating it as a requirement.
I read the relevant sections aloud without adding anything to them.
Fallon listened.
Her husband stopped refreshing the dashboard.
When I finished, Eli said his team would close its review if Sutton Arowave designated one accountable continuity owner for the covered commitments, gave that person the access necessary to perform the work, and provided notice before moving those duties again.
The other two clients wanted the same thing.
Not ownership.
Not my sister’s title.
The work.
Fallon pushed the temporary delegation toward me.
“You already have this.”
I tapped the expiration line.
It ended with the transition period.
She saw it.
I said nothing.
Fallon asked Eli whether the clients would accept her as continuity owner instead.
I kept my eyes on the table.
Eli said they would review any proposed person against the operating history attached to the open commitments.
Fallon knew enough by then not to ask what that meant in front of everyone.
I picked up my coffee.
Cold.
I put it back down.
For a minute, we discussed nothing more important than whether Mara had ordered dinner for the staff still upstairs.
She had not.
I told her to order whatever was fastest and include something without cheese because one of the coordinators hated it.
Then Fallon turned the delegation over.
“If I remove the expiration and make the function permanent for these accounts, will that satisfy them?”
I asked Eli to answer.
He said the clients would close the reviews once they received the final document and confirmed the permissions were still active.
Fallon looked at me.
“Is that what you want?”
I could have made her say more.
I could have asked why she had removed me before the signature, why she had wanted the clients to see her name everywhere before she knew what each line required, or why support had only become leadership after the screen turned amber.
I did none of that.
I said, “I want the authority to match the responsibility.”
She nodded once.
I said, “I want changes to the client-continuity function documented before they take effect.”
She nodded again.
I said, “I won’t sign a statement saying the old roster was a mistake.”
“It wasn’t,” she said.
That was enough.
Mara revised the document while Fallon and I watched.
The temporary language came out.
The listed permissions stayed.
The three covered client groups were named, and the notice requirement was added beside the continuity function rather than beside me personally.
I read every line.
Fallon read every line.
I read it once more.
Then Fallon approved it.
I accepted the role.
Mara sent the document to the three client teams, and I checked my permissions again before anyone told the office the issue was resolved.
They were still active.
Eli closed his review first.
The second account followed.
The last amber indicator stayed on the dashboard a little longer, then changed after the third client confirmed the same operating structure.
No one cheered.
A few people simply went back to their desks.
That felt right.
Fallon remained the person named at the top of the succession documents, and I did not challenge that.
What changed was narrower and more concrete: on the accounts carrying most of our open commitments, she could no longer remove the continuity function quietly and expect the clients to treat the company as unchanged.
I shut down the customer screen.
My shoulders hurt from sitting badly all day, and I rolled one of them until it cracked.
Fallon gathered the abandoned coffee cups and stacked two inside a third.
“I thought putting my name there would make the transition cleaner,” she said.
I closed the old roster.
“It didn’t.”
“No.”
I put the new roster in the shared folder.
She stood beside the door for a moment, then asked whether I was coming to the succession dinner that night.
I looked at the clock and remembered I had been awake since before dawn.
“No.”
She accepted that answer.
I packed my laptop, the legal pad, and the charger I had nearly left under the conference table.
Before closing the notebook, I found the white name card Fallon had placed at the far end of the table that morning.
I turned it over.
Eli had given me a new direct escalation number before we ended the call, and I used the white card to write it down.
