What Makes a Capital Project? (And What the Forecast Can’t Tell You)

A five- or ten-year forecast identifies individual capital needs. The owner still has to decide which ones belong together.

The five-year forecast placed lighting in Year 3, ceilings and paint in Year 5, and carpet in Year 6.

They appeared as separate line items. That did not necessarily make them separate projects.

Replacing the lighting would require access above the ceiling, protection of the occupied space, movement of furniture, and disruption to the employees working there. Completing the ceilings, paint, and carpet a few years later would mean returning to the same area and disrupting it again.

Each line item had its own remaining useful life.

But were they four future projects—or one?

Who Decided They Were Separate Projects?

A facility condition assessment may identify hundreds of capital needs across a five- or ten-year period.

Parking lots. Roofing. Façades. Windows. HVAC equipment. Electrical distribution. Lighting. Ceilings. Paint. Carpet.

Each asset is evaluated individually and assigned a condition, remaining useful life, anticipated cost, and recommended replacement year. That information gives the owner a view of what the portfolio may require.

It does not define the projects.

Somewhere between the condition assessment and annual capital approval, those individual lifecycle needs have to be organized into projects.

That does not always happen deliberately. Because the forecast is organized by asset and replacement year, the capital plan may carry the same structure forward. By the time leadership sees the funding request, the project boundary can appear settled.

A lighting replacement becomes a lighting project because that is how it appeared in the forecast. Two years later, the ceiling becomes another.

The forecast did its job. Someone still had to decide whether those renewals belonged together.

One Façade or Two Projects?

The same issue appears on a larger scale.

A New York City building may need façade repairs as part of its Local Law 11 compliance work. The forecast may show window replacement several years later.

The façade work may already require engineering, permits, scaffolding, sidewalk protection, and disruption to occupants. If the windows are approaching the end of their useful life, should the owner replace them while that infrastructure is already in place?

Maybe.

The windows may have meaningful life remaining. Replacing them early accelerates the expenditure and gives up some of that life. It could also make the façade project too large to fund or complete within the required period.

Separating the work has consequences too.

The owner may have to install scaffolding and sidewalk protection again several years later. Occupants may be disrupted twice. Newly completed façade work may have to be reopened at the window interfaces. Design, permitting, mobilization, and access costs may all return with the second project.

The question cannot be answered by looking only at the replacement year for the windows or the compliance deadline for the façade.

Someone has to compare one coordinated project against two separate ones.

When Separate Needs Belong Together

Capital needs do not have to share the same replacement year to belong in the same project. Sometimes the building tells you they belong together before the spreadsheet does.

The five-year forecast placed parking lot resurfacing in the current year. Drainage improvements were scheduled two years later. Curbs and exterior lighting appeared farther out.

Before defining the resurfacing project, the team considered the other work planned within the same footprint. None of it had reached its individual replacement year. But completing it before the new pavement went down could avoid cutting into the finished lot and mobilizing again several years later.

The resurfacing need created the project opportunity. Capital planning determined whether the later work belonged in it.

The forecast placed a roof replacement in the current year. The rooftop units were scheduled for Year 4.

Before defining the roofing project, the team considered the age and condition of the units, their supports and penetrations, and what replacing them later would do to the new roof.

The two needs were not scheduled for the same year. They still had to be evaluated as part of the same project decision.

That is what actually makes a project: not a shared date, but a shared moment when access, disruption, and opportunity line up.

It cuts the other way just as easily.

A funded project can turn into a magnet. Someone remembers the lobby carpet is tired or the parking lot striping is faded and asks whether it can just get added while the crews are already there. One addition rarely breaks a budget. A pattern of them does, and the original scope becomes harder to deliver.

The opposite failure is quieter. Each lifecycle item stays in its own lane because it sits in a different budget year or reports to a different department. Nobody connects the ceiling to the lighting to the carpet. The organization returns to the same area several times because separate projects were easier to budget than one coordinated project was to plan.

The test is simple: Does bundling the work avoid repeated access, mobilization, and disruption, or does it just make the project bigger?

Someone Has to Own the Tradeoff

Facilities wants the ceiling and finish work bundled with the lighting—one disruption to the floor instead of two. Finance wants the ceiling work to wait because the money falls in next year’s budget, not this one. Design and construction may see an efficiency in doing it all at once, or a scheduling and permitting risk the forecast never flagged.

Nobody in that room is wrong. That is the problem.

Three good arguments point in different directions, and none of the people making them necessarily owns the outcome.

Without someone accountable for the call, the scope follows whichever voice carries the most weight that quarter—not necessarily what best serves the building.

Sometimes scope creeps in a little at a time until the original budget no longer covers it. Other times, everything remains separate because no one owns the case for combining it.

The forecast does not assign that authority. Somebody in the room has to.

Before Approving the Project

Executives do not need to decide whether lighting, ceilings, paint, and carpet belong in the same project.

They need to know somebody already has.

Before signing off on a lifecycle replacement as a capital project, ask two questions:

What else will we disturb to complete this work, and when are we planning to come back?

Who decided what belongs in this project—and what was left out, and why?

The first question catches a project that is too narrow—one that will send a crew back to the same area in eighteen months.

The second catches a project that has grown beyond what it was meant to accomplish.

The forecast will tell you when an asset is due. It cannot tell you what belongs in the same project.

Someone drew that project boundary, deliberately or by default.

Before approving the project, leadership should know which one it was.