She added a note to her assessment.
Finding 1: Potential inconsistency between investor-facing summary and amended infrastructure guarantee. Further clarification required. Do not characterize as misrepresentation without reviewing document history and responsible-party explanations.
Then she moved to the construction budget.
At 8:06 p.m., she found another problem.
The environmental remediation estimate had been revised upward in an engineering attachment.
The increase was not enormous relative to the total project cost, but it was material to the contingency reserve.
The main financial model appeared to use the earlier estimate.
Naomi checked the formulas.
The older number flowed through several tabs, affecting the projected financing requirement and the estimated return.
She searched for a later version.
There was one.
It contained the revised estimate.
But it was marked DRAFT — NOT FOR INVESTMENT COMMITTEE.
Naomi examined the metadata.
The file had been created after the engineering update and before the most recent investor presentation.
Why had the updated estimate not been incorporated into the main model?
She wrote another question.
Finding 2: Main model appears to rely on superseded environmental remediation estimate despite the existence of a later draft containing revised costs. Need to establish whether the draft was approved, whether the revised figure is reliable, and why the main model was not updated.
She continued.
The next two hours produced no dramatic discovery.
Instead, they produced a series of smaller inconsistencies.
A financing schedule used a date that did not match the amended agreement.
A projected sale date assumed that a permitting milestone would be achieved before the current public timetable suggested it could be completed.
A contingency line appeared in one spreadsheet but was not clearly reconciled with the figure used in the executive summary.
Each issue could have an innocent explanation.
Together, they created a pattern that required careful examination.
At 10:37 p.m., Naomi closed the spreadsheet and stood to stretch.
Her apartment was quiet.
The city lights shone through the window, and the reflection of her desk lamp hovered against the dark glass.
She made tea, returned to her chair, and opened a blank document.
She titled it:
Preliminary Risk Assessment — Hale Waterfront Development
Under the title, she wrote a sentence that would guide the entire review.
The purpose of this assessment is not to determine whether the project should proceed, but to identify whether the information currently available supports the assumptions being presented to decision-makers.
She read it twice.
Then she continued.
The findings below are preliminary and should not be treated as a substitute for a full engineering, legal, or financial audit. Each issue should be verified against the complete record before any conclusion is drawn about responsibility or intent.
Only after writing those qualifications did she begin describing the discrepancies.
She was nearly finished with the first section when her phone rang.
Richard Cole.
Naomi answered.
“Hello?”
“Have you started reviewing the documents?”
“Yes.”
“And?”
“I've identified several issues that need clarification.”
Richard was silent.
“How many?”
“Three material questions so far, plus several smaller inconsistencies.”
He exhaled.
“Can you send me your preliminary notes?”
“I can send you the questions. I won't send conclusions until I've had an opportunity to verify the underlying information.”
“That makes sense.”
“Richard, I need to ask you something.”
“Go ahead.”
“Was the environmental remediation estimate updated before the most recent investor presentation?”
Another silence.
“Yes,” he said finally. “The engineering team provided an updated estimate.”
“Was it incorporated into the main financial model?”
“I believe the team was working on that.”
“Was it incorporated before the presentation?”
“I would need to check.”
Naomi looked at the document on her screen.
“The current model appears to use the earlier figure.”
Richard said nothing.
She continued.
“I also found a discrepancy involving the infrastructure guarantee.”
“Which discrepancy?”
“The summary describes the guarantee as protection against certain delay-related costs, but the amended agreement appears to make the guarantee conditional on a milestone that depends on the infrastructure agreement itself.”
Richard's breathing changed.
“I'll need to review the exact language.”
“Of course.”
“Please don't send anything to the investors yet.”
“I haven't agreed to send anything directly to the investors. But the contract requires material findings to be reported to the investment committee.”
“I understand.”
“Then I assume we agree that the issues need to be examined.”
“Yes.”
He sounded tired.
Before ending the call, Naomi asked, “Richard, do you believe the project can still proceed successfully?”
He took several seconds to answer.
“I believe it can.”
“Is that based on the current model?”
“It is based on the project as I understand it.”
“That isn't quite the same thing.”
“No,” he said quietly. “It isn't.”
At 7:30 the following morning, Naomi received a calendar invitation for an emergency meeting at Hale Urban Holdings.
The attendees included Victor Hale, Richard Cole, the company's general counsel, the chief financial officer, and two representatives of the project team.
The meeting title was brief.
Waterfront Project — Preliminary Findings
Naomi arrived at the office at 8:55.
The atmosphere was different from her previous visit.
Employees moved quickly through the corridors. Several people stood in small groups near the conference rooms, speaking in low voices. A woman carrying a stack of documents nearly collided with Naomi before apologizing and hurrying away.
Richard met her at the elevator.
“Thank you for coming.”
“What's happened?”
“The investors requested an update this morning.”
“About the issues I raised?”
“About the project generally.”
He looked exhausted.
“Victor wants the team to understand the concerns before we respond.”
They entered the conference room.