InterLAB tools · 37 checks · evidence · GO/NO-GO

Release readiness

A check matrix tailored to your release type: CI and tests, migrations, backups, a rollback plan, monitoring, security, data. Each check gets evidence, each accepted risk gets a recorded exception, and the release gets role sign-off. You get a GO / NO-GO decision with reasons and a report for the team.

Free, no sign-up

Verdict

Insufficient data

preliminary

Blocking checks are not checked or not backed by evidence.

The verdict becomes final once every required role records a decision (RR-S3).

verified: 0
unverified: 0
failed: 0
exception: 0
not applicable: 0
not checked: 27

About the release

Release name

Version

Release date

Time

HH:MM

Environment

Release owner

Release type

HotfixAn urgent fix to a live systemMinor releaseSmall features and fixesMajor releaseNew areas, noticeable behaviour changesFirst launchThe product reaches users for the first time

Release specifics

Flags make some checks required or blocking (see the table on the page).

Has database migrationsChanges personal or payment data handlingChanges infrastructure (servers, network, configuration)Feature flags are usedMobile app store release

Matrix: 2 blocking, 15 required, 10 recommended; 10 not applicable to this release.

How the readiness check works

The release and its specifics
Release type (hotfix, minor, major, first launch) and flags: migrations, personal and payment data, infrastructure, feature flags, app stores. They set each check's level: blocking, required, recommended or not applicable.
Checks with evidence
Each check has a status, evidence (a link, CI output, a screenshot reference, text), who checked it and a note. “Passed” without evidence counts as “unverified”. Pasted CI output is parsed: GitHub Actions and GitLab jobs, and Jest, Vitest, pytest, JUnit, Mocha, Playwright and Go summaries.
Exceptions and plans
A failed check can be accepted as a risk — only with a reason, mitigation, approver and expiry date. The “Rollback plan” and “Monitoring” sections serve as evidence for the related checks.
Verdict and sign-off
The verdict follows published rules: NO-GO, “Insufficient data”, GO with exceptions or GO — with a list of reasons linked to checks. It becomes final once every required role decides; each decision saves a pinned version with a snapshot of the evidence.

Verdict rules

The tables below are generated from the same code as the calculation. Rules apply in order: NO-GO first, then “Insufficient data”, then GO with exceptions, otherwise GO.

