Public Service Saturation

Abstract

Public agencies usually report program authority, budgets, caseloads, and processing volume. Those measures do not show whether a service has actually reached the people who qualify for it. This paper defines public service saturation as the share of the eligible population that has been resolved. A resolved resident is either served or offered the service and recorded as opted out. The model depends on a concrete population baseline, a clear eligibility rule set, and auditable counts for served, opted-out, unresolved, and unknown cases. With those elements in place, agencies can compare delivery performance across jurisdictions, assess service strategies, and estimate administrative cost per resolved resident.

1. Purpose

The operating question is simple:

For a given public service, how much of the eligible population has been resolved?

This paper is meant as a descriptive framework for agencies, legislative staff, advocates, and researchers. It is not a theory of public administration. It is a way to describe service reach in concrete, reportable terms.

2. Core Definitions

Term	Meaning
P	Population baseline used for measurement
E	Eligible population
S	Served population
O	Opted-out population
U	Unresolved population
K	Unknown population

For this paper:

• served means the resident received the service
• opted out means the resident was clearly offered the service and affirmatively declined it
• unresolved means the resident is eligible but neither served nor opted out
• unknown means the agency cannot yet determine eligibility with confidence

The basic formulas are:

E = { p in P | eligibility_conditions(p, service) = true }
U = E - S - O
Saturation = (S + O) / E

An informed opt-out counts as resolved. Passive non-participation does not.

3. Population Baseline

Saturation requires a denominator. Without one, an agency can report activity but not coverage.

The baseline may be:

• a census
• a population register
• a service-specific enrollment universe
• another authoritative population file

This framework assumes the baseline is accurate enough to function as the public reference point for measurement. If it is incomplete or stale, the resulting saturation rate will inherit that limitation. The remedy is not to abandon the model. The remedy is to document the baseline and its quality.

4. Eligibility and Resolution

Every public service has zero or more conditions on delivery. Those conditions may include age, income, residence, disability status, household composition, or service area.

For reporting purposes, eligibility should be treated as a classification function:

eligibility(person, service) -> eligible | ineligible | unknown

The key distinction is between unresolved and unknown:

• unresolved means the resident is eligible but not yet resolved
• unknown means the agency cannot yet determine whether the resident is eligible

That separation prevents incomplete data from being hidden inside a general non-participation category.

5. Delivery Standard

If a public benefit is available, it should be easy to find and easy to receive. Saturation is therefore not just a count of approvals. It is a low-friction delivery standard.

For measurement purposes, delivery has four steps:

1. Identify the resident or household that may qualify.
2. Offer the service in a clear and usable way.
3. Resolve the case through receipt or opt-out.
4. Record the outcome for future reporting.

This paper assumes that discoverability matters. A service that exists in statute but is difficult to find, understand, or access is not saturated.

6. Treatment of Opt-Out

Opt-out counts toward saturation only when it is meaningful. At minimum:

• the resident was classified as eligible
• the resident was given a clear offer
• the resident had a practical way to accept or decline
• the decline was recorded
• the resident can re-engage later when appropriate

The point of saturation is not universal uptake. The point is universal resolution of the eligible population.

7. Core Metrics

An agency using this framework should report, at minimum:

Metric	Description
population_baseline	Population record used
eligible_population	Computed or estimated denominator
served_population	Eligible residents who received the service
opted_out_population	Eligible residents who affirmatively declined
unresolved_population	Eligible residents not yet resolved
unknown_population	Residents lacking enough information for classification
saturation_rate	(served + opted_out) / eligible
discoverability_rate	Share of eligible residents shown the service
take_up_rate	Share accepting among residents shown the service
median_time_to_resolution	Time from eligibility determination to outcome
admin_cost	Administrative cost in the reporting period
cost_per_resolved_resident	admin_cost / (served + opted_out)

The same framework supports marginal analysis:

Marginal saturation cost = additional administrative cost / additional resolved residents

That makes it possible to compare administrative effort against actual gains in coverage.

8. Cross-Jurisdiction Benchmarking

The main value of this framework appears when jurisdictions report the same measures in the same shape.

