Can your platform change safely?

1. 0Unknown / absentThe requirement is unclear, unavailable, or unowned.
2. 1Partially readySome evidence exists, but material gaps remain.
3. 2ReadyEvidence, ownership and controls are sufficient for the next step.

Score evidence, not optimism. If you cannot point to the data, owner, metric or control, score it 0 or 1.

1. 01

   Tenant isolation

   Every query, job and file is scoped to a tenant, and a missing scope fails closed.

   0 1 2
2. 02

   Permission model

   What users may do is kept separate from which records they may see.

   0 1 2
3. 03

   Data model fit

   The schema still matches how the business works without workarounds.

   0 1 2
4. 04

   Integration inventory

   Every integration, its owner and its failure impact is listed.

   0 1 2
5. 05

   Integration resilience

   Retries, idempotency and timeouts protect against partner failures.

   0 1 2
6. 06

   Automated tests

   Critical paths are covered by tests that run on every change.

   0 1 2
7. 07

   Release safety

   Deployments are repeatable, staged and can be reversed quickly.

   0 1 2
8. 08

   Database migrations

   Schema changes are reviewed, reversible and safe on live data.

   0 1 2
9. 09

   Observability

   Errors, slow requests and failed jobs are visible within minutes.

   0 1 2
10. 10

    Performance headroom

    Load is measured and the platform has room for the next growth step.

    0 1 2
11. 11

    Security and access

    Secrets, admin access and audit trails are controlled and reviewed.

    0 1 2
12. 12

    Data migration readiness

    Legacy data can be mapped, reconciled and verified before cutover.

    0 1 2
13. 13

    Documentation

    Architecture, runbooks and integration contracts are current.

    0 1 2
14. 14

    Incident response

    Someone is on call and past incidents led to real fixes.

    0 1 2
15. 15

    Cost visibility

    Infrastructure and third-party costs are known per tenant or feature.

    0 1 2