# RFP Checklist — KLA vs Arize Phoenix (Regulated Agent Workflows)

Last updated: 2025-12-17 · Version v1.0  
Not legal advice.

## What this checklist is
Phoenix is excellent for open-source tracing and evaluation workflows (often OpenTelemetry-native). This checklist helps you verify whether your program also covers **governance + proof** for regulated audits.

## Audit deliverables (minimum viable)
- Human oversight SOP + evidence records (approvals, escalation, overrides)
- Post-market monitoring plan + sampling policy section
- Audit log retention policy + integrity verification mechanics
- Evidence pack export bundle (manifest + checksums; redaction rules documented)
- Annex IV-style documentation export mapping (fields → evidence)

## Questions to ask any vendor
- Can you enforce workflow checkpoints (block/review/allow) as **controls**, not only observe?
- Do you have role-aware approval queues, escalation SLAs, and override justifications?
- Can you export an auditor-ready evidence pack with integrity verification?

## Where Phoenix typically fits
- Strengths: engineering iteration loops (tracing + evaluation) and open tooling.
- Common gap to close for audits: decision governance (approvals/overrides) and proof-grade export bundles tied to workflow versions and policies.

Links:
- Compare page: `/compare/kla-vs-arize-phoenix`
- Evidence pack checklist: `/resources/evidence-pack-checklist`
- Sample Evidence Room export: `/downloads/evidence-room-sample.pdf`