Launch worksheet
Work through the launch checks.
Your selections stay on this page until you reload or leave. Print or save a PDF through your browser to keep a record. Completing this list is not an accessibility certification.
0 of 16 checks completed
Agree the launch scope and owners.
Write down the published domain, pages where the assistant should appear, and information it should use. Confirm who can make website changes and who is authorised to approve business facts.
Name the person responsible for the inbox and the person who can resolve a content gap. If one person fills several roles, still record each responsibility so the handover remains clear when the team changes.
Use a small test set with expected results.
Choose questions whose answers you can check against the website. Include a natural paraphrase and a question with an extra condition, such as a holiday, an exception, or a location outside the normal service area.
Add at least one plausible question the source does not answer and one explicit request for a person. Decide what the response should do before testing so a fluent answer does not hide an unsupported claim.
| Record | What to write |
|---|---|
| Question | The exact wording entered by the tester. |
| Expected evidence | The source page, confirmed fact, or approved answer. |
| Actual result | The response and any record created in the workspace. |
| Decision | Accept, revise, or keep as a known issue. |
| Owner | The person who will complete and retest the change. |
Test the page around the assistant.
Open the published page at desktop and narrow widths. Check the widget against navigation, sticky buttons, consent controls, form fields, and page-end links. Try the page with browser zoom and reduced motion.
Use a keyboard through the complete flow and include the screen reader/browser combinations relevant to your audience. The checklist helps organise that review; marking boxes does not establish WCAG conformance for the whole website.
Verify that a person receives the work.
Use test contact information your team controls and confirm the resulting lead in the correct site. If live chat is enabled, assign an eligible specialist and set them Available while testing.
Request a person from the widget, send a message while waiting, claim it from the specialist desk, reply, and end the session. Repeat with nobody online and confirm the visitor sees an honest offline queue rather than an immediate-response promise.
Agree who can correct answers through Ask Sairo and whether external AI connections are appropriate for the team. Test a correction on the intended website and review the connection’s read or write access before using it for live work.
Leave a maintainable launch record.
Record the approval date, the scope tested, the known limitations, and the location of the website snippet. Keep a way to remove or disable that snippet without disrupting unrelated website code.
Schedule review as part of your operating process after a content update, a theme change, or a change of responsibility. Reuse the original test questions so the next check has a meaningful baseline.
Common questions
Does this checklist save information to Sairo?
The checkboxes on this page stay in the current browser page only. They are not submitted to a workspace and reset on reload. After you create an account, the in-app setup at Get started saves add site, verify, crawl, install, and the first test answer. Use Print here if you want a paper copy of the review aid.
Can I use this as an accessibility certificate?
No. It is a practical launch aid. A conformance assessment needs its own defined scope, testing, evidence, and findings.