Can we launch with known defects?
Uncontrolled residual quality exposureA release decision depends on defect impact, applicable obligations, workarounds, and authorized acceptance. Do not treat a defect count or sponsor enthusiasm as sufficient evidence of readiness.
What to do now
- List remaining defects and consequences
- Confirm safe usable workarounds where applicable
- Obtain the proper risk and release decisions
- Assign correction owners and follow-up dates
When to escalate
Escalate when
A defect breaches mandatory requirements or cannot be safely accepted.
Who decides
The acceptance authority and relevant quality owner
Example
A minor display defect may be accepted while a transaction-reconciliation failure blocks release.
Mistake to avoid
Assuming all low-count defect lists are acceptable.
Prevent a repeat
Check that closure evidence proves the agreed outcome instead of relying only on a completion percentage.
Suggested ApprovedFlow setup
- Tasks
- Documents
- Approvals
Attach acceptance criteria and test evidence to the deliverable or task, then record the authorized review decision. See the platform
Related cases
- How do we measure quality without counting defects alone?Narrow quality metrics
- Quality reviews find the same defects repeatedly. How do we improve prevention?Repeated defect causes
- We are closing with residual risks. What must be transferred?Unowned residual risk exposure
- We still have open actions at closure. Must every action be finished first?Uncontrolled residual work transfer