A Pause in the Work

The board approved an interim payment to Ellis Construction after confirming the contractor's identity and the amount owed. Two committee members signed the authorization, and a separate employee verified the bank details by calling the contractor at a number from the original contract. The work could resume while the disputed payment was investigated.

Leila visited the site with the project manager. She asked about the width of the entrance, the handrail and the route from the parking area. The project manager wrote down each question and promised to have the accessibility assessor review the completed work.

“We want families to use the room,” Leila said. “We also want them to reach it safely.”

My father called the board's decision an overreaction. At a meeting with Ms. Patel, he argued that the company could not afford to pause whenever an invoice looked unusual.

“Then we need a process that checks unusual invoices quickly,” she said. “Ignoring them isn't a process.”

Daniel interviewed the accounts-payable staff. One employee, Sara, described receiving an email that appeared to come from the contractor, asking for a change in bank details. She followed the existing procedure by uploading the revised invoice and sending it to a manager for approval. The procedure did not require a second check by telephone.

The manager's approval was recorded, but the message itself had been deleted from the shared inbox. Sara had saved a copy in a folder for the project. Daniel asked her to provide it directly to the review team. She did so and explained that she had kept it because the new account number looked unfamiliar.

“Did you raise that concern?” he asked.

“I mentioned it to my manager. He said the contractor had confirmed it.”

The manager said he did not remember the conversation. The review team recorded both accounts and checked the available messages. A calendar entry showed a call with someone claiming to represent the contractor, but it did not establish what was discussed.

The company contacted the bank and its legal advisers. They began a formal effort to trace and recover the payment. No one promised that the money would be returned. The committee told the grant administrator about the discrepancy and the steps underway, including the limits of what had been established.

My father objected to that disclosure. “We could have fixed it before anyone knew.”

Ms. Patel replied, “The grant agreement requires reporting a material issue. We can explain what we know and update them as we learn more.”

He turned to me. “Are you enjoying this?”

“No. I would rather the entrance had been finished and the payment had reached the right company.”

He seemed disappointed that I would not admit to a revenge plot. I had been hurt by the way he spoke to me, but the review was not a stage on which I needed him to lose. It was a way to establish facts and protect the project.

After the meeting, Sara asked whether she was going to lose her job. I could not answer for Lane Holdings. I told her the review would report what the records supported and that she could speak with the committee's independent contact if she felt pressured. Daniel gave her the contact details in writing.

A week later the contractor returned to the site. Leila sent Ms. Patel a photograph of the handrail being installed. She did not post it as proof that the entrance was complete. She wrote: Work has resumed. We will announce an opening date after the final inspection.

I read the message twice. It was a small model of what the entire company needed: a statement that distinguished progress from a finished result.