Local decision and evidence register

Do not enter secrets, personal data, production data, or undisclosed vulnerability details. Answers stay in this browser until you export them.

Reviewed: 0/40Gaps: 0Blockers: 28
  1. Decision authority · blocking

    Name the accountable role and project-defined acceptance evidence for decision authority.

    Expected evidence: Reference a reviewed artifact and decision date.

  2. Decision authority · blocking

    Define the stop, pause or rollback consequence when decision authority evidence is absent.

    Expected evidence: Reference a reviewed artifact and decision date.

  3. Scope freeze · blocking

    Name the accountable role and project-defined acceptance evidence for scope freeze.

    Expected evidence: Reference a reviewed artifact and decision date.

  4. Scope freeze · blocking

    Define the stop, pause or rollback consequence when scope freeze evidence is absent.

    Expected evidence: Reference a reviewed artifact and decision date.

  5. Production environment · blocking

    Name the accountable role and project-defined acceptance evidence for production environment.

    Expected evidence: Reference a reviewed artifact and decision date.

  6. Production environment · blocking

    Define the stop, pause or rollback consequence when production environment evidence is absent.

    Expected evidence: Reference a reviewed artifact and decision date.

  7. Identity and access · blocking

    Name the accountable role and project-defined acceptance evidence for identity and access.

    Expected evidence: Reference a reviewed artifact and decision date.

  8. Identity and access · blocking

    Define the stop, pause or rollback consequence when identity and access evidence is absent.

    Expected evidence: Reference a reviewed artifact and decision date.

  9. Security sign-off · blocking

    Name the accountable role and project-defined acceptance evidence for security sign-off.

    Expected evidence: Reference a reviewed artifact and decision date.

  10. Security sign-off · blocking

    Define the stop, pause or rollback consequence when security sign-off evidence is absent.

    Expected evidence: Reference a reviewed artifact and decision date.

  11. Migration execution · blocking

    Name the accountable role and project-defined acceptance evidence for migration execution.

    Expected evidence: Reference a reviewed artifact and decision date.

  12. Migration execution · blocking

    Define the stop, pause or rollback consequence when migration execution evidence is absent.

    Expected evidence: Reference a reviewed artifact and decision date.

  13. Data reconciliation · blocking

    Name the accountable role and project-defined acceptance evidence for data reconciliation.

    Expected evidence: Reference a reviewed artifact and decision date.

  14. Data reconciliation · blocking

    Define the stop, pause or rollback consequence when data reconciliation evidence is absent.

    Expected evidence: Reference a reviewed artifact and decision date.

  15. Integrations · blocking

    Name the accountable role and project-defined acceptance evidence for integrations.

    Expected evidence: Reference a reviewed artifact and decision date.

  16. Integrations · blocking

    Define the stop, pause or rollback consequence when integrations evidence is absent.

    Expected evidence: Reference a reviewed artifact and decision date.

  17. Queues and events

    Name the accountable role and project-defined acceptance evidence for queues and events.

    Expected evidence: Reference a reviewed artifact and decision date.

  18. Queues and events · blocking

    Define the stop, pause or rollback consequence when queues and events evidence is absent.

    Expected evidence: Reference a reviewed artifact and decision date.

  19. Business acceptance

    Name the accountable role and project-defined acceptance evidence for business acceptance.

    Expected evidence: Reference a reviewed artifact and decision date.

  20. Business acceptance · blocking

    Define the stop, pause or rollback consequence when business acceptance evidence is absent.

    Expected evidence: Reference a reviewed artifact and decision date.

  21. Capacity and performance

    Name the accountable role and project-defined acceptance evidence for capacity and performance.

    Expected evidence: Reference a reviewed artifact and decision date.

  22. Capacity and performance · blocking

    Define the stop, pause or rollback consequence when capacity and performance evidence is absent.

    Expected evidence: Reference a reviewed artifact and decision date.

  23. Recovery procedure

    Name the accountable role and project-defined acceptance evidence for recovery procedure.

    Expected evidence: Reference a reviewed artifact and decision date.

  24. Recovery procedure · blocking

    Define the stop, pause or rollback consequence when recovery procedure evidence is absent.

    Expected evidence: Reference a reviewed artifact and decision date.

  25. Backup restore

    Name the accountable role and project-defined acceptance evidence for backup restore.

    Expected evidence: Reference a reviewed artifact and decision date.

  26. Backup restore · blocking

    Define the stop, pause or rollback consequence when backup restore evidence is absent.

    Expected evidence: Reference a reviewed artifact and decision date.

  27. Monitoring and alerts

    Name the accountable role and project-defined acceptance evidence for monitoring and alerts.

    Expected evidence: Reference a reviewed artifact and decision date.

  28. Monitoring and alerts · blocking

    Define the stop, pause or rollback consequence when monitoring and alerts evidence is absent.

    Expected evidence: Reference a reviewed artifact and decision date.

  29. Support readiness

    Name the accountable role and project-defined acceptance evidence for support readiness.

    Expected evidence: Reference a reviewed artifact and decision date.

  30. Support readiness · blocking

    Define the stop, pause or rollback consequence when support readiness evidence is absent.

    Expected evidence: Reference a reviewed artifact and decision date.

  31. Training and access

    Name the accountable role and project-defined acceptance evidence for training and access.

    Expected evidence: Reference a reviewed artifact and decision date.

  32. Training and access · blocking

    Define the stop, pause or rollback consequence when training and access evidence is absent.

    Expected evidence: Reference a reviewed artifact and decision date.

  33. Stakeholder communications

    Name the accountable role and project-defined acceptance evidence for stakeholder communications.

    Expected evidence: Reference a reviewed artifact and decision date.

  34. Stakeholder communications · blocking

    Define the stop, pause or rollback consequence when stakeholder communications evidence is absent.

    Expected evidence: Reference a reviewed artifact and decision date.

  35. Cutover sequence

    Name the accountable role and project-defined acceptance evidence for cutover sequence.

    Expected evidence: Reference a reviewed artifact and decision date.

  36. Cutover sequence · blocking

    Define the stop, pause or rollback consequence when cutover sequence evidence is absent.

    Expected evidence: Reference a reviewed artifact and decision date.

  37. Rollback execution

    Name the accountable role and project-defined acceptance evidence for rollback execution.

    Expected evidence: Reference a reviewed artifact and decision date.

  38. Rollback execution · blocking

    Define the stop, pause or rollback consequence when rollback execution evidence is absent.

    Expected evidence: Reference a reviewed artifact and decision date.

  39. Operational handover

    Name the accountable role and project-defined acceptance evidence for operational handover.

    Expected evidence: Reference a reviewed artifact and decision date.

  40. Operational handover · blocking

    Define the stop, pause or rollback consequence when operational handover evidence is absent.

    Expected evidence: Reference a reviewed artifact and decision date.

Method, assumptions and limitations

Reviewed 14 July 2026. Product facts were checked against both the public code at the cited repository revision and official documentation. Where documentation and code differ, this guide describes behavior supported by code. Interpretations and recommendations concern implementation work, not product guarantees.

This material is not a quote, audit, certification, or legal, tax, or accounting advice. Edition, enabled modules, configuration, custom code, infrastructure, data, third-party providers, and operating practices affect the outcome.