View source for Monitor adapt and communicate

{{SumpStep/top|step=11|phase=4|title=Monitor, adapt and communicate}}<div class="sump-intro">
The measures are running, and this step turns them into a loop. It asks whether the improvement is arriving, what to change where it is not, and how to tell people either way. Monitoring is the routine tracking of the indicators fixed earlier, evaluation is the harder question of why the readings look the way they do, and communication is what keeps the support that the next round of the plan will need. What DREAMS adds here matters most in the outskirts. Because the baseline was measured for named groups using their own thresholds, the same measurement can simply be run again, which turns the plan's central question into something answerable rather than assertable.
</div>

<div class="sump-prereq">
<div class="sump-prereq__title">Before you start this step</div>
<div class="sump-prereq__list">
<div class="sump-prereq__item"><div class="sump-prereq__box"></div><div class="sump-prereq__text">The dated before-readings for each indicator, with the method and the population group they were measured for recorded beside them, since a later reading is only comparable if it repeats both.</div></div>
<div class="sump-prereq__item"><div class="sump-prereq__box"></div><div class="sump-prereq__text">The delivery record from [[Manage implementation|implementation]], showing what was actually built and when each measure started running.</div></div>
<div class="sump-prereq__item"><div class="sump-prereq__box"></div><div class="sump-prereq__text">A first review already in the calendar with the body that will receive it named because a monitoring report with no audience gets written late or not at all.</div></div>
</div>
</div>

== Ask the same question again ==

The diagnosis did more than map the area. It measured the neighbourhood twice, once against a textbook standard and once with the amenities a named group weights most and the walking times they said they accept. Geretsried in the Munich lab shows what that leaves you holding.

<div class="dreams-figures" style="--sump-accent: var(--dreams-primary);">
<div class="dreams-figure"><div class="dreams-figure__value">64 in 100</div><div class="dreams-figure__label">everyday amenities are within a 15-minute walk in Geretsried on the textbook standard. This is the figure a normative map reports.</div></div>
<div class="dreams-figure"><div class="dreams-figure__value">36 in 100</div><div class="dreams-figure__label">is the same neighbourhood measured for its older residents. This is the figure a plan written for them has to move.</div></div>
<div class="dreams-figure"><div class="dreams-figure__value">3 in 10</div><div class="dreams-figure__label">of those older residents reach a grocery in the time they say they need. Groceries, pharmacies, bakeries and general practitioners are what hold their score down.</div></div>
</div>

Those figures come from [[Publications/7|Deliverable 3.1]], and the useful thing about them is that they are reproducible. Run [[MinuteMap]] again on the configuration that now exists, holding the preference set, the amenity list and the time thresholds exactly as they were, and the difference between the two runs is the answer to the question the plan was written to settle. Not whether the area improved on average, but whether it improved for the group whose access was worst.

Two disciplines make that comparison worth anything. Hold the method fixed and let only the world change, which means recording the model version, the data sources and the date of every run because an amenity list rebuilt from newer data will move the score on its own. And read the amenity-level figures rather than only the headline. A single composite number is slow and blunt, while the components underneath it are where a new grocery or a new bus stop actually registers.

One honest limit. A model re-run tells you whether something is reachable, not whether anyone goes. The survey side of the diagnosis is what answers the second question, and the two belong in the same report.

== Outputs move first, outcomes move later ==

DREAMS sorts every indicator into one of two kinds. An output indicator describes the intervention itself, meaning the thing exists and is being used. An outcome indicator describes the change the project was for. The distinction sounds academic until you watch the two behave differently in time ([[Publications/6|Deliverable 6.1]]).

<div class="dreams-lab">
<div class="dreams-lab__tag">[[Living_Labs/1|Living lab Vienna, Liesing]]</div>
The flexible activity hub set up in Liesing was judged on both kinds at once. Its output targets were countable and immediate, meaning two events or offers a week, at least ten visitors on a day with activity, a hundred visitors at a film or theatre evening, and three local organisations drawn into preparing the programme. Its outcome targets were the actual ambition, meaning a fifth off the travel time residents need to reach cultural offers, four in five visitors arriving on foot or by bike, and a corresponding fall in the carbon of those trips. The bike-sharing station beside it was set up the same way, with weekly pick-ups as the output and satisfaction and carbon as the outcomes.
</div>

Outputs arrive within weeks and outcomes often arrive after the pilot money has run out, so a report that carries only one of them will mislead in a predictable direction. Early reporting that leans on outputs sounds like success. Later reporting that leans on outcomes sounds like failure. Carry both from the first review, label which is which, and resist the substitution that comes naturally under pressure, where a healthy usage figure is offered as evidence that access improved. Strong outputs beside flat outcomes usually mean the service has been discovered by people who were already reasonably well served, which is worth knowing early and is fixable.

== Measure while it is running ==
<div class="sump-lead-fig">[[File:MeasureWhileRunning.svg|frameless|link=|alt=|400px]]</div>
DREAMS collects at three moments, before the intervention, during it and after it. The middle one is the one cities most often skip and the one this step depends on, because a design that only compares a before with an after tells you nothing until the money is spent and the decision is behind you ([[Publications/6|Deliverable 6.1]]).

