Your Policy Process Is a Public Health Issue
State health leaders are doing everything right — and still watching good work get undermined by the infrastructure holding it together. Here's what changes when that infrastructure finally matches the mission.
Nobody who leads a state health agency got into this work for the administrative challenge of it. They got into it because the mission matters — because what their agency does, or doesn't do, has real consequences for real people. The work is extraordinary. The people doing it are committed and capable. And the structural gap most of them are quietly managing has nothing to do with either of those things.
It has to do with infrastructure. Specifically, the infrastructure that sits underneath every regulation, every policy update, every inspection protocol, and every eligibility determination — the systems that take good policy decisions and make sure they actually reach the people responsible for carrying them out.
In most state health agencies, that infrastructure is cobbled together from shared drives, email chains, and the institutional memory of a handful of long-tenured staff. It works — until it doesn't. And when it doesn't, the consequences ripple outward in ways that are hard to see from inside the agency, but felt immediately by the people the agency exists to serve.
The Invisible Infrastructure
Policy Management Is a Public Health Issue
When health leaders talk about public health infrastructure, they mean hospitals, laboratories, disease surveillance systems, emergency response networks. Rarely does policy management make that list. But it belongs there.
Every clinical standard, every inspection protocol, every Medicaid eligibility rule, every licensing pathway — the quality of those documents and the reliability of the process that creates, updates, and delivers them — that is health infrastructure. It determines whether a family gets the care they're entitled to, whether a facility is held to the right standard, whether a community is protected by the rule that was actually written to protect them.
The gap between a regulation as written and a regulation as practiced is not a compliance gap. It's a care gap. And closing it is one of the highest-leverage things a health agency leader can do for the people they serve.
That gap lives in the space between legal, policy, operations, and field staff — a shared responsibility that in practice belongs to whoever is most overwhelmed that week. It shows up as inconsistency. As lag. As the critical context that lives in one coordinator's head and nowhere else.
The Argument That Lands in Budget Conversations
Policy management is not an administrative cost. It's the operational layer that determines whether every other investment your agency makes — in programs, in people, in technology — actually delivers the outcome it was designed to deliver.
When that layer is strong, your agency's capacity multiplies. When it's weak, good work gets undermined at the last mile. The question isn't whether you can afford to strengthen it. It's what it's already costing you not to.
The Stakes
What Your Work Makes Possible — And What Slows It Down
Health agency leaders are managing some of the highest-stakes regulatory work in government. The situations below aren't failures — they're the structural friction points that emerge in virtually every agency operating at scale. They exist because the volume and complexity of policy work has outpaced what manual systems can reliably handle. Naming them isn't a critique. It's a starting point for closing the gap.
Inspection standards that change at the top but travel slowly to the field
A protocol is updated based on new evidence. It's published. But field inspectors across a large territory are still working from what they were trained on — because there's no mechanism that pushes the change to them and confirms receipt. The update exists. It just hasn't arrived yet.
The downstream effect
A family places an elderly parent in a facility that passed an inspection against an outdated standard. They trusted the state said it was safe — and the state believed it was enforcing the right rule. Both things were true. Neither was enough.
Institutional knowledge that walks out the door at retirement
Your most experienced policy coordinator knows why every rule was written the way it was — which interpretations are contested, which edge cases require judgment, which informal history shapes every formal decision. When she retires, the agency keeps her files. The context that makes those files meaningful doesn't transfer.
The downstream effect
Her successor makes decisions without the reasoning behind the rules. Interpretations drift. Consistency erodes. The community protection those rules were designed to provide becomes dependent on whoever happens to be in the role — and what they were able to reconstruct.
Policy updates that don't reach the caseworkers applying them
An eligibility rule is revised. Legal approves it. It's published. But without a system that delivers the change directly to the staff making decisions, caseworkers continue applying the version they were trained on. Nobody is at fault. The updated rule exists. It just hasn't reached the people enforcing it yet.
The downstream effect
A low-income family is denied coverage they now legally qualify for. Most people don't know how to appeal. Most don't. The rule your agency worked hard to update never reached the family it was updated to help.
Licensing workflows that haven't caught up to the law
A rule change creates a faster pathway — expedited reciprocity, a new exemption, a streamlined track. Leadership knows. Legal knows. But the internal workflow documentation hasn't been updated, so applications still move through the old process. The intent was acceleration. The reality is the same timeline as before.
The downstream effect
A rural clinic waits months for a practitioner it urgently needs. The community it serves goes without care it was entitled to faster. The law changed. The infrastructure didn't follow.
Emergency protocols that depend on finding the right document first
A public health event requires rapid rulemaking. The agency has the authority. The staff are ready. But the protocol — the right template, the right approvals, the right notification sequence — isn't in a system anyone can access immediately. The capability exists. The infrastructure to deploy it quickly doesn't.
The downstream effect
Response time is determined not by the situation's urgency but by how long it takes to locate the process. In a public health emergency, that lag has consequences the agency never intended and the community never deserved.
What Your Agency Looks Like on the Other Side
When the Infrastructure Finally Matches the Mission
The agencies that have made this investment describe it consistently — not as a technology upgrade, but as the moment their policy infrastructure finally matched the quality of the work their teams were already doing. Here's what that looks like in practice.
✓ Every inspector and caseworker is working from the current rule — always
When a regulation changes, the people responsible for applying it know immediately. No lag. No version confusion. No risk that someone is enforcing a standard that was superseded six months ago. The gap between published and practiced closes by design, not by sending a reminder and hoping it lands.
✓ Institutional knowledge outlasts the people who built it
The reasoning behind every policy decision is documented, searchable, and connected to the rule it informs. When a 20-year veteran retires, her expertise stays with the agency. Her successor inherits context, not just files. The agency's knowledge compounds over time instead of resetting with every transition.
✓ Families receive what the updated rule entitles them to
When a policy is revised to expand eligibility or improve access, the change reaches the caseworkers applying it immediately. The work your team put into updating that rule reaches the people it was updated to help — without a lag that creates inequitable outcomes nobody intended.
✓ Every decision is defensible when it needs to be
When a licensing denial, a benefits determination, or an enforcement action is challenged, the agency produces a complete documented trail — the rule in effect, the version applied, the process followed, the consistency across comparable cases. That's not just legal protection. That's institutional confidence that extends to the communities trusting the agency to get it right.
✓ Emergency response deploys at the speed the situation demands
Protocols are current, accessible, and assigned. When a public health situation requires rapid action, the team executes — the process is in the system, the approvals are mapped, the notifications are automated. Response time is determined by the situation, not by document retrieval.
"
Our work is too important to rely on outdated or unreliable systems. Working with Esper is a factor in improving outcomes for children and families in Mississippi.
Andrea Sanders — Commissioner, Mississippi Department of Child Protective Services
Where Esper Fits
Built for This Specific Work
About Esper
Policy management software built specifically for government agencies.
Esper is not a document storage system and it's not a generic workflow tool. It's built around the specific way government agencies write, manage, update, and enforce policy and regulation — from the first draft through public comment, legal review, publication, and field delivery.
Health agencies use Esper to close the gap between policy as written and policy as practiced. Every active regulation lives in one versioned system with full revision history, automated update workflows, and AI-enabled search so any staff member can find the current version in seconds. When a standard changes, the people responsible for applying it know immediately. When a coordinator retires, her institutional knowledge stays in the system. When a decision is challenged, the audit trail is already there.
The result isn't just operational efficiency. It's that the work your agency is doing — the policy decisions, the updated rules, the improved pathways — actually reaches the people it was designed to reach. That's the outcome that matters.
Agencies are live on Esper in under three months, supported by a team that has done this across state and local governments nationwide. It doesn't require your IT team to start from scratch.
"Centralizing and organizing our administrative rules process will allow us to better serve our stakeholders and citizens more efficiently while increasing the transparency of the process."
Stephen Appleby — Division Director, NH Department of Education
If this resonates, it's worth 30 minutes.
We work with state health agencies across the country. The conversation we have most often isn't about software features — it's about what it looks like when policy infrastructure finally supports the mission the way it should. When the work your team does reaches every person it was designed to reach.
If that's a conversation worth having, we're ready when you are.
What's new
View All
What NASCIO’s Top 10 Priorities Reveal About the Future of State Government IT
2026 marks the 20th release of NASCIO’s “State CIO Top Ten Policy and Technology Priorities” list, a report drawn from ...read more
What Is Regulatory Reform?
Key Takeaways Regulatory reform has evolved through three waves: the first focused on cutting red tape, the second introduced review ...read more
Beyond Records Management: Modernizing the Policy Lifecycle
Records management policy was once treated as an administrative function. Now, it sits at the center of governance, compliance, and ...read more