EU procurement rules make life-cycle costing an evidence model

Life-cycle cost is a defined evaluation model

The direct answer in Article 68 is that life-cycle costing can extend beyond purchase price, but it is not an invitation to insert an opaque total-cost number. The Directive identifies costs borne by the contracting authority or other users, including acquisition, use, such as energy and other resource consumption, maintenance, and end-of-life costs such as collection and recycling. The selected components still have to fit the procurement and the stated method.

A defensible record should therefore name each included cost category, the relevant period and unit, the quantity or usage assumption, the data source, the formula, currency and timing treatment where applicable, and the accountable owner. It should also distinguish a tenderer-supplied value from an authority assumption or derived calculation. If a cost category is excluded or cannot be evaluated comparably, that boundary should be visible rather than silently represented as zero.

Environmental externalities require a verifiable monetary method

Article 68 permits life-cycle cost to include costs attributed to environmental externalities linked to the product, service, or works during its life cycle. It gives greenhouse-gas and other pollutant emissions as examples. The condition is important: the monetary value must be capable of being determined and verified. A sustainability label, qualitative preference, or proprietary score is not automatically the same as a life-cycle cost under this provision.

Where environmental externalities are monetized, the method must use objectively verifiable and non-discriminatory criteria. It must be accessible to interested parties, and the required data must be capable of being supplied with reasonable effort by normally diligent economic operators, including operators from third countries that are parties to relevant procurement agreements. If EU legislation makes a common method mandatory, that method must be used. The version and legal basis of the method belong in the evaluation record.

Disclosure makes the calculation contestable before award

The procurement documents must state both the data tenderers are expected to provide and the method the contracting authority will use to determine life-cycle costs. That requirement creates an evidence boundary before bids are scored. Suppliers should be able to understand the inputs, and evaluators should apply the stated method rather than introducing new cost factors or weights after seeing proposals.

A strong system retains the published method, solicitation version, questions and clarifications, each original input, validation and normalization action, calculation output, exception, evaluator note, approval, and final rationale. It should recalculate deterministically and show the effect of a corrected input without overwriting the original submission. Access controls are also material: changing a method or assumption after the deadline must be governed, visible, and handled under the applicable procedure.

What a procurement platform should demonstrate

A useful product test starts with a disclosed model that combines acquisition, energy or resource use, maintenance, end-of-life, and one eligible environmental externality. Enter bids with different units, a missing value, an implausible assumption, a correction, and a late attempt to change the method. Reviewers should inspect validation, clarification, version control, equal treatment, calculation reproducibility, approval, audit history, and the explanation available to decision-makers and tenderers.

Directive 2014/24/EU requires implementation in Member State law and does not decide the lawful method for a particular procurement. Contracting authorities, procurement and technical teams, economists, sustainability specialists, auditors, and counsel remain responsible for applicability and design. Software can calculate the approved model and preserve evidence; it cannot make weak assumptions objective, make unavailable data reasonably obtainable, or turn an undisclosed criterion into a defensible award basis.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Procurement Technology Current will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.