How to Share Effective Public Comments (Without Overthinking It)

Get Connected Icon
Mar 13, 2026
by Assessments Department

When ARRT invites feedback on updates to our discipline documents, it's because your daytoday experience helps keep our work relevant. Your comments, brief or detailed, are all welcome and useful.

Our survey starts with questions on specific proposed changes and ends with "Any other comments?" This structure makes it easy to react to targeted items and then add anything we didn't ask.


If you'd like to make your feedback more actionable, try these quick tips:

Understand the issue: Review the specific change you're responding to.

Identify your connection: Note how it affects your role, colleagues, or specialty.

Be specific: Say what you support or question.

Provide a basis: Share a short example, observation, or reason.

Suggest alternatives: Offer a clearer term, a different approach, or an example.

Above all, don't let "perfect" be a barrier. Short impressions still help guide improvements!

Below are some examples to illustrate different kinds of feedback that support the review process.

Helpful, concise comments:

·         "The removal of [task] reflects what I'm seeing in the field. No concerns."

·         "I support the change, but clarification on terminology in A.3.C.4. would make it easier to apply."

·         "[specific revision] improves clarity for new practitioners. I support adopting it as written."

Helpful, specific comments:

·         "The proposed shift from [x] to [y] is logical, but in my organization, this could create implementation challenges because  [brief reason]. Consider adding an example or more guidance."

·         "Proposed task [x] overlaps with an existing task [y]. Combining them or clarifying the distinction would reduce confusion."

·         "The addition of [x] to the Patient Care section captures an important skill, but the phrasing may be too narrow. In my role, we also address [related activity], so widening the description could better reflect common practice."

Less helpful (but still better than silence):

·         "The update to this section seems fine overall."

·         "This feels unclear to me."

·         "The updates to the documentation section seem fine to me, but adding a few examples could make it clearer."

(These may still be useful because they flag areas that might need attention.)

Thank you for taking the time to share your perspective. Your feedback strengthens the documents that guide our work.