8.1 Canonical Benchmark Row

Field	Meaning
jurisdiction_id	Reporting jurisdiction
service_id	Service or program being measured
period	Reporting window
population_baseline	Population record used
eligible_population	Denominator
served_population	Residents who received the service
opted_out_population	Residents who declined after offer
unresolved_population	Eligible residents not yet resolved
unknown_population	Cases lacking enough information for classification
saturation_rate	(served + opted_out) / eligible
discoverability_rate	Share of eligible residents shown the service
take_up_rate	Share accepting among residents shown the service
median_time_to_resolution	Resolution speed
admin_cost	Administrative cost for the period
cost_per_resolved_resident	Administrative cost per resolved resident
delivery_strategy	Primary delivery approach used

8.2 Example

Jurisdiction	Service	Eligible	Served	Opted Out	Unresolved	Saturation	Discoverability	Take-up	Cost per Resolved	Strategy
County A	Rental assistance	18,400	12,900	1,800	3,700	79.9%	88.0%	79.9%	$142	proactive outreach + prefill
County B	Rental assistance	17,950	10,400	950	6,600	63.8%	71.0%	89.5%	$166	website + caseworker intake

8.3 Comparison Rules

Cross-jurisdiction comparisons should follow four rules:

1. Use the same denominator logic.
2. Separate unresolved from unknown.
3. Report delivery strategy with the outcome.
4. Compare like services to like services.

Without those controls, the numbers may look comparable while measuring different things.

9. Delivery Strategy and ROI

Once the benchmark is stable, service delivery becomes a comparative management question.

Strategies may include:

• passive website publication
• caseworker-led intake
• direct mail or SMS outreach
• cross-program prequalification
• address-based service matching
• default enrollment where legally appropriate

Those strategies can be assessed against the same questions:

• Does the strategy increase discoverability?
• Does it increase take-up after offer?
• Does it reduce the unknown population?
• Does it reduce unresolved cases?
• What is the cost per additional resolved resident?

This makes ROI a delivery question rather than a rhetorical one. The measure is not whether activity increased. The measure is whether more eligible residents were resolved, and at what administrative cost.

10. Service-Class Profiles

The same saturation model can be used across different service types, but the interpretation changes by service class.

Service class	Typical denominator	Main risks	Main comparison metrics
Universal services	Broad population or simple subset	Geographic gaps, slow uptake, weak discoverability	Saturation, discoverability, time to resolution
Means-tested benefits	Fact-dependent household population	Unknown cases, documentation burden, low take-up after offer	Saturation, unknown rate, discoverability, take-up, cost per resolved
Case-managed services	Narrow population with higher factual complexity	Capacity limits, longer timelines, repeated contact requirements	Saturation, unresolved rate, wait time, median time to resolution, cost per resolved

The reporting model stays constant. The expected shape of the numbers does not.

11. Data and Governance Requirements

To use this framework in practice, an agency needs the ability to:

• maintain a population baseline
• calculate or estimate eligibility
• distinguish unknown from unresolved cases
• present a clear offer
• record service receipt and opt-out
• maintain auditable reporting periods
• compare results across agencies and jurisdictions

It also needs clear policy rules for:

• data quality
• notice and consent
• inter-agency data sharing
• correction and appeal
• reporting methodology

12. Limits

This framework has practical limits.

• If the baseline is wrong, the denominator is wrong.
• If eligibility is highly fact-specific, unknown counts may remain significant.
• If privacy or consent constraints are weak, a higher saturation rate may be obtained in the wrong way.
• If a service is capacity-constrained, unresolved counts may reflect resource limits as much as workflow limits.

These limits do not defeat the model. They define the conditions under which the model should be read.

13. Conclusion

Public service saturation is a descriptive measure of whether a benefit has reached the people it is meant to reach. It requires a concrete denominator, a clear eligibility model, separate counts for served, opted-out, unresolved, and unknown cases, and a common reporting structure.

With those elements in place, agencies can compare jurisdictions, assess delivery strategies, and judge whether administrative spending is actually converting eligible residents into resolved residents.