Example release brief
Read this sample to see how a release brief can give the team a clear plan before rollout.
- Rollout
- Internal preview
- Readers
- Product and support
What changed
The onboarding checklist shows the next step when someone returns after an interruption. It distinguishes completed steps from steps that still need attention.
Before rollout
- Start the checklist on a phone and finish it on a laptop.
- Confirm the next step after closing and reopening the page.
- Ask support to review the recovery instructions.
Support handoff
If someone reports a missing step, ask what they completed and what the checklist shows now. Include the step name when passing the issue to product.
Ask for a complete, portable report
Ask your agent for a finished HTML report with clear section headings, readable tables, and references to the sources it used. Package styles, images, and scripts as local assets. Review its claims and sources before you share it; publishing does not verify the report’s conclusions.
For example, a research summary can include its question, findings, supporting charts, source notes, and next steps. A project update can combine a written explanation with a table of decisions. Your report keeps its own design and content.
Preview the actual files
Connect ChatGPT or Claude Code to your workspace and ask your agent to publish the finished report privately. Review the page on a small screen before you share it. Check table labels, chart explanations, and links between sections.
The guides for ChatGPT and Claude Code explain how each agent can transfer your files. You can also publish finished files in the browser.
Share it with its intended readers
Start private while you review the report. Invite specific people for a limited audience, use team access for workspace knowledge, or choose public access for an open resource. The page owner controls invitations; inviting someone to one report does not add them to the workspace.
If the report contains forms or other saved data, review those collection permissions separately. Making a report public does not make its existing private records public.
Keep the link useful over time
When the analysis changes, publish a new file revision to the same page. New visits open the current publication. An existing reader keeps the version already open until they reload, preserving their place and any unsaved work.
Use version history to review the files you published. A file rollback keeps the address and saved records; it does not roll data back.
Make public knowledge discoverable
Give a public report a descriptive title and an accurate summary, then explicitly enable search visibility if you want it considered for indexing. Search engines decide whether to include and rank a page. Keep private material out of the published files.
Connect an agent