> For the complete documentation index, see [llms.txt](https://docs.layerlens.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.layerlens.ai/8.-evaluate-score-the-outputs/workflow.md).

# Evaluate (workflow)

Stage 4. **Evaluate** runs scorers and judges over your outputs to produce verdicts and scores.

## The question this stage answers

*"How good is the AI output — quantitatively?"*

## What to do

1. **Define quality dimensions.** What does "good" mean for this feature? Helpfulness? Faithfulness? Tone? Structured-output validity? List them.
2. **Pick scorers for objective dimensions.** Exact match, regex, JSON schema, semantic similarity, etc.
3. **Build judges for subjective dimensions.** One per dimension. GEPA-optimize against ≥30 labeled examples.
4. **Run.** Standard evaluation, or trace evaluation against your trace set.
5. **Read the verdict.** Top-line plus per-row failures. Spend most of your time on the failures — they're where you'll improve.

## What you'll have at the end

* A reusable scoring config (your scorers + judges)
* A baseline score
* A list of failed rows / failed traces with root-cause links

## Pre-deploy vs continuous

* **Pre-deploy** — run before merging changes; gate CI
* **Continuous** — run on production traces on a schedule; alert on drift

Both use the same scoring config; the cadence and consumer are different.

## Where to next

* [Improve →](/8.-evaluate-score-the-outputs/workflow.md)
* [Concept: Evaluations](/8.-evaluate-score-the-outputs/evaluations-1.md)
* [Concept: Judges](/8.-evaluate-score-the-outputs/judges-1.md)
* [Concept: Scorers](/8.-evaluate-score-the-outputs/scorers-1.md)
* [Tutorial: First evaluation](/8.-evaluate-score-the-outputs/01-first-evaluation.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.layerlens.ai/8.-evaluate-score-the-outputs/workflow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.