Procurement Transformation Toolkit

Design Your
Operating Model
End to End

A complete toolkit for designing, documenting and presenting your operating model — from vision & taxonomy through to roles, risk and the roadmap.

16 Design Modules
15+ PPTX Export Types
4 Starter Templates
Customisation
Design Modules Click any module to open it
01
👁
Vision & Guiding Principles
Define your procurement vision, set word choices and establish the operating model principles.
Open →
02
🔄
Reasons for Change
Map current state challenges to future state outcomes and define the transformation themes.
Open →
03
🗂
Taxonomy
Build your 4-level process taxonomy — L1 domain through L4 sub-process activities.
Open →
05
📊
Category Scope
Map L1/L2 spend categories to procurement coverage and define the make vs buy delivery model.
Open →
05
💡
Capabilities
Map strategic, operational and enabling capabilities with current maturity levels.
Open →
06
🔁
Process Flows
Document and design the core procurement process flows from P2P to category.
Open →
07
📊
Data Requirements
Identify the data inputs and outputs across procurement activities and systems.
Open →
08
⚖️
Governance
Define decision rights, governance forums, KPI targets, MSP SLAs and the policy register.
Open →
09
🖥
IT Enablement
Map the technology landscape, system integrations and digital enablement roadmap.
Open →
10
🏢
Organisation Design
Design the structure, reporting lines and team configuration for your function.
Open →
11
👤
Roles & Responsibilities
Define each role, RACI responsibilities and capability requirements across the team.
Open →
12
👥
FTE Requirements
Size the team — model headcount requirements by role and business unit.
Open →
13
📣
Change Management
Plan stakeholder engagement, communications, training and readiness activities.
Open →
14
⚠️
Risk Register
Identify, score and mitigate the key risks to your operating model transformation.
Open →
15
🗺
Implementation Roadmap
Build the phased roadmap — workstreams, milestones and quick wins by quarter.
Open →
16
Issue Tracker
Track project issues, assign owners from the project team, and monitor resolution.
Open →
17
📋
GCC RFP
Build and export the RFP for your Global Capability Centre procurement.
Open →
All data is stored in-browser. Export a workbook backup regularly via the Dashboard. ⚙ Settings & Templates →

📊 Operating Model Dashboard

Live status across every design module. Click any card to navigate directly to that section.

Overall Completion

Sections with at least one item count as In Progress; fully configured sections count as Complete.

— Complete — In Progress — Not Started
How scoring works: Each module card shows a completion percentage based on the data entered. Vision requires a statement with 2+ words and 5+ guiding principle pairs selected. Taxonomy needs 10+ items. Category Scope needs managed % on all categories. Capabilities need current + target ratings. Process needs 5+ steps. Data needs 5+ objects. Governance counts policies + KPIs + SLAs (5+ total). IT needs 5+ systems. Org needs 5+ roles. Roles needs 3+ definitions. FTE needs current + target on all functions. Roadmap needs 3+ workstreams. Change Management needs stakeholders, comms, and training entries. Risk needs 3+ items. Issue Tracker needs 3+ issues. Decision Log needs 3+ entries. RFP needs 5+ activities. The overall ring sums complete (100%) + in-progress (50%) modules.

S2P Operating Model Workbook

Load your Operating_Model_Data.xlsx to populate all sections at once, or save all current section data back to a single workbook.

Section Load Status
Vision
Guiding Principles
Taxonomy
Category Coverage
Make vs Buy
Capabilities
Process
Data Register
Data Quality
Policy Register
Decision Rights
Gov Forums
Gov KPIs
IT Systems
IT Automation
IT Cap Map
Org Current
Org Future
R&R Roles
R&R RACI
FTE Requirements

Operating Model Canvas

Auto-generated single-page summary of your entire operating model. Each pillar pulls live data from the relevant modules. Add key messages to tell the story behind the numbers.

Cross-Module Recommendations

Contextual insights based on data patterns across all design modules.

Click Refresh to generate recommendations...

Vision & Guiding Principles

Build your vision statement, define guiding principles, and shape the ambition for your procurement operating model.

A great procurement vision statement is short, ambitious, and company-specific. Use these principles to craft one that resonates with senior stakeholders and motivates your team.

Tip 1
Keep it to one sentence
A vision statement should be memorable enough to repeat in a hallway conversation. Aim for 15–25 words. If it needs a semicolon, it’s too long.
Tip 2
Start with the outcome, not the activity
Say what Procurement delivers to the business — not what it does internally. “Trusted partner driving sustainable value” lands better than “best-in-class procurement processes.”
Tip 3
Anchor to your company’s strategic language
Use the same vocabulary your CEO uses. If the company is focused on “resilience,” “innovation,” or “sustainability,” weave that language in deliberately.
Tip 4
Make it aspirational but credible
A good vision is a stretch — it describes where you’re going, not where you are. But it must be believable. Avoid hyperbole that your own team will roll their eyes at.
Tip 5
Reflect the transformation journey
The best statements signal a shift: from transactional to strategic, from reactive to proactive, from cost-focused to value-creating. The contrast gives it energy.
Tip 6
Test with a non-procurement stakeholder
If a CFO or COO can read it and immediately understand what Procurement aspires to be, it works. If they need procurement jargon decoded, rewrite it.
Example Vision Statements
Global Manufacturer
“To be the trusted strategic partner that delivers sustainable competitive advantage through world-class supplier relationships, data-driven insights, and operational excellence across every dollar we spend.”
Financial Services Firm
“To transform procurement into a proactive business partner — protecting value, enabling innovation, and building a resilient supply chain that supports the firm’s growth ambitions.”
Consumer Goods Company
“A future-ready procurement function that sources with purpose, partners with integrity, and creates measurable impact for our customers, communities, and planet.”
Technology Company
“To deliver speed, transparency, and strategic value through a digitally enabled procurement model that empowers our teams and elevates our supplier ecosystem.”
1

Vision Statement

Select descriptive words to auto-generate your statement, then edit freely.

Rewrite with ChatGPT
Click a style to copy the prompt → paste into ChatGPT → copy ChatGPT's response → click Paste below.
🌅 Guiding Principles Define the operating model choices that will guide your procurement function

Ten principles for designing an effective set of operating model guiding principles — drawn from leading S2P transformation practice.

