At a neighborhood health meeting, residents may agree that a pilot is hard to use while disagreeing about the cause. One person describes an appointment time that excludes shift workers, another says the reminder arrived too late, and a third wants the service moved. If the team records only a stack of comments, the next meeting begins with the same uncertainty. A useful feedback record connects each comment to a decision, a reason and a named return point.
The CDC and ATSDR Principles of Community Engagement treats engagement as a continuing relationship rather than a one-time collection exercise. For a planning team, that means people should be able to see how their knowledge entered the work. It does not mean every suggestion must be adopted. It means the route from comment to decision must be visible enough to examine.
This method is deliberately narrow. It is not a new survey, a vote on the whole program or a promise of consensus. It is a short record for the comments that could change an active pilot. The team can use it during a working session, then publish or share the parts that do not contain personal information.
Begin with the decision the comment could affect
Write the decision at the top of the record before summarizing the feedback. “Should the evening session start one hour later?” is usable. “People want better access” is not, because nobody can tell what action is under review. The decision should be small enough for the current team to make or forward to one named owner.
Then capture the comment in the speaker's meaning without turning it into a polished slogan. Add the setting in which it arose, the group or service step it concerns and the evidence that would help test it. A report that the reminder comes too late could be checked against send times and missed appointments. A request for a different location may require a short access walk, not another opinion poll.
When several partners interpret the same comment differently, use the site's method for making competing readings testable. The feedback record should preserve the disagreement and the next observation. It should not hide uncertainty behind an average score.
Use three honest outcomes instead of a vague “noted”
Change now. Use this outcome when the team has authority, the likely benefit is clear and the change does not create a new safety or access problem. Record the exact adjustment, who will make it and the first date on which people can see the difference.
Test before changing. Use this when the comment is plausible but the cause is uncertain. Name one bounded test, the evidence it should produce and the date of the decision. A two-week reminder-time test is more accountable than promising to “look into communications.”
Do not change now. This is a legitimate outcome only when the record gives a reason: the team lacks authority, evidence points elsewhere, the change would disadvantage another group, or a prerequisite is missing. Name the person or body that can reconsider it and the condition that would reopen the decision. Silence and “noted” are not outcomes.
The current CDC Program Evaluation Framework links collaborative engagement with credible evidence, transparency and acting on findings. A compact feedback record supports those actions without pretending that one meeting is a complete evaluation. It shows what the team heard, what it checked and what it will do next.
Return the record to the people who supplied the evidence
Close the loop in the same place and format where the feedback was gathered whenever possible. A short notice at the service desk, a community-partner email or a five-minute opening at the next meeting may work better than a long report. State the decision first, then the reason, the owner and the next review date. Remove names and sensitive details that are not needed to explain the choice.
At the next review, compare the promised action with what actually happened. If the time changed, did the intended group use the session? If the team ran a test, is the decision now clear? If the request was forwarded, did the receiving owner answer? The record is complete only when the response returns to the community and creates a new, observable planning step.
A good feedback process does not measure respect by the number of sticky notes collected. It makes a small chain visible: a specific comment, the decision it could affect, the evidence needed, the team's reason and the return to the people who contributed. That chain gives a public-health pilot a practical way to learn without confusing listening with agreement.