“Then why are you calling me?”
“Because I found something I don't understand.”
I turned down the oven.
“What did you find?”
“A transportation authorization from last month's flooding exercise. It lists twelve accessible vehicles assigned to the eastern evacuation corridor.”
I leaned against the counter.
“All right.”
“Jordan, those vehicles weren't there.”
I frowned.
“What do you mean?”
“I mean I supervised that corridor. We had six accessible vehicles available, not twelve.”
“Could the others have been assigned but not deployed?”
“That's what I thought. So I checked the dispatch logs.”
“And?”
“The vehicle identification numbers belong to buses that haven't been in service for months.”
I stopped moving.
Leah continued.
“Three were sold. Two were retired after inspections. One was transferred to a different company.”
“Who submitted the authorization?”
“Southeastern Transit Services.”
I looked toward the window.
That name was familiar.
Several years earlier, my team had discovered that Southeastern's fleet reports overstated the number of vehicles available for emergency transportation. The company had cooperated with a review, corrected its records, and continued working under revised agreements.
At the time, we had concluded that the discrepancies resulted from outdated reporting practices.
Now Leah was telling me that another report contained vehicles that did not exist in the company's current operational fleet.
“Are you certain about the identification numbers?” I asked.
“Yes.”
“Have you contacted Southeastern?”
“No. I wanted to speak with you first.”
“Good.”
There was a pause.
Then Leah asked, “Jordan, do you think somebody's falsifying the records?”
I looked at the authorization number she had sent to my phone.
“I don't know.”
“But—”
“Leah, we don't know yet.”
She sighed.
“I know.”
“We need to preserve the documents, verify the source information, and determine whether this was a data error, a contractual reporting problem, or something more serious.”
She was quiet.
Then she said, “You always make me feel better and more worried at the same time.”
I smiled faintly.
“It's a talent.”
She laughed.
But neither of us was particularly amused.
Because if the records were inaccurate, our evacuation plans might be relying on transportation capacity that would not exist when people needed it.
And if the inaccuracies were deliberate, the problem could extend far beyond one company.
By eight the following morning, I had assembled a small internal review team.
Tyler Brooks, my deputy director, arrived carrying coffee and a laptop.
Emily Carter joined us from the planning division.
Marcus Bell, our communications specialist, brought the relevant dispatch records.
Leah participated remotely from North Carolina.
We met in a windowless conference room at the regional operations center.
I placed the disputed authorization on the screen.
“Before we begin,” I said, “I want to establish something.”
Everyone looked toward me.
“We are not conducting a criminal investigation. We are determining whether our operational records are reliable and whether immediate corrections are necessary.”
Tyler nodded.
“And if we find evidence of intentional misconduct?”
“We preserve it and refer it to the appropriate authority.”
Emily looked at the screen.
“What about the upcoming hurricane-season exercise?”
“We continue planning, but we don't rely on any unverified capacity figures.”
Marcus frowned.
“That could affect three counties.”
“Yes.”
“And our shelter transportation agreements.”
“Yes.”
He leaned back.
“That's a problem.”
I nodded.
“Which is why we're here.”
We began comparing records.
The original authorization.
Fleet inspection reports.
Contract amendments.
Dispatch logs.
Vehicle assignments.
Maintenance records.
By noon, we had identified twenty-seven entries requiring clarification.
Not twenty-seven fraudulent entries.
Not twenty-seven confirmed violations.
Twenty-seven records that did not match the available supporting information.
That distinction mattered.
But it did not make the problem small.
At 1:15 p.m., Tyler came into my office.
He closed the door.
“Jordan, there's something else.”
I looked up.
“What?”
“I found a contract amendment.”
He handed me a document.
It was dated four months earlier.
The amendment expanded Southeastern Transit Services' role in regional emergency transportation.
It also changed how the company reported vehicle availability.
I read the relevant section.
Then read it again.
“Who approved this?”
Tyler pointed to the signature block.
A name appeared beneath the authorization line.
Daniel Whitaker.
Southeastern's operations director.
And beside it was the signature of a state procurement administrator named Richard Voss.
I knew Voss.
Not well.
We had attended several regional planning meetings together.
He was fifty-three, meticulous about procedure, and widely regarded as someone who understood government contracting better than most people in the room.
“What concerns you?” I asked.
Tyler pointed to a paragraph.
“The amendment allows the contractor to report vehicles available through affiliated companies.”
I nodded.
“That isn't necessarily unusual.”
“No.”
“But?”