Definition

Value for money (VfM) is the assessment of whether an intervention delivers the best achievable result for the resources committed to it. In UK development practice it is structured around four questions, known as the 4Es, which follow the chain from money spent to change achieved.

Economy — are we buying inputs at the right price and quality? The cost of the inputs the intervention acquires: staff, vehicles, training venues, commodities, consultancy. Economy is about paying an appropriate price for an appropriate standard, not the lowest price available.

Efficiency — how well are inputs converted into outputs? The productivity of the conversion. Cost per household surveyed, cost per health worker trained, cost per kilometre of road. Efficiency questions are answered in unit costs and in timeliness.

Effectiveness — how well do outputs produce the intended outcomes? Whether the things delivered actually caused the change sought. A programme can be highly efficient at producing outputs that change nothing.

Equity — how fairly are the benefits distributed? Whether results reach the people who are hardest to reach and most disadvantaged, or concentrate among those who were easiest to serve.

Origin

The framework’s institutional form comes from the UK. DFID set out its approach to value for money in 2011, built around economy, efficiency and effectiveness — the 3Es — as a response to Treasury pressure to demonstrate that aid spending was justified. Equity was added as a fourth E in subsequent DFID practice and became standard; when DFID merged into the Foreign, Commonwealth and Development Office in 2020, FCDO inherited the framework, and it now flows down to FCDO’s implementing partners and their sub-grantees as a reporting requirement.

The 4Es framing has since spread well beyond UK-funded work, partly because no comparable, equally simple alternative has emerged.

The point is the balance

This is the part that consistently gets lost, and it is the whole idea.

Value for money is about the balance between the four Es, not about maximising any one of them. Each E can be improved at the direct expense of another, and a VfM assessment that reports strongly on one E in isolation is not evidence of value — it is often evidence that a trade-off was made without being examined.

Consider the trade-offs plainly:

• Economy against effectiveness. The cheapest trainer, the cheapest venue and the cheapest curriculum will improve your economy metrics and may produce training that changes no behaviour.
• Efficiency against equity. This is the most important tension in the framework and the least well handled in practice. Cost per beneficiary is always lowest where beneficiaries are densest and easiest to reach. Serving a remote settlement costs several times more per person than serving a peri-urban ward. A programme that optimises cost-per-beneficiary will systematically retreat from exactly the populations development funding exists to serve — and its efficiency dashboard will look excellent while it does so.
• Effectiveness against economy. The intervention that works may be the more expensive one. Concluding otherwise from a unit-cost comparison alone is the classic VfM error.

Equity was added to the framework precisely because the first three Es, applied on their own, contain a structural bias against reaching the marginalised. Reporting efficiency without equity alongside it reintroduces that bias.

Value for money is not cheapness. An intervention can offer excellent value at high unit cost, and terrible value at low unit cost. Any VfM discussion that resolves into “spend less” has misunderstood the framework.

Artefacts it produces

• A VfM framework for the programme: which indicators evidence each E, at what frequency, from which source.
• Unit cost analysis, with the cost basis stated — which costs are included, how shared and central costs are apportioned. Unit costs computed on different bases are not comparable, and most published comparisons quietly are not.
• Cost-effectiveness analysis where the outcome can be expressed in a common measure.
• Benchmarks, internal or external, against which the unit costs are read. A unit cost without a benchmark is a number, not a finding.
• A VfM narrative in periodic reporting, which is where the trade-offs are supposed to be argued rather than only tabulated.

How it relates to the other frameworks

• The logframe provides the outputs and outcomes that efficiency and effectiveness are measured against. VfM adds the cost dimension the logframe’s activities row largely leaves implicit.
• A results framework is usually the right level at which to assess VfM, because trade-offs between the Es become visible across a portfolio in a way they do not within one project.
• The OECD-DAC criteria overlap but are not the same. DAC efficiency is close to the efficiency E; DAC effectiveness carries the differential-results question that the equity E makes its own heading. The frameworks are complementary, and evaluations commissioned against both should say which questions each is answering rather than duplicating.
• A theory of change is what tells you whether an effectiveness finding is credible — it identifies where in the chain the money stopped converting into change.
• Outcome harvesting sits awkwardly with VfM, because retrospectively harvested outcomes resist unit costing.

Common mistakes

1. Reporting economy and calling it VfM. Procurement savings are one E of four, and the least informative one.
2. Cost per beneficiary with no equity lens. As above: the metric rewards retreat from hard-to-reach populations, and it does so silently.
3. Unit costs on undeclared bases. If overheads, capital and staff time are treated differently in two figures, comparing them is meaningless. State the basis every time.
4. Benchmarking against incomparable programmes. Different contexts, different populations, different intervention intensities. A benchmark is a prompt for a question, not a verdict.
5. Assessing VfM only at the end. The framework’s use is in steering decisions during implementation. A VfM annex written in the final quarter changed nothing.
6. Ignoring timeliness. Late delivery is an efficiency problem, and one that budget-execution reporting hides completely.
7. Treating the 4Es as four independent scores. They are a chain with trade-offs. A dashboard of four green lights that never discusses a trade-off has not assessed value for money.

How Monival supports this

Partially, and it is worth being clear about which parts.

The effectiveness side is where Monival is genuinely useful. Indicators carry baselines, targets and period actuals, with a defined means of verification and data source, so the outcome evidence a VfM assessment needs is in one place and traceable. Indicators fed from field data can be disaggregated by other questions on the same form — by location, by sex, by disability status, by any dimension you captured — which is the substrate an equity analysis is built on. Without that disaggregation, equity claims are assertions.

Monival also carries budgets and donors modules that hold the financial dimension of a programme alongside its results, which is where the cost side of an efficiency calculation starts.

The honest limits: Monival does not compute unit costs, run cost-effectiveness analysis, or produce a VfM assessment. Deciding the cost basis, choosing benchmarks and arguing the trade-offs between the Es is analytical work, not a report the software generates.

Where an organisation needs results and finance genuinely reconciled — actuals from the general ledger meeting results data so that unit costs are computed from real expenditure rather than re-keyed estimates — Sibasi delivers that as an implemented solution integrating Monival with Microsoft Dynamics 365 Business Central and the Power Platform. That is a delivery engagement with existing client references, not a feature toggle.