TemplatesConversion

Keep a precise PDF conversion review log

Download an Excel or CSV conversion QA log for exact source/output revisions, text defects, tables, reading order, corrections and verification evidence.

At a glance

A conversion QA log should identify the exact source and output, where a defect appears, what changed and how the correction was checked. This template separates observed findings from correction and verification, so an edited draft never silently inherits an earlier review.

Worksheet previewIllustrative data

One observable defect per row keeps review and correction traceable.

Template preview: issue evidence
CheckSource locationFindingVerification
TextExample page 2Decimal omittedNot reviewed
Table headersExample page 4Header context missingUnresolved

Scroll sideways to see all columns. Use arrow keys when the table is focused.

Fix the comparison pair before logging issues

Record a source digest or frozen version and the exact HTML/PDF output revision. An unversioned browser page and an older screenshot are not a stable pair. State which pages, tables and interactions are in the agreed review coverage.

Use separate check labels for text fidelity, sequence, tables, figures, forms and interaction. A high extraction similarity does not settle whether a number retained its qualifier or a table retained its relationships.

  1. Delete illustrative rows and fix the source/output comparison pair.
  2. Write one observable issue per row with exact locations.
  3. Separate fidelity, semantics and reader-interaction checks.
  4. After an edit, update the output revision and repeat affected checks.
  5. Record sampled coverage and unresolved findings with the release decision.

Write a finding another reviewer can reproduce

Use page, heading, element or table/cell locations. Describe the source and observed output concretely, such as a missing negative sign or a note attached to the wrong table. Do not infer missing wording from an unreadable scan; request owner clarification.

Correction and verification are different columns. The person applying an edit should record it, then the reviewer should inspect the delivered revision and affected dependencies. Leave unresolved or unreviewed outcomes visible.

Carry the log into the release decision

Retain the relevant review environment, coverage and actual evidence with approval. A corrected issue can require repeated reading-order, navigation or table checks. Summarize remaining findings without reducing the whole document to an unsupported accuracy percentage.

Worksheet fields

The records sheet has 10 columns. Keep a stable ID and source evidence when sorting or extending it.

Field dictionary
ColumnHow to use it
Issue IDStable ID for one finding.
Source revisionByte digest or frozen source version.
Output revisionExact output version inspected.
Source locationPage and meaningful element, not a vague document-level note.
Output locationHeading, element ID or table/cell location.
CheckText, reading order, table, figure, form or interaction.
FindingObserved difference or barrier; do not invent missing content.
CorrectionWhat changed, or why owner clarification is needed.
VerificationNot reviewed, confirmed correction or unresolved, with evidence.
ReviewerActual reviewer/team, entered when work is performed.

Scroll sideways to see all columns. Use arrow keys when the table is focused.

The original worksheet schemas and fictional rows are offered under CC0. You can adapt them without a required backlink. This reuse statement covers the template assets, not the third-party references.

Sources and scope

Methods, worksheets and illustrative examples are DocAccessible editorial contributions. These references support the technical or product details described above. W3C techniques are informative guidance; they are not a certification scheme.

  1. pypdf: text extraction

    Why text extraction differs from OCR and cannot establish all visual or semantic meaning.

  2. W3C PDF3: reading and tab order

    The relationship between PDF tag order, reading sequence and interactive elements.

  3. W3C H63: HTML table header scope

    Associating row and column headers with data cells in HTML.

Written by the DocAccessible team under our editorial policy. Suggest a correction if a source or product detail needs updating.

Put the method to work.

Choose the right next step for your document.

Create a conversion draft to review