Choose a profile
API/SDK, CRM, support, signed webhook, or Enterprise Control.
Evaluation PathFocused workflow review
Start with one workflow and one starter profile.
Clariva evaluations are meant to be focused. Choose a workflow, match it to a standard profile, review approved and rejected requests, and decide what is needed for production.
Process
A practical path from demo to scope decision.
The goal is to confirm whether the workflow fits a standard evaluation path
before deeper enterprise review begins.
The first review focuses on one workflow path. Broader pilot or production scope
is discussed only after the control model appears relevant.
Map one workflow
Define the source application, AI task, expected user, and general data context.
Review decisions
Inspect approved and rejected request examples with audit evidence.
Set production scope
Confirm what appears standard and what would require deeper enterprise review.
Evaluation Checklist
What a focused evaluation needs.
A good evaluation does not require every future use case. It needs one real workflow with enough context to test the control path.
Workflow
- Source application or system.
- AI task the workflow performs.
- Expected user or team owner.
Controls
- Data classes that need handling.
- Policy template or policy goals.
- Provider route preference.
Review
- Security, privacy, or compliance owner.
- Evidence needed for approval.
- Production readiness questions.
Evaluation Output
What your team receives from the review.
Starter profile fit
Which onboarding path best matches the workflow and where custom scope may be needed.
Control evidence
Approved and rejected examples showing policy, proof, route, and audit behavior.
Production scope
A clearer view of integration steps, security review items, provider routing, and deployment assumptions.
Review Package
Evaluation artifacts your team can review.
Architecture overview
Where Clariva sits in the selected request path and which boundary it controls.
Sample admitted request
An illustrative request that passes policy, proof, routing, and readiness checks.
Sample rejected request
An illustrative failed request with a structured rejection reason and no provider execution.
Audit record format
What decision evidence remains after an admitted or rejected request.
Provider-route summary
Which provider routes are eligible and when execution is blocked.
Open review questions
Security, privacy, legal, procurement, and production-readiness items that need customer-side review.
Evaluation
Use one workflow to test the control model.
The demo intake helps select the closest starter profile before custom enterprise scoping begins.