Who this guide helps
Teams reviewing outputs for a defined task
The short answer
Use task-specific criteria and failure examples rather than a single aesthetic score. Accuracy, brief compliance, usability and originality concerns need separate checks.
Practical workflow
Define format, factual boundaries, visual or narrative constraints and unacceptable elements. Review authorized samples with humans. Preserve ambiguous and rejected outputs. Distinguish preference from verifiable defects such as incorrect dimensions or omitted text. Keep tuning examples separate from later test cases where practical.
What a useful handoff looks like
Report decisions with reasons and sample limits. Re-test after changes to tools or instructions. Let the responsible creator approve production use rather than converting a rubric score into automatic acceptance.
Mistakes to avoid
Do not claim universal superiority from a small internal trial or remove failures to improve results.
Working example: fields to record
| Field | Illustrative entry — replace with your own facts |
|---|---|
| Criterion | Brief requirement or format |
| Failure | Unsupported factual detail |
| Decision | Reviewer rationale and revision |
Add your own entries; the example is illustrative. Keep sensitive information private.
Sources & further checks
Official references are starting points for further checks, not approval of a specific case, product or project.
Editorial note
AI-assisted editorial guidance; not expert certification.
Original editorial guidance. Examples are illustrative, not client cases, measured outcomes or promised services.
Legal and health-related decisions require appropriately qualified local professionals. This site is an independent editorial resource, not a law firm or medical provider.