The Board Approved the Project
Board approval authorizes a project to move forward. It does not remove the execution risk that follows.
You are in the boardroom asking for approval to move forward with a $50 million new construction project.
It is the largest capital request you have ever brought to this board. If approved, it will reshape the company’s long-range plan, affect shareholder dividends for years, shift net income, and leave less funding available for other priorities.
You have felt that weight for months.
You negotiated the design contract. You pushed consultants to hit milestones. You reviewed invoices, answered internal questions, and rewrote the procurement language for the selected delivery method more times than you want to admit. You kept tightening scope language, trying to close gaps before they became problems.
You are tired, but today is about the vote.
The presentation goes well. The project justification aligns with the company’s plan to expand into other markets. The projected return clears the hurdle rate. The schedule feels achievable. The renderings land. The financial model shows dividends rising year over year once the facility is fully operational.
You close the slide deck and open the floor.
A board member who used to own a construction company leans forward.
“Before we vote, I have a couple questions.”
“What’s the estimate range at this stage?”
You answer honestly. At this level of design, the range is roughly minus 20 percent to plus 30 percent.
He does the math quickly.
“So we’re not approving a fifty-million-dollar project. We’re approving something between forty and sixty-five.”
He looks back at the return slide.
“What happens to the return if we’re at sixty-five?”
Before you respond, the accountant speaks.
“At sixty-five, our internal rate of return falls below the acceptable threshold. That changes the investment profile.”
The room shifts.
This is not about renderings or schedule sequencing anymore. It is about downside. And downside is what boards remember.
The former contractor asks another question.
“Who is the project manager on our side?”
You explain that the design team is engaged, the contractor will be selected through a structured process, and internal leadership will oversee major decisions.
He does not let it go.
“I’m not asking who is running meetings. I’m asking whether we have someone with the experience to keep us closer to forty than sixty-five.”
That reframes everything.
You have carried the design contract. You have refined procurement language and kept the process moving. But that is not the same as having a clearly defined, experienced owner-side lead whose job is to manage scope, pricing pressure, delivery risk, and decision-making before those issues compound.
The lawyer speaks next.
“Who drafted the contract?”
You explain that outside counsel prepared it using standard industry forms and language.
She nods.
“And who reviewed it on our side to confirm that risk is allocated intentionally, not just traditionally?”
She does not elaborate. She does not need to.
The board member follows up.
“How did we decide on this delivery approach?”
You walk through the rationale: speed of execution, market conditions, and the need for tighter alignment between design decisions and pricing. You explain that early contractor input shaped the recommendation, and that the structure was selected intentionally.
He listens quietly.
“When I was on the other side of the table, I liked this structure. Most of the risk stayed with the owner, and if scope was not tight, that is where margins tended to grow. I just want to be sure we understand that before we move forward.”
There is no accusation in his tone. Just experience.
The chair calls for the vote. Hands go up. The motion passes, by one vote.
There are brief congratulations around the room. As the meeting wraps, the chair looks at you and says, almost casually:
“Alright. Keep us out of trouble now.”
You gather your materials and leave the room.
The vote passed by one. The risk did not change.
Because board approval does not remove uncertainty. It makes clarity more important.
A board can approve the business case. It cannot approve away estimate volatility, immature scope, poorly allocated contract risk, or the absence of experienced owner-side leadership. It cannot approve away decisions that have not yet been framed clearly enough to make on purpose.
That work still has to be done.
And that is where many organizations get exposed. They treat approval as proof the project is under control, when in reality the hardest part is still ahead. Cost pressure, schedule constraints, and contract exposure do not usually appear all at once. They build quietly through assumptions that were never tested hard enough, responsibilities that were never defined clearly enough, and decisions that were made after flexibility had already started to disappear.
The board approved the project.
They did not approve unmanaged risk.
If your organization is taking a major capital project to the board, or has already received approval and needs stronger oversight after the vote, YCC helps owners manage the exposure that remains after authorization is granted.
