When a model change breaks your brand voice, the failure is usually quiet. Nothing throws an error; the draft just reads flatter, hedges more, or starts every paragraph with the same connective. To catch that, teams run a regression set: a fixed batch of prompts whose outputs are scored after every prompt, model, or pipeline change. If the scoring is one person saying "this feels off," you cannot tell whether the model regressed or the reviewer had a bad morning.
The published guidance on model routing makes the same point in a different context: cost and complexity signals can select a model, but only evaluation on representative examples shows whether the output is acceptable, and that routing decision should be backed by a benchmark you built for your own workload Braintrust's routing guide. A voice rubric is that benchmark for prose. Most teams evaluating RAG systems already track five distinct metrics (retrieval correctness, response accuracy, grammar, coherence, relevance) rather than one overall score, which is why a multi-row rubric is the standard shape DoorDash's RAG support case study.
The insight most first searches miss: the rubric is not the hard part. The raters are. Two competent people with the same rubric will drift apart unless you measure their agreement first. Research on rubric scoring in graduate education found that inter-rater reliability can be achieved, but the apparent strength of that reliability varies substantially depending on which statistical measure you choose Goertzen and Klaus on rubric reliability. So pick your measure, fix it in advance, and do not shop around after you see the numbers.



