Make readiness visible.

• The executive sponsor and day-to-day implementation owner are named.
• One pilot workflow is selected and bounded.
• The current workflow is mapped from trigger to outcome.
• Every important record has a defined source of truth.
• Required fields and data owners are documented.
• Duplicate, incomplete, and sensitive data are identified.
• Success measures have written definitions and sources.
• Exceptions and escalation paths are documented.
• Staff, volunteer, and customer access needs are listed.
• Training time and coverage are reserved.
• A rollback and recovery plan exists.
• The 30-day review date and decision rule are scheduled.

Saved only in this browser.

• The use case is reversible and does not make a consequential decision.
• Approved tools and accounts are named.
• Prohibited data is defined in plain language.
• Test records are fictional or appropriately de-identified.
• A qualified reviewer and backup reviewer are assigned.
• The review checklist and escalation path are documented.
• Baseline time and quality measures are recorded.
• The pilot has an end date and expand, revise, pause, or stop decision.

Saved only in this browser.