Tip 1
Start with the operating model ambition
Your principles should flow from where you want to be in 3–5 years, not where you are today. Use the Vision statement as the anchor.
Tip 2
Anchor each choice to a real tension
Every option on the scale represents a genuine trade-off. Don’t pick the most centralised option by default — understand what you’re giving up.
Tip 3
Use present tense to signal commitment
Write principles as “We centralise…” not “We will centralise…” Present tense signals this is already the direction of travel.
Tip 4
Make each principle independently defensible
You should be able to explain each choice in 30 seconds to a sceptical CFO. If you can’t, revisit the selection.
Tip 5
Fewer decisions made well > more decisions made poorly
You don’t need to decide everything now. Focus on the choices that will have the most downstream impact on design.
Tip 6
Test every principle against a concrete scenario
Pick a real sourcing situation and ask: would this principle lead to a better outcome? If not, revisit the wording or the choice.
Tip 7
Co-create with key stakeholders
Principles only owned by Procurement stay Procurement principles. Finance, IT, Legal, and BU leaders must shape and own them too.
Tip 8
Link each principle back to the vision
Every guiding principle should be traceable to at least one element of the vision statement. If it isn’t, question whether it belongs.
Tip 9
Write principles for the 3–5 year aspiration
Write principles for the 3–5-year aspiration, not current constraints. Use present tense (“We centralise…”) to signal leadership commitment.
Tip 10
Revisit at each transformation milestone
Principles set at the start of a transformation will need revisiting as the organisation matures. Build in an annual review cycle.
Guiding Principles
Select one option per dimension to define your operating model design choices across 23 key decisions.
0 / 23 selected
A
Strategy & Decision Rights Decentralised → Centralised
Operating model centralization
Category strategy ownership
Sourcing decision rights / thresholds
Policy strictness / compliance posture
B
People & Delivery Model Dispersed → Unified
Outsourcing level (transactional)
Role specialization
Location model
Capability emphasis
C
Process & Governance Flexible → Controlled
Process standardization
Controls / approvals
Requisition intake
Exception handling
D
Technology & Data Manual → Automated
Platform strategy
Automation ambition
Analytics maturity
Data governance
E
Supplier & Commercial Model Transactional → Strategic
Supplier rationalization
SRM depth
Contracting model
Risk posture
F
Service & Stakeholder Experience Reactive → Proactive
Procurement front door
Service levels / SLAs
Stakeholder involvement
Additional Principles

    No additional principles added yet.

    Slide 1 of 2 — Vision Statement
    Operating Model Vision

    Reasons for Change

    Define the transformation themes — mapping current state challenges to future state outcomes.

    2

    Current & Future State

    Select the transformation themes most relevant to your operating model.

    Current State
    Future State

    S2P Operating Model Workbook

    Load your Operating_Model_Data.xlsx to populate all sections at once, or save all current section data back to a single workbook.

    Section Load Status
    Vision
    Guiding Principles
    Taxonomy
    Category Coverage
    Delivery Model
    Capabilities
    Process
    Data Register
    Data Quality
    Policy Register
    Decision Rights
    Gov Forums
    Gov KPIs
    IT Systems
    IT Automation
    IT Cap Map
    Org Current
    Org Future
    R&R Roles
    R&R RACI
    FTE Requirements

    Process Taxonomy

    Build and manage your 4-level process hierarchy. Double-click any label to edit it.

    Level 1: 0 Level 2: 0 Level 3: 0 Level 4: 0

    A well-structured process taxonomy is the backbone of your operating model. It defines what Procurement does, guides role design, enables process maturity assessment, and drives continuous improvement. These principles help you build one that holds up under scrutiny.

    Tip 1
    Align to a reference framework
    Reference established frameworks like APQC PCF or SAP S/4HANA process maps before customizing. Starting from scratch without a reference creates gaps and makes benchmarking impossible.
    Tip 2
    Make processes mutually exclusive
    Each activity should belong to exactly one process. Overlapping process boundaries create confusion about ownership, handoffs, and accountability — especially in RACI assignments.
    Tip 3
    Design end-to-end, not functionally
    Organize around outcomes and flows, not org chart silos. A process like "Source to Contract" should span from need identification through award, crossing any internal functional boundaries.
    Tip 4
    Use a consistent naming convention
    Pick one style and stick to it across every level. Noun-form ("Supplier Onboarding") and verb-noun-form ("Onboard Supplier") are both valid — but never mix them within the same level of the hierarchy.
    Tip 5
    Calibrate granularity to purpose
    L4 activities should be granular enough to assign to a role and measure with a KPI, but no more granular than that. If an activity cannot be owned or measured, it belongs inside a higher-level process.
    Tip 6
    Plan for technology alignment
    Map your L3 and L4 processes to system modules (e.g., sourcing tool, P2P platform, contract repository). This makes it easier to identify automation opportunities and articulate the case for technology investment.

    A 4-level process hierarchy gives you the right balance: strategic legibility at the top and enough operational precision at the bottom to assign ownership, map to systems, and measure performance.

    Level 1 — Process Domain
    Broadest grouping
    3–6 top-level groupings that define the major end-to-end process areas of the function. These map to the CPO’s organizational agenda and appear on operating model overviews and board-level presentations.
    e.g. Strategic Sourcing, Procurement Operations, Supplier Management, Risk & Compliance
    Level 2 — Process Group
    Logical cluster
    A coherent cluster of related processes within a domain. L2 is the primary unit for scoping transformation workstreams, assigning process owners, and measuring maturity. Typically 3–6 groups per domain.
    e.g. Category Management, Sourcing Execution, Contract Management, Purchase-to-Pay
    Level 3 — Process
    Manageable unit of work
    A discrete, named process with a clear trigger, output, and owner. L3 is the primary unit for RACI assignment, SLA setting, and system mapping. Each L3 should be something a role can meaningfully “own.”
    e.g. Supplier Qualification, RFx Management, Contract Drafting, Purchase Order Processing
    Level 4 — Activity
    Most granular
    A specific task or step within a process. L4 activities are granular enough to map to a job step, a system transaction, or an individual workflow action. Use sparingly — only where the detail adds genuine design or measurement value.
    e.g. Issue RFQ, Score Supplier Responses, Obtain Legal Sign-off, Release PO to Supplier

    Taxonomy Review

    Category Scope & Delivery Model

    Define your L1/L2 spend categories, map procurement coverage to your process taxonomy, and set delivery model (Make vs Buy) for each category.

    Category Coverage Register
    Enter L1/L2 spend categories, annual spend, and map which process taxonomy L2s currently cover each category vs. what is out of scope.
    No process taxonomy loaded — build your taxonomy first to enable L2 coverage mapping.
    No categories added yet. Click + Add Category to start.
    Make vs Buy — Delivery Model
    For each spend category define the delivery model (BU, Corp, GCC or MSP) for current and target state across each process area.
    Add categories in the Coverage Register tab first — they will appear here automatically.

    Capability Assessment

    Assess capability groups and items across People, Process and Technology — with Current, Go-live and Long-term milestones. Groups show rolled-up averages.

    Capability Group Level
    Item Level (auto)
    L2
    Scale
    Dimension 1
    Dimension 2
    Dimension 3
    Markers:
    Current
    Go-live
    Long-term
    | Groups show rolled-up averages (unweighted, rounded to nearest integer)
    📋 Work Inventory H/M/L effort to close capability gaps

    📋 5b Work Inventory

    H/M/L effort required to close capability gaps, organised by dimension and phase. Override effort ratings and add notes.

    Open this panel from the sidebar to generate the work inventory from your capability data.
    1

    Load Process Data

    Upload an Excel (.xlsx) file and select the sheet that contains your process steps. The sheet should have columns: Step ID, Process Step Description, Next Step ID, Shape Type, Function, Phase, Connector Label.

    No file selected

    Data Requirements

    Define the ERP master data objects that procurement processes consume and produce. Map data to processes, assess quality, and assign governance ownership.

    Data Objects
    Good Quality
    Needs Attention
    Process Mapped
    Click any cell to cycle: — Not used → ← Input → → Output → ⇄ Both
    Score 1–5 per dimension. Current / Target. Blue bar = current, orange line = target. Gap drives remediation priority.

    IT Enablement

    Catalogue your procurement technology landscape, map systems to capabilities, identify automation opportunities, and assess data & analytics maturity.

    Systems Catalogued
    Live
    Planned / In-Flight
    Automation Opportunities
    Priority is automatically derived from Value vs Effort: High Value + Low Effort = High Priority. Use this to build your automation backlog and roadmap.

    FTE Requirements

    Model procurement staffing needs by function. Upload your current headcount, run the volume driver calculator, and compare against industry benchmarks.

    Current FTE
    Target FTE
    Benchmark Mid
    Gap (Target − Current)
    📂
    Upload Current State Headcount
    Click to upload a CSV or Excel file with columns: Function, Current_FTE (or Headcount). Optional: Level, Type.
    Volume Drivers
    Sourcing Events / Year
    Spend Under Management ($M)
    Active Suppliers
    POs Processed / Year
    Contracts Executed / Year
    Total Procurement Team Size
    Derived FTE Requirements
    Enter volume drivers on the left to calculate FTE requirements.
    Benchmark ratios used: Strategic Sourcing: 8–15 events/FTE  |  Category Mgmt: $80–150M spend/FTE  |  Supplier Mgmt: 40–80 suppliers/FTE  |  P2P: 1,500–2,500 POs/FTE  |  Contracts: 60–120 contracts/FTE  |  Analytics & Governance: 8–18% of total team

    Headcount plan by role. Roles are sourced from Roles & Responsibilities. Add roles there to populate this table.

    Role Department Current FTE Target FTE Gap Notes
    No roles defined yet. Add roles in the Roles & Responsibilities section.
    Benchmark Assumptions
    Ratios used in the Volume Calculator and FTE Model ranges. Edit to reflect your industry or peer data.
    Enter your organisation details to position against benchmarks
    Total Company Employees
    Total Managed Spend ($M)
    Annual Savings Realized ($M)

    Org Structure

    Design current and future state organizational structures. Supports BU, Corp, GCC and MSP role types (rename in Settings). Pan & zoom, grid edit view, search, collapse/expand, and Current vs Future diff mode included.

    Operating Model:
    Center of Excellence — strategic expertise hub with distributed execution
    🏛 CoE Design Best Practices
    01
    Clearly separate strategic work (CoE) from transactional execution (operations) — dual accountability leads to gaps.
    02
    CoE should be small and expert-heavy — typically 10–15% of total procurement headcount, focused on category strategy and standards.
    03
    Establish a governance forum between CoE leads and business stakeholders — a monthly steering group prevents CoE from becoming ivory-tower.
    04
    Invest in knowledge management infrastructure: category playbooks, sourcing templates, and market intelligence repositories.
    05
    CoE roles should have rotational options or clear career ladders to prevent siloing and loss of operational credibility.
    06
    Define clear RACI between CoE and operational procurement — who approves strategy, who executes sourcing events, who manages suppliers.
    📋 MSP Model Best Practices
    01
    Always retain strategic sourcing, governance, and supplier relationship management internally — these cannot be outsourced without losing strategic control.
    02
    Define SLAs and KPIs upfront: cycle time, savings delivery rate, contract compliance, and user satisfaction scores.
    03
    Build a governance cadence: weekly operational review, monthly performance scorecard, quarterly strategic review with MSP leadership.
    04
    Retained team is typically 15–25% of a fully insourced equivalent — right-size it based on strategic coverage required, not just headcount reduction.
    05
    Protect institutional knowledge: require documented category strategies, supplier portfolios, and playbooks as MSP contract deliverables.
    06
    Plan for re-insourcing risk — MSP transitions are expensive. Maintain capability documentation so you can transition back if needed.
    🔗 Hybrid Considerations
    01
    Define clear ownership handoff points between retained and MSP layers — ambiguity at the boundary creates gaps and finger-pointing.
    02
    Avoid dual accountability: each category or process should have a single owner — either retained or MSP, not both.
    03
    Governance overhead increases significantly in hybrid models — budget for a dedicated MSP Governance role and governance tooling.
    04
    Monitor for shadow procurement — business units may bypass the hybrid model entirely if it creates friction. Measure compliance rates.
    📊 Span & Layer Guidelines
    01
    Target span of control: 5–8 direct reports per manager for knowledge work procurement roles.
    02
    Maximum recommended org layers: 4 for orgs under 50, 5 for 50–150 staff, 6 for 150–300 staff.
    03
    Flat structures improve agility but require higher individual contributor capability and strong lateral coordination.
    04
    Deep hierarchies slow decision-making — audit your layer count whenever the org grows more than 30% through acquisition.
    05
    VP/Director ratios: typically 1 VP per 30–50 staff in procurement functions. Above this, consider whether spans need adjusting.
    ▶ = click to expand/collapse   Click node to edit
    100%
    vs Future state: Removed in future Title/type changed Unchanged
    Click Load Template to start from a pre-built structure, or + Add Role to build from scratch

    Roles & Responsibilities

    Define roles, build a RACI matrix against your taxonomy, create job descriptions, then export to PPTX, Excel, or Word.

    What is RACI?
    R — Responsible A — Accountable C — Consulted I — Informed
    1. R (Responsible) — does the work. A task can have more than one R, but avoid spreading ownership too thin.
    2. A (Accountable) — ultimately answerable, approves the output. There must be exactly one A per row.
    3. C (Consulted) — provides input before decisions are made. Requires two-way dialogue.
    4. I (Informed) — kept updated after decisions. One-way communication only.
    5. Every row must have at least one R and exactly one A. The A may also hold R.
    6. Minimize the number of Rs per row — diffused responsibility often means no responsibility.
    7. If a role has only I assignments throughout, question whether it belongs in the matrix.
    8. Validate the completed matrix with representatives from every role before publishing.
    9. Click any cell to cycle it: blank → R → A → C → I → blank. The colored dot on each row shows completeness.
    Best Practices: Role Names
    1. Name roles by function, not by person — the matrix should survive team changes.
    2. Pick one convention (job titles or descriptive labels) and apply it consistently throughout.
    3. Consider four natural tiers: Executive/Governance, Category/Strategic, Operational/Tactical, Business Stakeholder.
    4. If multiple people do the same job, list the role once (e.g. "Regional Buyer" covers all regional buyers).
    5. Keep names to 2–4 words. Long names break the matrix layout and reduce readability.
    6. Avoid internal acronyms that business stakeholders outside procurement may not recognize.
    7. Distinguish shared-service roles from embedded/business-unit roles to show where accountability sits.
    8. Design for future-state — use the roles you want to have, not just the ones that exist today.
    Best Practices: Role Descriptions
    1. Write from the role's perspective: "This role is responsible for…" rather than listing activities abstractly.
    2. State decision rights explicitly — what spend levels, categories, or approvals this role can authorise.
    3. Note key interfaces and handoffs: who does this role receive inputs from, and hand off to?
    4. Keep it concise — 3–5 sentences is ideal. This is a reference tool, not an HR job specification.
    5. Describe outcomes, not just activities — what does "good" look like for this role?
    6. Separate business-as-usual responsibilities from transformation activities if both apply.
    7. Align descriptions with the RACI level chosen — descriptions should reflect the granularity of the matrix rows.
    8. Review with current role holders and future-state design leaders before finalising.
    1

    Taxonomy Source & RACI Level

    The RACI rows automatically sync from your Taxonomy section whenever you open this panel. You can also click Use Current Taxonomy to refresh manually, or upload a 4-column CSV (L1, L2, L3, L4) to use a standalone taxonomy.

    No taxonomy loaded
    RACI at level:
    2

    Roles

    Define the roles, departments, and teams that participate in your procurement activities. Add each role manually, upload from CSV, or export what you have. Click Quick Check to review naming consistency and completeness.

    No roles yetClick Add Role to define the roles in your RACI matrix.
    Quick Check Results
    3

    RACI Matrix

    Click any cell to cycle through RACI values — R (Responsible), A (Accountable), C (Consulted), I (Informed) — or click again to clear. Use Analyze for quality feedback, or Preview to review slides before exporting.

    Matrix not readyLoad a taxonomy (Step 1) and add at least one role (Step 2) to generate the matrix.
    Scroll to see all roles
    RACI Analysis Results
    Total Roles
    JDs Complete
    Drafts
    Not Started

    Governance — Policy Register

    Inventory your procurement policies across 8 categories. Track which you have, which you need, and where each file lives.

    0Total
    0Have
    0Need
    0Gap
    Policy Coverage0%

    Decision Rights Matrix

    Define who Approves, Recommends, holds Veto, provides Input, or is Notified for each key procurement decision. Click any cell to cycle through values.

    Cell values: A Approve R Recommend V Veto I Input N Notify/Inform Empty = not involved  |  Click cell to cycle

    Governance Forums

    Define the governance bodies that oversee procurement — their purpose, cadence, chair, members, and standing agenda topics.

    KPI Scorecard

    Define and track the procurement metrics your function is measured against. Enter current values to see on-track / at-risk / off-track status.

    0KPIs
    0On Track
    0At Risk
    0Off Track
    0No Data

    MSP Service Level Agreements

    Define and track the service level agreements with your Managed Service Provider across key procurement activities. Set contractual targets and monitor current performance.

    0SLAs
    0Met
    0At Risk
    0Breach
    0No Data

    Change Management

    Plan and track stakeholder engagement, communications, training and adoption for your operating model transformation.

    Total Stakeholders
    High Influence
    Comms Planned
    Training Modules
    Name Department/Function Role in Transformation Influence Interest Current Sentiment Engagement Approach Owner Actions
    Audience Message Channel Frequency Owner Date Status Actions
    Target Audience Module Method Duration Scheduled Date Completion % Status Actions
    Overall Readiness Score: / 5.0  (click cells to cycle 1–5)
    Workstream Leadership Alignment Stakeholder Buy-in Process Clarity Technology Readiness Skills & Capability Communications Avg Actions

    Risk Register

    Identify, assess and track operational risks with mitigation actions and ownership.

    Total Risks
    High / Critical
    Mitigated
    Avg Score
    ID Category Description L I Score Rating Mitigation Action Owner Status
    ID Function L3 Process Description Impact Priority Target Date Owner Status

    Business Case

    Quantify the value of your operating model transformation. Track savings and benefits alongside the cost to operate to build a compelling, evidence-based business case.

    Savings & Benefits Tracker

    Track projected and realised savings by category — hard savings, cost avoidance, efficiency gains, and revenue uplift.

    0Benefits
    $0Pipeline
    $0Validated
    $0Realised
    $0Confidence-Weighted

    Cost to Operate

    Model the current vs. future state operating costs — people, technology, MSP fees, facilities, and training.

    $0Current Annual
    $0Future Annual
    $0Annual Delta
    $0One-off Investment
    Payback (months)

    Implementation Roadmap

    Define the phased delivery plan, key milestones and quick wins for your operating model transformation.

    Workstreams
    Milestones
    On Track
    Quick Wins Complete

    Help & Documentation

    Guides, reference and tips for getting the most from the Operating Model Design tool

    Work through the 14 modules in order — each builds on the last. You don't need to complete every field before moving on; return to any section at any time.

    1
    Choose a Starter Template (optional)
    Go to Settings → Starter Templates and load a template that best matches your operating model type. This pre-populates Taxonomy, Capabilities and Risk Register with a sensible starting point.
    💡 Load a template before entering custom data — it replaces existing content.
    2
    Set up Branding & Appearance
    Go to Settings → Cover & Branding to set your presentation title, client name and tagline. Pick your colour scheme and font in Slide Appearance. These apply across all PPTX exports.
    3
    Vision & Guiding Principles
    Write the mission statement, value proposition and strategic objectives. This text appears verbatim in your Vision PPTX slide and sets the tone for everything that follows.
    4
    Reasons for Change
    Map the transformation themes — select current & future state pairs that define why change is needed and what success looks like. Provides the strategic rationale for the operating modeling model design.
    5
    Taxonomy
    Build your 4-level process taxonomy using the table. Add Level 1 (top-level domain), Level 2 (process group), Level 3 (process) and Level 4 (sub-process / activity) rows. Drag to reorder. This is the structural backbone for process ownership and design.
    💡 Use a starter template to get pre-filled Level 1/2 process groups as a starting point.
    6
    Category Scope
    Define which spend categories fall within procurement's remit. Add L1 / L2 categories with annual spend, then use the Coverage Register tab to flag which process taxonomy areas apply and set a future target state. Switch to the Make vs Buy tab to assign a delivery model (BU / Corp / GCC / MSP) for each category.
    💡 Build the Taxonomy first — Category Scope reads your taxonomy L2s automatically for the coverage chips.
    7
    Capabilities
    Add capabilities grouped by level (Strategic, Operational, Enabler). Rate the current maturity (1–5) for each. The maturity bar chart is exported automatically to the Capabilities PPTX.
    8–10
    Process, Data Requirements & Governance
    Document the end-to-end process flows, identify the data inputs and outputs needed across the function, and define governance ownership and accountability frameworks.
    11
    IT Enablement
    Map your technology landscape across the P2P, analytics and category management stacks. Note integration points and digital enablement priorities.
    12–13
    Organisation Design & Roles
    Design the structure and define each role with RACI responsibilities. The Roles table feeds directly into the FTE sizing model in the next section.
    14
    FTE Requirements
    Model headcount requirements by role and business unit. Use the Process Time Split sub-tab to allocate each FTE function's time across process L2 activities. The summary is included in the full deck export and the Excel workbook.
    15
    Change Management
    Add stakeholders with influence/interest ratings, build your communications plan and rate readiness by ADKAR workstream. Exports to a dedicated 3-slide PPTX.
    16
    Risk Register
    Log risks with likelihood, impact and mitigation owners. The heat map and risk table are auto-generated in the Risk PPTX export.
    17
    Implementation Roadmap
    Build the phased roadmap with workstreams, milestones and quick wins. This is typically the closing section of the full deck.
    💡 Preview your full deck on the Dashboard before exporting to check flow and consistency.
    18
    Export & Deliver
    Use Dashboard → Export Full Deck for a single combined PPTX, or export individual section PPTXs from within each module. Download the Excel workbook from the Dashboard for a data-only backup.
    01👁Vision & Guiding Principles
    Build your procurement vision statement, select word chips, and set guiding principles across 23 operating model decisions with trade-off analysis.
    ⬇ Exports: Vision PPTX slide
    02🔄Reasons for Change
    Map current state challenges to future state outcomes. Select transformation themes to define your change narrative.
    ⬇ Exports: C&F State PPTX slide
    03🗂Taxonomy
    Build a 4-level hierarchical process taxonomy using a drag-and-drop table. Supports Level 1 (domain), Level 2 (process group), Level 3 (process) and Level 4 (sub-process / activity) with notes.
    ⬇ Exports: Taxonomy PPTX + Workbook
    04📊Category Scope
    Define L1/L2 spend categories with annual spend, map which process taxonomy L2s currently manage each category vs what is out of scope, and set a future target. The Make vs Buy tab sets delivery model (BU/Corp/GCC/MSP) per category.
    ⬇ Exports: Workbook (Category_Coverage + Cat_MvB tabs)
    05💡Capabilities
    Define capabilities by level (Strategic / Operational / Enabler) and rate current maturity 1–5. Auto-generates a maturity bar chart.
    ⬇ Exports: Capabilities PPTX + Workbook
    06🔁Process Flows
    Import a process XLSX, then view, filter and edit steps inline in the table — click any cell to edit, use ↑ ↓ to reorder, 🗑 to delete, or "+ Add Row" to insert a blank step. Status, Shape Type, Phase and Connector Label use managed dropdown lists (configure in Settings → Process Lookup Lists). Generates a flowchart diagram for any L4 sub-process.
    ⬇ Exports: Process PPTX slide
    07📊Data Requirements
    Map the data inputs, outputs and systems across procurement activities. Assign data owners and note quality issues.
    ⬇ Exports: Data Req PPTX slide
    08⚖️Governance
    Five sub-tabs: Policy Register defines procurement policies. Decision Rights maps ARVIN accountability. Forums defines governance cadences. KPI Scorecard tracks procurement metrics with RAG status. MSP SLAs defines and monitors service level agreements with your Managed Service Provider across sourcing, contracting, operations, supplier management and reporting.
    ⬇ Exports: KPI PPTX + MSP SLA PPTX + Forums PPTX + Workbook
    09🖥IT Enablement
    Map the current and target technology landscape, identify integration gaps and prioritise digital investments.
    ⬇ Exports: IT PPTX slide
    10🏢Organisation Design
    Design the organisational structure, reporting lines and team configuration. Document team sizing rationale and span of control.
    ⬇ Exports: Org Design PPTX slide
    11👤Roles & Responsibilities
    Two tabs: RACI Matrix defines role titles, departments and RACI assignments across procurement processes. Job Descriptions builds editable JD cards per role with Purpose, Reports To, Decision Authority, Key Responsibilities, Qualifications and KPIs — auto-tracks completion status. Roles feed into FTE modelling.
    ⬇ Exports: RACI PPTX + JD PPTX + Workbook (11_RR_Roles + 11_RR_RACI + 11_Job_Descriptions)
    12👥FTE Requirements
    Model full-time equivalent headcount by role and business unit. Supports current-state vs. future-state comparisons. The Process Time Split sub-tab lets you allocate each function's time across process L2 activities.
    ⬇ Exports: FTE PPTX + Workbook (incl. 12_FTE_ProcTime sheet)
    13📣Change Management
    Manage stakeholders (influence/interest matrix), build a communications plan and track readiness across ADKAR workstreams.
    ⬇ Exports: 3-slide Change Mgmt PPTX
    14⚠️Risk Register
    Three tabs: Register logs risks with likelihood (1–5) and impact (1–5), filter by category, owner or status. Heatmap auto-generates a 5×5 risk heat map. Dependencies tracks cross-functional dependencies with L3 Process mapping (tied to Taxonomy), filtering by function, L3 process, impact and status, plus expandable descriptions.
    ⬇ Exports: Risk PPTX (3 slides) + Workbook (14_Risk_Register + 14_Risk_Dependencies)
    15💼Business Case
    Two-tab section: Savings & Benefits tracks projected and realised savings across categories with confidence weighting. Cost to Operate models current vs. future state costs with auto-populate from FTE and IT modules, payback calculation, and category grouping. Together they quantify the value of your operating model transformation.
    ⬇ Exports: Savings PPTX + Cost Model PPTX + Workbook (19_Savings + 20_Cost_Model)
    16🗺Implementation Roadmap
    Build a phased delivery roadmap with workstreams, milestones and quick wins plotted by quarter across up to 4 phases.
    ⬇ Exports: Roadmap PPTX + Workbook
    17📋GCC RFP
    Build the Activity Collection for your GCC RFP. Import L1–L4 process steps from the Taxonomy module, then fill in SLA expectations, volume estimates, FTE, delivery split, location split, and digitization ratings. Filter by L1, L2 or digitization level. Use the Prep Checklist to track readiness across all 13 steps with auto-completeness checking. Preview as PPTX summary (excluded from master deck). Export as the standard MSP procurement xlsx when complete.
    ⬇ Exports: RFP Activity Collection xlsx + RFP Summary PPTX + Workbook (16_RFP_Activities + 16_RFP_PrepPlan + 16_RFP_Config)
    18Decision Log
    Log cross-module design decisions with benefits, trade-offs and rationale. Filter by module or status (Confirmed / Challenged / Review). Preview and export as a 2-slide PPTX with summary stats and detail table.
    ⬇ Exports: Decision Log PPTX (2 slides) + Workbook (2_Decision_Log)
    19⚠️Issue Tracker
    Two tabs: Issues tracks project issues with category, priority, status, owner and resolution — filter by category, priority and status. Project Team manages the team directory with roles, departments and workstreams. Preview and export both tabs as PPTX slides.
    ⬇ Exports: Issue Tracker PPTX + Workbook (17_Issues + 17_Project_Team)
    20🎨Operating Model Canvas
    Auto-generated single-page summary across 6 pillars: People, Process, Technology, Governance, Data and Delivery Model. Each pillar pulls live metrics from other modules with health indicators. Add editable key messages per pillar for executive presentations. Accessible via the Dashboard › OM Canvas tab. Preview and export as a single PPTX slide.
    ⬇ Exports: OM Canvas PPTX (1 slide) + Workbook (21_OM_Canvas)
    ⬗ Export Full Deck
    Generates a single combined PPTX containing a cover slide, agenda, and one divider + content slide per section. Use Settings → Full Deck Composition to include or exclude individual sections. The slide order follows the module sequence.
    👁 Preview Deck
    Opens a full-screen preview of all slides before exporting. Navigate with the filmstrip thumbnails on the left or use ← → keyboard arrows. Press Esc to close. The preview reflects your current Settings and live data.
    ⬇ Section Exports
    Each module with a PPTX export button generates a standalone file with 1–3 slides specific to that section. These use the same colour scheme and font as the full deck, controlled by Settings.
    📊 Excel Workbook
    Downloads a multi-sheet Excel file with 40+ tabs covering all modules: Settings, Vision, Reasons, Guiding Principles, Decision Log, Taxonomy, Category Coverage, Make vs Buy, Capabilities, Process, Data Requirements, Policy Register, Governance (Decision Rights, Forums, KPIs, MSP SLAs), IT (Systems, Automation, Capability Map), Org Design (Current + Future), Roles (RR Roles, RACI, Job Descriptions), FTE (Model, Process Time, Role Allocation), Change Management (Stakeholders, Comms, Training, Readiness), Risk (Register + Dependencies), Roadmap (Workstreams, Milestones, Quick Wins), GCC RFP (Activities, Prep Plan, Config), and Issue Tracker (Issues + Project Team). Use as a data backup or share with stakeholders.
    How Settings affect exports
    Color Scheme — changes the left accent bar, divider slide backgrounds, rule lines and badge colours across all exports.
    Font Family — applies to all text in all PPTX files.
    Title / Body / Divider sizes — control font sizes across all slide types.
    Cover & Branding — the cover slide title, subtitle, client name and tagline appear on the cover of both the full deck and section exports that include a cover.
    Footer — project name, organisation name and date appear in the footer bar of every content slide. Toggle off to remove.
    ActionShortcut / Method
    Navigate to a moduleSidebar click
    Open full deck previewDashboard → Preview Deck
    Next slide in preview or
    Previous slide in preview or
    Close preview modalEsc
    Jump to slide via filmstripClick thumbnail on left panel
    Export full deckDashboard → Export Full Deck
    Download Excel workbookDashboard → Workbook tab → Export
    Reset all dataSettings → App Preferences → Reset
    Load a starter templateSettings → Starter Templates
    Change colour scheme or fontSettings → Slide Appearance
    Toggle a section in/out of full deckSettings → Full Deck Composition
    Edit a Process step fieldClick cell → type → Enter or click away
    Cancel a Process cell editEsc
    Add a Process step+ Add Row button below table
    Manage Process dropdown listsSettings → Process Lookup Lists
    Power-User Tips
    💾All data is stored in the browser's memory — it resets when you close or refresh the tab. Export a workbook backup regularly via the Dashboard, especially after a long working session.
    🎨Change your colour scheme in Settings and immediately use Preview Deck on the Dashboard to see how the full presentation looks before committing to an export.
    📑You can exclude sections from the full deck without deleting their data — use Full Deck Composition in Settings to toggle sections on/off per export.
    📋Starter Templates pre-populate Taxonomy, Capabilities and Risk Register. Load one at the start of a new project to skip the blank-page problem, then customise from there.
    📋The Process dropdown lists (Status, Shape Type, Phase, Connector Label) are fully configurable. Go to Settings → Process Lookup Lists to add your client-specific values before you start editing steps — they take effect immediately in the inline dropdowns.
    🖨For client-ready decks, fill in Cover & Branding in Settings with the client name and a tagline like "Confidential — Draft v1.0" so it appears on the cover slide automatically.
    Data is automatically saved to browser storage as you work — you can close the tab and return later to find your session restored. To share or create a portable backup, use Dashboard → Workbook tab → Export Excel. To reload a session, drop the exported xlsx back on to the Dashboard's Import tab. You can also export individual section PPTXs at any point to preserve the presentation output.
    The PPTX export library is bundled directly in the HTML file — this message should not normally appear. If you see it, try opening the file in a different browser (Chrome or Edge recommended). The file must be opened locally from disk, not served from a web server with restrictive Content Security Policy headers.
    Each section with a table (Taxonomy, Capabilities, Risk Register, etc.) has its own Add row and delete controls. You can clear rows individually. The Reset All Data button in Settings → App Preferences clears all sections at once — use it with caution after exporting a backup.
    Strategic CoE — a centralised centre of excellence with broad category coverage and high strategic maturity. Best for large enterprises.

    Business Partnering — embedded procurement partners aligned to business units. Good for decentralised organisations.

    Shared Services / P2P — high-volume transactional model focused on P2P automation and compliance. Good for SSC environments.

    Greenfield Build — foundational structure for a new procurement function. Starts simple with quick wins and phased capability build.
    Yes — open Settings → Delivery Model Labels and type your preferred names for each of the four delivery types. The labels update live across Category Scope (Make vs Buy), Org Design and FTE Model. Your custom names are also saved to the Excel workbook (0_Settings tab) and restored when you reload a session.
    Logo insertion is not currently supported directly in the tool. After exporting your PPTX, open it in PowerPoint and use Insert → Header & Footer or add the logo as a slide master element. The exported files are fully editable standard .pptx files.
    The full deck follows the fixed module order (Vision → Principles → Taxonomy → … → Roadmap). To reorder, export the full deck and then rearrange slides directly in PowerPoint. You can also export individual section PPTXs and manually combine them in the order you prefer.
    The slide preview is rendered in HTML and is an approximation of the final PPTX layout. Font rendering, spacing and exact positioning may differ slightly between the HTML preview and the actual PowerPoint output. The PPTX export uses precise point-based coordinates and is the authoritative version. Minor pixel differences in the preview are expected.
    The tool is designed for desktop/laptop use and works best at screen widths above 1100px. It is usable on a large tablet in landscape orientation, but some table-editing features and the slide preview modal are optimised for mouse interaction. PPTX export functionality requires a browser that supports the Blob and FileSaver APIs (Chrome, Edge, Firefox, Safari 15+).
    Once you have imported a process file and selected a sub-process, the Steps table is fully editable. Click any cell to open an inline editor — short fields show a text input, longer fields (Description, Notes) open a textarea, and Status / Shape Type / Phase / Connector Label open a dropdown. Press Enter or click away to save; Escape cancels. Use the ↑ / ↓ buttons on the right of each row to reorder steps, and 🗑 to delete a row (you will be asked to confirm). The + Add Row button below the table adds a blank step at the end. All edits are auto-saved and flow through to the XLSX export on the 6_Process tab. To customise the dropdown options, go to Settings → Process Lookup Lists and add, remove or reset options for each list.
    The Org Structure panel has several tools for large charts: Scroll-wheel to zoom and click-drag to pan the canvas. Use ⊟ Collapse All to reduce the tree to just the root, then expand only the branches you need. Search dims all non-matching nodes and jumps the viewport to the first match. Switch to ▦ Grid view to see and edit all roles in a filterable table (filter by name or type). The ± Changes button in each tab highlights what's different between Current and Future state. Zoom percentage is shown next to the +/− buttons and ⌖ resets the view.
    The Decision Log is a cross-module record of every significant operating model design choice you make. It captures: the decision itself, the primary benefit, the key trade-off accepted, and the WWHTBT (What Would Have To Be True) — the conditions under which a different approach would have been the right call. To log a decision from the Vision section, select a word on the scale, click Challenge this choice to see the WWHTBT text, optionally add your own context, then click + Log to Decision Log. You can also add decisions manually from any module by clicking + Add Manually in the Decision Log panel. Each decision can be marked as Confirmed, Under Review, or Challenged to track stakeholder feedback. Export the full log as a text file to use as a steering committee defence document.
    WWHTBT stands for What Would Have To Be True — a strategic decision-making tool that forces you to articulate the conditions under which an alternative choice would be superior. Rather than simply defending your chosen approach, WWHTBT makes your reasoning explicit: "We chose X because we believe Y and Z are true about our organisation. If A were true instead, we would have chosen B." This is especially powerful when presenting to steering committees or CFOs who will challenge every design decision. The Vision section includes pre-written WWHTBT statements for each word on the scale, which you can adapt with your specific organisational context.
    ADKAR
    A change management model: Awareness, Desire, Knowledge, Ability, Reinforcement. Used to track individual readiness through a transformation.
    Business Partnering Model
    An operating model where procurement professionals are embedded within business units, providing dedicated commercial support closer to the customer.
    Category Management
    A strategic approach to procurement that groups related spend into categories and applies specialist expertise to optimise total cost and supplier performance.
    Category Scope
    The set of spend categories and sub-categories within procurement's remit. Defined by which categories are actively managed by procurement (in scope) vs. managed directly by the business (out of scope). Documented in a Coverage Register together with spend data, process taxonomy alignment and future target state.
    CoE (Centre of Excellence)
    A centralised team that sets standards, develops capability and drives strategic value across the procurement function.
    FTE (Full-Time Equivalent)
    A unit of measure for workforce capacity. 1.0 FTE = one full-time employee. Used to size teams and model headcount requirements.
    GCC (Global Capability Centre)
    A captive delivery centre — typically offshore or nearshore — that provides specialised procurement services (e.g. analytics, sourcing support, P2P processing) at scale. A modern evolution of the traditional shared services centre, with a broader capability remit and higher-value activities.
    Heat Map (Risk)
    A visual matrix plotting risks by likelihood (x-axis) and impact (y-axis), colour-coded from green (low) to red (critical) to enable prioritisation.
    L1 / L2 / L3 / L4
    The four levels of the process taxonomy hierarchy. L1 = top-level domain (e.g. Source-to-Contract), L2 = process group (e.g. Sourcing), L3 = process (e.g. RFP Management), L4 = sub-process or activity (e.g. Evaluate Supplier Responses).
    Maturity Level
    A 1–5 scale rating how advanced a capability is: 1 = Ad hoc, 2 = Developing, 3 = Defined, 4 = Managed, 5 = Optimised.
    MSP (Managed Service Provider)
    A third-party organisation contracted to deliver a defined procurement function or category on behalf of an organisation. In the Make vs Buy model, MSP represents fully outsourced delivery. In this tool the four delivery model options are BU (business unit), Corp (corporate CoE), GCC (global capability centre), and MSP (managed service).
    Operating Model
    The design that describes how an organisation is structured, how it operates and how it delivers value — covering people, processes, technology and governance.
    P2P (Procure-to-Pay)
    The end-to-end process from identifying a business need through supplier selection, purchase order, goods receipt and invoice payment.
    RACI
    Responsible, Accountable, Consulted, Informed. A framework for clarifying roles and responsibilities across processes and decisions.
    S2C (Source to Contract)
    The upstream procurement process spanning from spend analysis and category strategy through supplier identification, RFx, negotiation and contract execution. S2C sits upstream of P2P and is where the majority of commercial value is created.
    Shared Services Centre (SSC)
    A centralised unit delivering transactional procurement activities (e.g. PO processing, invoice management) at scale and lower cost.
    Stakeholder Mapping
    The process of identifying and categorising stakeholders by their level of influence (power) and interest in the change, used to inform engagement strategies.
    SRM (Supplier Relationship Management)
    A systematic approach to managing and developing relationships with key suppliers to improve performance, innovation and risk mitigation.
    Taxonomy (Process)
    A hierarchical classification of an organisation's procurement processes into four levels: L1 (domain), L2 (process group), L3 (process) and L4 (sub-process / activity). Used to establish process ownership, design workflows and identify automation opportunities.
    TCO (Total Cost of Ownership)
    The full cost of a procurement decision over its lifecycle, including acquisition, operation, maintenance and disposal — beyond just purchase price.
    Version 2.0 — February 2026

    The Operating Model Design tool is a self-contained, browser-based design environment for transformation practitioners. Built as a single HTML file — no installation, no server, no data leaves your machine.

    What's New in v2.0
    NEWCategory Scope module — Coverage Register + Make vs Buy delivery model matrix
    NEWIT Capability Map rows auto-sourced from Capabilities module when populated
    IMPRACI Roles & Responsibilities auto-syncs rows from live Taxonomy hierarchy
    NEWWelcome landing page with module quick-launch grid
    NEWFull Settings panel — colour schemes, fonts, sizes, cover branding, deck composition
    NEWFull Deck PPTX export with cover, agenda, dividers and all 14 sections
    NEWFull-screen deck preview with filmstrip navigation and keyboard shortcuts
    NEW4 Starter Templates (CoE, Business Partner, SSC, Greenfield)
    NEWDivider slide font size control
    NEWThis Help section
    IMPUnified PPTX style — consistent fonts, title sizes and backgrounds across all exports
    IMPSection dividers always use theme NAVY for visual consistency
    IMPNo coloured header bars on content slides — dark title + thin rule only
    IMPDashboard redesigned with preview + export actions side by side
    FIXChange Management PPTX now uses shared style constants
    NEW06 Process: Inline row editing — click any cell in the Steps table to edit it (text input, textarea or dropdown)
    NEW06 Process: ↑ ↓ move row and 🗑 delete row action buttons on every step
    NEW06 Process: "+ Add Row" button adds a blank step directly in the table
    NEWSettings → Process Lookup Lists — manage approved dropdown options for Status, Shape Type, Phase and Connector Label
    NEW10 Org Structure: pan & zoom (wheel + drag), zoom % controls and reset button
    NEW10 Org Structure: Grid edit view — editable table with filter bar (text + type dropdown)
    NEW10 Org Structure: Expand All / Collapse All branch controls
    NEW10 Org Structure: Search & highlight — dims non-matching nodes, jumps to first match
    NEW10 Org Structure: Current vs Future diff mode — colour-codes Added / Changed / Removed roles
    NEW10 Org Structure: Legend now shows actual node types (BU/Corp/GCC/MSP) matching Settings labels
    FIX10 Org Structure: org data now correctly saved & restored across sessions (was lost on reload)
    NEW16 RFP: Import from Taxonomy replaces Import from Process — reads L1–L4 from Module 3
    FIXSettings accordion groups open and close reliably
    NEW1 Vision: Trade-off slider — select words on a 5-position scale, see benefit & trade-off at each position
    NEW1 Vision: Challenge this choice (WWHTBT) — collapsible panel shows what conditions would make a different choice better
    NEW1 Vision: Log to Decision Log — saves any word choice with its rationale to the cross-module Decision Log
    NEWDecision Log — new module collecting all design choices, trade-offs and WWHTBT across the operating model
    FIX1 Vision: selected words, custom words, pairs and WWHTBT annotations now persist across sessions
    IMPDashboard: Org Structure card now shows correct role counts from live data
    Built for practitioners, by practitioners. All data is processed entirely client-side — nothing is transmitted to any server.

    Settings

    Customize exported PPTX appearance, branding, deck composition and starter templates

    Live Preview
    Color Scheme
    Font Family

    Font Sizes
    Slide Title
    Body Text
    Divider Slide Text
    Footer
    Date Format
    Cover Slide Preview

    Cover, agenda and closing slides are always included.

    Keyboard Shortcuts
    Navigate sectionsSidebar click
    Preview deckDashboard → Preview Deck
    Preview: next slide→ or ↓
    Preview: prev slide← or ↑
    Close previewEsc
    Download workbookDashboard → Workbook
    Data Management

    Resetting section data will clear all entered content across all modules. This action cannot be undone.

    Each template pre-populates Taxonomy, Capabilities, and Risk Register with a typical starting point. Your existing data will be replaced — export a workbook backup first.

    🏛️
    Strategic Centre of Excellence
    Centralised function driving strategic value, supplier partnerships and category leadership across the enterprise.
    🤝
    Business Partnering Model
    Embedded procurement partners aligned to business units, balancing central governance with local agility.
    ⚙️
    Shared Services / P2P
    High-volume transaction processing, compliance and P2P optimisation with strong automation focus.
    🌱
    Greenfield Build
    Building a procurement function from scratch — foundational structure, quick wins and phased capability build.

    These lists power the dropdown menus when you inline-edit a Process Step row. Add or remove options; changes take effect immediately.

    Checking storage…
    How auto-save works: Every time you add, edit or change anything, your data is automatically saved to this browser's local storage within a second. It will be waiting for you next time you open this file in the same browser on the same computer.

    Moving or sharing the file? Use Save Workbook (top-right ↓ button) — the xlsx contains all your data and settings and can be reloaded into any copy of this tool.

    Browser storage is tied to this file's location on disk. If you move or rename the HTML file, save the workbook first — then drag it back in after moving.

    GCC RFP Builder

    Define procurement activities, set SLAs and volume estimates, then export the Activity Collection xlsx for your MSP RFP.

    Total Activities
    With SLAs
    FTE Assigned
    Digitization Rated
    📋 RFP Preparation Checklist

    Track the steps required before exporting your RFP Activity Collection. Click a module link to jump to that section.

    # Step Module Deadline Responsible Notes
    Loading configuration…
    0 activities

    Decision Log

    A structured record of all operating model design choices, their trade-offs, and the rationale behind each decision. Use this as a defence document for steering committee challenges.

    Issue Tracker

    Log, assign and track project issues through to resolution. Manage your project team to populate owner dropdowns.

    Total Issues
    Open
    Critical / High
    Resolved
    Slide Preview — Guiding Principles Summary
    Slide Preview 0 / 0
    Taxonomy Slide Preview 0 / 0
    Save As
    No folder selected
    R&R Slide Preview 0 / 0