Purpose and use
A modernization proposal exists, but the organization has not established what behavior, data, integrations, reporting, and operational constraints must remain intact.
Who should use it
Enterprise, Government, Partner decision owners, technical owners, reviewers, and delivery partners.
Decision supported
A modernization proposal exists, but the organization has not established what behavior, data, integrations, reporting, and operational constraints must remain intact.
Behavior and data
For each item, record the responsible owner, evidence, and whether the answer is Yes, Partly, No, Unknown, or Not applicable when the worksheet format supports it.
- Identify critical calculations, approvals, permissions, exceptions, and reports
- Trace rules across code, stored procedures, jobs, configuration, and manual workarounds
- Define reconciliation and parity scenarios
- Mark known, unknown, disputed, intentional, and accidental behavior
Architecture and operations
For each item, record the responsible owner, evidence, and whether the answer is Yes, Partly, No, Unknown, or Not applicable when the worksheet format supports it.
- Inventory dependencies, vendors, environments, and integrations
- Identify unsupported components and key-person risk
- Define observability, rollback, and continuity constraints
- Separate stabilization, seam creation, migration, and replacement
Commercial decision
For each item, record the responsible owner, evidence, and whether the answer is Yes, Partly, No, Unknown, or Not applicable when the worksheet format supports it.
- Name the decision owner and acceptance basis
- Estimate by bounded seam rather than whole-system optimism
- Require explicit exclusions and client responsibilities
- Prefer reversible phases with evidence between commitments