Airport Feedback Reasons Need an Explicit Denominator

A passenger feedback reason needs a denominator before it becomes a percentage. The share of selected reasons is not necessarily the share of feedback interactions. Neither is automatically the share of passengers.

Airport teams can use each view. They need to know which one they are reading before choosing an operational response or briefing a supplier.

This is a reporting-definition task. Give every reason measure an explicit base, preserve skipped steps, and keep the meaning attached as the result moves into a presentation.

Draw the collection path before calculating the result

Consider a hypothetical airport reviewing an arrivals-area feedback flow. An initial rating may be followed by an optional reason question. Depending on the approved configuration, respondents might select one reason or several.

That example describes a possible design, not a promise about every FeedbackNow interface. Confirm the actual collection behavior with the technical owner before defining the report.

Document who sees the reason step. Is it offered after every rating, only after selected ratings, or through a separate issue-reporting interaction? Those paths answer different questions.

If only dissatisfied respondents receive the reason step, its distribution describes that offered path. It should not be labeled as the distribution of concerns among everyone using the terminal.

Keep interactions, answered questions, and selections separate

Define the unit being counted at each step. An initial interaction, a completed reason question, and an individual selected option are distinct records in the analytical design.

They may coincide in a single-choice flow. They need not coincide when a question permits several answers or can be skipped. Check the actual data model rather than assuming a one-to-one relationship.

Kent State University's statistical tutorial distinguishes percentages based on total selected responses from percentages based on cases answering a multiple-response question. The latter can sum to more than the whole when cases select several options.

That is general survey-analysis guidance, not an airport benchmark or a requirement to use a particular statistical package. Its useful lesson is to name the base.

Choose the denominator for the decision

A share of selections describes the composition of recorded choices. It can help the analyst explain which categories account for more of that set.

A share of answered interactions describes how often an option appears among interactions that answered the question, provided those links are available and correctly defined. With multiple selections, categories can overlap.

Neither view establishes how many unique travelers experienced the condition. Anonymous interactions should not be relabeled as unique people without evidence that supports that identity claim.

Keep separate calculation names for the two views, even when a particular extract happens to produce the same value. Numerical agreement in one period does not make their definitions equivalent. The airport should be able to explain which base a later report uses without rebuilding the original analysis.

Show the missing step without inventing its meaning

Keep the number of interactions without a recorded reason visible where the collection design supports it. Distinguish a skipped optional step from a reason step that was never offered.

No selected reason does not mean no concern. It also does not establish that a particular concern was present. Leave the interpretation open rather than allocating missing answers to the most convenient category.

Ask how incomplete interactions are represented in the extract. A blank field, absent record, and explicit no-answer code may require different handling. Document the agreed treatment before producing a trend.

If the data cannot distinguish those states, record the limitation. The operational review can still use the available selections without claiming complete visibility of every response path.

Make the report reconcile to its defined base

For the illustrative arrivals flow, write a compact calculation note. Identify the included location, period, offered ratings, answered reason interactions, selected options, and exclusions.

Then reconcile a controlled extract using the authorized analytical process. Confirm that the displayed measure follows the written definition, including the handling of multiple choices and missing answers.

This is not a live passenger experiment. Use approved test data or a properly authorized extract. Keep any test activity distinct from the operational series.

A chart title should carry the essential meaning. A share of reason selections should be labeled that way, not simply passenger issues or dissatisfaction rate.

Use reasons to sharpen inquiry, not declare root cause

Suppose supplies is a prominent selected category. The service team can inspect the relevant area and review replenishment observations. The category is a passenger-selected description, not a confirmed explanation of every underlying condition.

Keep that distinction when discussing performance with a contractor. Reason composition alone does not establish service compliance, affected passenger totals, or the financial effect of a change.

FeedbackNow's real-time passenger-experience focus can bring useful detail into the operating conversation. Defined denominators help the airport keep that detail meaningful as it reaches different readers.

When the flow changes, reassess the base. Offering reasons after additional ratings or enabling several selections can change the measure even if the category names stay the same.

The Bottom Line

Define the collection path. Name the counted unit.

Show missing answers and state the denominator. Airport feedback reasons become more actionable when everyone understands exactly what their percentages describe.

Explore FeedbackNow for real-time passenger feedback and operational context.