You’ve just finished updating your documentation policy. It’s airtight — compliant, organized, defensible. You’ve dotted every “i,” cited every requirement, and built in all the right safeguards.
You hit send feeling pretty satisfied.
A week later, your BTs are frustrated, your billing team is confused, and staff are quietly building workarounds.
What went wrong?
Sometimes the problem isn’t the policy.
It’s who helped write it.
Policies written for staff but not with them often look perfect on paper and fall apart in practice.
A policy’s real purpose isn’t to control — it’s to guide. It’s the roadmap your organization uses to balance compliance requirements, operational realities, and the shared mission of delivering excellent care. When the people who live that balance every day have a voice in shaping policy, the result is something far more durable.
Including diverse voices — from clinicians to billing teams to operations staff — turns policies from rulebooks into practical tools that connect people to their purpose.
Why Inclusion Matters in Policy Development
It Keeps Policies Grounded in Reality
Frontline and administrative staff live the policies we write. Their insights ensure procedures match the actual flow of work — not just the imagined version on paper.
When a BT or billing specialist can say, “That’s not how it actually happens,” leadership has the chance to fix problems before rollout instead of after frustration builds.
It Helps Catch Risk Early
Each role in an organization sees compliance risk from a different angle.
A behavior analyst may notice documentation issues affecting clinical integrity, while a billing coordinator might immediately recognize an audit exposure. Bringing these perspectives together turns policy development into an early risk-detection system.
It Strengthens Trust and Culture
Inviting input signals respect. It communicates that compliance isn’t just a leadership responsibility — it’s a shared organizational function.
When staff have a voice in shaping the rules that guide their work, they are far more likely to support them.
It Supports Equity and Retention
Policies that ignore the realities of direct care can unintentionally create inequities or burnout.
Involving frontline voices early helps prevent those unintended consequences and reinforces a culture where staff feel heard and valued.
It Makes Implementation Smoother
People support what they help create.
When a policy reflects the collective wisdom of the organization, rollout feels less like an executive order and more like a team effort.
Practical Strategies for Including Diverse Voices
Creating an inclusive compliance culture doesn’t require a complete overhaul. Small, intentional adjustments to your policy process can make a meaningful difference.
You might start with your next policy review or when developing a new policy.
Solicit Feedback Early
Gather input before drafting the policy.
Consider:
• hosting informal listening sessions
• sending brief surveys or conducting short interviews
• asking simple questions like “What works well?” and “What’s confusing?”
Some organizations also conduct policy perception audits to identify barriers or unintended consequences.
Sharing redlined drafts and collecting feedback through supervisors or liaisons can also ensure more voices are represented.
Include Staff in the Development Process
Cross-functional policy committees are a simple way to incorporate multiple perspectives.
Consider including representatives from:
• clinical teams
• operations
• HR
• billing
Some organizations open nominations for committee participation and rotate membership over time so new perspectives continue to shape the process.
While compliance leadership may retain final authority over policy language, staff contributions often reveal operational realities leadership alone might miss.
Establish Ongoing Policy Practices
Sustainable inclusion happens through routine practices.
Organizations may choose to:
• designate policy champions who communicate the purpose and importance of policies
• appoint policy managers who serve as internal experts on implementation
• schedule annual policy review weeks within the compliance calendar
• provide short trainings on how staff can offer meaningful feedback
• maintain a simple suggestion box for operational ideas separate from formal compliance reporting systems
These practices reinforce that policy development is an ongoing conversation, not a one-time event.
Managing Expectations in Collaborative Policy Development
Including diverse voices doesn’t mean every idea will make it into the final draft. This is where leadership communication becomes essential.
Clear communication about both the decision and the reasoning behind it shapes how staff experience the outcome.
When people understand how decisions were made, they are far more likely to feel respected — even if their suggestions weren’t adopted.
Communicating Policy Decisions Effectively
Several practices can help leaders communicate final policy decisions thoughtfully.
Acknowledge the process.
Recognize the input that shaped the policy and thank those who contributed.
Lead with the “why.”
Frame policies through their purpose rather than simply announcing the rule.
Instead of:
“Starting next week, staff may not text client information.”
Try:
“To protect confidentiality and meet HIPAA standards, we’ll be moving client communication to a secure platform.”
Understanding the purpose behind a policy makes compliance feel mission-driven rather than punitive.
Clarify what’s required vs. what’s flexible.
Explain which elements are driven by regulations or payer requirements and which reflect internal operational decisions.
Transparency builds credibility.
Use multiple communication channels.
Policy changes are more likely to be understood when shared through multiple formats, such as email summaries, team huddles, quick-reference materials, or Q&A opportunities.
Keep the feedback loop open.
Remind staff that policies evolve and that ongoing feedback continues to shape improvements.
Bringing It Back to Mission
Policies are the scaffolding of your organization — they support the mission.
But if that scaffolding is built without the people who walk on it every day, it won’t hold for long.
Including diverse voices in policy development isn’t just a compliance best practice. It reflects the core values of ABA: collaboration, respect, and a commitment to quality care.
When policies are written together, they do more than establish rules.
They create systems that sustain your mission, protect your clients, and support the people who make the work possible.
One question worth asking the next time your organization updates a policy:
Who’s missing from the conversation?
The answer can often tell you as much about how the policy will work as the policy itself.
And if your organization is working to strengthen its policy development process, this is work we love supporting.
