Release readiness
Also called: readiness note, release readiness report, release sign-off
Release readiness is the evidence-backed judgement that a build can ship, usually written up as a short readiness note with a recommendation.
Release readiness is the state of knowing enough about a build to decide whether to ship it. The readiness note is the document that carries that knowledge to the people making the call.
Most readiness reports list activity: cases executed, defects closed, pipelines green. None of that tells a Head of Engineering whether Friday is wise. A useful note opens with a recommendation, then says what changed for users, what was verified and on which surfaces, what is still open, what was deferred and who accepted it, and what to watch after go-live.
My test for a readiness note is whether someone outside the team can read it in three minutes and know the call. If they cannot, the note needs rewriting before the release needs more testing.
Template: Release readiness note template