A public pledge needs a way to show progress

A pledge with future milestones

HHS and CMS announced an industry prior-authorization pledge (opens in a new tab) in June 2025. One stated commitment was:

“Enhance transparency and communication around authorization decisions and appeals.”

— HHS and CMS announcement, June 2025

The announcement described voluntary insurer commitments, including future milestones in 2026 and 2027. It was not a new universal requirement taking effect immediately, nor evidence that the promised changes had already improved outcomes.

People hearing a commitment need to know what change they can expect and when. Service teams also need a way to examine whether the promised experience has arrived.

Begin with the missing explanation

Consider a hypothetical participant asking a service coordinator about a request awaiting a decision. The coordinator can see that the request was sent but cannot explain the next stage clearly.

A headline about faster or simpler processes does not answer that immediate question. The person needs an accurate account of what is known and an appropriate contact for the rest.

A public pledge can create expectations before local arrangements change. Organizations sharing the announcement should make the timing clear, so people do not mistake a future commitment for a service they can rely on today.

Define the change in observable terms

Ask what would look different if a commitment were implemented successfully. Would a person receive a clearer explanation, find the correct contact sooner, or understand which next step is available?

Choose language that distinguishes the process from its outcome. A faster response does not necessarily mean a favorable decision. A digital exchange does not necessarily mean the explanation is understandable.

These distinctions help leaders avoid celebrating a technical milestone as if it answered every concern. Different questions may require different evidence and different responsible teams.

Make the timetable specific enough to review

A commitment may apply to certain organizations, services, or stages at different times. Before repeating it, check the source and scope.

Keep a record of what the organization has said publicly and who will review that information as milestones approach. If the external timetable changes, the local explanation needs attention too.

For the participant in our example, the useful update may be quite modest: the current process still applies, and the named service can answer questions about this request. That is more dependable than suggesting a future reform has already solved the problem.

Ask about experience as well as volume

Counting processed requests can help an organization understand activity. It does not reveal whether people understood the decision or knew what to do next.

Appropriate feedback can ask about those specific moments. Staff may also identify repeated transfers, inconsistent explanations, or unclear ownership.

Interpret findings carefully. A small set of comments can point to a problem worth investigating without establishing how common it is. Formal performance claims need suitable measures, context, and qualified analysis.

Keep participants out of the coordination burden

People should not have to reconcile conflicting explanations from multiple organizations. Name the appropriate route for the question and make clear what the local team can help with.

Ask whether the participant wants a chosen supporter involved. Keep individual records and requests within authorized private channels.

When the issue is outside the team’s expertise, say so and help locate the right contact. An honest boundary can preserve trust more effectively than an answer that sounds reassuring but cannot be substantiated.

A current role for genus

genus content and pathways can organize reviewed explanations and resources for a defined audience. Configured care experiences can provide appropriate program updates and human contact routes around that information.

genus does not process prior authorization, determine coverage, or verify insurer performance. The organization must maintain the source, scope, and timing of any explanation it shares.

We see value in making commitments understandable enough to revisit. People can then distinguish what has been announced from what is available now, and know where their own question belongs.

A useful review can include the people receiving explanations, not only the teams producing them. Their questions may reveal a difference between information being delivered and information being understood well enough to act on.

Keep the original commitment available beside the update, so a changed measure or timetable is visible rather than quietly replacing the earlier promise.

A question for the next progress update

What has changed since the pledge, who has experienced that change, and what evidence supports the account we are giving?