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

Lesson 5 of 5

Preparing plan-to-produce sign-off

10 min

Listen to this lesson

0:00 / 6:13

Sign-off is a decision by accountable people that the process is fit to run the business, with known and accepted risks. For Contoso the plant manager signs as plan-to-produce process owner, Dan signs for the costing steps, and the quality lead signs for the inspection steps. Priya prepares the package and chairs the review; she does not sign for the business.

What goes in the package

SectionContentContoso example
Scope and coverageScenarios traced to scope items and variants; out-of-scope list with reasonsBJ5, BEI and BJN steps plus PTP-01 to PTP-09; repetitive manufacturing out of scope (not used)
ResultsPlanned, run, passed, failed, blocked, by risk46 planned, 46 run, 43 passed, 3 failed and retested
Evidence indexWhere each test's document chain livesTest records in SAP Cloud ALM with linked evidence
Open defectsSeverity, workaround, owner, target dateNo Critical or High; 2 Medium, 4 Low
Accepted risksRisk, mitigation, owner, expiryRework orders need a manual component until release 2
ReconciliationsStock and values after the cycleFinished and component stock value to G/L; order balances zero after settlement
SignaturesName, role, date, conditionsPlant manager, Dan, quality lead

Contents of the plan-to-produce sign-off package. Counts are illustrative.

SignaturesPlant manager (process owner), Dan (costing), quality lead (inspection)
Accepted risksEach with mitigation, owner and expiry date
ReconciliationsStock quantities and values; order balances after settlement
Defect statusOpen defects by severity with workarounds
Results and evidenceExecuted tests with document chains
CoverageScope items, variants and integration steps
The package is built bottom-up: no signature without the layers beneath it.
The Sign-Off Table · thesignofftable.com/academy/sap-pp-303

Exit criteria

Agree exit criteria at the start of the test phase, not the week before the review. Contoso's plan-to-produce criteria: every High-risk scenario executed and passed with evidence; no open Critical or High defects without an accepted, documented workaround; planning results for the October cycle match the expected tables; stock values and order balances reconciled after period-end; and every accepted risk with an owner and expiry. If a criterion is missed, the package says so plainly and the signatories decide.

  1. Week −3Exit criteria checkPriya reports status against each criterion
  2. Week −2Retests and reconciliationFixed defects retested; Dan reconciles values
  3. Week −1Package sentSignatories receive it two days before the review
  4. ReviewDecisionSign, sign with conditions, or not yet
  5. AfterArchiveSigned package kept with the evidence for audit and hypercare
The run-up to plan-to-produce sign-off.
The Sign-Off Table · thesignofftable.com/academy/sap-pp-303

Recording accepted risks

An accepted risk is a known gap the business chooses to live with for a limited time. Write it so someone who was not in the room understands it a year later: what the gap is, what could go wrong, how it is mitigated, who owns it and when it expires. "Rework is a bit manual" is not an accepted risk. "Rework orders for CMC-ALT-100 need the replacement rotor added manually; risk of missing component cost on about 15 orders a month; mitigation: daily check by the supervisor; owner: production supervisor; expires with release 2 in Q1" is.

An accepted risk is a time-limited state with an owner, not a permanent exception: it ends with a fix or comes back for review at expiry.
The Sign-Off Table · thesignofftable.com/academy/sap-pp-303

What would you do?

The day before the review, a High defect is still open: settlement in plant 1720 Chicago posts variances to the wrong account. A fix is in test and should be ready in five days. Detroit is clean. What should Priya recommend?

Run the review as a decision meeting, not a presentation of slides. Priya walks through the exit criteria one by one, shows the open defects and accepted risks, and asks each signatory for a decision on their part: sign, sign with conditions, or not yet. Conditions are written down with an owner and a date before the meeting closes. Keep the signed package with the test evidence. Luis uses it for the cutover go/no-go, the hypercare team uses the accepted risks as a watch list, and the next release's regression tests start from the same scenario list.

In the review each signatory decides on their own part, and a conditional signature only counts with a written owner and date.
The Sign-Off Table · thesignofftable.com/academy/sap-pp-303

After go-live, plan-to-produce sign-off becomes a release sign-off. For every SAP S/4HANA feature pack or significant change, Priya's team reruns the High-risk scenarios (PTP-01 to PTP-04 at least) in CMR, Contoso's pre-production system, compares MRP proposals and order values with the expected results kept from the conversion, and the plant manager signs a short release decision in SAP Cloud ALM.

Key points
  • Business owners sign; the test lead prepares and presents.
  • The package holds coverage, results, evidence, defects, reconciliations and accepted risks.
  • Exit criteria are agreed at the start and reported plainly at the end.
  • Accepted risks have a description, mitigation, owner and expiry.

Check your understanding · not graded

Lesson check

  1. 1. Who signs the costing part of Contoso's plan-to-produce sign-off?

  2. 2. When should exit criteria be agreed?

  3. 3. Which accepted-risk entry is usable?

  4. 4. A High defect is open in one plant only, with a fix in test. What is a sound recommendation?