Three weeks after the Granite review was officially closed, Westbridge called an emergency meeting.
The request came from Elaine Foster just after seven on a Tuesday morning. Her message contained no details, only a sentence asking whether I could be at their headquarters by nine.
I knew from experience that executives did not schedule emergency meetings before breakfast to discuss good news.
I drove through light rain and arrived twenty minutes early. Elaine was waiting in a glass conference room with two members of her internal audit team and Westbridge's general counsel.
She stood when I entered.
“We found something in the historical payroll records.”
I set my bag down.
“How serious?”
“We don't know yet.”
That answer was enough.
The last time someone had said those words to me, twelve thousand people had been waiting for money.
I took the seat nearest the screen.
Elaine opened a file.
“During the shift-differential review, our auditors found a series of adjustments made between 2021 and 2024.”
“How many employees?”
“Four hundred and eighteen.”
“Total value?”
“Approximately one point eight million dollars.”
I looked at the report.
“Overpayments?”
“Mostly underpayments.”
That changed the room.
“Have employees been notified?”
“No.”
“Good.”
Elaine looked surprised.
I explained.
“Not until we know the exact population. If the calculation is wrong, you don't want to send four hundred eighteen people a correction notice and then send another one explaining that the first correction was incorrect.”
The general counsel nodded.
“That was our concern.”
I asked for the raw data.
For the next two hours, my team reconstructed the adjustment history.
The problem was familiar but not identical to Granite.
Someone had created a manual override for employees who moved between shifts.
The override had originally been temporary.
Instead, it had remained active.
The system treated the adjusted employees differently from everyone else.
The difference was small.
But over three years, small differences became significant.
I found the first irregularity at 11:37.
“Who created this rule?”
The audit manager checked the record.
“An outside payroll consultant.”
“Which one?”
He gave me the name.
It wasn't Evan.
But it was the same consulting network.
I looked at Elaine.
“You've got another connection.”
“To Granite?”
“Indirectly.”
She frowned.
“How?”
I explained the relationship between the consultant network, cost-reduction projects, and the former Northbridge team.
Elaine sat back.
“Do you think this is connected?”
“I don't know.”
The phrase had become one of the most useful sentences in my professional life.
I refused to turn patterns into accusations before the evidence existed.
We traced the rule's creation.
It had been recommended as a temporary efficiency measure.
The consultant had estimated that it would reduce payroll processing time by forty percent.
The estimate had been based on assumptions.
The same kind of assumptions I had seen before.
Not identical.
But familiar.
The consultant had treated exceptions as inefficiencies.
That was the mistake.
Exceptions were not necessarily failures.
Sometimes they were evidence that the system was correctly noticing something unusual.
By the end of the day, Westbridge had a verified list of affected employees.
They planned to correct every underpayment.
No one would be asked to return legitimate wages caused by the company's error.
Elaine authorized interest adjustments where appropriate.
The board approved the correction without argument.
That was the part I noticed most.
No one asked how quickly they could hide the cost.
They asked how quickly they could make the employees whole.
That was progress.
Two days later, another surprise arrived.
Robert called.
“Claire, are you sitting down?”
“Yes.”
“You're going to want to see this.”
He sent me a document.
It was from Granite.
A former board member had requested copies of the final investigation materials.
That wasn't unusual.
What was unusual was the reason.
The board member was preparing for litigation involving another company.
The company had recently acquired a business whose payroll transition had been overseen by a consultant connected to Evan Cole.
Robert wanted my help identifying whether the same methodology had been used.
I opened the file.
The language was nearly identical.
Aggressive automation.
Immediate staffing reduction.
Minimal parallel testing.
Savings tied to implementation speed.
I felt the old tension return.
Not fear.
Recognition.
“Robert,” I said, “how many companies used this model?”
“We don't know.”
“Can we find out?”
“We're trying.”
I stared at the document.
The Granite story had never been only about Granite.
That possibility had been sitting at the edge of my thinking for months.
Now it had moved into the center.
I agreed to help with the review.
Not because I wanted to reopen the past.
Because if the same structure had been sold to other companies, there could be other employees who had been exposed to the same risks.
My team began collecting public filings, internal records provided by clients, and contract language.
We found similarities.
But similarities were not proof.
Some companies had successfully implemented automation.
Others had experienced payroll disruptions.
Several had changed consultants midway through their projects.
One company had quietly reversed a restructuring after employees complained about repeated errors.
We mapped the information.
The pattern became clearer.
The consultants had not necessarily created every failure.
But their sales model consistently emphasized the same financial promise.
Reduce headcount.
Reduce manual controls.
Reduce transition time.
Increase reported savings.
The risk was left outside the presentation.
That mattered.
Because executives did not buy failures.
They bought projections.
And projections could make dangerous assumptions look like certainty.
Three weeks later, I was invited to speak to Westbridge's board.
I did not give them a motivational presentation.
I showed them the numbers.
I showed them where automation worked.
I showed them where it failed.
I showed them what happened when exception controls were removed.
And I showed them the difference between reducing labor and reducing risk.
One director asked, “If you were in our position, would you proceed?”
I answered carefully.
“I would proceed only after deciding which risks you are willing to accept and documenting why.”
He nodded.
“That's not a yes.”
“No.”
“It's not a no either.”
“Correct.”
The room became quiet.
I had learned not to make decisions for executives.
My job was to make the consequences visible.
That afternoon, Elaine walked me to the parking lot.
“You've changed the way this company talks about payroll.”
“I hope so.”
She smiled.
“People now ask what a control protects instead of what it costs.”
That was the best compliment I had received in years.
Then my phone rang.
The number was unfamiliar.
I almost ignored it.
Instead, I answered.
“Hello?”
A man's voice said my name.
“Claire?”
“Yes.”
“This is Evan Cole.”
I stopped walking.
The parking lot suddenly seemed very quiet.
“I thought you might call eventually,” he said.
I didn't answer.
“I have something you should know.”
“What?”
“There was another file.”
My grip tightened around the phone.
“What file?”
“The original project file.”
“Where?”
“Not at Granite.”
I looked across the parking lot.
“Then where?”
He gave me an address.
It was a storage facility.
He said the files had been retained by his former firm.
“Why are you telling me?”
He was silent for a moment.
“Because I told myself it was just a consulting project.”
His voice sounded different from the last time I had heard his name in an investigation report.
Less certain.
“I told myself companies wanted savings. I told myself executives knew what they were buying. I told myself if the controls were removed, someone else would rebuild them.”
“And?”
“And then I saw what happened to your payroll.”
I said nothing.
He continued.
“I should have stopped it.”
“You had a contract.”
“I know.”
“You were being paid.”
“I know.”
“You had no authority to make the final decision.”
“I know.”
“Then what do you want from me?”
“I want you to see the file.”
He gave me a date and a time.
I wrote it down.
Then I asked one question.
“Why now?”
He answered quietly.
“Because I finally understand that calling something an efficiency project doesn't make the consequences disappear.”
The call ended.
I stood beside my car.
For a moment, I considered deleting the number.
Instead, I saved it.
Not because I trusted Evan.
Because evidence had taught me never to ignore information simply because I disliked its source.
The storage facility was two hours away.
The file could contain nothing important.
It could contain exactly what Evan claimed.
Or it could contain something that changed the entire story.
I started the car.
The rain had stopped.
But I had the unmistakable feeling that another storm was beginning.
Click here to continue reading: PART 10: The storage file revealed a decision made before my termination, and for the first time I saw exactly how close the company came to an even greater failure
The Friday afternoon meeting looked routine until Harold placed a stranger’s laptop on my desk and told me my decade of experience was finished
Part 9 of 12
