AI curriculum
Course outline for LLM and Agent Evaluation
A fluent completion message is not evidence that an agent changed the right state within its authority. Evaluate answer support, retrieved evidence, tool effects, and stop conditions separately. Compare two configurations on held-out fixtures and report review cost and disagreement alongside quality.
- Technology
- AI Operations, Evaluation and Observability
- Duration
- 6 hours
- Modules
- 3 · 2 hours each
- Level
- Level 5
About LLM and Agent Evaluation
A fluent completion message is not evidence that an agent changed the right state within its authority. Evaluate answer support, retrieved evidence, tool effects, and stop conditions separately. Compare two configurations on held-out fixtures and report review cost and disagreement alongside quality.
LLM and Agent Evaluation Course Objectives
- Define separate answer-quality, task-success, and invariant checks.
- Assemble development and held-out datasets with valid and adverse cases.
- Test tool effects, denied writes, and interruption outcomes independently of agent narratives.
- Compare human judgments and automated-judge outputs against adjudicated examples.
- Justify acceptance thresholds using error consequences and review effort.
Pre-requisites
- Application-evaluation competence equivalent to AI Application Evaluation.
- Understanding of tools, agent loops, and action boundaries equivalent to Agentic AI Foundations.
- Basic testing and data-analysis skills; observability and security experience are useful extensions.
Before this course
Complete the required courses or bring equivalent experience. Recommended courses add useful depth; they are not enrolment gates.
Required preparation
Recommended preparation
Can design application tests and explain an agent loop before evaluating tool effects, authority, and task success.
Find your place in the learning mapLab Setup
- Computer with a test runner and spreadsheet or analysis notebook.
- Use synthetic state, supplied model outputs, and mock tools; online behavior and judge calls can be simulated without paid APIs or live users.
- Supply fresh-session runs, stopped-stream versus canceled-work versus completed-action fixtures, and a separate held-out set to avoid tuning on final acceptance cases.
Detailed Course Outline
Module 1: Evaluation contract and settings
- Offline evaluation: Define task contracts and compare configurations on held-out fixtures; separate development examples from final acceptance cases to limit evaluation leakage.
- Online evaluation: Design a simulated monitoring plan for deployed behavior, review effort, and adverse outcomes; distinguish observed signals from a live causal experiment.
- Quality metrics: Choose answer-support and correctness criteria based on error consequences; keep quality scores separate from authority invariants and task completion.
Practical outcome: Define a bounded task contract, error-cost table, held-out split, and simulated online monitoring plan without claiming a live experiment.
Module 2: Answers versus actual effects
- Agent success metrics: Check durable state, permitted effects, and stopping behavior independently; distinguish stopped streams, canceled pending work, and already committed actions.
- RAG metrics: Evaluate retrieved evidence and answer support separately; detect missing sources and unsupported claims even when an answer appears fluent.
- Regression suites: Version valid and adverse cases covering malformed arguments, denied writes, and interruptions; fail forbidden effects regardless of narrative quality.
Practical outcome: Build independent checks for answer support, tool arguments, permitted effects, durable state, and stopping; fail fluent answers when state or authority is wrong.
Module 3: Judgment and comparison
- Evaluation datasets: Construct representative synthetic cases with explicit expected outcomes and held-out splits; repeat fresh-session comparisons without tuning on final results.
- Human evaluation: Use explicit rubrics, adjudicated examples, and disagreement records; include reviewer effort and error consequences when choosing acceptance thresholds.
- Automated judges: Compare judge outputs with human adjudication and independent state checks; document disagreements and reject scores that overlook unauthorized effects.
Practical outcome: Compare two configurations over repeated fresh-session fixtures, adjudicate judge disagreements, and report quality, review effort, and threshold limitations.
Practical exercise
- Submit a versioned suite, held-out results table, and threshold/disagreement dossier for two configurations or supplied runs.
- Include valid tasks, absent evidence, denied writes, malformed arguments, and interrupted execution; inspect actual final state.
- Run at least ten held-out cases per configuration and require every authority invariant to pass independently of answer scores.
- Reject all seeded unauthorized-effect cases, adjudicate every human/judge disagreement, and report task acceptance and total review effort separately.
What you will produce
Evaluate agent task outcomes with independent state, authority, and answer-support checks.
How the work is checked
- Held-out results cover at least ten cases per configuration and all specified adverse categories.
- All unauthorized effects fail acceptance even when the response is fluent.
- Interrupted-run checks distinguish a stopped response stream, canceled pending work, and an already committed action by inspecting final mock state.
- Judge disagreements have adjudicated outcomes and documented limitations.
- Threshold rationale includes error consequences and reviewer effort, not stated model confidence.
Six-hour offline and simulated-online evaluation lab; calibration, statistical inference, and live experiments require specialist follow-up.
When another approach is better
- A judge score alone is unsuitable when correctness depends on externally observable state or permission.
- A small fixture suite cannot establish population-level reliability or calibrated confidence.
- Do not run live online evaluation on consequential users without a separate safety and experiment plan.
How we train
Contact us for full course details, including duration, delivery options and lab requirements.
Ask about exercises, instructor feedback and the prior knowledge you need. Tool-specific courses marked provisional may become modules in a broader course.
Discuss your learning goals