Site Readiness Assessment¶
Readiness assessment — instantiates Over-Scaling Guardrail
Requires each new location to demonstrate its own local readiness against tier-calibrated criteria before it opens, so no site inherits approval from the pilot instead of earning it.
A Site Readiness Assessment is a per-location evaluation: before a new branch, school, clinic, warehouse, or deployment site goes live, it must show — for itself — that the conditions for safe operation are actually present on the ground. Its defining property is locality. Where a growth limit governs how many sites may open and a maturity check evaluates the whole organization, this mechanism refuses to let readiness travel by assumption. The pilot's success does not certify site fourteen; site fourteen has its own staffing, its own local partners, its own building, its own risk profile, and it must clear a concrete criteria list scaled to how much harm a failure there could do. The output is not a number but a verdict on one place: ready, ready-with-conditions, or not yet — and exactly what is missing.
Example¶
A retail bank is rolling its new full-service branch format out across a region after two flagship pilots went well. Rather than replicate on the pilots' say-so, it runs a Site Readiness Assessment before every opening. Each candidate branch is first placed in a risk tier: a small in-store kiosk handling deposits is low tier; a full branch with a vault, notary, and small-business lending is high tier and faces a stricter bar. Then the branch is checked against tier-appropriate criteria — is the manager hired and trained, not just slotted; is the cash-handling and security setup certified; are local compliance and fraud-monitoring live; is there a named escalation path to a regional operations lead. The fourth candidate branch looks fine on paper but its trained manager just resigned and the vault certification is pending. The assessment returns not yet, with the two gaps named, and the opening waits — even though three identical branches opened cleanly last month, because readiness is a fact about this site, not the format.
How it works¶
What distinguishes the assessment is that it localizes readiness and tiers the bar:
- Assign a risk tier. Classify the site by how much harm a failure there could cause — volume, vulnerability of those served, reversibility — which sets how strict its criteria must be.
- Instantiate the criteria locally. Apply the readiness checklist to this specific site's people, systems, facility, and local partners, gathering concrete evidence rather than a claim of similarity to the pilot.
- Return a per-site verdict. Ready, conditional, or not-yet, with each unmet criterion named — so a "no" says precisely what must become true here.
- Refuse inheritance. Prior sites' success is explicitly not accepted as evidence for this one; each opening earns its own clearance.
The assessment judges one site's readiness; it does not set the count of sites or run the org-wide oversight review.
Tuning parameters¶
- Criteria strictness by tier — how demanding the bar is at each risk level. Strict bars protect high-harm sites but slow openings; loose bars speed rollout but let weak sites through.
- Tier boundaries — where a site crosses from one risk class to the next. Coarse tiers are cheap to run but blunt; fine tiers match the bar to the hazard but add classification overhead.
- Evidence depth — whether a criterion is met by attestation, document, or on-site verification. Deeper evidence catches paper-readiness but costs assessor time.
- Conditional-open latitude — how many gaps may be carried as post-open conditions versus hard blocks. Latitude keeps rollout moving but risks opening sites that never close their gaps.
When it helps, and when it misleads¶
Its strength is that it kills the single most dangerous scaling error in multi-site systems: treating a hand-picked, heavily-supported pilot as proof that ordinary sites are ready. By forcing each location to demonstrate local readiness, it closes the gap between what worked under ideal pilot conditions and what will hold under everyday ones — an operational readiness review, the discipline aerospace and other high-consequence fields use to verify a specific unit is prepared before it goes live, not merely that the design once worked somewhere.[1]
Its failure mode is checklist theater: an assessment that verifies easy-to-document items (is the sign up, is the manual printed) while missing the tacit conditions that actually determine whether a site copes. Tiering can be gamed, too — misclassifying a high-harm site downward to dodge the stricter bar. And a lenient conditional-open policy can let sites launch with gaps that quietly never close. The discipline that keeps it honest is to verify the criteria that predict real failure on the ground, tier by the true hazard rather than by convenience, and to track whether conditional gaps are actually resolved after opening.
How it implements the components¶
Site Readiness Assessment fills the localized-readiness slice of the archetype's machinery:
scale_readiness_criteria— it instantiates the readiness criteria at the level of a single site, gathering concrete local evidence that each condition is met before the site opens.risk_tier_model— it classifies each site by potential harm and calibrates how strict the criteria must be to that tier, so high-consequence sites face a higher bar.
It does not evaluate the organization's oversight and accountability maturity (control_capacity_indicator, external_accountability_signal — that is Governance Maturity Check); this assessment judges one site's local readiness, not the whole control system.
Related¶
- Instantiates: Over-Scaling Guardrail — the assessment makes each new site earn its own clearance rather than inherit the pilot's.
- Sibling mechanisms: Rollout Cap · Franchise Growth Limit · Hiring Pace Limit · Governance Maturity Check · Quality-Before-Growth Rule · Incident-Rate Freeze Rule · Pilot Expansion Ladder · Scale Gate · Staged Expansion Review
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Site Readiness Assessment operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it requires each new location to demonstrate its own local readiness against tier-calibrated criteria before it opens, so no site inherits approval from the pilot instead of earning it.
Independent corroboration: The frozen evidence defines Site Readiness Assessment as 'Requires each new location to demonstrate its own local readiness against tier-calibrated criteria before it opens, so no site inherits approval from the pilot instead of earning it', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Public Administration & Policy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Requiring each location to earn opening approval against locally demonstrated criteria is program-implementation assurance. GSA siting rules ground local access and site-specific evaluation, while engineering supplies readiness evidence.
Related originating lineages:
- Accounting & Auditing — Documented evidence prevents unsupported approval carryover.
- Architecture & Urban Planning — architecture_urban_planning contributes architecture and spatial planning to this mechanism's defining operation—Requires each new location to demonstrate its own local readiness against tier-calibrated criteria before it opens, so no site inherits approval from the pilot instead of earning it—without displacing the selected primary historical lineage.
- Engineering & Design — Commissioning verifies local physical and technical conditions.
- Law & Governance — law_governance contributes legal doctrine, regulatory governance, and procedural accountability to this mechanism's defining operation—Requires each new location to demonstrate its own local readiness against tier-calibrated criteria before it opens, so no site inherits approval from the pilot instead of earning it—without displacing the selected primary historical lineage.
- Organizational & Management Science — Staffing, process, and ownership readiness cannot be inherited from a pilot.
Review resolution: The blind reviewers disagree on primary lineage (public_administration_policy versus architecture_urban_planning). Authoritative or primary research supports public_administration_policy as the best historical origin: Requiring each location to earn opening approval against locally demonstrated criteria is program-implementation assurance. GSA siting rules ground local access and site-specific evaluation, while engineering supplies readiness evidence. The cited U.S. General Services Administration, Sustainable and Equitable Siting Rule directly supports the mechanism's defining operation. All independently supported contributing domains are retained without an arbitrary cap. origin_mode=cross_disciplinary_synthesis records lineage, while domain_reach=multi_domain records later applicability separately from provenance.
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:
References¶
[1] Hirshorn, S. R., Voss, L. D., and Bromley, L. K. NASA Systems Engineering Handbook. NASA/SP-2016-6105 Rev 2 (2017). Defines NASA operational readiness review as verifying that the deployed system and its supporting hardware, software, personnel, procedures, capabilities, and documentation are ready for normal operations. registry ↩