The invitation arrived in February, almost fifteen months after the assault.
Sarah forwarded it to Chloe with a short note explaining that Richard Vance wanted to discuss a possible role in an independent review of Apex Medical Supply's procurement procedures. The company had completed the first stage of its internal reforms and wanted an outside technical perspective on how project records could be misused to support fraudulent payments.
Chloe read the message twice before calling me.
“I'm not sure I want anything to do with Apex.”
“You don't have to.”
“They were happy to believe Julian when he said I was unstable. Now they want my expertise.”
“Those can both be true,” I said. “The question is whether the work would be worthwhile to you.”
She exhaled.
“I hate that you're right.”
We agreed that she should not answer immediately. She could ask for the scope of the review, the compensation, the expected time commitment, and the safeguards that would prevent the company from using her personal experience as publicity.
If she chose to participate, it would be because the work suited her professional interests, not because Richard wanted to feel that Apex had made amends.
The next morning, Chloe wrote back requesting a formal description of the proposed assignment. She also asked whether the review would be conducted by an independent team and whether she would have direct access to the relevant technical records.
Richard's response arrived within two days. The company had retained an external compliance firm to oversee the project. Chloe would not report to the executives involved in the original scheme, and her work would be limited to examining technical documentation and procurement controls.
The fee was consistent with her professional experience. She could decline without affecting the restitution process or any other legal matter.
Chloe took the proposal to her adviser and reviewed the terms. She asked Sarah to confirm that the arrangement did not conflict with any restrictions or obligations arising from the criminal proceedings. Once those questions were answered, she agreed to an initial meeting.
She told me she felt nervous on the drive to Apex's headquarters.
“I haven't been inside that building since before Thanksgiving.”
“Would you like me to come with you?”
She considered it, then shook her head.
“No. I think I need to walk in by myself.”
She arrived ten minutes early and checked in at reception. The lobby looked much as she remembered it: polished stone floors, glass doors, and framed photographs of company milestones. A receptionist offered her coffee and directed her to a conference room on the third floor.
Richard was waiting with two representatives from the external compliance firm.
He stood when Chloe entered.
“Thank you for coming,” he said. “I know this isn't an easy request.”
She shook his hand and took the chair nearest the door.
“I agreed to discuss the work. I haven't agreed to anything beyond that.”
Richard nodded.
“That's entirely fair.”
The meeting began with the compliance firm's director outlining the project. The team wanted to understand how the procurement process had allowed payments to be approved against canceled projects, how technical reports had been reused without proper verification, and what changes would make similar manipulation more difficult.
Chloe asked for examples of the revised controls.
The director explained that the company had separated vendor approval from payment authorization, added independent confirmation for project status, and required a documented technical review whenever an engineering report was attached to a procurement file. Employees would also have a protected channel for reporting concerns.
Chloe listened closely.
“Who verifies that the project is still active?” she asked.
“The project manager.”
“And who confirms the manager's status report before payment?”
“The compliance team, for payments above the threshold.”
“What happens if the manager and the procurement officer are the same person?”
The director paused.
“That shouldn't happen under the revised structure.”
“But what prevents it?”
They discussed the question for several minutes. Chloe pointed out that a policy could be well written and still fail if the people responsible for checking it were relying on the same source of information. The review needed to test whether the controls worked in practice, not merely whether the company had adopted them on paper.
Richard watched her with an expression I had never seen on his face during the marriage. He was listening to Chloe as a professional whose judgment mattered, rather than as a difficult spouse described by one of his executives.
At the end of the meeting, he asked whether she would consider joining the review team for six weeks.
“I'll consider it if the scope remains technical,” Chloe replied. “I won't give interviews about my marriage, and I won't participate in any public announcement about the company's response to the case.”
“Understood.”
“I also want the right to document concerns that aren't resolved. I'm not going to sign a report saying the controls are adequate if I don't believe they are.”
The compliance director agreed that the report would identify unresolved weaknesses and include recommendations for further testing.
Chloe left with a copy of the proposed terms. She did not sign them in the conference room. She reviewed the agreement with her adviser at home, made two requested changes, and returned the signed version only after the company accepted them.
When the assignment began, she treated it like any other engineering project. She examined the records, tested the approval sequence, and documented inconsistencies. She did not speculate about people's motives when the paperwork did not support a conclusion.
One afternoon, she discovered that a revised vendor form allowed the same employee to enter a project code and certify that the project remained active. The system recorded the action as two separate steps, but both entries came from the same account.
She marked the issue and asked the compliance team to reproduce the process using a test account.
The weakness was confirmed.
The company changed the system so that project-status verification required a second authorized user. It also added an automated warning when a payment request referenced a canceled project.
Chloe was pleased with the result, though she remained cautious about declaring the problem solved. She recommended another review after the changes had been in use for several months.
At the end of the six-week assignment, Richard invited her to a meeting with the board's audit committee. Chloe agreed to present the technical findings but declined an offer to be photographed beside the company president.
The presentation was straightforward. She explained the weaknesses, showed how the controls had been tested, and identified the changes that remained incomplete. She did not mention Julian except where his actions were necessary to explain the original failure.
When she finished, one board member asked whether she believed the revised system would prevent future fraud.
“No system can guarantee that nobody will attempt to misuse it,” Chloe replied. “The objective is to make unauthorized activity harder to conceal and easier to detect. Your controls need to be tested regularly, and the people responsible for reviewing transactions must be independent of the people requesting them.”
The board accepted the report and authorized additional testing.
Afterward, Richard approached her in the corridor.
“You did excellent work,” he said.
“Thank you.”
“I should have listened to you sooner.”
Chloe studied him.
“Yes,” she said. “You should have.”
He looked as though he had expected her to soften the answer.
“I believed Julian because he was someone I knew professionally. I thought I understood his character.”
“You understood the version of himself he showed you.”
Richard nodded.
“I don't expect you to forgive me.”
“Good. Because I haven't decided what I feel about it.”
She said it without hostility. She was not trying to punish him. She was simply refusing to make his discomfort her responsibility.
They parted politely.
On the drive home, Chloe called me.
“I think that went well.”
“Did you enjoy the work?”
“I did. I hated being back in the building at first, but once we started looking at the records, it felt like a normal technical assignment.”
“Would you do it again?”
“Maybe. If the scope is clear.”
She laughed.
“I think I've finally learned that I can say yes to the work without saying yes to everything attached to it.”
That evening, she cooked dinner at her house. She had planted herbs in small pots by the kitchen window, and the room smelled of basil and garlic. We ate at her secondhand dining table while she told me about the remaining system changes.
When I asked whether returning to Apex had stirred up memories of Julian, she admitted that it had.
“I saw the room where he used to hold those quarterly presentations. I remembered how proud he was of himself, how everyone listened when he spoke.”
“Did it upset you?”
“For a while. Then I remembered that the room was just a room. He doesn't get to own every place where I once felt small.”
She cleared the plates and carried them to the sink.
“I wanted to prove I could walk into that building without falling apart. But I didn't have to prove it to anyone. I just wanted to know whether I could do the job.”
“And now you know.”
She smiled.
“Now I know.”
The following month, Apex issued an internal report summarizing the changes to its procurement system. Chloe's name appeared among the external technical reviewers, but the company did not use her personal history to promote the reforms.
That was exactly what she had requested.
She continued working at her engineering firm, where she was given responsibility for a more complex project. Her manager encouraged her to mentor junior staff, and she discovered that she enjoyed explaining difficult concepts to people who were eager to learn.
Sometimes she still thought about the morning at Bay Six. The memories had not vanished. But she was no longer measuring every new experience against that day.
She had returned to a building associated with her former marriage, done work she valued, and left on her own terms.
Julian had once tried to make her feel that her professional judgment was unimportant. Now she was using that judgment in a room full of people who had to take it seriously.
She did not need their admiration.
She needed the work to be honest.
Click here to continue reading: PART 11: The Last Restitution Notice Arrived Before Thanksgiving, and Chloe Finally Saw the Difference Between Justice and Getting Her Old Life Back
The Phone Call Before Sunrise Revealed What My Daughter’s Husband Believed He Could Get Away With
Part 10 of 12
