Deployment Scope

Template Library

Deployment Scope

Define baseline, source decisions, target environment, approved users, approved data, enabled/disabled capabilities, and deployment restrictions.

ES-112 Scope Deployment Boundary

Library AreaTemplate Library

Current PageDeployment Scope

FocusScope

UseDeployment Boundary

Repository Areadocs/template-library/deployment/

← Previous Deployment Overview

Current Deployment Scope

Next → Environment Readiness Check

Template purpose

Use this template to define exactly what is being deployed and under what restrictions.

Project

<Project name>

Document control

Field	Value
Artifact owner	<owner>
Primary reviewers	<reviewers>
Status	<draft / in review / accepted / revised>
Last updated	<YYYY-MM-DD>
Related Engineering Stage	ES-112 — Deployment and Transition
Project workspace target	docs/project-workspace/deployment/deployment_scope.md

Baseline / candidate

Field	Value
Baseline / Commit / Tag	<baseline>
Source Release Decision	docs/project-workspace/release/release_decision_record.md
Source Operational Decision	docs/project-workspace/operations/operational_readiness_summary.md
Deployment Type	<pilot / production / internal / limited / rollback / transition-only>

Target environment

<environment>

Approved users

User Group	Approved?	Restrictions	Evidence
<user group>	<yes/no>	<restriction>	<evidence>

Approved data

Data Type	Approved?	Restrictions	Evidence
<data type>	<yes/no>	<restriction>	<evidence>

Enabled capabilities

Capability	Evidence	Notes
<capability>	<evidence>	<notes>

Disabled capabilities

Capability	Disabled How	Verification
<capability>	<feature flag / config / access / exclusion>	<evidence>

Deployment restrictions

Restriction	Reason	Enforcement
<restriction>	<reason>	<enforcement>

Scope exceptions

Exception	Rationale	Approved By
<exception>	<rationale>	<authority>

Review checklist

• [ ] Baseline/candidate is identified.
• [ ] Source release and operational decisions are linked.
• [ ] Target environment is defined.
• [ ] Approved users and data are explicit.
• [ ] Enabled and disabled capabilities are clear.
• [ ] Deployment restrictions are enforceable.

Continue to Environment Readiness Check

Proceed to the next ES-112 deployment and transition artifact.

Open Environment Readiness Check →