MarchwardServices

MEAL

Measuring what security work actually changes

We help security and justice programmes understand what is changing, why it is changing and whether the improvement is likely to last. Our work covers monitoring, evaluation, accountability and learning, with clear reporting on what the evidence can and cannot show.

Evidence that informs the next decision

Agree the intended change, review what happens and adjust while there is still time to act.

A repeating cycle of agreeing outcomes, monitoring delivery, reviewing evidence and adjusting the work, with accountability throughout.
Accountability runs throughout. Findings state the strength of the evidence and its limitations.

An illustrative example

A training programme needs more than an attendance count

Attendance tells you who took part. Observing people at work shows whether they can apply what they learnt. A later review examines whether staffing, supervision and resources allow that improvement to continue.

The four strands, as we use them

Monitoring

We track whether activities are happening on time and to the required standard, while keeping an eye on changes in the operating environment. This shows how delivery is progressing and where it needs attention.

Evaluation

At agreed points, we examine what has worked, why and what should change. We use the six OECD DAC criteria: relevance, coherence, effectiveness, efficiency, impact and sustainability.

Accountability

We look at accountability both to the funder and within the institution itself. Reporting on expenditure matters, but so does whether the organisation is becoming more answerable to the people it serves.

Learning

We use structured reviews to compare what was intended with what happened, understand the reasons and agree changes. The findings need to inform the next decision, rather than remain in a report.

Will the improvement last?

We assess what can continue after external support ends, including the funding, people and authority needed to sustain it. Our method below explains how we model the position at twelve and twenty-four months.

Our method and evidence

The reasoning behind the work

Explore how we assess change, handle uncertainty and judge what can last.

Why accountability matters
In most sectors, accountability means reporting upwards to the donor
It is a duty owed by the implementer to the funder, discharged through quarterly returns. Useful, but it is administration.
In our sector, accountability is the thing being built
The Geneva Centre for Security Sector Governance lists accountability as one of the seven principles of good security sector governance, alongside transparency, rule of law, participation, responsiveness, effectiveness and efficiency. A police force that cannot be held to account is not a police force that has been reformed.
Accountability as an outcome
Does the complaints mechanism work? Does internal affairs take disciplinary action? Does the parliamentary committee see the budget? Does the oversight body use its powers? Those are measurements, and they belong in the results framework rather than in an annex.
We will use whichever term your framework uses
If your programme documentation says MEL, our reporting will say MEL. The distinction above is about what we measure, not about what we call it.
The challenges of measurement
Success often looks like nothing happening
The clearest evidence is not a slogan but a finding. The independent impact evaluation of a large United Kingdom police reform programme in the Democratic Republic of the Congo found serious crime fell significantly while people’s sense of safety moved on a different timetable entirely. It warned that perceptions of change can run ahead of actual change, in both directions.
Attribution is usually the wrong question
The field moved years ago from asking whether a programme caused an outcome to asking what it contributed to one. We design for contribution, test the causal pathway, and say so. Claims of attribution in conflict-affected environments need particularly careful scrutiny.
Counting outputs creates the wrong behaviour
Officers trained, courts built, vehicles delivered. A study of police performance measurement across several countries found that quantitative indicators can lead officers to decline to register cases that would damage their numbers. Aid reviewers have found the mirror image, where reach targets pushed providers to spread services too thinly to work.
Capability scores go wrong in a specific and documented way
The United States special inspector general found that measurement methods for the Afghan security forces changed five times, making long-term tracking impossible, and that the highest rating available was "independent with advisors", which could not express the actual objective of a self-sustaining force. We cite that against ourselves, because scoring capability is what we do.
The data is imperfect and the honest response is to say where
Records are incomplete, some regions are inaccessible, and the people producing the numbers sometimes have an interest in them. We grade our own confidence source by source and publish the grading.
Evidence behind our approach
2007Year of the sector guidance

The OECD Development Assistance Committee handbook section on monitoring and evaluating security system reform remains the most cited sector-specific guidance. It is nearly twenty years old.

Amber-RedTwo review ratings

The Independent Commission for Aid Impact scored United Kingdom security and justice assistance Amber-Red in 2015, and the Conflict, Stability and Security Fund Amber-Red in 2018. Measurement was central to both findings.

20%Malawi, five years later

Community policing coverage fell from between 80 and 90 per cent in 2007 to 20 per cent by 2012, once external support ended. Reported by the same 2015 review.

How we design the evaluation
  1. Define the outcome before the activity

    Not what will be delivered, but what will be different, for whom, and how anyone would know. Reviews of this sector repeatedly find programmes where outcomes were never defined, which makes later evaluation impossible rather than merely difficult.

  2. Write the theory of change at the start, not halfway through

    The Congo evaluation above records that the programme’s theory of change was written over halfway through implementation. That is common and it is costly, because it means the baseline was collected against assumptions nobody had yet written down.

  3. Separate theory failure from implementation failure

    A programme can be delivered exactly as designed and still not work, because the design was wrong. Telling those two apart is the single most useful thing an evaluation does, and it is only possible if the theory was written down in advance.

  4. Set the baseline before delivery starts

    A baseline collected after the first activity is not a baseline. Where a genuine baseline is impossible, we say so and design around it rather than reconstructing one later and hoping nobody asks.

  5. Grade confidence, and publish the grading

    Every finding carries a confidence level and a source. A reader should be able to discount anything we assert, and the weak points should be marked by us rather than found by them.

  6. Build the human rights assessment into the evaluation, not beside it

    The Overseas Security and Justice Assistance guidance requires a human rights risk assessment to be built into evaluation processes and updated when circumstances change. In practice it is often produced once, filed, and never revisited. Reviewers have found it approving activity to proceed unchanged in every case examined, which is a control that is not controlling anything.

Assessing sustainment
A strong result at the end of a programme does not predict a lasting one
The most rigorous study of post-exit sustainability found that impact at the point of exit does not consistently predict whether benefits survive, and that the size of the impact does not improve the odds either. This supports treating sustainment as a separate part of the assessment.
Four things have to be in place before the money stops
Sustained resources, sustained capacity, sustained motivation, and linkages to something that outlasts the programme. In the same study, no project achieved sustainability without all of them in place before closure.
We model the position at twelve and twenty-four months after support ends
Who pays the recurring costs, who holds the mandate, who is still in post, and what happens to the equipment when it needs its first major service. Salaries are usually the answer, and usually the thing nobody has funded.
We will not pretend there is a body of evidence here
There is rigorous post-exit evidence in other sectors. For security and justice specifically there are strong individual cases and no systematic evidence base. We say that rather than implying otherwise, and it is a reason to measure rather than a reason not to.
The limits of our claims
  • That we proved impact. We test contribution against a stated theory of change, and we describe the strength of the evidence for it.
  • That the number of people trained is an outcome. It is implementation monitoring. It belongs in a progress report, not at the top of a results framework.
  • That capacity has been built, as a finished state. We name the capability, the standard it now meets, and how long it is likely to hold without us.
  • That a perception survey measures safety. It measures perception, which moves on its own timetable and sometimes in the opposite direction to the crime figures.
  • That our own assessment is independent of our interest. Where a finding would favour something we could supply, the report says so in the text so that the reader can discount it.

Working to your framework

Where a programme already has a results framework, a logframe or an evaluation contractor, we work inside it rather than proposing our own. Where there is none, we will build one proportionate to the size of the work, which for a small engagement means a short document rather than an apparatus. The Foreign, Commonwealth and Development Office judges evaluation against five principles, useful, credible, robust, proportionate, and safe and ethical, and proportionate is the one small suppliers most often fail in the wrong direction by over-engineering.