Transparent Cross-Subsidy Schedule¶

Funding policy — instantiates Endpoint Fan-Out Fulfillment

An explicit, reviewable rule that funds high-cost or essential endpoints out of pooled system revenue, making the who-pays-for-whom of universal service visible instead of hidden.

A Transparent Cross-Subsidy Schedule is the funding instrument that makes serving unprofitable-but-essential endpoints economically viable — a stated rule for channeling surplus from the low-cost, profitable parts of a system to the high-cost tail that could never pay its own way. Its defining virtue is in its first word: the cross-subsidy is transparent, written down and open to review, rather than buried in blended pricing where no one can see who is paying for whom. That distinguishes it sharply from the analysis that measures what each endpoint costs to serve; this mechanism does not measure cost, it decides who bears it — and it earns the "transparent" label only by exposing that decision to scrutiny instead of hiding it in the accounts.

Example¶

A national postal operator carries a universal-service obligation^[1] — deliver everywhere, at a uniform price. But a letter to a remote farm costs far more to deliver than the stamp, while dense-city mail is cheap and profitable. The Transparent Cross-Subsidy Schedule states, in the open, how this is squared: a defined margin from profitable urban and business volume funds the coverage floor of regular rural delivery, the rule is published, and a regulator reviews it periodically. Because the cross-subsidy is explicit, it can be argued about and defended as a deliberate social commitment — rather than lurking as an accounting artifact that a competitor could expose or a cost-cutter quietly erode. Everyone can see that the city subsidises the country, and can debate whether that trade is worth making.

The policy's output is a funded, defensible coverage floor for endpoints that pure economics would strand — with the subsidy visible enough to be a choice rather than an accident.

How it works¶

Take the cost picture as input — who costs more and less to serve — from the cost-to-serve analysis, without re-measuring it.
Define the pool and the rule — which surplus funds the subsidy and how it is allocated to below-cost essential endpoints.
Set the coverage floor the subsidy exists to guarantee — the minimum service the system commits to for those endpoints.
Publish and review — expose the rule and revisit it on a cadence, which is what makes the cross-subsidy transparent rather than hidden.

The distinguishing move is explicit, reviewable allocation tied to a guaranteed floor: the subsidy is a stated commitment with visible limits, not a blended price no one can decompose.

Tuning parameters¶

Subsidy breadth — which endpoints qualify as essential enough to fund. Broad preserves more coverage but costs more and invites reclassification.
Subsidy depth — how much is transferred per endpoint, trading the reach of the floor against the burden on the payers.
Funding source — which surplus pool bears the cost, a choice about who, exactly, cross-subsidises whom.
Transparency / review cadence — how openly the rule is published and how often revisited; the dial that keeps it a live commitment rather than an ossified one.
Sunset / conditions — whether a subsidy expires or is means-tested, bounding its open-ended growth.

When it helps, and when it misleads¶

Its strength is keeping essential or universal coverage alive that pure economics would abandon — and, by being explicit, making that commitment debatable and defensible rather than a resented mystery.

Its failure modes are the familiar ones of any subsidy, sharpened by visibility. It distorts prices — subsidised endpoints can be over-served while the payers quietly carry the cost — and it invites gaming, as parties reclassify themselves to qualify. Subsidies also ossify, outliving the need that created them. The classic misuse is the hidden cross-subsidy: a blended price that silently taxes some customers to serve others, which breeds resentment when exposed and lets competitors cream-skim the profitable endpoints the subsidy depended on. The discipline that keeps it honest is exactly its name — keep the rule explicit and periodically reviewed, so the subsidy stays a chosen commitment with limits rather than a buried, unexamined transfer.

How it implements the components¶

cost_allocation_rule — the schedule is the explicit rule allocating pooled cost from profitable endpoints to essential high-cost ones.
coverage_floor — it sets and funds the minimum-service commitment the subsidy exists to guarantee for those endpoints.

It does not measure what each endpoint costs to serve — that is the Endpoint Cost-to-Serve Analysis, whose output it allocates over — nor does it physically deliver the funded service, which falls to the Mobile Service Unit, Local Partner or Agent Network, and their siblings.

Instantiates: Endpoint Fan-Out Fulfillment — funds the coverage of endpoints that would otherwise be economically stranded.
Consumes: Endpoint Cost-to-Serve Analysis supplies the per-endpoint cost picture the schedule allocates over.
Sibling mechanisms: Endpoint Cost-to-Serve Analysis · Mobile Service Unit · Community Access Point · Long-Tail Support Tier

Notes¶

The word "transparent" is load-bearing, not decorative. A cross-subsidy that is not visible and reviewable degrades into a hidden tax — and hidden taxes are what breed resentment, invite cream-skimming, and collapse the moment someone exposes them. The mechanism's protective power comes entirely from being seen: publishing the rule is not a nicety bolted onto the funding, it is the funding's defence.

References¶

[1] A universal service obligation — the legal duty to serve everyone in a territory at a common standard, common in post, telecoms, and utilities — is the classic setting for an explicit cross-subsidy: the profitable core is required to fund service to the unprofitable edge, and transparency about that transfer is what makes the obligation politically durable. ↩