Salesforce Environment Register (Worksheet)

One row per non-production environment. Keep it current and give every environment a single named owner. A completed row records a decision and who made it — it does not by itself make an environment safe for a release.

Companion worksheet to Salesforce Sandbox Management: Reduce Release Risk Without Slowing Delivery.

How to use it

  1. List every non-production environment your team can reach, including ones nobody has touched in months.
  2. Assign one owner per environment. One name, not a team.
  3. Fill in active work before any refresh is requested — this is the field that prevents destroyed work at activation.
  4. Review at the start of each release cycle and whenever an environment changes purpose.

Per-environment entry

Copy this block once per environment.

Tabular version

Field Environment 1 Environment 2 Environment 3
Label
Type
Purpose
Owner
Active work
Last refresh
Data classification
Intended roles
Integration targets
Next refresh eligible
Activation owner
Readiness status

Notes on refresh eligibility

Minimum refresh eligibility intervals per Salesforce documentation (checked 16 November 2026): Developer and Developer Pro one day, Partial Copy five days, Full 29 days. These are the earliest you may request another refresh, not estimates of how long a copy takes. Confirm your own entitlements, licences and storage before planning around them.

Reference: Sandbox Licenses and Storage Limits by Type