Check What Actually Changed
A release summary should distinguish who can use a change, what problem remains, and what has not shipped. Match each claim to the latest applicable entry in the supplied change log.
This exercise uses a fictional product and records. It is not an actual release announcement or a test of any AI provider.
Get The Pack
Give the AI only the test input. Keep the review key and worksheet separate, and retain the first answer before requesting corrections.
Download comparison worksheet (.txt)
Check Three Release Claims
| Case | Draft claim | What the change log supports |
|---|---|---|
| REL-01 | Everyone can use the new layout. | Only invited test workspaces with the preview enabled have it. No general rollout date was announced. |
| REL-02 | Batch export has been fixed. | Batch export still fails on the recorded sample. Individual export is the documented temporary workaround for that sample. |
| REL-03 | Scheduled summaries shipped in the release. | They remain planned and are not in this release. No date is confirmed. |
Keep the useful part of the notice. For REL-02, report both the open problem and the temporary option; do not promise that the option works for every workflow.
Repeat With The Same Change Log
Reuse the three records on a later run. Compare whether each answer preserves rollout scope, unresolved issues, and planned status. Record a baseline if no comparable earlier answer exists.
Return to the release notes practice pack or choose your next check.
For real announcements, verify the current official notice and the scope for your account before acting. Use the team check-in workflow to decide what your team should verify or retest.