RISE board approvals and how to navigate them.

The RISE with SAP decision rarely closes without a board approval. The contract value, the strategic implications, the multi year commitment, and the operational footprint of the conversion put the decision above the routine procurement authority of even the largest organisations. The board approval moment is the final structural test of the negotiation, and the work that the negotiation team does in the weeks leading up to it determines whether the approval is a confident yes, a conditional yes with material modifications, or a deferred decision that puts the contract at risk. The work in this article is to document the structure of the board approval process for a RISE contract, the materials that produce confident board approvals, and the patterns that produce difficult board conversations.

Why the board cares about RISE

The board cares about RISE for four reasons. The first reason is the contract value. RISE contracts at enterprise scale routinely run between ten and one hundred million in total contract value, which sits at the upper end of board approval thresholds for procurement decisions. The contract value alone usually requires board sign off, regardless of the strategic merits.

The second reason is the commitment horizon. RISE contracts run five to seven years, which is longer than most other commercial commitments the board reviews. The horizon creates a strategic commitment that affects the organisation across multiple planning cycles, multiple budget periods, and potentially multiple management generations. The board takes that horizon seriously because the consequences of the decision extend beyond the tenure of any single executive.

The third reason is the operational dependency. RISE moves the SAP estate from buyer controlled infrastructure to a SaaS delivery model. The operational dependency on SAP, on the chosen hyperscaler, and on the BTP integration platform becomes structural rather than incidental. The board reviews the dependency to understand the risk it represents and the mitigation arrangements in place.

The fourth reason is the optionality cost. RISE forecloses certain alternative paths that the board may have considered viable, including continued brownfield S/4HANA on the buyer's own infrastructure, multi vendor ERP strategies, or selective adoption of competing cloud ERP products. The board examines the optionality the contract removes and whether the value delivered by RISE justifies that removal.

The board paper that gets the approval

The board paper that produces a confident RISE approval runs to twelve to eighteen pages and covers six sections. The structure of the paper is observable across the engagements documented at the firm, and the structure matters because the board reads against an expected sequence.

The first section is the executive summary. The summary is one page and addresses the decision being asked of the board, the recommendation, the total contract value, the key terms, and the expected outcome. The summary is written for board members who will read only the summary, and it must stand on its own without the rest of the paper. A board paper with a weak executive summary will receive a difficult reading of the body, regardless of the body's quality.

The second section is the strategic context. The section explains why the organisation is considering RISE at this time, what business pressures or opportunities are driving the decision, and how the RISE conversion fits into the broader strategic plan. The strategic context establishes that the decision is rooted in business need rather than in vendor sales pressure or in technology preference.

The third section is the alternatives analysis. The board needs to see that the team considered alternatives and rejected them for substantive reasons. The alternatives analysis covers brownfield S/4HANA on a buyer chosen hyperscaler, the continuation of the existing ECC estate under extended maintenance, the consideration of competing ERP products, and any hybrid model under evaluation. Each alternative is presented with its financial profile, its operational profile, and the specific reasons it was not selected.

The fourth section is the commercial terms. The section walks through the contract value, the term, the bundled components, the discount achieved, the uplift mechanism, the exit provisions, and the comparison to industry benchmarks. The commercial section is the most detailed section in the paper because the board will examine the negotiated terms more closely than any other element.

The fifth section is the risk and mitigation. The section identifies the operational, commercial, financial, and reputational risks the contract creates, and documents the mitigation in place for each. The risk section is where the negotiation team demonstrates that the deal has been pressure tested against adverse scenarios.

The sixth section is the implementation plan. The section confirms how the contract will be executed, who is accountable for the conversion, what the timeline looks like, and where the board will receive updates. The implementation section signals that the approval is not the end of the work, and that the board has visibility into the execution that follows.

The questions the board will ask

Boards ask predictable questions about RISE contracts. The negotiation team that prepares answers to the predictable questions enters the approval meeting with the confidence the questions reward. Six questions appear in almost every RISE board approval.

