November 20, 2026
Opinions & Expertise

Airport Feedback Pilots Need a Concurrent-Change Log

Share this article
Airport Feedback Pilots Need a Concurrent-Change Log

An airport pilot rarely has the terminal to itself. A feedback evaluation may run alongside a new service roster, revised passenger information, or a change in the physical journey.

That context belongs in the evaluation. A concurrent-change log helps teams explain what else changed while they were learning from real-time passenger feedback.

The purpose is not to delay improvement until the environment becomes perfect. It is to make a useful operating decision without attributing every observed difference to the pilot.

Separate a recorded change from an estimated effect

A log records what happened, where, and when. It does not calculate how much of a feedback movement came from each event.

HM Treasury's impact-evaluation guidance explains why attributing outcomes requires attention to what would have happened without the intervention. A simple before-and-after difference does not, by itself, establish that counterfactual.

This is general evaluation guidance, not evidence of an airport technology's effect. Its practical relevance is the distinction between describing an observed change and making a causal claim about the pilot.

A concurrent-change log supports that discipline. It gives reviewers context to investigate and helps an evaluator decide whether a proposed comparison is credible.

Log the passenger exposure, not just the project date

A procurement date is not necessarily the date travelers encountered a change. Record the first known passenger-facing exposure and the area affected, along with any uncertainty.

Keep a phased introduction visible. If one corridor changes before another, a single terminal-wide date can hide the comparison that reviewers need to understand.

Use a small set of fields: change description, responsible source, affected location, passenger-facing period, and confirmation status. Add a link to the authorized operating record rather than duplicating restricted details.

Include relevant changes outside the pilot team's control when they become known. Do not present an incomplete log as proof that nothing else happened.

Keep discovery time separate from exposure time. If a reviewer learns late about an earlier passenger-facing change, add the source and correction date without pretending the information was available to the original decision-maker.

Identify which comparisons may need another look after that discovery. Preserve the earlier report and issue an explained revision when appropriate, rather than silently replacing its account of the operating conditions.

Decide who updates it. A short regular check with authorized operations representatives is more useful than asking an analyst to reconstruct every event from memory after the trial ends.

Use a concrete comparison without overstating it

Consider a hypothetical airport testing an enhanced feedback review process at an arrivals help point. During the evaluation, the airport also introduces revised information boards nearby.

The new boards reach one approach route first and another later. A staffing change then extends the help point's operating hours.

The log keeps those exposures separate from the start of the feedback process. A reviewer can see that the later period contains a different service arrangement, not merely more days of the same pilot.

If sentiment changes, the report describes the movement alongside those facts. It does not assign the difference entirely to the feedback process or invent a percentage contribution from the boards.

The example is hypothetical and contains no claimed performance result. It shows why context can improve the decision even when it cannot isolate a causal effect.

Choose the comparison before polishing the story

Bring the log to a qualified evaluator while the trial is still running. The right response might be to extend observation, reconsider comparison periods, or narrow the question the evaluation can answer.

Simply deleting inconvenient days is not a defensible default. Document the reason for any exclusion and disclose its effect on the reported scope.

A comparison location also needs scrutiny. Similar architecture does not establish similar exposure if its service hours, passenger mix, or information arrangements changed differently.

The log cannot repair every limitation. Its value is to reveal where a stronger design or a more modest conclusion is needed.

Keep the original evaluation question visible when revising the analysis. If the team changes that question after seeing results, label the change instead of presenting the new question as the original plan.

Make the operating decision broader than attribution

An airport may still learn whether teams used the information, whether authorized reviews occurred, and whether the process fitted the operating environment. Those are useful implementation observations.

They are different from proving a satisfaction increase or a financial return. Give each conclusion the evidence it actually has.

FeedbackNow can support a purposeful real-time listening approach while the airport evaluates that approach with appropriate context. There is no need to turn every trial into an unsupported outcome claim.

Carry unresolved questions into the next phase. A decision to continue learning can be more credible than a confident number that the evaluation design cannot support.

Retain the approved change log with the report so that a later commercial summary does not detach an observed movement from the conditions under which it occurred.

The Bottom Line

Concurrent changes do not make a pilot worthless. They make explicit context essential.

Record passenger-facing exposures, scrutinize comparisons, and keep observed movement separate from claimed effect. Explore FeedbackNow for airport operations.

Contact us to learn more about how FeedbackNow can help improve your customer experience and operations!

Learn More

Get A Customized Demo Showing How We’ll Impact Your Business

Business Key Metrics
Operational Efficiency
Operational Benchmarks
Customer Satisfaction Scores
Customer Retention
Labour Costs
Labour Efficiency
Core Metrics
ROI
Critical KPIs
CX-Drive Revenue