Lesson 5 of 6
Conditional sign-off and risk acceptance
8 min
Listen to this lesson
Real programs rarely reach every exit criterion cleanly. A few defects remain, a scenario could not be tested because a partner system was late, a report is still being finished. The choice is not only between signing and refusing. A conditional sign-off accepts the phase on the record, subject to stated conditions that must be met by stated dates, with owners. Done well, it keeps the program moving while keeping every open risk visible.
Full versus conditional
| Full sign-off | Conditional sign-off | |
|---|---|---|
| Exit criteria | All met | Some not met, each with a decision |
| Open items | None that affect acceptance | Listed as conditions with owners and dates |
| Risk | Residual risk within agreed limits | Specific risks explicitly accepted by named owners |
| Follow-up | None required for this phase | Conditions tracked to closure; reviewed at the next gate |
| If conditions slip | Not applicable | Escalate; the sign-off may lapse or the go-live decision may change |
Full and conditional sign-off compared.
What makes a condition real
- Specific: "Fix defect 233 (tax on Chicago shipments) and retest scenarios O2C-CHI-01 to 03", not "resolve remaining tax issues".
- Owned: one named person is accountable for closing it.
- Dated: a due date that makes sense against the next gate or go-live.
- Verifiable: what evidence will show it is done, such as a passed retest run.
- With a fallback: what happens if it is not met, such as a workaround in production, a delayed go-live for that plant, or escalation to the steering committee.
- Is it specific?Yes → next · No → name the defect and scenarios, such as defect 233 and O2C-CHI-01 to 03
- Is one person accountable?Yes → next · No → name an owner, not a team
- Is there a due date before the next gate or go-live?Yes → next · No → set one that fits the plan
- Is the closing evidence defined?Yes → next · No → state it, such as a passed retest run
- Is there a fallback if it slips?Yes → the condition is real · No → agree a workaround, delay or escalation
Workarounds
Many conditions rely on a workaround: a temporary way of achieving the business result despite the defect. Before a workaround supports a sign-off, check that it is documented, that the people who will use it are trained, that it works at real volumes, and that it does not weaken a control. A manual tax adjustment for a handful of Chicago invoices might be acceptable for two weeks; for every invoice for a quarter, it probably is not.
| Check | Acceptable workaround | Not acceptable |
|---|---|---|
| Documented | Written steps for the manual tax adjustment | Known only to the consultant who found it |
| Trained | Chicago billing clerks have practised it | Users will learn it on day one |
| Volume | A handful of Chicago invoices for two weeks | Every invoice for a quarter |
| Controls | Adjustments reviewed and approved | Bypasses tax or approval controls |
Limit how much a single sign-off can carry. A sign-off with two or three well-defined conditions is a reasonable decision. A sign-off with thirty conditions is a refusal written politely, and the people downstream should treat it that way. Some programs set a rule in their governance plan, such as no conditional sign-off with an open critical defect, or a maximum number of open high defects across all conditions, so that the line is agreed before the pressure arrives.
The risk acceptance record
When a known risk is accepted, write it down in a consistent form. A simple template is enough:
- Risk: what could go wrong, in business terms.
- Cause: the defect, untested area or unmet criterion behind it, with references.
- Impact and likelihood: who is affected, how badly, how likely.
- Mitigation and workaround: what reduces the risk until it is closed.
- Condition to close: the specific action and evidence that will remove it.
- Owner and date: who closes it, by when.
- Accepted by: the name and role of the person accepting the residual risk, and the date.
- IdentifyUnmet exit criterion or open defect found in the test summary
- AssessImpact, likelihood, workaround; can it wait?
- DecideOwner accepts, rejects, or asks for more evidence
- RecordRisk acceptance record and condition on the sign-off
- TrackConditions reviewed in triage and at the next gate until closed
- Sign-offConditions recordedDan signs finance UAT with defect 233 as a condition, owner and date
- WeeklyReviewed in triageEach condition is closed, on track, or at risk
- Before the gateStatus confirmedClosed with evidence, open with a credible plan, or slipped
- On a slipBack to the acceptorDan decides what the new date means for the risk he accepted
- Go/no-goRemaining conditions visibleThe steering committee sees every condition still open
What would you do?
Dan is willing to sign finance UAT if defect 233 (sales tax not calculated for Chicago shipments) is fixed before go-live. How should the condition be written?
- Conditional sign-off accepts a phase subject to specific, owned, dated, verifiable conditions with a fallback.
- Full sign-off means all exit criteria are met with residual risk in agreed limits.
- Check workarounds for documentation, training, volume and control impact.
- Record each accepted risk with cause, impact, mitigation, condition, owner, date and acceptor.
- Track conditions to closure; slipped conditions go back to the risk acceptor.
Check your understanding · not graded
Lesson check
1. What distinguishes conditional from full sign-off?
2. Which is a well-formed condition?
3. A condition slips past its date. Who should decide what happens next?
4. Which check should be made before a workaround supports a sign-off?