CMS migration and redirect plan
Shows how a source inventory, destination and acceptance check stay connected.
Synthetic planning sample. Version 1.0, published November 7, 2026. Authored by Newton & Carter for demonstration; no client, participant or measured outcome is implied.
Newton & CarterDefine what ready means.
01
Scope
02
Build
03
Review
Inspect the artifact
The complete, machine-readable source is below. Use it to discuss the structure and acceptance of an engagement.
{
"version": "1.0",
"scenario": "Fictional Meridian County migration",
"records": [
{
"source": "/departments/public-works/trash",
"destination": "/services/waste",
"owner": "Public Works editor",
"checks": [
"Content inventory reconciliation",
"Permanent redirect",
"Search result and keyboard journey"
]
},
{
"source": "/forms/permit.pdf",
"destination": "/services/permits",
"owner": "Permit editor",
"checks": [
"Document accessibility review",
"Form labels",
"Resident task test"
]
}
],
"releaseGate": "Reconcile all agreed records and resolve failed priority journeys before launch."
}