LLM evaluation in production
The demo convinces. Two weeks later someone changes the model. Answers get shakier. Without evaluation nobody notices in time.
What evaluation means here
Not a one-off blind test with five favourite questions. A fixed set: question, expected source or decision, who maintains the set. After every prompt, model or index change the same set runs.
Without that, "better" is a feeling. In an audit a feeling counts for nothing.
What I measure
Tools like RAGAS help. They do not replace the rule. The rule sits in the flow: measure, then change. Not the other way around.
A typical finding
A team switches to a larger model. The prose sounds better. The source rate drops. Legal would have seen that only at acceptance. With a set of 40 questions it would have been visible on the day of the switch.
This hangs on source grounding. Evaluation without a source checks style. Evaluation with a source checks whether you may go live.
What the readiness check does with it
On day 3 of the LLM readiness check I look for a set and for someone who runs it after a change. If it is missing, the report calls it a blocker, not a nice-to-have.
Related: reconstructing answers, hybrid RAG. The service page is AI engineering. Proof from practice: the audit assistant.
Related articles
The EU AI Act from the seat of the person building the system
Traceability, human oversight, documentation: what an engineer can contribute to the AI Act, and where the legal classification begins.
Read articleLLM operations: from demo to a run someone owns
A prototype needs an API key. Operations need versioned prompts, a pipeline, and someone who owns the run when it breaks.
Read articleA call
30 minutes. If the use case does not belong in production, I'll say so.