Include inconvenient examples
An evaluation should contain more than clean, straightforward material. Include an ambiguous date, a superseded draft, a duplicated email, and a question the source does not answer. These examples help reveal whether the system can preserve uncertainty and version distinctions. Keep a separate set of examples for checking later revisions.