Policy Template with Local Options¶
Document — instantiates Slot-Template Design
A shared policy scaffold with bounded fields for local parameters, approved exceptions, and implementation choices.
A policy template with local options is a governing document that fixes a central intent and then designates a small set of fields where subordinate units may set their own parameters. Its defining move is the protected core plus bounded discretion: certain clauses are declared non-negotiable invariants that every local instance must preserve, while a few named parameters are handed down to local authority — and anything a unit wants that falls outside those parameters must go up for review, not be quietly adopted. It is not a catalog of good practices to draw from; it is a single binding policy that decentralizes exactly the choices it names and no others, with an appeal route for the cases the template didn't foresee. This is the principle of subsidiarity[n1] rendered as a fillable document.
Example¶
A public university system issues one academic-integrity policy adopted by all eleven campuses. The invariants are stated up front and marked non-negotiable: what constitutes plagiarism, a student's right to a hearing before sanction, and the requirement that every finding be recorded centrally. These survive intact on every campus — they are the policy's whole point.
Below the invariants sit the local-option fields. Each campus sets its own first-offense sanction (from a bounded menu: warning, resubmission, or grade penalty), its own reporting deadline (within a 5-to-15-business-day window), and whether it runs an honor council or a dean's-office process. One campus, facing a wave of AI-assisted-writing cases, wants to add mandatory course failure for a first offense — a sanction outside the menu. That is past the variation boundary, so it doesn't get to just do it: the request routes to the system's academic-affairs council for review, which either widens the menu for everyone or denies it. The core stays uniform, the named parameters flex locally, and the genuinely novel case is escalated instead of improvised.
How it works¶
The drafters explicitly partition the policy into three tiers: invariants (clauses stamped non-negotiable, with the intent they protect stated so no one mistakes a safeguard for a formatting choice), local-option fields (each with a bounded range or menu of permissible local values), and everything else, which by default belongs to no one until the review path assigns it. The variation boundary is the written line between "a value inside the local field's range" and "a change that needs escalation." Crucially, an out-of-bounds request is not simply forbidden — it has a defined destination and adjudicator, so pressure to deviate becomes a reviewable proposal rather than a silent local exception.
Tuning parameters¶
- Invariant tightness — how much of the policy is stamped non-negotiable. More invariants guarantee uniformity but leave less room for legitimate local fit.
- Option-field width — how wide each local parameter's permitted range is. Wider ranges respect local conditions; narrower ones keep instances comparable.
- Escalation threshold — how far a request must fall from the menu before it triggers review. A low threshold catches drift early but floods the review body.
- Review turnaround — how fast the escape path resolves. Slow adjudication tempts units to act first and ask forgiveness, eroding the boundary.
When it helps, and when it misleads¶
It fits multi-unit organizations that must honor a shared mandate — legal, safety, or mission — while allowing genuine local difference in the particulars. Its honest failure mode is the silent local exception: when the escape path is slow or punitive, units stop escalating and simply reinterpret the policy on the ground, and the invariant erodes exactly where no one is watching. The classic misuse is inverting the tiers under political pressure — quietly demoting an inconvenient invariant into a "local option" so a powerful unit can opt out — which hollows the policy while leaving its language intact. The guarding discipline is to keep the invariant/option partition explicit and periodically re-ratified, and to make the review path fast enough that escalation beats improvisation.
How it implements the components¶
invariant_specification— names the non-negotiable clauses and the intent each protects, so every local instance is checkable against them.variation_boundary— draws the written line between a permitted local-option value and a change that requires escalation.escape_or_review_path— gives out-of-bounds requests a defined adjudicator, converting local deviation pressure into a reviewable proposal.
It does not curate a menu of approved patterns to reuse, or specify how one sanctioned option is swapped for another — that membership_criteria and substitution_rule work is what Style Guide or Pattern Library provides; a policy template binds one intent rather than offering a library to pick from.
Related¶
- Instantiates: Slot-Template Design — a policy template is the governance instance: a protected invariant core with bounded local fields and an escalation route.
- Sibling mechanisms: Style Guide or Pattern Library · Curriculum Template · Document Template · Recipe Pattern · Design System Component Slot · Plugin Slot Registration · Product Configuration Matrix · Modular Form Schema
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: The mechanism establishes standing invariants, bounded local-option ranges, and escalation requirements governing future local policy variants.
Nearest alternative: Representation, Specification & Plan — The scaffold is a document, but its operative force is normative rather than merely descriptive.
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: A common policy scaffold with bounded local discretion is a multilevel implementation device in public administration.
Related originating lineages:
- Organizational & Management Science — Organizational design contributes standardization-with-local-adaptation templates.
Review resolution: Light authoritative-source research resolves the primary-origin disagreement in favor of public administration policy. OECD: When Should Place-Based Policies Be Used and at What Scale? 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 organizational management is substantive because that tradition materially developed or translated part of the mechanism; the cited provenance places the defining form in public administration policy.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
[n1] Subsidiarity — the governance principle that decisions should be made at the most local level competent to make them, with higher authority retaining only what the local level cannot properly handle. A policy template operationalizes it by naming which parameters are local and reserving the rest to central review. ↩