TemplatesPublishing

Record the document version you are actually publishing

Download a controlled document publishing worksheet with source and output revisions, format links, review coverage, open findings and update ownership.

At a glance

A publishing record should name the original, alternative formats, approved output revision, checks performed and responsible update owner. This template leaves the release decision pending until evidence exists. Generating or downloading a file is not the same event as approving it for publication.

Worksheet previewIllustrative data

Pending review and unconfirmed behavior remain visible in the example.

Template preview: publication readiness
DocumentOutput revisionOpen findingsDecision
Example policyNot approved yetReview pendingAwaiting review
Example applicationNot approved yetSubmission unconfirmedHeld for review

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

Bind links to an approved revision

Record the source revision and the exact reviewed output. Verify that public PDF and HTML links actually serve those versions. A stable URL can deliver changed bytes, so link existence alone is not sufficient release evidence.

State the role of each format: original download, reviewed HTML alternative or separate rebuilt PDF. Use descriptive link labels and retain source context so readers understand the choice.

  1. Replace examples with the source and routes intended for publication.
  2. Record the exact approved output revision and actual test coverage.
  3. Make format links descriptive and verify them anonymously.
  4. Provide a reader correction route in the published experience.
  5. A source or output change requires affected review before release.

Keep review scope with the decision

Record what was reviewed: text, tables, figures, forms, keyboard behavior or assistive-technology tasks. Include page sampling and unresolved findings. A blank open-findings cell should not be treated as a completed assessment when the checks remain pending.

The responsible team can approve, hold or request correction based on the agreed requirements. Keep that actual decision with evidence rather than inserting an automatic pass formula based on a checker score.

Plan what happens after release

Name an update owner and provide a reader correction route in the public experience. Source changes require affected comparison and review before remapping the public output. Preserve the earlier record so feedback can be traced to the revision a reader encountered.

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
Release IDStable publication record.
DocumentMeaningful document title.
Source revisionApproved current source or digest.
HTML / alternativeIntended public alternative route.
Original PDFIntended public original download route.
Approved output revisionExact revision tied to review evidence.
Checks and coverageWhat was actually reviewed; include sampling boundaries.
Open findingsRemaining barriers or uncertainty requiring a decision.
Update ownerTeam responsible for source changes and re-review.
Release decisionAwaiting review, approved or held, with actual decision evidence.

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. DocAccessible remediation options

    The different output paths and their review requirements.

  2. W3C: evaluating web accessibility

    Automated tools and knowledgeable human evaluation serve different roles.

  3. W3C PDF18: document title

    Setting a meaningful PDF document title.

  4. W3C PDF16: document language

    Setting the document's default language.

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.

Explore version-bound approval