Release evidence

QA Release Summary Template

A release summary should not say only "QA passed." It should show what was tested, where it was tested, what evidence exists, what risk remains, and who made the call.

Build the summary

Fill the parts people actually need.

Release name Build / commit Environment QA owner Summary date Release decision What this release should prove Scope tested Not tested / out of scope Test data used Execution summary Evidence links Open defects Accepted risks Post-release watch Next steps

Copy-ready handoff

Markdown summary

Make it useful

What good looks like

Evidence beats adjectives

Write "Playwright smoke passed on build a1b2c3d, run link attached" instead of "testing looked good."

Risk needs an owner

If something ships with a known issue, name who accepted it and what would trigger rollback or follow-up.

Environment matters

A pass on a branch preview does not mean the release candidate passed in staging. Name the place and build.

Leave a trail

Include test data, devices, logs, screenshots, traces, CI runs and open tickets so the team can audit the call later.