The first question is whether the price is benchmarked against comparable deals. The board wants to see that the negotiated terms compare favourably to what similar organisations have achieved. The benchmark data needs to be present in the board paper, sourced credibly, and presented at the same level of detail as the contract terms.

The second question is what the alternative path costs. The board wants the alternative analysis to be specific. A statement that brownfield is more expensive without a defended number is not enough. The board expects the alternative numbers to be available and to be presented with the same analytical depth as the RISE numbers.

The third question is what happens at renewal. The board recognises that renewal is the next major commercial event in the SAP relationship and asks how the organisation will be positioned for that conversation. The answer addresses the renewal preparation discipline, the alternative paths that will be maintained, and the contractual provisions that protect the buyer at renewal.

The fourth question is what happens if the conversion is harder than expected. The board has seen ERP conversions overrun before and wants to understand the operational risk and the contractual protections. The answer addresses the implementation methodology, the partner selection, the governance, and the contractual remedies if the conversion misses milestones.

The fifth question is what the exit looks like. The board wants to know that the organisation has a defined path to leave RISE if the relationship deteriorates or if the strategy changes. The answer addresses the exit clauses, the transition assistance commitments, the data extraction terms, and the operational handover provisions.

The sixth question is who has reviewed the contract. The board wants to know that the legal review, the procurement review, the finance review, and the architectural review have all been completed by appropriate parties, including any independent advisors the organisation has engaged. The answer documents the reviewers and the dates of their sign off.

The board pre read and the board chair conversation

The board paper is one part of the approval process. The pre read briefing and the board chair conversation are the other parts, and they often matter as much as the paper itself. The pre read briefing is a one to one or small group conversation with each board member before the formal meeting. The conversation walks the board member through the recommendation, addresses any concerns specific to that member, and confirms that the member has the information needed to participate constructively in the formal discussion.

The pre read briefing is the moment to identify board concerns that are not visible from the paper alone. A board member with a specific concern about data sovereignty, about the chosen hyperscaler, about the exit provisions, or about the implementation partner can raise the concern in the pre read where it can be addressed before the formal meeting. The same concern raised for the first time in the formal meeting often produces a deferred decision because the team cannot resolve it in the room.

The board chair conversation is a more strategic exchange. The chair carries the responsibility for the board process and for the quality of the discussion in the room. A conversation with the chair before the meeting confirms the agenda, the expected discussion areas, the time allocated, and the decision protocol. The conversation also gives the chair the context to lead the discussion productively rather than reactively.

What a deferred decision looks like and how to avoid it

A deferred board decision is the worst outcome of the approval process. The deferral does not reject the deal, but it puts the deal at risk. The SAP team reads the deferral as buyer hesitation and adjusts its commercial position accordingly. The internal coalition that supported the deal frequently fragments during the deferral period. The alternative paths that were available at the negotiation moment may have moved on by the time the deferred decision returns to the board.

Deferrals usually have one of three causes. The first cause is incomplete analysis, where the board paper did not cover an area the board considered important. The second cause is unresolved internal stakeholder concerns that surface in the meeting. The third cause is timing concerns, where the board questions whether the moment is right for the commitment. Each cause is preventable through preparation. The preparation discipline that prevents deferrals includes a board paper that covers every expected area, a pre read briefing that surfaces stakeholder concerns before the meeting, and a chair conversation that frames the timing question explicitly.

Conclusion: the board approval is part of the negotiation

The board approval is part of the negotiation, not a separate event. The materials that the board reviews, the conversations that prepare each member, and the decision that the board takes all sit inside the broader negotiation arc. The negotiation team that treats the board approval as the final test of the work, rather than as an administrative formality, produces approvals that are confident, decisions that hold across the implementation, and contracts that the organisation defends rather than regrets. The board paper, the pre read, and the chair conversation each carry the work of the negotiation into the room where the decision is made. The discipline of that work is the discipline that runs across the entire engagement.