CONTROLLED OPERATIONS REGISTER

Network Change Plan

Create an ordered network-change plan with validation, rollback triggers, and named owners for each phase.

No account or upload requiredRuns in this browser tabEditable draft, not approvalUp to 500 complete rows, 1,000 characters per cell, and 20,000 characters across the planning input.

Operational inputs

Prepare the network change plan

Define a narrow scope and accountable owner, then enter only current, authorized operational facts. Load the fictional example if you want to inspect the accepted format first.

Estate, service, or change scope0 / 180

Name one bounded environment, service, supplier, change, exercise, or review period. Avoid broad labels such as all IT.

Accountable IT owner0 / 180

Enter the role responsible for validating evidence and approving operational use. A role is safer than personal contact data.

Structured operational rows0 / 20,000

Enter one complete row per line. Separate cells with | in the exact order displayed below; empty, missing, or extra cells are rejected.

Required row orderPhase | Change action | Validation | Rollback trigger | Owner

Assumptions and evidence0 / 20,000

Record source systems, extraction or pricing date, requirements, dependencies, exclusions, and evidence references. Do not enter secrets.

This browser workspace does not scan a network, connect to provider accounts, inspect controls, approve spend, or apply infrastructure changes.

Scoped output preview

Your review artifact will appear here

Start with the fictional example to see a complete input, or enter authorized planning data. The generated draft will include its scope, owner, assumptions, and decision boundary.

Set one clear scope and accountable role.
Follow the exact displayed row order or load the fictional example.
Generate, inspect assumptions, then download for qualified review.

Transparent method

How the network change plan works

The tool validates every row against this tool's exact column schema, protects spreadsheet cells from formula execution, and appends scope, ownership, and evidence context to the CSV.

01Confirm the environment or service boundary, accountable role, authoritative sources, review date, dependencies, assumptions, and approval path before entering data.
02Check every asset reference, identity, license, price, count, address, control, status, owner, dependency, rollback step, and evidence reference against the source system.
03Review the formula-safe CSV register with the required security, privacy, finance, architecture, legal, change, service, and business owners before recording it in the official system.

Decision boundary

This workspace does not authorize operational change

Do not execute a migration, deployment, network change, site move, failover, restore, or recovery test from this draft alone. Use approved procedures, backups, rollback, communications, testing, and accountable authorization.

Operational review

Four checks before operational use

Remove passwords, tokens, private keys, unnecessary personal data, and sensitive production details.
Confirm the source system, extraction or pricing date, scope, owner, assumptions, dependencies, and evidence references.
Validate security, privacy, licensing, finance, architecture, continuity, support, testing, and rollback impacts.
Record approval, exceptions, execution evidence, remediation owners, and due dates in the authorized system of record.

Practical help