CAPEX arbitrage: deciding what to commit on an existing asset

Arbitrating a CAPEX budget is not about adding up desirable works. It is about choosing what you commit on an existing asset, in what order and under what conditions. The question is not only the amount, but the purpose: what stems from an obligation to be addressed, what maintains the use value of the building, and what aims to change its positioning.

These three purposes do not share the same urgency, the same tolerance to postponement, or the same sensitivity to the market. Distinguishing them allows you to prioritise without opposing, and to state what can wait a cycle, what conditions day to day operation, and what only makes sense if your holding strategy justifies it over the period considered.

Arbitrage relies on two distinct building blocks. The audit describes the actual condition and the points still to be resolved. The costing translates technical choices into budgets and schedules. Arbitrage comes afterwards: it compares trajectories, sets out assumptions and informs a decision. Without an audit, costing rests on guesses; without arbitrage, it remains a list of lines with no direction.

The first family covers compliance and safety. It funds what allows the building to be operated under acceptable conditions and to meet the requirements applicable to your asset. Those requirements depend on the file: use, configuration, history, installed equipment. They are checked item by item with the competent specialists, and not from a general rule transposed from another site.

The second family concerns upkeep and component end of life. Roof, facades, networks, technical equipment: each has a service life and a moment when replacement becomes more rational than repeated repair. This family funds operational continuity. Age, condition and maintenance history help anticipate these needs, while retaining an allowance for defects that are not visible.

The third family is transformation and repositioning: reconfiguring floor areas, changing a level of specification, addressing a different demand. Confusing these families produces two effects. A mandatory expense folded into a transformation project risks being postponed without checking its own deadlines. Conversely, a repositioning investment presented as constrained escapes any discussion of whether it is worth undertaking.

A costing is only worth as much as the reading of the building behind it. The technical diagnosis covers structure, services, envelope, equipment and their apparent condition. The capacity review looks at what the building can accommodate: grids, heights, loads, access, and the ability of the networks to absorb a use different from the one they were originally designed for.

Use and operating constraints come on top of this. An occupied asset imposes phasing, access arrangements, intervention windows and sometimes temporary installations. A continuously operated site cannot be treated like an empty building. These elements are not implementation details: they shape technical choices and weigh on the overall cost of the programme.

There remains the unknown. Some points can only be settled after surveys, opening up works or a specialist study. The aim is to identify them early, to measure their potential effect on the decision and to plan when they will be resolved. A named and bounded unknown stays manageable. An unmentioned one turns into a hazard once the works are already committed.

A single scenario describes a trajectory, but says little about the alternatives you give up. At least two scenarios allow comparison, and therefore choice. They must however be comparable: the same documented initial condition, the same time horizons, the same cost conventions, the same scopes. A minimal scenario and a transformation scenario are not judged on the amount committed alone, but on what each one makes possible afterwards.

Each scenario deserves to be described along the same axes: explicit assumptions, overall cost including identified contingencies, schedule and associated operating constraints, technical and calendar risks, degree of reversibility. Expected effects on letting or on an exit are treated as stated assumptions, expressed with their conditions, and not as results already embedded in the reasoning.

A sound set of scenarios also makes deferred choices visible. Postponing an intervention is not neutral: it may preserve an option, or on the contrary close one off because another element will have been renewed in the meantime. Making these sequences explicit lets you decide today knowing what the decision commits for later phases and what it leaves open.

The first mistake is costing without a diagnosis. You obtain a reassuring figure, built on implicit assumptions, which shifts as soon as the first discoveries are made. The second is placing contractor quotes side by side without a shared objective: each package is coherent on its own, the whole answers no strategy and leaves interfaces between trades unaddressed.

A third classic mistake concerns occupied sites. A programme designed as if the building were empty runs into working hours, nuisance, access and service continuity. Then comes the confusion between urgency and priority: what is most visible or most complained about takes precedence over what actually determines how the asset holds up over time.

The last mistake, and the most structural, is treating CAPEX independently of the holding strategy. A heavy programme on an asset you intend to sell in the short term, or a policy of continuous postponement on a long held building, can produce effects contrary to the original intent if the works address neither market expectations nor the intended use. The holding horizon is an input to the arbitrage, not a footnote.

The assignment begins with a diagnosis note: what was observed, what is documented, what remains to be verified. It provides a common basis for discussion and prevents each stakeholder from working on a different representation of the building. Findings are distinguished from interpretations, and the limits of the examination are stated explicitly.

Next comes a grid of costed and prioritised scenarios, built on stated assumptions, together with a proposed sequencing and a set of decision points. Each decision point specifies what needs to be known in order to decide, at what moment, and what postponement implies. The aim is to let you formulate a decision and the conditions attached to it.

This work replaces neither an in depth study of your file nor validation by the competent specialists on the technical and regulatory points that require it. What remains to be assessed is flagged as such. The scenarios describe possible trajectories and their conditions, with no guarantee of outcome. The decision, its timing and its scope remain in your hands.