Eleanor lowered her folder.
“Will someone actually contact us?”
“Yes.”
She studied my face.
Then nodded.
“That's all I'm asking.”
But I knew it wasn't.
She was asking whether the system would take her son's experience seriously.
Whether the records would be examined.
Whether the promises made during emergencies meant anything when the emergency arrived.
And whether the people responsible for those promises were willing to confront uncomfortable facts.
After the meeting, I approached Eleanor and Michael.
“Mrs. Price?”
She turned.
“Director Coleman.”
“Jordan is fine.”
She looked uncertain.
I smiled faintly.
“I wanted to thank you for speaking.”
She nodded.
Michael extended his hand.
“I'm Michael.”
I shook it.
“Nice to meet you.”
He looked at me.
“Do you know what was frustrating about that day?”
I waited.
“It wasn't just the delay.”
I nodded.
“It was that nobody could tell us what was happening.”
He looked toward his mother.
“We kept calling. People kept saying transportation was assigned. But nobody knew where it was.”
I listened.
“And when the first vehicle arrived, the driver looked at my chair and said he couldn't take me.”
His voice remained steady.
“But I could tell he was embarrassed too. He'd been sent without the right information.”
I nodded.
“That sounds like a serious coordination failure.”
Michael looked at me.
“Exactly.”
He paused.
“I'm not asking you to guarantee nothing ever goes wrong.”
“I understand.”
“I just want someone to be honest when the plan isn't working.”
I looked at him.
“That is a reasonable expectation.”
Eleanor watched us.
Then she said, “We've kept every message.”
I nodded.
“Those records may be useful.”
She handed me a card.
“Call us.”
“I'll make sure the appropriate review team contacts you.”
Michael smiled faintly.
“Thank you.”
As they walked away, I remained standing beside the emptying auditorium.
I thought about the old transportation plans.
The fleet reports.
The duplicate vehicle assignments.
And the people who had relied on them.
The numbers were no longer abstract.
They had names.
Faces.
Families.
And memories of waiting.
The independent contracting review continued for months.
Investigators examined payment records, subcontracting arrangements, vehicle registrations, insurance documents, and communications among the companies involved.
My office cooperated with requests for operational information.
We did not conduct the investigation ourselves.
That separation was important.
I had previously reviewed Southeastern's reporting practices.
I was responsible for the current emergency plans.
And I had a professional interest in understanding whether our earlier decisions had been based on incomplete information.
Those circumstances made independent examination essential.
During that period, I received regular updates about operational corrections, but not confidential investigative conclusions.
I sometimes found the separation frustrating.
I wanted answers.
I wanted to know how the discrepancies had developed.
I wanted to know whether people had deliberately misrepresented resources.
But wanting answers did not entitle me to control the investigation.
That was another lesson I had learned over the years.
One morning, Patricia Ellis asked me to meet her.
When I entered her office, she was sitting beside a stack of documents.
“Jordan, we need to discuss the earlier Southeastern review.”
I sat down.
“Okay.”
She opened a folder.
“The inspector general's team has asked for all records from the original capacity discrepancy.”
I nodded.
“We've preserved them.”
“Yes.”
She looked at me.
“They may also want to interview you about your conclusions at the time.”
“That's fine.”
Patricia paused.
“I want you to understand something.”
I waited.
“The fact that you accepted the company's corrective plan doesn't necessarily mean your decision was unreasonable.”
I nodded.
“But?”
“But we need to examine whether the scope of the review was sufficient.”
I looked down.
She continued.
“Your team verified updated fleet numbers, but the review did not independently trace every affiliated vehicle assignment.”
I remembered.
At the time, we had focused on the difference between the company's reported fleet and its actual operational capacity.
We had not examined the broader network of affiliated companies.
“That's true,” I said.
Patricia nodded.
“Was that consistent with the review's defined scope?”
“Yes.”
“Did you have evidence at the time suggesting a broader problem?”
“Not that I recall.”
“Then say that.”
I looked at her.
She continued.
“Don't defend the review as perfect. Don't condemn it with hindsight. Explain what you knew, what you checked, and why you reached your conclusion.”
I nodded.
“That I can do.”
Patricia smiled faintly.
“I know.”
The interview took place two weeks later.
Two investigators from the inspector general's office asked me about the original review.
They were professional.
Precise.
Patient.
They examined meeting notes.
Emails.
Supporting documents.
The corrective action plan.
And the decisions my team had made.
At one point, an investigator named Allison Grant asked, “Director Coleman, did you consider whether Southeastern's reported vehicles might also be listed by affiliated companies?”
I thought carefully.
“Not as a separate issue during that review.”
“Why not?”
“The discrepancy we were examining concerned the company's reported fleet size compared with its available operational vehicles.”
She nodded.
“Did you believe the corrected figures were reliable?”
“Yes, based on the documentation we received and the verification performed.”
“Would you reach the same conclusion today?”
I paused.
“Not without additional verification.”
“Why?”
“Because we now have information suggesting that vehicle availability may have been represented differently across related contracts.”
She made a note.
Then asked, “Do you believe your earlier review failed?”
I considered the question.
“I believe it addressed the problem we had identified. I also believe the current evidence raises questions that the earlier review did not resolve.”
She looked at me.
“Is that a yes?”
I shook my head gently.
“It's the most accurate answer I can give.”
For a moment, she studied me.
Then she nodded.
“Fair enough.”
The most difficult conversation came later that week.
Tyler entered my office carrying the original corrective action report.
He placed it on my desk.
“Jordan, I've been reviewing this.”
I looked up.
“What did you find?”
“Nothing new.”
He hesitated.
“But I keep thinking about something.”
I waited.
“When we first reviewed Southeastern, I was the one who recommended accepting the revised capacity figures.”
I remembered.
Tyler had done much of the detailed work.
“Yes.”
He looked down.
“What if I missed something?”
I considered that.
“We may have missed something.”
He swallowed.
“I should've checked the affiliate assignments.”
“Maybe.”
He looked at me.
“That's not very reassuring.”
I smiled faintly.
“I know.”
Then I leaned forward.
“Tyler, we need to distinguish between what we could reasonably have identified at the time and what became apparent later.”
He nodded.
“But if our process had a weakness, we need to correct it.”
“Yes.”
He sighed.
“I hate this.”
“So do I.”
For a moment, neither of us spoke.
Then Tyler asked, “Are you worried people will blame you?”
I considered that.
“Yes.”
He looked surprised.
I continued.
“I'm human.”
He smiled faintly.
“But I'm more worried about whether our plans were based on unreliable information.”
Tyler nodded.
“Me too.”
I looked at the report.
“Then let's focus on fixing what we can.”
The review's preliminary findings became public in early autumn.
They were more serious than I had expected.
The inspector general's office identified a network of affiliated transportation companies that had submitted overlapping capacity information for several emergency-service contracts.
Some vehicles had been listed as available under multiple agreements without clear disclosure of competing obligations.
Certain invoices contained charges that were not adequately supported by dispatch or service records.
The review also found weaknesses in the state's verification procedures.
But the findings were careful about responsibility.
Not every discrepancy was intentional.
Not every overlapping assignment resulted in a payment.
And the evidence did not establish that every company employee knew about the reporting problems.
The inspector general referred specific matters for further examination by the appropriate authorities.
The state procurement office suspended certain contract activities pending review.
Several companies cooperated.
Others disputed the findings.
Daniel Whitaker resigned from Southeastern Transit Services.
Richard Voss was placed on administrative leave while his role in the contracting process was examined.
No final conclusions about individual legal responsibility had yet been reached.
The public reaction was intense.
Some commentators described the matter as a major contracting scandal.
Others argued that the state was exaggerating administrative problems.
A few accused my office of failing to protect the public.
I read the coverage.
Then I turned off my phone.
Because the next hurricane season was approaching.
And regardless of what the investigation eventually established, people still needed reliable evacuation transportation.
We spent the following months rebuilding the regional transportation system.
Not from scratch.
But thoroughly.
We created a centralized vehicle-verification process.
Each provider had to identify specific vehicles, accessibility features, operational restrictions, and competing contractual commitments.
We developed procedures for confirming availability during exercises.
We revised dispatch coordination.
We required clearer documentation when vehicles were substituted.
We worked with disability advocates to improve evacuation planning for residents with mobility needs.
And we established a method for recording delays and failed assignments in a way that could be reviewed afterward.
The work was complicated.
It required cooperation from agencies that did not always agree.
It cost money.
It took time.
But the result was a system that relied less on assumptions.
And more on verifiable information.
Eleanor Price became one of our most persistent community advisers.
She attended planning meetings.
Asked difficult questions.
Reviewed public-facing transportation instructions.
And refused to accept vague explanations.
At first, some employees found her intimidating.
Then they began to appreciate her.
One afternoon, she sat across from me in a conference room.
Michael was beside her.
We were reviewing a revised evacuation information guide.
Eleanor pointed to a paragraph.
“This says residents should contact the transportation coordination center if their assigned vehicle is delayed.”
I nodded.
“Yes.”
“What happens if the center doesn't answer?”
I looked at Emily.
Emily made a note.
“We need to specify an alternate contact method.”
Eleanor nodded.
“And what if the resident doesn't have internet access?”
“We should include telephone and community contact options,” Emily said.
Michael leaned forward.
“What if the resident can't use a standard telephone?”
I considered that.
“Then the plan needs accessible communication options.”
He nodded.
“Exactly.”
We continued for another hour.
At the end, Eleanor closed her folder.
“You know something, Jordan?”
“What?”