ID	Rule
RR-E1	“Passed” without evidence (text, a link, a CI log or a completed tool section) is “unverified”.
RR-E2	“Passed”, but the pasted CI log shows failures (failed jobs, tests or step errors) — “unverified”; the evidence lines are shown.
RR-E3	“Not applicable” on a blocking or required check without a reason — “unverified”.
RR-E4	Hint: “link” evidence should contain an http(s) address. Does not affect the verdict.
RR-X1	An exception is valid only with a reason, mitigation, approver and expiry date, and only until it expires (expiry ≥ today). An invalid exception counts as “failed”.
RR-F1	Completed “Rollback plan” and “Monitoring” sections serve as evidence for RR-14, RR-16, RR-17, RR-18 and RR-19. A person still sets the status.
RR-V1	NO-GO: a blocking check failed without a valid exception.
RR-V2	NO-GO: a required role rejected the release (the role's latest decision).
RR-V3	“Insufficient data”: the release name or type is missing, or blocking checks are not checked or unverified.
RR-V4	GO with exceptions: blocking checks passed or have exceptions, but there are exceptions or unverified required checks.
RR-V5	GO: every blocking and required check passed with evidence (or is justifiably not applicable), with no exceptions.
RR-S1	Required sign-off roles depend on the release type and flags (table below).
RR-S2	A sign-off becomes stale if the release data (checks, evidence, exceptions, rollback plan, monitoring) changed after it.
RR-S3	The verdict is final only when every required role has a current decision; otherwise it is preliminary.

RR-E1

Rule: “Passed” without evidence (text, a link, a CI log or a completed tool section) is “unverified”.

RR-E2

Rule: “Passed”, but the pasted CI log shows failures (failed jobs, tests or step errors) — “unverified”; the evidence lines are shown.

RR-E3

Rule: “Not applicable” on a blocking or required check without a reason — “unverified”.

RR-E4

Rule: Hint: “link” evidence should contain an http(s) address. Does not affect the verdict.

RR-X1

Rule: An exception is valid only with a reason, mitigation, approver and expiry date, and only until it expires (expiry ≥ today). An invalid exception counts as “failed”.

RR-F1

Rule: Completed “Rollback plan” and “Monitoring” sections serve as evidence for RR-14, RR-16, RR-17, RR-18 and RR-19. A person still sets the status.

RR-V1

Rule: NO-GO: a blocking check failed without a valid exception.

RR-V2

Rule: NO-GO: a required role rejected the release (the role's latest decision).

RR-V3

Rule: “Insufficient data”: the release name or type is missing, or blocking checks are not checked or unverified.

RR-V4

Rule: GO with exceptions: blocking checks passed or have exceptions, but there are exceptions or unverified required checks.

RR-V5

Rule: GO: every blocking and required check passed with evidence (or is justifiably not applicable), with no exceptions.

RR-S1

Rule: Required sign-off roles depend on the release type and flags (table below).

RR-S2

Rule: A sign-off becomes stale if the release data (checks, evidence, exceptions, rollback plan, monitoring) changed after it.

RR-S3

Rule: The verdict is final only when every required role has a current decision; otherwise it is preliminary.

Evidence, exception, verdict and sign-off rules

Release type or flag	Who signs off
Hotfix	Tech lead
Minor release	Tech lead, QA
Major release	Tech lead, QA, Product owner
First launch	Tech lead, QA, Product owner
+ Changes personal or payment data handling	Data protection owner
+ Changes infrastructure (servers, network, configuration)	DevOps / SRE

Hotfix

Who signs off: Tech lead

Minor release

Who signs off: Tech lead, QA

Major release

Who signs off: Tech lead, QA, Product owner

First launch

Who signs off: Tech lead, QA, Product owner

+ Changes personal or payment data handling

Who signs off: Data protection owner

+ Changes infrastructure (servers, network, configuration)

Who signs off: DevOps / SRE

Required sign-off roles (RR-S1)

Check matrix

A check's level comes from the release type; flags can only raise it. Teams add their own checks with a chosen level and save them as a template for the next releases.

ID	Check	Hotfix	Minor release	Major release	First launch	Flags raise to
RR-01	Build and CI are green on the release commit (Code and CI)	blocking	blocking	blocking	blocking	—
RR-02	Release content is fixed: a tag or branch and a change list (Code and CI)	required	required	required	required	—
RR-03	All changes passed code review (Code and CI)	required	required	blocking	blocking	—
RR-04	Static analysis and linter show no new errors (Code and CI)	recommended	required	required	required	—
RR-05	Automated tests (unit and integration) passed (Tests)	blocking	blocking	blocking	blocking	—
RR-06	Smoke and E2E tests of critical flows passed on staging (Tests)	required	required	blocking	blocking	—
RR-07	QA checked regression in affected areas (Tests)	recommended	required	required	required	—
RR-08	The fix was verified against the original failure scenario (Tests)	blocking	recommended	recommended	not applicable	—
RR-09	The migration was run on a copy of production data (Database and migrations)	not applicable	not applicable	not applicable	not applicable	Has database migrations → blocking
RR-10	The migration is compatible with the current code (expand/contract) or downtime is agreed (Database and migrations)	not applicable	not applicable	not applicable	not applicable	Has database migrations → required
RR-11	Locks and duration of migrating large tables were assessed (Database and migrations)	not applicable	not applicable	not applicable	not applicable	Has database migrations → required
RR-12	A fresh backup was taken before the release (Backups)	recommended	recommended	required	required	Has database migrations → blocking; Changes personal or payment data handling → required
RR-13	Restoring from the backup was tested (Backups)	not applicable	recommended	recommended	required	Has database migrations → blocking
RR-14	A rollback plan exists: triggers, steps, owner, time (Rollback plan)	required	required	blocking	blocking	Has database migrations → blocking
RR-15	Rollback was rehearsed or the previous version is ready to deploy (Rollback plan)	required	required	required	required	—
RR-16	There is a data rollback plan (down migration or restore) (Rollback plan)	not applicable	not applicable	not applicable	not applicable	Has database migrations → required
RR-17	Key metric dashboards are ready (errors, latency, a business metric) (Monitoring and alerts)	required	required	blocking	blocking	—
RR-18	Error and availability alerts are set up and tested (Monitoring and alerts)	required	required	required	blocking	—
RR-19	Someone is assigned to watch the release, and for how long (Monitoring and alerts)	required	required	blocking	blocking	—
RR-20	Error tracking and logs are wired up for the new version (Monitoring and alerts)	recommended	required	required	required	—
RR-21	No secrets in code or artifacts; environment variables are configured (Security)	required	required	blocking	blocking	—
RR-22	Dependencies were scanned for known vulnerabilities (no critical ones) (Security)	recommended	required	required	blocking	—
RR-23	Access control for new endpoints and roles was checked (Security)	recommended	recommended	required	required	Changes personal or payment data handling → blocking
RR-24	Network rules and infrastructure access follow least privilege (Security)	not applicable	not applicable	not applicable	not applicable	Changes infrastructure (servers, network, configuration) → required
RR-25	Performance of changed critical paths was checked (Performance)	recommended	recommended	required	required	—
RR-26	Resource limits and scaling were checked (Performance)	recommended	recommended	recommended	required	Changes infrastructure (servers, network, configuration) → required
RR-27	Release notes or a changelog are ready (Docs and communication)	recommended	required	required	required	—
RR-28	Support and stakeholders were notified (Docs and communication)	recommended	recommended	required	required	—
RR-29	The release window is agreed and owners are reachable (Docs and communication)	recommended	required	required	required	—
RR-30	Operational runbooks are updated (Docs and communication)	not applicable	recommended	recommended	required	Changes infrastructure (servers, network, configuration) → required
RR-31	New feature flags default to off, with a kill switch (Flags and staged rollout)	not applicable	not applicable	not applicable	not applicable	Feature flags are used → required
RR-32	A staged rollout plan with expansion criteria (Flags and staged rollout)	not applicable	recommended	required	required	Feature flags are used → required; Mobile app store release → required
RR-33	The build passed store review; phased release is configured (Flags and staged rollout)	not applicable	not applicable	not applicable	not applicable	Mobile app store release → blocking
RR-34	The API stays compatible with older clients (Flags and staged rollout)	recommended	recommended	required	required	Mobile app store release → required
RR-35	Personal data handling follows the policy (consent, retention, access) (Data and compliance)	not applicable	not applicable	not applicable	not applicable	Changes personal or payment data handling → blocking
RR-36	Payment flows (charge, refund) were tested in the provider's sandbox (Data and compliance)	not applicable	not applicable	not applicable	not applicable	Changes personal or payment data handling → required
RR-37	Access to sensitive data is logged (Data and compliance)	not applicable	not applicable	not applicable	not applicable	Changes personal or payment data handling → required

RR-01

Check: Build and CI are green on the release commit (Code and CI)
Hotfix: blocking
Minor release: blocking
Major release: blocking
First launch: blocking
Flags raise to: —

RR-02

Check: Release content is fixed: a tag or branch and a change list (Code and CI)
Hotfix: required
Minor release: required
Major release: required
First launch: required
Flags raise to: —

RR-03

Check: All changes passed code review (Code and CI)
Hotfix: required
Minor release: required
Major release: blocking
First launch: blocking
Flags raise to: —

RR-04

Check: Static analysis and linter show no new errors (Code and CI)
Hotfix: recommended
Minor release: required
Major release: required
First launch: required
Flags raise to: —

RR-05

Check: Automated tests (unit and integration) passed (Tests)
Hotfix: blocking
Minor release: blocking
Major release: blocking
First launch: blocking
Flags raise to: —

RR-06

Check: Smoke and E2E tests of critical flows passed on staging (Tests)
Hotfix: required
Minor release: required
Major release: blocking
First launch: blocking
Flags raise to: —

RR-07

Check: QA checked regression in affected areas (Tests)
Hotfix: recommended
Minor release: required
Major release: required
First launch: required
Flags raise to: —

RR-08

Check: The fix was verified against the original failure scenario (Tests)
Hotfix: blocking
Minor release: recommended
Major release: recommended
First launch: not applicable
Flags raise to: —

RR-09

Check: The migration was run on a copy of production data (Database and migrations)
Hotfix: not applicable
Minor release: not applicable
Major release: not applicable
First launch: not applicable
Flags raise to: Has database migrations → blocking

RR-10

Check: The migration is compatible with the current code (expand/contract) or downtime is agreed (Database and migrations)
Hotfix: not applicable
Minor release: not applicable
Major release: not applicable
First launch: not applicable
Flags raise to: Has database migrations → required

RR-11

Check: Locks and duration of migrating large tables were assessed (Database and migrations)
Hotfix: not applicable
Minor release: not applicable
Major release: not applicable
First launch: not applicable
Flags raise to: Has database migrations → required

RR-12

Check: A fresh backup was taken before the release (Backups)
Hotfix: recommended
Minor release: recommended
Major release: required
First launch: required
Flags raise to: Has database migrations → blocking; Changes personal or payment data handling → required

RR-13

Check: Restoring from the backup was tested (Backups)
Hotfix: not applicable
Minor release: recommended
Major release: recommended
First launch: required
Flags raise to: Has database migrations → blocking

RR-14

Check: A rollback plan exists: triggers, steps, owner, time (Rollback plan)
Hotfix: required
Minor release: required
Major release: blocking
First launch: blocking
Flags raise to: Has database migrations → blocking

RR-15

Check: Rollback was rehearsed or the previous version is ready to deploy (Rollback plan)
Hotfix: required
Minor release: required
Major release: required
First launch: required
Flags raise to: —

RR-16

Check: There is a data rollback plan (down migration or restore) (Rollback plan)
Hotfix: not applicable
Minor release: not applicable
Major release: not applicable
First launch: not applicable
Flags raise to: Has database migrations → required

RR-17

Check: Key metric dashboards are ready (errors, latency, a business metric) (Monitoring and alerts)
Hotfix: required
Minor release: required
Major release: blocking
First launch: blocking
Flags raise to: —

RR-18

Check: Error and availability alerts are set up and tested (Monitoring and alerts)
Hotfix: required
Minor release: required
Major release: required
First launch: blocking
Flags raise to: —

RR-19

Check: Someone is assigned to watch the release, and for how long (Monitoring and alerts)
Hotfix: required
Minor release: required
Major release: blocking
First launch: blocking
Flags raise to: —

RR-20

Check: Error tracking and logs are wired up for the new version (Monitoring and alerts)
Hotfix: recommended
Minor release: required
Major release: required
First launch: required
Flags raise to: —

RR-21

Check: No secrets in code or artifacts; environment variables are configured (Security)
Hotfix: required
Minor release: required
Major release: blocking
First launch: blocking
Flags raise to: —

RR-22

Check: Dependencies were scanned for known vulnerabilities (no critical ones) (Security)
Hotfix: recommended
Minor release: required
Major release: required
First launch: blocking
Flags raise to: —

RR-23

Check: Access control for new endpoints and roles was checked (Security)
Hotfix: recommended
Minor release: recommended
Major release: required
First launch: required
Flags raise to: Changes personal or payment data handling → blocking

RR-24

Check: Network rules and infrastructure access follow least privilege (Security)
Hotfix: not applicable
Minor release: not applicable
Major release: not applicable
First launch: not applicable
Flags raise to: Changes infrastructure (servers, network, configuration) → required

RR-25

Check: Performance of changed critical paths was checked (Performance)
Hotfix: recommended
Minor release: recommended
Major release: required
First launch: required
Flags raise to: —

RR-26

Check: Resource limits and scaling were checked (Performance)
Hotfix: recommended
Minor release: recommended
Major release: recommended
First launch: required
Flags raise to: Changes infrastructure (servers, network, configuration) → required

RR-27

Check: Release notes or a changelog are ready (Docs and communication)
Hotfix: recommended
Minor release: required
Major release: required
First launch: required
Flags raise to: —

RR-28

Check: Support and stakeholders were notified (Docs and communication)
Hotfix: recommended
Minor release: recommended
Major release: required
First launch: required
Flags raise to: —

RR-29

Check: The release window is agreed and owners are reachable (Docs and communication)
Hotfix: recommended
Minor release: required
Major release: required
First launch: required
Flags raise to: —

RR-30

Check: Operational runbooks are updated (Docs and communication)
Hotfix: not applicable
Minor release: recommended
Major release: recommended
First launch: required
Flags raise to: Changes infrastructure (servers, network, configuration) → required

RR-31

Check: New feature flags default to off, with a kill switch (Flags and staged rollout)
Hotfix: not applicable
Minor release: not applicable
Major release: not applicable
First launch: not applicable
Flags raise to: Feature flags are used → required

RR-32

Check: A staged rollout plan with expansion criteria (Flags and staged rollout)
Hotfix: not applicable
Minor release: recommended
Major release: required
First launch: required
Flags raise to: Feature flags are used → required; Mobile app store release → required

RR-33

Check: The build passed store review; phased release is configured (Flags and staged rollout)
Hotfix: not applicable
Minor release: not applicable
Major release: not applicable
First launch: not applicable
Flags raise to: Mobile app store release → blocking

RR-34

Check: The API stays compatible with older clients (Flags and staged rollout)
Hotfix: recommended
Minor release: recommended
Major release: required
First launch: required
Flags raise to: Mobile app store release → required

RR-35

Check: Personal data handling follows the policy (consent, retention, access) (Data and compliance)
Hotfix: not applicable
Minor release: not applicable
Major release: not applicable
First launch: not applicable
Flags raise to: Changes personal or payment data handling → blocking

RR-36

Check: Payment flows (charge, refund) were tested in the provider's sandbox (Data and compliance)
Hotfix: not applicable
Minor release: not applicable
Major release: not applicable
First launch: not applicable
Flags raise to: Changes personal or payment data handling → required

RR-37

Check: Access to sensitive data is logged (Data and compliance)
Hotfix: not applicable
Minor release: not applicable
Major release: not applicable
First launch: not applicable
Flags raise to: Changes personal or payment data handling → required

Check matrix v1.0, 2026-10-13: level by release type

Limitations

The tool checks the completeness and consistency of evidence, not the systems themselves: a link to a green CI run is not opened or verified.
CI output parsing recognises common formats; if a format is not recognised, the output stays as text evidence.
Sign-off records names and decisions as entered — it is not an electronic signature and does not replace your company's approval procedure.
The matrix is a sensible minimum for web and mobile products, not an industry standard: regulated industries add their requirements as custom checks.
Data lives in one browser; collaboration works through JSON export and import.

Privacy

The release, evidence, names and decisions are stored only in this browser's localStorage and are not sent to a server on their own. “Clear everything” deletes them together with versions.
The result reaches us only if you send a request yourself and keep the “Attach the result” box ticked — the form shows exactly what will be sent. The summary holds the release name and version, type, verdict, blockers, exceptions and sign-off by role; links, evidence, notes and names are never included.
Before export, the tool warns if the evidence looks like it contains keys or passwords from pasted CI output.
Analytics receives only the verdict (a category) and the export format — no names, people or evidence.

Related tools

All tools · 40

Screenshot → Bug reportA screenshot or video → private data hidden, the problem marked up, reproduction steps, a human check and export to GitHub, GitLab or Jira.

User flow testerA user-flow builder → ready Playwright tests guarded against running on production, coverage of key routes and a pass/fail results view.

API Mock StudioImport OpenAPI or define endpoints → test data, different HTTP responses, delays and errors, a request log, contract checks and a ready mock server.

UI consistency checkerDesign tokens vs CSS: off-system colours and sizes, WCAG contrast, screenshot comparison against an approved baseline, and triage.

MVP validation toolkitHypotheses with thresholds, a landing page and lead form, UTM links, a funnel, interviews and an experiment report → continue, pivot or stop.

Proposal builderProposal templates for IT projects: scope, phases, estimate, timeline, assumptions and exclusions, versions with number control, approval and PDF.

Tell us about your task — we'll review your request and get back to you

Want an independent look before you ship?

A code and release process audit: we review CI, migrations, rollback and monitoring on your project and give you a prioritised risk list. The first short conversation about the format is free.

The first short conversation is free — we choose the format
NDA — yours or ours
Pricing after a brief and an agreed scope

Message on WhatsApp