Content validation checklist

Use this checklist before labeling the site an accepted District deliverable.

Completed product-documentation checks

• Current module names, primary controls, and visible stage labels were checked against the Enterprise demonstration release on August 6, 2026.
• Screenshots use the clearly identified Enterprise Demo and synthetic records; every inserted image has meaningful alternative text.
• The production documentation build, strict link check, TypeScript check, development server, and dependency audit pass.

District acceptance still required

• Process owners confirm lifecycle stages and required approval gates.
• Role representatives confirm permissions, priority tasks, and local terms.
• Sensitive-data, records, export, and screenshot guidance is approved.
• Every Quick Step is completed successfully in the release candidate by an intended-role representative.
• District service desk, security, and business escalation contacts are added.
• At least one representative from each learning path completes its exercise.
• UAT feedback and application changes are reflected in the guide.
• Production URL, owner, review cadence, analytics choice, and publishing method are approved.
• District-approved screenshots replace or supplement demo screenshots if production branding is required.
• Timber-sale terminology and exercise are validated with a process owner.
• An Overview screenshot is captured from a clean demonstration dataset and added to the screenshot register.
• Process owners confirm that the conditions each module raises on Overview are the ones their roles act on.

Record the acceptance date, application version, reviewers, exceptions, and approval location in the release record. Re-run affected checks whenever a workflow, permission, integration, or label changes.

See Guide version and screenshots for the technical validation record and screenshot refresh instructions.