By the third week, the investigation had become a test of patience.
Not just mine.
Rebecca's team was answering requests from attorneys, auditors, directors, and employees who feared their names would be exposed.
Richard's representatives submitted documents showing that some earlier complaints had been investigated properly.
That evidence mattered.
The review could not treat everything that happened under his leadership as misconduct.
One accusation involving a denied promotion turned out to have a documented business explanation.
The employee had lacked a required certification.
Another complaint about a supervisor's language was supported by three separate accounts.
The investigators had to make those distinctions without assuming all accounts were either true or false.
I received only the governance summary.
It included a worrying observation.
Employees had different understandings of how to report concerns.
Some believed the division office was the only place they could go.
Others thought anonymous complaints would be traced back to them.
Our official policy said otherwise.
A policy nobody trusts is a weak protection.
Elias proposed a company-wide review of reporting channels, not just at North River.
I supported it.
I also asked what training managers received when they were promoted.
The answer was uncomfortable.
Technical performance counted far more than their ability to supervise people fairly.
We had rewarded production.
We had assumed leadership would follow.
That was an oversight no single disciplinary action could correct.
On Thursday, Daniel asked me to meet him at the park near his office.
We walked beside a narrow lake.
He told me he and Vanessa had attended one session with a couples counselor.
“Did it help?” I asked.
“It showed me how far apart we are.”
He picked up a fallen leaf.
“The counselor asked us what we needed to feel safe disagreeing.”
“What did you say?”
“That I needed Vanessa to stop involving her parents every time we argued.”
“And Vanessa?”
“She said I needed to prove I wasn't ashamed of her family.”
I watched a duck move through the reeds.
“That's a difficult place to begin.”
“She said I should ask you to end the investigation.”
“Did you?”
“No.”
He looked at me.
“Mom, she thinks refusing to ask means I don't love her.”
“What do you think?”
“I think love shouldn't mean doing something wrong.”
We continued walking.
Daniel told me about the day he first met Vanessa.
She had arrived early for a community arts fundraiser.
She had spent an hour helping volunteers arrange tables.
He remembered her laughing when a folding chair collapsed beneath a box of programs.
“She wasn't like this all the time,” he said.
“I believe you.”
“Her family gets under her skin.”
“That's possible.”
“It doesn't excuse how she's acting.”
“No.”
He sighed.
“I wanted you to know why I fell in love with her.”
“Thank you for telling me.”
We sat on a bench.
I remembered Thomas explaining once that people could be generous in one setting and fearful in another.
The question wasn't whether a person had good moments.
The question was whether they would take responsibility for the hurtful ones.
I didn't say that to Daniel.
He was doing enough thinking without another lesson from me.
That evening, Vanessa sent me a short email.
It had no greeting.
She asked me to meet Richard at his house and clear up the misunderstanding.
She wrote that a family should protect its own.
I read the message twice.
Then I replied that I would not discuss the workplace investigation privately with anyone involved.
I added that I was willing to speak with her someday about our personal relationship.
No answer came.
Meanwhile, the payroll audit uncovered errors in meal-break records.
Some were caused by an outdated timekeeping system.
Others required individual review because supervisors had edited entries without adequate explanations.
We authorized corrections once the amounts could be verified.
Employees would be told how to dispute the calculations.
The finance team estimated that completing the process would take weeks.
It was tedious work.
That was what doing it properly looked like.
At the next governance meeting, I asked whether workers had been informed about the changes.
Nora said the company had arranged paid information sessions on different shifts.
Translation services were available where needed.
Employees could ask questions without their direct supervisors present.
There was no applause when she finished.
We simply moved to the next agenda item.
I was glad.
This was not a ceremony.
It was repair work.
Then Rebecca raised an issue we hadn't anticipated.
Someone had sent copies of confidential interview questions to several North River managers.
The review team didn't yet know how they had circulated.
The documents contained no witness names.
But sharing them could undermine trust in the process.
Richard's attorney denied that his client was responsible.
The investigators were checking access logs and document distribution records.
Rebecca said the legal implications depended on what they found.
I asked her to avoid speculation.
After the meeting, I remained alone in the conference room.
I thought about that polished dining table at the Whitmore mansion.
Friday night had seemed like a simple question of who was kind and who wasn't.
Now people who had never attended that dinner were deciding whether they dared tell the truth about their jobs.
I couldn't fix that with a triumphant speech.
I could only help make sure the system kept working after the headlines and gossip disappeared.
The possibility of postponing the wedding had opened a financial question Daniel hadn't wanted to confront.
The venue had already received a substantial deposit.
The contract allowed a date change under certain conditions but did not promise a full refund.
The photographer had reserved the day and turned down other work.
Several suppliers had purchased materials.
Daniel understood that calling off a celebration did not erase those costs.
He gathered the contracts in a binder.
Vanessa had copies of most of them.
For a few, he had only emailed approvals with no final signed document.
He asked a lawyer for advice about his own obligations.
The lawyer told him to avoid making assumptions about who owed what until the documents were reviewed.
That answer frustrated him.
He had wanted a simple rule.
Instead he got a list of practical steps.
Confirm the cancellation policy.
Ask for itemized costs.
Document each person's approval.
Negotiate rather than make threats.
Daniel called me afterward.
“I never thought the paperwork would feel so personal,” he said.
“What part is hardest?”
“Every vendor asks whether we want to reschedule or cancel. I don't know what to tell them.”
“Then don't commit to a new date until you're sure.”
He sighed.
“Vanessa wants me to reserve next summer.”
“Do you want that?”
“I don't know.”
“That sounds like an answer for now.”
On Sunday, I spent the afternoon sorting Thomas's papers.
I had kept more of them than I realized.
There were old insurance renewals, drawings of our first warehouse, and notes from long meetings.
I found a handwritten list of questions he'd prepared before hiring our first operations manager.
One question stood out.
That evening, I checked the letter we planned to send to employees after the wage corrections.
It began with an apology for errors identified in timekeeping records.
It explained that people would receive individual calculations and a way to request review.
It did not ask them to be grateful for the payment.
I asked Finance to remove a sentence praising the company's generosity.
Paying what was owed wasn't generosity.
The director agreed immediately.
By the time the revised letters went out, the language was plain and accountable.
Several employees still disputed the figures.
That did not mean the effort had failed.
It meant the process needed to hear them and check the details again, where appropriate.
I found the experience more convincing than any speech about values.
What do you do when someone on your team tells you something you don't want to hear?
Thomas had circled it twice.
I remembered the candidate's answer.
He had said he listened politely and then decided whether the person was right.
Thomas had asked how he knew he had listened if he never checked the evidence.
The man hadn't known what to say.
We didn't hire him.
I put the list in my handbag to show Elias.
At Monday's leadership development session, I read the question aloud without naming its author.
Several managers gave thoughtful answers.
One said he scheduled private follow-ups so employees would not be embarrassed in front of colleagues.
Another said he asked for a second perspective before acting.
A third admitted that when the team was behind schedule, he sometimes treated questions as obstacles.
That admission led to the most useful discussion of the morning.
The managers described pressures they faced when production targets were tight.
Some had been promoted for solving problems quickly.
They had never learned how to distinguish a delay caused by a complaint from a delay caused by neglect.
Elias proposed adding management quality to the performance review system.
He wanted evidence of fair scheduling, timely responses to safety concerns, and documented follow-through.
I supported the proposal but asked for safeguards.
“We shouldn't reward managers merely for having fewer complaints,” I said.
“Otherwise they'll learn to discourage people from reporting them.”
The HR director agreed.
We spent an hour refining the measures.
It was tedious.
I was relieved that it was.
Repairing management habits should not feel like the final scene of a movie.
It should feel like people doing serious work.
At home that evening, I found a voicemail from June at the community kitchen.
They were short of volunteers for Wednesday's lunch shift.
She asked whether my schedule allowed me to help.
I called back and said yes.
For two hours on Wednesday, I chopped carrots and stacked bowls.
Nobody asked about Richard.
Nobody called me Madam Chair.
June told me the soup needed more pepper.
I added it.
She tasted another spoonful.
“Better,” she said.
That was the entire performance review.
Before leaving, I helped June scrub the large soup pots. I had barely finished when she found another stack beside the stove. She thanked me, handed me a fresh cloth, and went back to work. The task was not glamorous. It was necessary. I thought of Richard at the dinner table, and wished he could have seen how much dignity there was in doing it without an audience.
On Friday, our finance director presented the first corrected payroll statements.
They showed the dates reviewed, the hours verified, and the amounts to be paid.
A sample letter explained how employees could question a calculation.
I asked whether the letters had been tested with people outside the payroll department.
They hadn't.
We asked a small employee advisory group to review the wording without seeing anyone's private figures.
They flagged several confusing terms.
The payroll team revised the explanation.
It took an extra day.
The result was clearer.
I wondered how much frustration could be avoided by asking that question at the beginning of every project.
Elias said we could build user testing into future administrative changes.
He put it on the follow-up list.
I was satisfied to see a name and a deadline beside it.
A promise without an owner tends to become a memory.
A promise with a responsible person has a better chance of becoming work.
I went home feeling that we'd made a small but genuine improvement.
My phone buzzed.
Daniel had sent a photograph.
It showed his engagement ring box on a bare wooden table.
Below it were five words.
We have postponed the wedding.
Click here to continue reading: PART 7: My Son Faced a Harder Choice While Catherine Finally Explained Her Silence at Dinner
The Dinner Insult That Followed Me Home and the Questions I Had to Ask Before Monday
Part 6 of 12
