Policy Gap Analysis¶
Method — instantiates Completeness Audit
Compares a policy framework against relevant actors, situations, exceptions, rights, obligations, or edge cases to locate missing treatment.
Policy Gap Analysis lays a governing framework — a policy, regulation, benefit rule, or standard — beside the full population of actors, situations, exceptions, rights, and obligations it purports to govern, and locates the cases the framework fails to treat: situations with no applicable rule, contradictory rules, or ambiguous treatment. Its defining move, and what separates it from the siblings that merely find gaps, is that it carries each missing treatment through to a disposition — amend the rule, explicitly exclude the case, escalate it to whoever can decide, or defer it with a trigger — so the audit ends in decisions rather than a list. Its coverage universe is normative: rules held against the situations those rules are supposed to reach.
Example¶
A city is rewriting its rental-assistance eligibility rules. The analyst first bounds what the policy claims to govern, then builds the situation space it must reach: household types (single, multigenerational, unrelated co-tenants), immigration statuses (citizen, mixed-status household, undocumented dependents), income sources (wages, gig, informal cash, none), and precipitating events (eviction pending, fleeing domestic violence, recently aged out of foster care). Laying the draft rules against that space, several situations have no rule at all — a mixed-status household whose lease-holder is undocumented but whose children are citizens; income entirely from untraceable cash. One pair of clauses conflicts, giving opposite answers for a household living in a shelter. Each finding gets a disposition: the mixed-status case is escalated to counsel, the cash-income case receives a new documentation rule, and one rare edge case is explicitly excluded with a written rationale. The lacuna — a gap where no rule governs the situation — is not merely noted; it is assigned an outcome.[1]
How it works¶
The method is comparative and normative rather than instrumented. It fixes the policy's claimed jurisdiction (inside, outside, contested), enumerates the situations that jurisdiction implies, and tests each against the rule set for three defects at once: no applicable rule, conflicting rules, and treatment too ambiguous to apply. What distinguishes it from a bare gap hunt is the closing step — every located gap is routed to a disposition, so the analysis cannot end with an undocumented backlog of "we should look at that someday."
Tuning parameters¶
- Situation-space breadth — how many actor-and-exception combinations are enumerated. Broad finds more untreated cases but risks analysis paralysis.
- Conflict sensitivity — whether the method flags only missing rules or also contradictory and redundant overlapping ones.
- Disposition strictness — which gaps must be repaired before the policy ships versus deferred with a trigger and rationale.
- Interpretation stance — literal rule-text reading versus purposive reading when judging whether a case is already "covered."
- Escalation routing — how contested gaps reach the authority that can actually amend the rule, rather than dying in the analyst's notes.
When it helps, and when it misleads¶
Its strength is converting "the policy seems fine" into an enumerated set of untreated situations, each carrying a decision — the disposition step is what stops discovered gaps from becoming an invisible backlog. Its failure mode is that the analysis is only as good as the situation space imagined: unconsidered actor combinations stay invisible, and "excluded" can quietly become the disposition for politically inconvenient cases — silent exclusion dressed up as scope language. The guarding discipline is to pair the method with an explicit exclusion register and an appeal path so exclusions are named and contestable, and to seed the situation space from real cases and complaints rather than only from the drafters' imagination.
How it implements the components¶
scope_boundary_statement— it fixes what the policy claims to govern (inside, outside, and the contested edge), so completeness is judged against a declared jurisdiction rather than a vague one.gap_analysis— it identifies situations with no applicable rule, conflicting rules, or treatment too ambiguous to apply, across the governed population.gap_resolution_policy— it assigns each located gap a disposition (amend, explicitly exclude, escalate, or defer with rationale), so the audit ends in decisions.
It does not set a recurring review schedule for the policy — the standing audit_cadence belongs to Risk Register Review — and it reasons over rules on paper rather than enacting live scenarios, so it does not run the sampling_probe that surfaces gaps by playing them out in Scenario Tabletop Review.
Related¶
- Instantiates: Completeness Audit — it is the rule-versus-situation comparison that ends in gap dispositions.
- Sibling mechanisms: Coverage Checklist Walkthrough · Data Completeness Check · Risk Register Review · Scenario Tabletop Review · Stakeholder Inclusion Review · Test Coverage Audit · Requirements Traceability Matrix
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: The mechanism evaluates a policy's claimed jurisdiction against actors, cases, rights, obligations, conflicts, and ambiguity and returns documented gap findings.
Nearest alternative: Analysis, Modeling & Optimization — Comparative analysis supports the review, but the operative result is assurance about the existing policy framework's coverage.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Public Administration & Policy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Systematically checking a policy against actors, cases, rights, and edge conditions is policy-design and implementation analysis.
Related originating lineages:
- Law & Governance — Legal analysis materially shapes coverage testing for obligations, exceptions, and rights-bearing cases.
Review resolution: Light authoritative-source research resolves the primary-origin disagreement in favor of public administration policy. OECD: Closing the Policy Development and Implementation Divide directly documents the defining practice or theory described in the selected origin rationale. Other domains are retained only where the blind reviews identify material co-development or translation; broad application is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
Attribution caveat: The boundary with law governance is substantive because that tradition materially developed or translated part of the mechanism; the cited provenance places the defining form in public administration policy.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
References¶
[1] Alchourrón, C. E., and Bulygin, E. Normative Systems. Springer Vienna (1971). Defines a normative gap as a case lacking a solution and treats judicial resolution as supplying an outcome. registry ↩