Skip to main content
Monitor shifts in the quality of your models before they affect students at scale.

What you’ll do

  • Compile a sample of text passages
  • Use Grade Level Appropriateness to evaluate the passages’ grade levels
  • Make a model, prompt, or infrastructure change
  • Run the evaluation again to see any grade level changes

What you’ll need

  • Node.js or Python
  • Google API key ↗ (needed for Grade Level Appropriateness and Vocabulary Complexity)
  • OpenAI API key ↗ (needed for Vocabulary Complexity)
  • Small sample of text passages

Steps

1

Install the SDK

Install the package for the language your pipeline uses:
TypeScript
2

Evaluate grade levels for your sample

Inputs must be de-identified. Do not submit students' Personally Identifiable Information (PII) or any regulated or sensitive personal information.
Use Grade Level Appropriateness to evaluate the grade level of each passage in your sample.
Count how many passages sit above your target grade level – this will be your baseline count.
3

Make product changes

Implement a set of feature and updates in your product.This could include model updates, prompt edits, shifted inputs, or even infrastructure changes.
4

Rerun grade level evaluations on your sample

With your product changes implemented, repeat the Grade Level Appropriateness evaluations on the same sample.Count how many passages now sit above your target grade level, and compare this to your baseline count from the earlier step.
If more passages sit above the target than last time, investigate the changes in your last release to see what may have caused this regression.If the count rose after a prompt edit, see Improve quality by refining prompts.
Store each new count with the date and product version (i.e. model version, prompt version, etc.), so a later shift has something to compare against.
5

Monitor vocabulary complexity to anticipate grade level changes

Vocabulary level often rises before the grade band does. As a result, you can treat passages’ rising vocabulary complexity as a signal to investigate whether their grade level may also be rising soon.Use Vocabulary Complexity to evaluate your sample before and after product changes and compare how many passages are scored very_complex or exceedingly_complex.
If a passage’s very_complex or exceedingly_complex counts go up, even when its grade level has not, investigate your product changes now.Waiting for the grade band to rise gives you less time to correct the issue and more chance of the regression reaching students.

Resource Library - Monitor quality in production

Track scores on a sample of production outputs so you catch a shift before it reaches students.

Quickstart

Run an evaluator in the Evaluators playground, a Python notebook, or with the SDK.

Tutorial: Vet content quality in production

Score each output and rewrite anything above your grade-band target.

Tutorial: Improve quality by refining prompts

Compare two prompt versions on grade band, vocabulary, and sentence structure.