Running Assessments
This page covers the mechanics of running an assessment — starting a run, watching it progress, and reviewing what it produces. For the conceptual picture, see Assessments Overview.
Who can access
Members of the engagement team.
Before you run
An assessment retrieves and reasons over the engagement's evidence, so quality depends on what's connected:
- Upload the client's documents and let them finish indexing.
- Optionally connect a database or run AI interviews for more coverage.
See Evidence Collection.
Running a run
- In Diagnose, select one or more frameworks.
- Confirm evidence coverage (how many sources will feed the run).
- Click Run Assessment.
- Watch the run stream through its stages:
| Stage | What's happening |
|---|---|
| Generate | Producing answers from retrieved evidence |
| Review | Checking answers and evidence coverage |
| Analyze | Scoring and identifying gaps |
| Report | Assembling the findings |
Runs are versioned — each run is preserved, so you can re-run and compare as evidence grows.
Reviewing answers
When the run completes, review per-dimension answers. Each answer shows:
- a confidence pill (Not grounded / Low / Medium / High),
- citations with source type, match score, and an excerpt,
- an "Open source" link into the Evidence Vault.
Accept the answers you trust — accepting unlocks downstream analysis and materializes the evidence into the vault. Then send gaps to Plan.
Best practices
- Read confidence and citations, not just the answer. Accept on the strength of the evidence.
- Re-run after adding evidence. Versioning is there to let the assessment improve.
- Don't accept Not grounded answers as findings. They indicate an evidence gap to fill.
Common errors
| Symptom | Likely cause | What to do |
|---|---|---|
| Run won't start | Selected framework isn't fully prepared (compiled) | Pick another framework or contact your Celeredge admin |
| Many Not grounded answers | Thin evidence for those questions | Add targeted documents or run an AI interview, then re-run |
| Run seems stuck | Long-running background job | Refresh to see streamed progress; if it stalls, start a new versioned run |