Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 2 of 7

Roles and decision rights

8 min

Listen to this lesson

0:00 / 14:55

A sign-off framework fails most often not on templates but on ambiguity about who decides. "The business signs off" does not name anyone. The design task in this lesson is to name the roles, say what each one attests, recommends or accepts, and make the decision rights explicit enough that nobody has to ask in the gate meeting.

Three verbs

Use three different verbs and never mix them up. To attest is to confirm a fact you are responsible for: "the tests in this plan were executed as written and the evidence is complete" (test lead) or "the system is technically ready" (Basis lead). To recommend is to give an informed opinion: "order to cash is ready" (key user). To accept is to make the decision and own its consequences: "we will run order to cash on this system" (process owner).

  1. Testers executeKey users and testers run cases and record results and evidence
  2. Test lead attestsPlan executed, evidence complete, defects logged and current
  3. Key user recommendsProcess works for daily business, with any concerns stated
  4. Process owner acceptsAccepts the process for go-live, with listed exceptions
  5. Steering decidesGo/no-go across all acceptances and residual risks
From execution to decision. Each step adds a different kind of statement.
The Sign-Off Table · thesignofftable.com/academy/sap-xpr-401

The Contoso RACI

DecisionResponsibleAccountableConsultedInformed
Test strategy and evidence standardPriya (test lead)Grace (PMO)Process owners, DanSteering committee
UAT acceptance, order to cashMaria (key user)O2C process ownerPriya, financeGrace
UAT acceptance, procure to payPurchasing key userP2P process ownerAna (AP), PriyaGrace
Financial data acceptanceMigration lead, finance teamDan with the controllerInternal auditSteering committee
Technical readinessSam (Basis)IT directorKenji (ABAP), integration leadGrace
Cutover readinessLuis (cutover)GraceAll track leadsSteering committee
Go/no-goGrace preparesSteering committee chairAll accountable ownersWhole program

A RACI for Contoso's sign-off decisions. Exactly one accountable role per decision.

Two rules keep a RACI honest. First, one accountable role per decision; joint accountability means nobody is accountable. Second, the accountable role must have the authority the decision needs. A process owner who cannot stop a go-live is not accountable for process acceptance; they are consulted.

Decision rights for open defects

The most contested decision in any program is whether a known defect may go live. Write the rights down before the first test cycle, by severity and by area.

Process owner may acceptLow impact with a good workaround: accepted by the process owner with a fix date
Steering with process ownerHigh impact but a tested workaround: steering decides on the process owner's recommendation
Process owner, short expiryLow impact, poor workaround: accepted with a short expiry and close monitoring
Blocks go-liveHigh impact and no reliable workaround: cannot be risk-accepted
Who may accept an open defect depends on impact and workaround. Contoso's matrix; adapt to your program.
The Sign-Off Table · thesignofftable.com/academy/sap-xpr-401
SeverityDefinition at ContosoMay be accepted by
CriticalStops a business process, posts wrong financial values, breaks a legal or control requirement, no workaroundNot acceptable for go-live
HighMajor function fails; workaround exists but is costly or riskySteering committee, on the process owner's recommendation
MediumFunction impaired; reasonable workaroundProcess owner
LowCosmetic or minor inconvenienceKey user, recorded in the log

Severity definitions and acceptance rights. Financial misstatement is always critical.

A named deputy keeps a gate moving, but only within the same authority limits, and every deputy decision is recorded.
The Sign-Off Table · thesignofftable.com/academy/sap-xpr-401

What would you do?

Maria finds that the credit block for Great Lakes Fleet Services does not trigger on orders above the limit. There is a manual workaround: the credit team reviews a daily report. The O2C process owner wants to accept it himself to keep the gate green. Under Contoso's rules, what happens?

DecisionAccountableConsultedInformed
UAT acceptance, order to cashO2C process owner (Maria attests as key user)Priya (test lead)Grace
Finance reconciliations at go/no-go 2DanLuisGrace's decision group
Accept a medium defect for go-liveOwning process ownerPriya, fix ownerPMO
Go/no-go 1 and 2Grace's decision groupLuis, Sam, DanAll workstreams

Four Contoso decisions and their single accountable role.

Key points
  • Separate attest (facts), recommend (opinion) and accept (decision).
  • Use a RACI with exactly one accountable role per decision, holding real authority.
  • Set decision rights for open defects by severity and workaround before testing starts.
  • Name deputies with the same limits and record when they act.

Check your understanding · not graded

Lesson check

  1. 1. What does the test lead attest at a gate?

  2. 2. Why should each decision have exactly one accountable role?

  3. 3. Under Contoso's rules, who may accept a medium-severity defect?

  4. 4. Who is accountable for the finance reconciliations at go/no-go 2?