Checklist

Pre-delivery checklist for AI-generated documents

Documents fail slowly and quietly. Nine passes, five minutes, and the export still works a year later.

Document QA workflow

Outline

  • Exactly one level-one heading; ranks increase by one.
  • No two sections share a title.
  • Heading text tells a scanning reader what the section answers.
  • No block runs past 220 words.

Data and tables

  • Equal cells per row, named columns, one unit per column.
  • JSON parses and carries the keys downstream consumers expect.
  • One date format throughout, unambiguous about day and month.
  • Ten rows sampled by eye for impossible values.

Links and accessibility

  • Every internal link resolves; every anchor matches a live heading.
  • Informative images have descriptive alt text; decorative ones have empty alt.
  • Link text makes sense read alone.

Versioning

  • Version and date appear in the document, not only in the filename.
  • Superseded versions are marked superseded.
  • Three-line change log kept for anything operational.

Sign-off

Reviewer

Date

Version reviewed

Record what was reviewed and what was not. An accepted finding is a decision, so write the reason next to it.

Automate the repeatable half

The list stays useful. The console makes it fast.

Run the same checks on the file before you walk the list by hand.