The readings taken during the run are usually cheap, being operator data that already arrives, manual counts on days when something is open, and short feedback forms handed out while people are there.

When a reading disappoints, ask three questions before touching the measure. Was it delivered as designed, which the delivery record from [[Manage implementation|the previous step]] should answer in a line. Is the indicator sensitive enough to have registered a change of the size this measure could plausibly produce, which is the test [[Set targets and indicators|applied when the indicator was chosen]] and worth applying again now. And is the measure reaching the group it was written for, which requires breaking the reading down rather than reading the area average. Only after those three does adaptation become a decision rather than a reflex. Then choose plainly between adjusting the measure, extending it to gather more evidence and stopping it, and record which you chose and why, because the reasoning is what the next cycle inherits.

<div class="dreams-callout">
<div class="dreams-callout__label">A short window is a reading, not a verdict</div>
Measurement periods in the outskirts get shortened, moved and pushed into the wrong season, usually because something upstream slipped. When that happens the numbers are still worth having, but they no longer support the comparison they were designed for. Say so in the report, in the same paragraph as the figure rather than in a footnote, and state what the shortened window can and cannot show. A qualified result that is trusted is worth more than a clean one that quietly is not.
</div>

== Say what you found, including when nothing moved ==
<div class="sump-lead-fig">[[File:Broadcast.svg|frameless|link=|alt=|600px]]</div>
<div class="sump-lead"><div class="sump-lead-text">
Communication is the third part of this step and the one most easily postponed. Four audiences have a claim on the results. The councils that each adopted their own part of the plan need to see their own commitments tracked, in the form they voted on. The coalition needs enough detail to keep making decisions together. The operator needs the usage picture early enough to act on it. And residents, who were told a service was coming, need to hear how it went, including from an area where a previous promise was not kept.

Publish the results that did not move. An outskirt that only ever hears about successes learns that the reporting is promotional, and the next plan starts from a worse position than this one did. A negative result that is explained, with the three questions above answered honestly, is also the most transferable thing a living lab produces, and it is the raw material [[Review and learn lessons|the last step]] works with.
</div></div>

<div class="dreams-handoff dreams-handoff--dive">
<div class="dreams-handoff__label">Go deeper</div>
<div class="dreams-handoff__items">
<div class="dreams-handoff__item">
<div class="dreams-handoff__item-title">[https://bsr-sump.eu/training/m2-monitoring-and-evaluation/ Module 2 on monitoring and evaluation] <span class="dreams-handoff__item-source">(Baltic Sea Region Competence Centre)</span></div>
<div class="dreams-handoff__item-desc">Sets out how to assemble a local framework, choose indicators that align with European practice, and settle who collects and archives what, drawing on cities that have struggled with exactly the data-consistency problem. For building the monitoring system itself rather than reading its results.</div>
</div>
<div class="dreams-handoff__item">
<div class="dreams-handoff__item-title">[https://app.transformtransport.org/15minCS/europe-map.html 15-Minute City Score Europe map]</div>
<div class="dreams-handoff__item-desc">Scores walking access to essential services across hundreds of functional urban areas, so you can see how your re-measured area compares with other European neighbourhoods on a consistent method, with the [https://transformtransport.org/research/urban-mobility-metrics/15min-city-score-toolkit-urban-walkability-analytics/ toolkit behind it] available if you would rather run the metric yourself.</div>
</div>
<div class="dreams-handoff__item">
<div class="dreams-handoff__item-title">[https://changing-transport.org/wp-content/uploads/2013-evaluation_matters.pdf Evaluation Matters] <span class="dreams-handoff__item-source">(CIVITAS practitioners' guide)</span></div>
<div class="dreams-handoff__item-desc">Explains how to pair impact evaluation with process evaluation, so a disappointing reading can be traced either to the measure or to how it was delivered.</div>
</div>
</div>
</div>

<div class="sump-sources">
<div class="sump-sources__title">Sources and further information</div>
<div class="sump-sources__item"><span class="sump-sources__ref">EU SUMP Guidelines, Second Edition</span> (Rupprecht Consult, 2019), Step 11, Monitor, adapt and communicate.</div>
<div class="sump-sources__item"><span class="sump-sources__ref">[[Publications/6|DREAMS Deliverable 6.1]]</span>: the measurement framework, the three collection moments, the output and outcome classification, and the Vienna indicator set.</div>
<div class="sump-sources__item"><span class="sump-sources__ref">[[Publications/7|DREAMS Deliverable 3.1]]</span>: the Geretsried multi-amenity compliance figures by preference set.</div>
<div class="sump-sources__item"><span class="sump-sources__ref">[[MinuteMap]]</span>: used to re-measure a neighbourhood on the same basis as its baseline.</div>
<div class="sump-sources__item"><span class="sump-sources__ref">[https://nachhaltig-mobil-planen.de/_SUMP/DE/Planung/SUMP-Prozess/4-Umsetzung-Monitoring/11-Fortschritt/fortschritt.html Fortschritt messen]</span>, German national SUMP portal, Bundesministerium für Verkehr.</div>
</div>{{SumpStep/bottom|step=11}}