Purpose and use
A vendor proposal is being considered without a clear view of architecture fit, data boundaries, implementation responsibilities, lock-in, operating cost, and exit conditions.
Who should use it
Enterprise, Government, Partner decision owners, technical owners, reviewers, and delivery partners.
Decision supported
A vendor proposal is being considered without a clear view of architecture fit, data boundaries, implementation responsibilities, lock-in, operating cost, and exit conditions.
Fit and architecture
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.
- Named business problem and system boundary
- Integration and data ownership model
- Identity, access, tenant, and environment boundaries
- Failure handling, observability, rollback, and support
- Model, platform, and third-party dependencies
Commercial and operational risk
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.
- Implementation and client responsibilities
- Usage, cloud, model, and support cost drivers
- SLA and support commitments matched to actual capacity
- Data export, knowledge transfer, termination, and lock-in
- Background IP and client-specific work product
Evidence
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.
- Reference architecture and data-flow diagram
- Security and privacy materials through approved channels
- Known limitations and roadmap dependencies
- Acceptance tests and proof of value
- Decision record and unresolved-risk owner