How to anchor RTM governance with a concrete, owner-led RACI that keeps thousands of outlets and distributors aligned

A clear end-to-end RACI for RTM vendor selection and rollout in a mid-sized Indian FMCG manufacturer typically assigns Sales/RTM Operations as commercial owners, Finance as ROI and control gatekeeper, IT as architecture and integration authority, and Operations/Distribution as execution validators. Defining this RACI upfront reduces delays and political friction by clarifying who decides what, and when.

A typical phase-wise RACI looks like:

1. Discovery and requirements
2. Responsible: Sales Ops / Head of Distribution (capture pain points: distributor visibility, fill rate, claim TAT, field adoption).
3. Accountable: CSO.
4. Consulted: Finance (trade-spend, leakage pain), IT (integration, compliance), Regional Sales Managers.

5. Informed: Procurement, HR (for training implications).

6. Solution shortlisting

7. Responsible: Sales Ops / RTM CoE, supported by Procurement.
8. Accountable: CSO or RTM program sponsor.
9. Consulted: IT (architecture fit, offline, ERP/tax integration), Finance (commercial models, ROI), Operations/Distribution (distributor readiness).

10. Informed: Country/regional managers, Trade Marketing.

11. Commercial and contract negotiation

12. Responsible: Procurement.
13. Accountable: CFO for commercial terms; CIO for technical SLAs/data clauses.
14. Consulted: CSO/RTM sponsor (scope, modules), Legal (risk, data privacy), IT security.

15. Informed: Sales Ops, Operations.

16. Pilot design and execution

17. Responsible: Sales Ops / RTM CoE (pilot scope, metrics, training, change management).
18. Accountable: CSO or RTM sponsor.
19. Consulted: IT (environments, integration), Finance (measurement of leakage and claim TAT), Regional Sales for pilot territory, Vendor implementation team.

20. Informed: CFO, CIO, HR.

21. Pilot evaluation and scale decision

22. Responsible: RTM CoE consolidating feedback and metrics.
23. Accountable: RTM steering committee (CSO, CFO, CIO).
24. Consulted: Pilot region leadership, Finance controllers, IT ops.

25. Informed: Board or executive committee as needed.

26. Full deployment

27. Responsible: RTM CoE / Project manager (rollout plan, tracking), Regional Sales for local adoption, IT for rollouts and support.
28. Accountable: CSO for commercial outcomes; CIO for stability and integration; CFO for financial controls and leakage targets.
29. Consulted: Operations/Distribution, HR (training), Vendor.
30. Informed: All country managers, key distributors.

This explicit RACI materially reduces friction because it:

• Prevents late vetoes (e.g., IT blocking a vendor after Sales already committed) by involving veto players early as Consulted or Accountable.
• Clarifies that Finance and IT own specific risks (ROI validity, integration, compliance) so Sales does not bear all blame.
• Reduces duplicated work and parallel evaluations by centering responsibility in an RTM CoE or Sales Ops owner.
• Provides escalation clarity when scope creep, integration delays, or adoption gaps appear, enabling faster decisions and fewer political stalemates.

For a Southeast Asian CPG manufacturer modernizing RTM, the most effective single program owner is usually a cross-functional RTM Center of Excellence (CoE) or Sales Operations–led transformation role, rather than pure Sales or Operations alone. A cross-functional owner can balance commercial outcomes, distributor operations, and technical constraints while coordinating Finance and IT.

Implications of different choices:

1. Sales as sole owner
2. Strength: Strong focus on revenue growth, coverage, and field adoption; high visibility with commercial leadership.
3. Risk: Underestimates integration, data governance, and compliance; may sideline Finance and IT, causing late vetoes and trust gaps.

4. RACI impact: Sales tends to over‑claim decision rights, leading to friction when Finance or IT re‑asserts control during contracting or go‑live.

5. RTM Operations / Distribution as sole owner

6. Strength: Deep understanding of distributor economics, claims, fill rate, and logistics.
7. Risk: May lack authority with Sales and Trade Marketing on scheme design, incentives, and field behavior; may underweight analytics and control tower needs.

8. RACI impact: Operations may be treated as “support,” making escalation harder when Sales resists process changes.

9. Cross-functional RTM CoE as owner

10. Structure: A small team reporting to the CSO or a CXO sponsor, with embedded leads or dedicated liaisons from Sales, Operations, Finance, and IT.
11. Strength: Institutionalises shared ownership; CoE can design templates for coverage, DMS integration, scheme workflows, and analytics, then replicate across markets.
12. RACI impact:
    • Responsible for day‑to‑day program management, requirements, pilots, and vendor coordination.
    • Accountable to the steering committee for delivery of business outcomes and adherence to architecture and compliance.
    • Finance remains Accountable for financial controls; CIO for architecture and security; CSO for commercial KPIs, but all decisions flow through one CoE channel.

How ownership choice influences decision flows and escalation:

• A CoE owner can formalise decision checkpoints: vendor shortlist approval, pilot scope, rollout phasing, standard vs local template decisions, and kill criteria, reducing ad‑hoc interventions.
• Escalations (e.g., scope creep, data quality issues, field resistance) go through the CoE to a clearly defined steering group (CSO, CFO, CIO) instead of bouncing between departments.
• RACI clarity improves because roles are defined around domains (commercial KPIs, finance controls, IT architecture, operations execution) with the CoE orchestrating trade‑offs.

In practice, central RTM CoE ownership, backed by a steering committee, creates faster, more coherent decision flows than giving unilateral control to either Sales or Operations.

In a large Indian CPG company, the RACI for RTM decision-making should give the CSO clear accountability for commercial outcomes (coverage, fill rate, scheme ROI) while preserving CIO veto power on architecture and security in a structured, time‑bound way. The design must avoid situations where IT blocks late or Sales bypasses IT through shadow initiatives.

A practical RACI pattern is:

1. Business case and target outcomes
2. Responsible: Sales Ops / RTM CoE.
3. Accountable: CSO (numeric and weighted distribution targets, cost‑to‑serve goals, scheme ROI, leakage reduction).
4. Consulted: CFO (financial validation), CIO (feasibility implications).

5. Informed: Regional Sales, Operations.

6. Architecture, integration, and security standards

7. Responsible: Enterprise Architect / IT lead.
8. Accountable: CIO (defines non‑negotiables: ERP/tax integration, offline-first design, data residency, SSO, security protocols).
9. Consulted: CSO/RTM CoE (practicality for field and distributors), CISO, Compliance.

10. Informed: Vendor, Procurement.

11. Vendor evaluation and selection

12. Functional fit (SFA, DMS, TPM workflows):
    • Responsible: RTM CoE.
    • Accountable: CSO.
    • Consulted: Regional Sales, Trade Marketing, Operations.
13. Technical fit (integration, scalability, compliance):
    • Responsible: IT evaluation team.
    • Accountable: CIO (with explicit right to disqualify vendors failing minimum standards).
    • Consulted: Vendor, RTM CoE.

14. Final decision:
    • Accountable: Jointly CSO (commercial) and CIO (architecture), with CFO concurrence on cost/ROI.
    • Mechanism: steering committee decision based on a shared scorecard combining commercial and technical criteria.

15. Implementation and rollout

16. Responsible: RTM CoE/project manager for timelines, configuration, training; IT for infrastructure and integrations.
17. Accountable: CSO for adoption and commercial KPIs; CIO for stability, data integrity, and security.

18. Consulted: Regional leadership, Finance (claim workflows), HR (training), Vendor.

19. Governance and changes

20. Scope changes impacting business case (new modules, major customisation):
    • Accountable: CSO (value) + CIO (risk), via change control board.
21. Architecture changes:
    • CIO holds veto but within pre‑defined review SLAs and must propose alternative paths where possible.

This RACI design keeps the CSO firmly in charge of “what outcomes we need” and “which business workflows we standardise,” while the CIO owns “how we implement safely.” Time‑boxed, transparent veto rights and joint scorecards prevent IT bottlenecks without eroding architectural governance.

In an African CPG manufacturer implementing an RTM control tower, the most damaging RACI missteps are those that leave no single owner for key decisions—especially around data definitions, distributor onboarding, and exception handling. These gaps create “no‑owner” failure modes where dashboards exist but cannot be trusted or actioned.

Critical missteps to avoid include:

1. Dual or unclear ownership of master data definitions
2. Problem: Sales, IT, and sometimes Distributors all influence outlet, SKU, and territory definitions without a final authority. This leads to duplicate retailers, mismatched SKUs, and conflicting hierarchies between RTM and ERP.

3. Fix: Assign one function (often RTM CoE or Sales Ops) as Accountable for outlet and territory definitions, with IT Responsible for implementation and Finance Consulted for financial hierarchies. Establish clear rules for ID creation, changes, and deactivations.

4. No clear sign-off for distributor onboarding and data responsibilities

5. Problem: Ambiguity over who approves new distributors, who validates their opening balances and masters, and who ensures DMS/RTM integration quality. Issues get bounced between Sales, Finance, and IT.

6. Fix: Make Sales/Distribution Accountable for business approval and basic data completeness; Finance Accountable for credit limits and compliance checks; IT Responsible for integration setup. Use a standard onboarding checklist with explicit sign‑offs before a distributor is visible in the control tower.

7. Unassigned ownership of data quality and reconciliation

8. Problem: Nobody is clearly Responsible for reconciling RTM control tower data with ERP, or for resolving anomalies (e.g., negative stocks, missing invoices, inconsistent secondary sales).

9. Fix: Assign a data steward role within RTM CoE as Responsible, with IT providing tools and logs, and Finance Accountable for final reconciled numbers. Define SLAs for anomaly resolution and escalation routes for persistent issues.

10. Undefined escalation paths for exceptions and alerts

11. Problem: Control tower flags stockouts, beat non‑compliance, or claim anomalies, but no function is clearly designated to act. Alerts accumulate and dashboards lose credibility.

12. Fix: For each alert type, define: who is Responsible to act (e.g., Regional Sales Manager, Distribution Manager), who is Accountable for closure (e.g., Country Sales Head), and who is Consulted/ Informed (e.g., Supply Chain for stockouts, Finance for claim anomalies). Encode these in SOPs.

13. Vendor managing key governance decisions by default

14. Problem: In the absence of clear internal RACI, the integrator or RTM vendor informally decides on data structures, rules, and exception handling. This creates dependency and internal confusion.
15. Fix: Keep the vendor Responsible only for implementing agreed designs and SLAs; internal stakeholders must stay Accountable for definitions, thresholds, and business rules.

Preventing these missteps requires a written RTM control tower RACI, tied to master data governance, distributor onboarding, and alert handling, so that every critical decision has a named owner.

In an emerging-market CPG RTM modernization, vendor selection must be governed by explicit decision checkpoints and RACI assignments so that the CFO can see a clear, auditable trail from requirements to final recommendation. The aim is to show that commercial, technical, and financial risks were all formally evaluated.

Key checkpoints and associated RACI include:

1. Checkpoint 1 – Business case definition
2. Scope: Pain points, target KPIs (numeric distribution, fill rate, claim TAT, leakage reduction), and expected ROI.
3. Responsible: Sales Ops / RTM CoE.
4. Accountable: CSO.
5. Consulted: Finance (for ROI logic, trade-spend baselines), IT (for feasibility), Operations.

6. CFO assurance: signs off that the ROI model, cost assumptions, and baseline data are reasonable.

7. Checkpoint 2 – Requirements and evaluation framework

8. Scope: Functional requirements (DMS, SFA, TPM, analytics), technical criteria (integration, offline, compliance), scoring model, and weightings.
9. Responsible: RTM CoE.
10. Accountable: Jointly CSO (functional) and CIO (technical).
11. Consulted: Finance (control and audit needs), Regional Sales, Operations.

12. CFO assurance: reviews and endorses financial control requirements (claim workflows, audit trails) and ensures they appear as evaluation criteria.

13. Checkpoint 3 – Shortlist confirmation

14. Scope: Longlist to shortlist based on RFP responses and initial demos.
15. Responsible: RTM CoE + Procurement.
16. Accountable: CSO.
17. Consulted: IT (technical fit), Finance (cost envelopes, commercial models), Compliance/Legal.

18. CFO assurance: confirms that shortlisted options are within budget envelopes and meet minimum control requirements.

19. Checkpoint 4 – Technical due diligence and reference checks

20. Technical due diligence:
    • Responsible: IT evaluation team.
    • Accountable: CIO.
    • Consulted: Vendor, RTM CoE.
21. Reference checks (adoption, leakage, claim TAT, data quality):
    • Responsible: RTM CoE.
    • Accountable: CSO.
    • Consulted: Finance (questions on financial controls), IT.

22. CFO assurance: receives documented reference summaries, understands other CPGs’ leakage and claim experiences, and validates readiness to proceed.

23. Checkpoint 5 – Final scoring and recommendation

24. Scope: Consolidated vendor scores across functional, technical, financial, and risk dimensions, and a written recommendation.
25. Responsible: RTM CoE.
26. Accountable: RTM steering committee (CSO, CIO, CFO or delegate).
27. Consulted: Procurement (commercials and contractability), Legal, Regional Sponsors.

28. CFO assurance: participates directly in the scoring review, validates financial sections (TCO, payment milestones, leakage control capabilities), and co‑signs the final recommendation.

29. Checkpoint 6 – Contract and milestone approval

30. Scope: Contract terms, SLAs, milestone-based payments linked to adoption, data quality, and leakage KPIs.
31. Responsible: Procurement and Legal.
32. Accountable: CFO for financial commitments; CIO for technical clauses.
33. Consulted: CSO/RTM CoE, Vendor.
34. CFO assurance: confirms that payment milestones and exit clauses align with the approved business case.

This structure gives the CFO a clear audit trail: who defined needs, how vendors were evaluated, what reference evidence was gathered, and why the chosen vendor was selected, supported by signed checkpoint documents and scorecards.

For a CPG company digitizing trade promotion management and distributor claims within its RTM stack, financial sign-offs should be split so that Trade Marketing designs schemes, Sales/RTM Ops validates execution and eligibility, and Finance controls payout and auditability. The RACI must protect against leakage without turning Finance into a day-to-day bottleneck.

A balanced split typically looks like:

1. Scheme design and configuration
2. Responsible: Trade Marketing (mechanics, eligibility rules, target outlets/SKUs, timelines).
3. Accountable: Head of Trade Marketing or CSO (commercial intent, budget alignment).
4. Consulted: Finance (budget caps, allowable discount structures, compliance), Sales/RTM Ops (feasibility, field workflows), IT (system constraints).

5. Finance role: sets guardrails (maximum discount levels, accrual rules, accounting treatment) but does not approve each scheme configuration line‑by‑line.

6. Scheme approval and publication in RTM

7. Responsible: Trade Marketing to submit scheme with documented objectives and financial impact estimate.
8. Accountable: Jointly CSO and Finance controller for scheme portfolio; they approve total budget, high‑risk mechanics, and key parameters.
9. Consulted: RTM CoE/IT for configuration feasibility and control checks.

10. Finance role: approves scheme at aggregate level (budget, mechanics risk) rather than operational details, ensuring they are not a day‑to‑day choke point.

11. Claim submission and validation workflow

12. Responsible: Distributors submit claims via RTM; Sales/RTM Ops validates field execution (e.g., outlet coverage, volumes, proof of performance such as scan data or photo audit).
13. Accountable: Sales/RTM Ops for first‑level approval against scheme rules.
14. Consulted: Trade Marketing for interpretation of scheme intent; Finance for unusual or borderline cases.

15. Finance role: defines system-based validation checks (e.g., volume caps, date windows, cross‑checking with secondary sales) that run automatically, reducing manual review.

16. Financial approval and payout

17. Responsible: Finance operations to process approved claims and apply accounting entries.
18. Accountable: Finance controller or CFO delegate for final payout approval and overall trade‑spend control.
19. Consulted: Sales/RTM Ops only for exceptions or disputes; Internal Audit for spot checks.

20. Finance role: focuses on batch approval, exception management, and audit trails—not on every individual transaction, provided automated controls and sampling are robust.

21. Monitoring and post-event ROI analysis

22. Responsible: Trade Marketing and Sales Ops for evaluating scheme performance versus objectives (incremental volume, numeric distribution, leakage).
23. Accountable: CSO for commercial decisions on future schemes; Finance for validating ROI calculations.
24. Consulted: IT/Analytics for data and models.
25. Finance role: co‑owns the ROI narrative, confirming that reported scheme uplift aligns with actual spend and claims data.

By embedding Finance at the design and control-framework level, using automated checks and sampled reviews, and pushing operational eligibility checks to Sales/RTM Ops within the RTM system, the organisation maintains strong financial control without turning Finance into a perceived blocker for every scheme and claim.

For unified CPG RTM rollouts, leading firms use a dual-lane RACI where IT is accountable for architecture and integration integrity, while Sales Operations is responsible for day-to-day, field-facing change requests within pre-agreed guardrails. This preserves architectural control while allowing rapid iteration on beats, schemes, and UI flows.

Practically, a change board or RTM CoE screens CRs into two buckets: configuration-level (owned by Sales Ops) and architecture-impacting (owned by IT). Sales Ops is R for gathering requirements, impact analysis on field execution, and UAT; IT is A for approving anything that touches data models, integrations, security, or performance. Finance and Trade Marketing are usually C for changes that affect schemes, credit, or claim workflows.

• Field-facing config (forms, visit types, schemes, territories): Sales Ops = R/A, IT = C, Finance/Trade Marketing = C, Vendor = R (technical changes only).
• Core data model, integration, and performance: IT = A/R, Vendor = R, Sales Ops = C, Finance = C for financially relevant objects.
• Change intake and prioritisation: RTM CoE or Program Manager = A, Sales Ops and IT = R for their lanes, all others = C/I.

Most organizations encode this in a simple CR SOP: routing rules, decision SLAs, and a one-page matrix shared with regions so that Sales does not bypass IT for structural changes, and IT does not block low-risk, configuration-only tweaks.

Avoiding “orphaned” adoption typically requires making the RTM CoE accountable, Regional Sales Managers responsible for on-the-ground execution, and HR responsible for policy levers and data inputs. The RTM CoE becomes the single owner of onboarding, training design, and adoption tracking, with field and HR as enablers.

For an Indonesia SFA rollout, user onboarding and training can be structured so that the RTM CoE is A for the playbook, learning paths, and adoption KPIs; Regional Sales Managers are R for ensuring reps attend training, complete checklists, and meet first-30-day usage targets; and HR is R for maintaining the master roster, mapping IDs to employees, and embedding SFA usage into performance and incentive policies. IT is typically C for access provisioning and support.

• User onboarding (ID creation, role mapping): RTM CoE = A, IT = R, HR = R (roster accuracy), RSMs = C.
• Training (content, schedule, completion): RTM CoE = A/R (content and reporting), RSMs = R (attendance enforcement), HR = C (LMS integration).
• Adoption tracking (KPIs, escalations): RTM CoE = A/R for dashboards and weekly reviews, RSMs = R for coaching low adopters, HR = C to link to appraisal and incentives.

This model works when adoption metrics (e.g., call compliance, daily logins) are published per region and explicitly referenced in RSM scorecards, so responsibility cannot be quietly pushed back to “the system” or HR.

When Procurement leads RTM sourcing in Indian FMCG firms, a robust RACI gives Procurement accountability for commercial discipline, IT accountability for technical fit, and Sales accountability for business fit, with a cross-functional committee owning the final vendor recommendation. This reduces the risk of a three-way stalemate.

Procurement is generally A for the sourcing process: RFP, evaluation framework, commercial negotiations, and contract terms. Sales or RTM Operations is A for defining business requirements and assessing usability, coverage capabilities, and trade-promotion fit. IT is A for architecture, security, integration feasibility, and scalability. Finance is C for ROI, budget, and TCO; Legal is C for risk and compliance.

• Business fit scoring: Sales/RTM Ops = A/R, Procurement = R (process), IT/Finance = C.
• Technical due diligence: IT = A/R, Procurement = R, Vendor/SI = R (evidence), Sales = C.
• Commercial evaluation & contracting: Procurement = A/R, Finance = C, Legal = C, Sales/IT = C.

To avoid deadlock, many enterprises establish an RTM selection committee chaired by the CSO or a transformation lead, who is A for the final consolidated recommendation to the CFO/CEO. The committee signs a short decision memo summarizing each function’s assessment so that Procurement cannot be isolated as the only decision-maker.

In multi-country RTM standardization across Southeast Asia, leading enterprises distinguish global versus local decisions by assigning a central RTM CoE or Global Process Owner as accountable for core models and KPIs, while country teams are accountable for localized schemes and coverage rules within that framework. This prevents fragmentation while allowing market-specific flexibility.

Global is typically A for data models (outlet, SKU, hierarchy), standard KPIs (numeric distribution, strike rate, fill rate, trade-spend ROI), common workflows (order-to-cash, claims), and integration patterns with global ERP. Country teams are A for local scheme types, retailer segmentation within global taxonomy, route design, and execution tactics, with Global as C to ensure alignment.

• Global decisions (non-negotiable): RTM CoE/Global Process Owner = A, Global IT = R, Country Sales/IT = C.
• Local decisions (within guardrails): Country Sales/Trade Marketing = A/R for schemes, segmentation, and beats; RTM CoE = C, Country Finance = C for spend.
• Change requests impacting global standards: RTM CoE = A, Global IT = R, Affected country leads = C.

Operationally, many firms enforce this via a global design authority that must sign off any local change affecting core objects or KPIs, plus a configuration catalog that clearly tags each parameter as global-controlled or country-controlled, avoiding ad-hoc local overrides in the RTM platform.

For organizations new to governance, a starter RTM RACI should stay very simple: name one Program Owner accountable overall, then clearly assign responsibility for a small set of recurring decisions such as configuration changes, distributor onboarding, and scheme approvals. Overly detailed matrices usually fail in emerging-market field realities.

A pragmatic template defines 5–7 key decisions and maps them to 4–5 roles: Program Owner, Sales/RTM Ops, IT, Finance, and Country Manager. For each decision, only one A is allowed, one or two R, and a short list of C. Junior and middle managers can then use it as a rule-of-thumb: who to call, who can approve, and who must be informed.

• Example core decisions: (1) Pilot design, (2) Go-live approval, (3) Distributor onboarding, (4) Scheme launch, (5) Config changes, (6) Incident resolution, (7) KPI changes.
• Example role mapping: Program Owner = A for (1–5); Sales Ops = R for (1,3,4,5); IT = R for (1,2,5,6); Finance = R for (2,4,7); Country Manager = A for (2,3,4) in their market.

Printing this on a single slide, sharing it in kick-offs, and attaching it to SOPs is usually enough to embed basic governance without slowing daily operations.

In large CPG RTM vendor selections, a robust decision flow assigns Sales or RTM Ops accountability for business evaluation, IT accountability for technical due diligence, Procurement accountability for commercial closure, and an executive steering group accountability for the final vendor choice. This structure prevents deals from stalling between business sign-off and contracting.

Typically, Sales/RTM Ops is A for functional fit and pilot outcomes, with R for drafting business requirements and scoring field usability, trade-promotion features, and coverage capabilities. IT is A for technical fit—architecture, integration, security—and runs POCs and reference checks. Procurement is A for commercial evaluation: pricing, contract terms, and compliance with sourcing policy. Finance is C for ROI and budget approval. A CSO- or CXO-led steering committee is ultimately A for the consolidated vendor decision, based on inputs from Sales, IT, and Procurement.

• Evaluation phase: Sales/RTM Ops = A/R for business fit; IT = A/R for technical fit; Procurement = R for process; Finance = C.
• Technical due diligence: IT = A/R, Vendor/SI = R, Procurement = C, Sales = C.
• Commercial approval & contracting: Procurement = A/R, Finance = A for budget, Legal = R, Sales & IT = C.

Many enterprises formalize this via a vendor selection memo signed by Sales, IT, and Procurement, then submitted to the steering committee or CFO for final approval, closing the typical “no-owner” gap.

For mid-sized CPGs digitizing RTM in Africa, concrete milestone sign-offs tied to named functional approvers create discipline and reduce blame games. Each key go/no-go point should have exactly one accountable owner and clear responsible contributors.

Typical milestones include: (1) master data readiness, (2) first successful ERP–RTM sync, (3) pilot start, (4) pilot exit, (5) country go-live, and (6) adoption stabilization. Sales/RTM Ops, IT, and Finance each take accountability for different gates, with the Country Manager or Program Owner endorsing overall go/no-go.

• Master data freeze (basic outlet/SKU set): Sales/RTM Ops = A/R, IT = R for loading and validations, Finance = C, Country Manager = I.
• First successful ERP sync (primary/secondary sales, inventory, tax): IT = A/R, Vendor/SI = R, Finance = C for reconciliation, Sales Ops = C.
• Pilot start approval: Program Owner = A, Sales Ops = R, IT = R, Finance = C, Country Manager = C.
• Pilot exit (minimum adoption and stability metrics): Program Owner = A, Sales = R for field metrics, IT = R for system stability, Finance = R for preliminary ROI/uplift checks.
• Country go-live: Country Manager or CSO = A, Sales Ops = R, IT = R, Finance = C, HR = C for training completion.
• Adoption threshold (e.g., 80% active users for 4–6 weeks): Sales Ops = A/R, IT = R (monitoring), RSMs = R (coaching), Finance = I.

Documenting these milestones and owners in the RTM rollout plan, and reviewing them at each steering-committee meeting, anchors accountability as the program scales.

For consolidating multiple SFA/DMS tools into a single RTM platform, a robust cutover RACI assigns IT accountable for technical migration and rollback capability, Operations/RTM CoE accountable for process readiness and SOPs, and regional sales managers responsible for frontline risk assessment—with explicit authority to recommend delaying cutover based on field readiness criteria.

IT is responsible for data migration mapping, test cycles, performance checks, and integration with ERP, tax, and reporting systems, and is accountable for having a tested fallback/rollback plan. RTM Operations is responsible for updated processes (order capture, claims, returns), training completion, support playbooks, and is accountable for asserting that “day in the life” processes can run end to end on the new platform.

Regional sales managers are responsible for validating field readiness: app performance in their territories, offline reliability, distributor understanding, and basic usage during pilot. A good pattern is a formal “go/no-go” checklist where regional sales managers sign off on readiness metrics (training coverage, minimum usage, incident rates), and although final go-live decision sits with an RTM steering committee, regional leaders are explicitly consulted and can escalate if local risk is high. The RTM steering committee (often CSO as accountable, with CIO and Head of Distribution consulted) makes the final decision, based on evidence rather than top-down pressure alone.

In politically sensitive environments, an RTM steering committee works best when the CSO, CFO, and CIO have explicitly defined decision rights and a shared RACI across scope, budget, and rollout pacing, documented in minutes and charters so no one can later claim they “were not informed.” The RTM CoE lead or Head of Distribution is often accountable for day-to-day governance and for surfacing decisions to the committee.

Scope changes (new modules, markets, or major features) typically fall with CSO as accountable for commercial justification, with CFO and CIO consulted on budget and architecture impact. Budget reallocations see CFO as accountable for approving spend changes within board-approved envelopes, with CSO responsible for demonstrating ROI or risk mitigation and CIO responsible for validating technical feasibility and vendor impact.

Rollout pacing decisions—slowing, accelerating, or pausing waves—are often owned collectively but with clear roles: CSO is accountable for sales impact, Head of Distribution is responsible for operational readiness signals, CFO is consulted on revenue and capex implications, and CIO is responsible for confirming that systems and support can handle the pace. Every steering committee meeting should end with a short written decision log listing who decided what, who was consulted, and who was informed; this simple discipline is the main defense against later political revisionism.

For a mid-size FMCG digitizing secondary sales, the role most effective as single point of accountability for RTM vendor selection and rollout sign-offs is typically the Head of Sales/CSO or the Head of Distribution/RTM Operations reporting into Sales, not the CFO. This concentrates ownership with the function that lives with day-to-day consequences.

Sales leadership is closest to coverage, distributor relationships, and field execution, and can judge whether the tool truly improves numeric distribution, fill rate, and scheme execution. Making Sales formally accountable means they own both the benefits and the disruption cost, which reduces the tendency to push risk back onto Finance or IT after go-live.

The CFO’s comfort then comes from being formally consulted and often approving at key financial gates—business case validation, contract sign-off parameters, and go-live only after reconciliation and compliance checks meet agreed thresholds. But the CFO is explicitly not accountable for functional choices or adoption; that responsibility sits with the Sales-side sponsor who signs off that the system is usable, adopted, and aligned to RTM processes.

For cross‑functional RTM transformation, a simple but effective structure is a steering committee chaired by the CSO or Country GM, with CFO and CIO as co‑owners of risk, and a named RTM Champion reporting into Sales or RTM Ops. The RACI should give the champion clear mandate to run the process while the committee provides political cover and arbitration.

Steering Committee Structure
Actors on committee: CSO / Country GM (Chair), CFO, CIO/CDO, Head of RTM/Distribution, HR Head, Procurement Head, sometimes Head of Trade Marketing.

• Mandate: approve scope, budgets, timelines; resolve cross‑functional conflicts; own final go/no‑go.
• Cadence: monthly during selection, bi‑weekly during pilot and early rollout.

RACI – RTM Champion Role
- R:
- Consolidate requirements from Sales, Ops, Finance, IT, HR.
- Coordinate RFP, demos, pilots, and training plans.
- Maintain risk register and action logs.
- A: RTM Champion for day‑to‑day program delivery within agreed scope and budget.
- C: Steering committee (for directional choices, escalations).
- I: Country leadership outside the program.

RACI – Vendor Selection
- R: RTM Champion and Procurement (RFP, evaluation matrix, reference checks).
- A: CSO / Steering Committee
- C: CFO (ROI and affordability), CIO (architecture, security), HR (if incentives and org structure are impacted), Trade Marketing (TPM needs).
- I: Field and distributor reps.

RACI – Contract Negotiation
- R: Procurement
- A: CFO (financial terms) + Procurement Head (contract risk)
- C: Legal, CIO (SLAs, uptime, data), RTM Champion (practical SOW scope)
- I: CSO.

RACI – Pilot Execution & Rollout Training
- R: RTM Champion and RTM Ops for pilots; HR for training frameworks and change‑management communications.
- A: Head of RTM/Distribution
- C: Regional Sales Managers, IT (environment readiness), Vendor.
- I: Steering committee (via highlight reports).

RACI – Go/No‑Go & Expansion
- R: RTM Champion prepares decision pack with KPIs: adoption rates, fill‑rate improvement, claim‑TAT, leakage, incident logs.
- A: Steering Committee (CSO/Country GM, CFO, CIO)
- C: HR (incentive changes), Ops, Finance controllers.
- I: All stakeholders.

This model gives the champion operational freedom but shields them from personal blame by making all pivotal decisions collective and minuted at the steering committee level.

In RTM platform vendor selection, Procurement needs a RACI that shows a traceable, consensus‑based process: business and RTM Ops own functional scoring, IT owns security and architecture, and Procurement plus Finance own commercial decisions. Voting rights and weights should be documented upfront.

RACI – Functional Demo Scoring
Actors: RTM Ops, Sales, Trade Marketing, Finance, IT, Procurement.

• R: RTM Ops (DMS, distributor processes), Sales & Trade Marketing (SFA, TPM, perfect store) for scoring use‑cases against checklists.
• A: CSO or Head of Sales for functional fit.
• C: Finance (claims, trade‑spend workflows), IT (UX, offline, performance), Procurement (process adherence).
• I: CFO, CIO.

Common practice: - Each function gets weighted criteria (e.g., Sales 40%, RTM Ops 25%, Finance 15%, IT 20%), agreed in advance.
- Scores and comments are captured centrally by Procurement.

RACI – Security & Technical Review
- R: IT Security and Architecture teams for penetration risk, data residency, integration patterns, and scalability checks.
- A: CIO / CDO
- C: RTM Ops (operational implications), Vendor (documentation, certifications, SLAs)
- I: CSO, Procurement.

A vendor cannot progress without at least a minimum technical threshold (pass/fail gates) even if functional scores are high.

RACI – Commercial Negotiation & TCO
- R: Procurement for price benchmarking, payment terms, risk clauses, and negotiation.
- A: CFO for overall spend and TCO approval; Procurement Head for contractual risk.
- C: CSO (commercial priorities), CIO (hidden cost of integrations or customizations), Legal (liability, IP, data protection).
- I: RTM Ops.

Final Decision & Voting Rights
- R: Procurement consolidates evaluation report (functional, technical, commercial) with a recommendation.
- A: Steering Committee (CSO, CIO, CFO), usually requiring at least two of three sign‑offs.
- C: RTM Ops, Trade Marketing, Country GMs where applicable.
- I: Board or regional HQ.

Procurement demonstrates defensibility by maintaining: - A scoring matrix with contributor names and timestamps.
- A decision memo recording weights, any exceptions, and why the chosen vendor was selected despite trade‑offs.

During RTM pilots, the cleanest structure is to give a single Pilot Owner accountability for overall success, while Operations, Sales, and Finance hold responsibility in their respective domains. This keeps process, performance, and ROI clearly owned, yet avoids a vacuum when trade-offs are needed.

Operations (RTM Ops or Sales Ops) is typically R for process design: journeys, order flows, claim handling, and distributor touchpoints. Sales is R for defining performance metrics such as numeric distribution uplift, strike rate, lines per call, and territory productivity targets. Finance is R for baselining and measuring ROI, including leakage reduction and claim TAT. A cross-functional Pilot Owner—often the Head of Distribution/RTM CoE or a Transformation Lead—is A for deciding whether the pilot meets combined success criteria and for making the vendor recommendation.

• Pilot scoping & hypothesis: Pilot Owner = A, Operations = R, Sales = R, Finance = R, IT = C.
• Pilot execution: Operations = R for workflows and issue resolution, Sales = R for field adoption, IT = R for stability, Finance = C.
• Evaluation & vendor recommendation: Pilot Owner = A/R for summary, Sales = C, Operations = C, Finance = C, IT = C.

This structure works best when pilot scorecards explicitly show metrics by owner (process, performance, ROI), but only the Pilot Owner is authorized to declare pass/fail and propose next steps to the steering committee.

For RTM pilots in fragmented general trade, governance works when Sales is responsible for commercial hypotheses, IT is responsible for technical stability, Finance is responsible for uplift validation, and a single Program Owner is accountable for overall pilot success and decisions when results are ambiguous. This avoids endless debate over mixed metrics.

Sales or RTM Ops is typically R for defining pilot objectives: target outlets, expected changes in numeric distribution, strike rate, and lines per call, plus scheme designs. IT is R for integrating RTM with ERP and DMS, ensuring offline reliability, and monitoring technical incidents. Finance is R for establishing baselines, constructing control groups where possible, and validating uplift, leakage reduction, and claim TAT improvements. The Program Owner—often Head of Distribution or a Transformation Lead—is A for overall design, execution oversight, and go/no-go decisions.

• Pilot design: Program Owner = A, Sales = R, IT = R, Finance = R, Country Management = C.
• Pilot execution: Sales/RTM Ops = R for field execution, IT = R for stability, Finance = C, Vendor/SI = R.
• Evaluation & decision: Program Owner = A/R for recommendation, Sales = C (commercial view), Finance = C (ROI view), IT = C (technical feasibility), CSO/CFO = I or A for final sign-off.

When metrics are ambiguous, the RACI makes it clear that the Program Owner must call the decision, based on structured inputs, instead of decisions being deferred indefinitely.

For van‑sales RTM pilots, minimum governance should include: a clear RACI for incidents and data issues, a sign‑off matrix for pilot changes and go‑live, an escalation chart with time‑bound SLAs, and a simple issue‑triage SOP. These artifacts prevent confusion when outages or discrepancies inevitably occur.

1. Sign‑Off Matrix (before pilot go‑live)
Actors: RTM Ops, Sales, IT, Finance, Vendor.

RACI elements: - Pilot scope and success KPIs (coverage, strike rate, fill rate, error thresholds):
- R: RTM Ops & Sales
- A: CSO / Sales Director
- C: Finance (ROI, costs), IT (feasibility), Vendor.
- Technical readiness (connectivity tests, offline behaviour, integrations):
- R: IT + Vendor
- A: CIO/IT Head
- C: RTM Ops, Sales.
- Training completion (drivers/reps, supervisors, distributor staff):
- R: RTM Ops, Vendor
- A: Head of RTM
- C: Sales, HR.
This becomes a checklist signed by each owner.

2. Escalation Chart for Outages & Critical Incidents
Tiers & RACI: - Tier 1 – Field Support (within 15–30 minutes)
- R: Local support desk or RTM Ops first‑line support; Vendor L1.
- A: RTM Ops Lead.
- C: IT (if infrastructure suspected), Sales Supervisor (for local workaround instructions).
- Tier 2 – Application/Integration Incident (within 2–4 hours)
- R: Vendor L2/L3 and IT integration team.
- A: IT Incident Manager.
- C: RTM Ops, Vendor PMO.
- I: Regional Sales Manager.
- Tier 3 – Major Outage / Revenue Impact (same day)
- R: IT + Vendor joint taskforce.
- A: CIO for technical resolution; CSO for commercial decisions (e.g., shift to manual orders).
- C: Finance (impact, reconciliations), RTM Ops, Country GM.
- I: Internal Audit if data loss.

3. Issue Triage SLA & Ownership
Define categories and who is Responsible: - Data discrepancies (stock, invoicing, claim mismatch):
- R: RTM Ops to investigate and coordinate with Vendor and Finance.
- A: Head of RTM.
- Usability or training gaps (rep not following SOP):
- R: Sales Supervisors / Regional Sales Managers.
- A: Sales Director.
- Configuration errors (wrong price list, scheme rule):
- R: RTM Ops + Vendor.
- A: RTM Ops Head.

A one‑page Pilot Run Handbook that includes the RACI table, escalation contacts with response times, and sample workaround instructions (e.g., offline order capture templates) is usually enough to keep ownership clear in high‑pressure moments.

When running parallel RTM pilots with two vendors, CPGs get the cleanest outcome by agreeing upfront on a common RACI and objective evaluation criteria: RTM Ops and Sales are responsible for operational metrics and adoption, Finance for leakage and claim KPIs, IT for integration stability, and a steering committee is accountable for the final vendor choice.

RACI – Pilot Evaluation Governance
Actors: RTM Ops, Sales, Finance, IT, Procurement, Vendor A, Vendor B, Steering Committee.

• R (pilot design, KPI definitions, baseline data): RTM Ops + Sales Ops.
• A: CSO / Sales Director
• C: Finance (trade‑spend, leakage measures), IT (data capture feasibility), Procurement (documentation), Vendors (effort estimates).

• I: Country GM.

• R (ongoing data collection and reporting from both pilots): RTM Ops / Analytics.

• A: Head of RTM/Distribution
• C: Finance, IT, Sales.
• I: Steering Committee.

Objective Decision Criteria (agreed pre‑pilot)
At minimum: - Adoption and usability:
- Field adoption rate (active users, on‑time sync, journey‑plan adherence).
- Distributor engagement (usage of DMS, claim submission via system vs manual).
- R: RTM Ops; A: Sales Leadership.

• Operational uplift:
• Changes in fill rate, numeric distribution, strike rate vs baseline.
• Van‑sales productivity (lines per call, drop size).

• R: Sales Ops; A: CSO.

• Leakage and claims:

• Claim‑leakage reduction (% of claims rejected or adjusted).
• Claim TAT and auditability (digital evidence completeness).

• R: Finance; A: CFO or Commercial Finance Head.

• Integration and stability:

• Uptime, sync failures, integration incident volume.
• Effort for changes and support responsiveness.
• R: IT; A: CIO.

Procurement is: - R for consolidating results into a formal evaluation report and ensuring both vendors were treated consistently.
- A for process integrity (RFP rules followed, no bias).
- C: RTM Ops, Sales, Finance, IT.

Final Vendor Selection RACI
- R: RTM Ops and Procurement for presenting side‑by‑side comparison, including narrative of trade‑offs.
- A: Steering Committee (CSO, CFO, CIO; sometimes Country GM) based on the pre‑agreed criteria and weights.
- C: Country Sales/Ops, Finance controllers, IT.
- I: Vendors and broader organization.

Document all of this in a Pilot Evaluation Charter before go‑live to avoid political challenges later (“my region is different” or “IT blocked my preferred vendor”).

Across African RTM programs, a two-tier governance model works best: RTM Operations is accountable for distributor onboarding, DMS integration, and ongoing performance, while local Sales teams are responsible for commercial justification and relationship inputs. This keeps control with Operations without sidelining market realities.

Decision flow typically runs as follows: local Sales (and possibly Country Management) raises a distributor onboarding proposal with volume, coverage, and risk rationale; RTM Operations evaluates operational fit, DMS readiness, and financial hygiene; Finance reviews credit and terms; IT reviews integration feasibility; and a small RTM steering group signs off. RTM Operations is A for approving onboarding and integration go-live; local Sales is R for proposals, commercial KPIs, and day-to-day relationship; IT is R for integration build and testing; Finance is R for credit checks and claim settlement processes.

• Distributor onboarding approval: RTM Operations = A, Local Sales = R, Finance = C/R (credit), IT = C, Legal = C.
• DMS integration scope & go-live: IT = R, RTM Operations = A, Vendor/SI = R, Local Sales = C.
• Periodic performance and compliance reviews: RTM Operations = A/R for scorecards, Local Sales = R for corrective action, Finance = C, Country MD = I.

High-performing firms codify this in a standard distributor lifecycle SOP with thresholds (minimum volume, digital readiness) and clearly named approvers so borderline cases do not stall or get pushed through informally.

For prescriptive AI in RTM control towers, governance works best when a Data Science or Analytics CoE is accountable for model integrity, Sales is responsible for business acceptance and override rules, and Finance is accountable for KPI definitions used in financial reporting. This triangulation avoids finger-pointing when forecasts or ROI are questioned.

Data Science is typically A for model design, validation, and versioning; R for documenting assumptions, performance, and change logs. Sales is R for defining acceptable recommendation behaviors (e.g., outlet targeting limits, scheme eligibility rules), approving override workflows, and confirming usability in the field. Finance is A for the final definition and sign-off of financial KPIs (promotion ROI, uplift, leakage, trade-spend ratios) used in board or audit-facing reporting.

• AI model changes (features, algorithms, thresholds): Data Science/Analytics = A/R, Sales = C, Finance = C.
• Override rules & business guardrails: Sales/RTM Ops = A/R, Data Science = C, Finance = C for any financial impacts.
• Official KPI definitions and sign-off: Finance = A, Sales = C/R for target setting, Data Science = R for computation methodology.

A lightweight AI governance forum, meeting regularly, should maintain a model release calendar, approve changes, and ensure that any revisions that alter financial KPIs trigger explicit Finance re-approval before numbers appear in executive dashboards.

For offline-first RTM apps where uptime is critical, incident governance works best when internal IT is accountable for overall incident response, the vendor is responsible for root-cause fixes, and Sales Operations is responsible for business impact assessment and communication to the field. Clear RACI and escalation tiers prevent confusion when outages hit.

Internal IT is usually A for incident management: triage, severity classification, and coordination, even if much of the work is outsourced. The vendor or system integrator is R for identifying and resolving application defects, sync issues, and performance bottlenecks within SLA. Sales Ops or RTM CoE is R for translating technical incidents into operational guidance (e.g., temporary paper orders, re-synchronization instructions) and for tracking business impact metrics like missed calls or order backlog.

• Monitoring & first-line triage: IT (or managed services) = A/R, Vendor = R for technical diagnosis, Sales Ops = C.
• Fixes & releases: Vendor/SI = R, IT = A for acceptance and deployment, Sales Ops = C for UAT on field scenarios.
• Communication & workarounds: Sales Ops/RTM CoE = A/R, RSMs = R for enforcement, IT/Vendor = C.

A simple escalation matrix—per severity level—with named contacts in IT, Vendor, and Sales Ops, plus measured incident SLAs, ensures that when sync failures occur, everyone knows who leads, who informs, and how decisions on rollbacks or hotfixes are taken.

The most practical way to make RTM RACI politically defensible is to document it as a short governance charter plus visual decision-flow diagrams, then over-communicate this via town halls, training decks, and distributor-facing SOPs. Clarity matters more than length.

Leading manufacturers create a 2–3 page “RTM Governance Playbook” that includes: a single RACI table for vendor selection, pilot, and rollout; simple swim-lane diagrams for key decisions (e.g., distributor onboarding, scheme approval, go-lives); and a list of named role owners (not just functions). This document is endorsed by the CSO and CIO, giving it political weight, and is attached to SFA/DMS training for Regional Sales Managers and shared with priority distributors as part of onboarding packs.

• Use one RACI chart per phase (selection, pilot, rollout) with clear A for each decision.
• Publish the governance playbook on internal portals, reference it in steering-committee minutes, and include a slide in every RTM update to remind stakeholders of sign-off rules.
• For distributors, provide a simplified one-page RACI that shows who they should contact, who approves claims or system changes, and who resolves disputes.

When these materials are consistently referenced in meetings and emails, the RACI becomes a shared norm rather than a static template.

In sensitive distributor onboarding, the RACI that works best makes the Head of Distribution accountable for overall distributor readiness and adoption, regional sales managers responsible for field-level engagement and pushback handling, and the RTM vendor responsible for enablement assets, training, and product-level fixes—but never as the owner of distributor relationships.

Typically, the Head of Distribution/RTM Operations is accountable for the onboarding plan, selection of pilot distributors, alignment of commercial policies (credit, schemes, SLAs), and final sign-off on whether a distributor is considered “live.” Regional sales managers are responsible for day-to-day communication with distributors, organizing trainings, ensuring attendance, gathering feedback, and doing the first line of pushback handling on topics like perceived complexity, workload, or incentive impact.

The RTM vendor is responsible for delivering structured training (classroom, remote, job aids), configuring environments, and supporting “floor-walks” in the early weeks. For escalations where a key distributor refuses adoption, the Head of Distribution is accountable for the commercial decision (exceptions, phased adoption, or replacement), with regional sales managers responsible for presenting ground reality and alternatives, and the vendor consulted for simplifying workflows or adding temporary workarounds. This prevents the vendor being blamed for structural distributor resistance and keeps commercial decisions with internal leadership.

In multi-country RTM deployments, severe-incident RACI works when IT and the RTM vendor are responsible for immediate technical response, the RTM CoE/Operations is accountable for business continuity decisions, and CSO/CFO are informed via structured escalation for high-impact issues such as quarter-close outages or invoice-impacting mismatches.

For mobile app outages on peak days, IT is responsible for incident triage, vendor coordination, and communication on recovery timelines; the RTM vendor is responsible for root-cause analysis and patches; RTM Operations is accountable for invoking contingency processes (manual order-taking, simple Excel capture) and for deciding priority geographies or channels. For ERP mismatches affecting invoicing, IT and vendor are responsible for isolating interfaces and halting further corrupt syncs; Finance is accountable for deciding whether to pause invoicing or issue provisional invoices, and for signing off on any manual corrections.

For systemic claim-calculation errors, RTM Operations and Finance share accountability: RTM Operations is accountable for identifying impacted claims and triggering re-calculation; Finance is accountable for approving remediation and communicating with auditors. A clear escalation ladder—L1 country IT/RTM Ops, L2 regional RTM CoE and vendor leadership, L3 global CIO/CSO/CFO for major financial or reputational risk—prevents confusion about who can declare a “major incident” and who can authorize downtime, rollbacks, or exceptional manual workarounds.

In multi‑country RTM deployments, governance works best when the global RTM CoE is accountable for standards, core design, and vendor framework agreements, while local Sales and Operations are accountable for localization choices, adoption, and go‑live readiness in their markets. The CoE defines the “rails”; countries decide how to run on them.

Typical RACI – Vendor Selection (global platform decision)
Actors: Global RTM CoE, Global IT, Global Procurement, Country Sales/Operations, Country IT, Finance.

• R (shortlist, evaluation framework, use‑cases): Global RTM CoE
• A (final vendor framework selection): Global RTM CoE + Global IT; often co‑signed by global CSO/CFO
• C: Global Procurement (commercials), Country Sales/Ops, Country IT, Finance
• I: Country GMs.

Global CoE usually owns: standard process blueprints, data model, integration principles, and minimum UX/MDM requirements. Global IT owns: security, cloud, integration and data‑residency policies.

Typical RACI – Localization Decisions (per country)
- R: Country RTM Lead / Sales Ops for business rules (schemes, discounts, channel structure), Country IT for local integrations (e‑invoicing, tax, local ERPs)
- A: Country Sales Director (commercial fit) + Country Operations/Distribution Head (execution feasibility)
- C: Global RTM CoE (guardrails, template reuse), Global IT (compliance with enterprise architecture), Finance/Tax (local statutory rules)
- I: Global Procurement.

A common pattern is a “template vs variance” matrix maintained by the CoE: - Items marked “Global Standard – no change” (e.g., data model fields, key KPIs, core SFA workflows) where CoE is A, countries C. - Items marked “Localized within guardrails” (e.g., scheme logic, assortment rules, journey plans) where Country Sales/Ops is A, CoE C.

Typical RACI – Rollout Sign‑offs (per country)
- R (UAT, training, cutover plan): Country RTM Lead, Country IT
- A (go‑live decision): Country GM + Country Sales Director
- C: Global RTM CoE (readiness checklist), Global IT (integration & security sign‑off), Finance (if trade promotions or claims are impacted)
- I: Global leadership.

To avoid “who has final say” conflicts: - Make the CoE accountable for standards and platform, but clearly state that country GMs are accountable for business outcomes and adoption, including the right to delay go‑live if readiness criteria are not met. - Encode these rules in a Global RTM Governance Charter: one page of principles, one RACI table, and a standard sign‑off form for each country wave.

For RTM modernization in Africa with offline‑first apps, the cleanest pattern is to make RTM Operations accountable for distributor onboarding and data quality, with Sales and IT in supporting roles. RTM Ops should own the operational discipline; IT owns tools and integrations; Sales owns relationship leverage.

RACI – Distributor Onboarding (day‑to‑day)
Actors: RTM Operations, Sales (Regional/Area Managers), Enterprise IT, Finance/Compliance, Vendor.

• R (onboarding execution: checklists, DMS setup, master data capture): RTM Operations
• A: Head of RTM Operations / Distribution
• C: Sales (to confirm assortments, credit limits, coverage), IT (access, device & connectivity prerequisites), Finance (GST/VAT, KYC)
• I: Vendor PMO.

Practical signals of RTM Ops ownership: - RTM Ops signs the “distributor live” checklist (master data loaded, opening stock captured, pricing configured, offline sync tested). - Distributor training is planned and tracked by RTM Ops (with vendor), not left to Sales alone.

RACI – Data Quality Governance (codes, hierarchies, secondary sales)
- R (daily/weekly monitoring and correction of distributor data): RTM Operations data steward(s)
- A: RTM Operations Head
- C: Sales (for outlet and territory changes), IT (for integration errors, sync failures), Finance (where data feeds claims or credit control)
- I: Country leadership.

A common failure mode is leaving master data “shared” between Sales and IT. To prevent that, most successful CPGs: - Create a named RTM Data Owner in Operations who maintains outlet, distributor, and territory masters.
- Give IT R for technical data pipelines (interfaces, jobs, backups) and A for data‑platform uptime, but never for commercial data accuracy.

RACI – Changes to Distributor Scope or Status
- R: Sales (business decision to appoint/terminate/resize)
- A: Sales Director / Country GM
- C: RTM Operations (system and process impact), Finance (credit, incentives), IT (access removal, routing changes)
- I: Vendor (for configuration).

Document these in a Distributor Lifecycle SOP: onboarding, data corrections, temporary suspensions, and exits, each with a one‑line RACI so disputes do not default to IT.

In TPM‑heavy RTM deployments, the most robust pattern is to make Trade Marketing responsible for scheme setup, Finance accountable for claim validation rules and payouts, and Sales accountable for commercial approval and dispute closure. Clear RACI around the scheme lifecycle reduces leakage and blame.

RACI – Scheme Design & Setup
Actors: Trade Marketing, Sales, Finance, RTM Ops, IT, Vendor.

• R (scheme mechanics, eligibility, KPIs): Trade Marketing
• A: Head of Trade Marketing / Channel Programs
• C: Sales (practicality, volume targets), Finance (budget caps, ROI thresholds), RTM Ops (system and process feasibility), IT/Vendor (config complexity)
• I: Country GM.

Scheme configuration in DMS/TPM/SFA is typically: - R: RTM Ops or dedicated TPM Ops team
- A: RTM Ops Head
- C: Trade Marketing (to confirm rules), IT/Vendor (tech constraints).

RACI – Claim Capture & First‑Level Validation
- R (data capture: invoices, scans, proof of performance): Distributors / Field Teams, monitored by RTM Ops
- A: RTM Ops for ensuring claims follow the configured workflow and have required digital evidence
- C: Sales (exceptions, relationship context), Trade Marketing (alignment with scheme intent)
- I: Finance.

RACI – Financial Validation & Payout
- R: Finance for numerical validation, audit checks, and reconciliation to ERP
- A: Finance Controller / Head of Commercial Finance
- C: Trade Marketing (approval that claimed outcomes match scheme design), RTM Ops (system reports, leakage analysis), Internal Audit (spot checks)
- I: Sales, Procurement (if third‑party agencies involved).

RACI – Dispute Resolution
- R: Sales (Account / Regional Managers) for discussing and resolving distributor disputes within agreed guardrails
- A: Sales Director or Country Sales Head
- C: Finance (financial implications), Trade Marketing (interpretation of scheme rules), RTM Ops (evidence reports, logs)
- I: Legal (only for escalated or litigated cases).

Two operational controls help: - A Scheme Dossier per major promotion, owned by Trade Marketing, capturing mechanics, budgets, and RACI, including who can approve exceptions.
- A Claims Governance Dashboard owned by Finance and RTM Ops, tracking leakage ratio, average claim TAT, and dispute volumes by region and distributor.

This structure leaves no ambiguity over who designs schemes, who validates money, and who faces the distributor on disputes.

Among FMCG peers in India and Indonesia, the de facto pattern is a cross‑functional vendor selection committee where Sales/RTM Ops, IT, Finance, and Procurement all have defined roles, but accountability usually sits with the CSO for business outcome fit and with the CIO for architecture and risk approvals. CSO‑led accountability is more common when the mandate is growth and coverage; CIO‑led when the project is part of a broader ERP or digital‑core initiative.

Typical Vendor Selection Committee RACI
Actors: CSO / Sales Leadership, Head of RTM/Distribution, CIO/IT, CFO/Finance, Procurement, Trade Marketing, Country Ops.

• Requirements & Use‑Case Definition
• R: Head of RTM/Distribution, Trade Marketing, Regional Sales
• A: CSO / Sales VP
• C: IT, Finance

• I: Procurement.

• Technical & Security Evaluation

• R: IT Architecture & InfoSec
• A: CIO / CDO
• C: RTM Ops, Vendor

• I: Finance, Procurement.

• Commercial Evaluation & Contracting

• R: Procurement (TCO, terms, risk)
• A: CFO (for major spends) plus Procurement Head
• C: CSO, CIO, Legal

• I: RTM Ops.

• Functional Demo Scoring & Fit‑for‑Purpose

• R: RTM Ops, Sales, Trade Marketing
• A: CSO / Sales VP
• C: Finance (for claims, rebates, ROI), IT (for UX and offline readiness feedback)
• I: Procurement.

Final Decision Patterns Observed
- In most emerging‑market FMCGs, the CSO (or Country Business Head) is effectively Accountable for the final choice, often co‑signing with the CFO. CIO holds veto power on non‑conformance to architecture or security but rarely leads the decision alone.
- In large multinationals where RTM is embedded in a global ERP or CRM program, the CIO or global IT may be listed as Accountable for platform selection, with CSO Consulted but still heavily influential.

A common compromise is a two‑key model: - CSO (or Head of Sales) and CIO must both sign the recommendation paper; Procurement and Finance confirm that process and budget criteria are met.
- If either CSO (business fit) or CIO (risk) refuses, the steering committee (including CFO) arbitrates.

Across India and Indonesia, this dual‑accountability model is now standard, with CSO‑led accountability slightly more prevalent where RTM directly touches a large field force and distributor base.

Where distributors resist DMS adoption, successful CPGs define RACI so RTM Operations owns onboarding and compliance governance, Sales owns relationship and commercial consequences, and Legal steps in only for escalated contractual enforcement. This avoids Sales and Ops passing the issue back and forth while the distributor remains non‑compliant.

RACI – Distributor Onboarding & Training
Actors: RTM Operations, Sales, Vendor, Finance, Legal.

• R (onboarding plan, system setup, data migration, training sessions): RTM Operations
• A: Head of RTM/Distribution
• C: Sales (for timing, resource alignment), Vendor (training content, hand‑holding), Finance (changes in claim and invoicing process), IT (access, devices)
• I: Legal.

Onboarding completion should have a checklist signed by RTM Ops and distributor management.

RACI – Ongoing Compliance Monitoring
(e.g., order capture in DMS, invoice generation, claim submissions) - R: RTM Ops (monitor compliance dashboards: DMS usage, data latency, manual invoices).
- A: RTM Ops Head
- C: Sales (for commercial context), Finance (if manual processes bypass agreed schemes or GST workflows)
- I: Legal.

RACI – First‑Level Compliance Escalation
(early signs of resistance or non‑usage) - R: Regional / Area Sales Managers for direct distributor conversations, using data provided by RTM Ops.
- A: Country Sales Director
- C: RTM Ops (evidence, training offers), Finance (impact on claims, credit), Vendor (extra support)
- I: Country GM.

RACI – Formal Non‑Compliance & Sanctions
(repeated refusal, manipulation, or fraud) - R: RTM Ops and Sales jointly to compile evidence (logs, reports, communications).
- A: Country Sales Director / Country GM for decisions on penalties, reduced incentives, or distributor replacement.
- C: Legal (contract terms and step‑wise notices), Finance (holdbacks on claims/discounts), Compliance/Audit.
- I: Vendor.

Legal should be Consulted when designing standard distributor agreements and addendums that mandate DMS usage, access to data, and audit rights. During daily operations, they remain Informed, only becoming Responsible for drafting formal notices or termination letters once Sales and RTM Ops escalate.

Embedding this RACI in a Distributor Compliance Policy and sharing it internally ensures everyone knows their actions and escalation timeframes when pushback appears.

For perfect‑store and photo‑audit programs, the most effective RACI puts regional managers clearly responsible for addressing field non‑compliance, with RTM Ops accountable for accurate rules, dashboards, and alerts. Head office intervenes only on repeated or structural issues, avoiding ad‑hoc firefighting.

RACI – Journey Plan & Perfect‑Store Rule Definition
Actors: Trade Marketing / Channel, RTM Ops, Sales Leadership, IT.

• R: Trade Marketing (KPIs, must‑sell SKUs, display rules), RTM Ops (translating into SFA configuration and scoring)
• A: Head of Sales / CSO
• C: Regional Sales Managers, IT (technical feasibility), Finance (if linked to incentives)
• I: HR.

RACI – Monitoring Compliance & Photo Audits
- R: RTM Ops / Control Tower team for generating daily/weekly reports on journey‑plan adherence, photo quality, and perfect‑store scores.
- A: RTM Ops Head for data accuracy and timeliness
- C: Regional Sales Managers, HR (if gamification/incentives used)
- I: Country Sales Director.

RACI – First‑Level Non‑Compliance Handling (field)
- R: Area Sales Managers / Regional Sales Managers for coaching, ride‑alongs, and corrective action plans for low‑compliance reps.
- A: Regional Sales Managers
- C: RTM Ops (root‑cause insights, e.g., app issues, beat design), HR (performance management guidelines)
- I: Trade Marketing (where display rules are consistently ignored).

RACI – Escalation Path for Persistent Non‑Compliance
Level 1 (single rep, short term): - R: ASM for coaching and written action plan.
- A: RSM.
- C: HR, RTM Ops.

Level 2 (pattern across region or resistance): - R: RSM for formal warning, potential realignment of territories or incentives.
- A: Country Sales Director
- C: HR (disciplinary framework), RTM Ops (system checks), Trade Marketing (re‑examining rules if impractical).

Level 3 (systemic issues: many reps, multiple regions): - R: RTM Ops to flag systemic problem to Steering Committee (e.g., app usability, unrealistic targets).
- A: CSO / Steering Committee
- C: HR, IT, Trade Marketing.
- I: Country GM.

To reinforce this, CPGs often: - Add journey‑plan adherence and perfect‑store KPIs into RSM and ASM scorecards.
- Define a short Field Non‑Compliance SOP in the SFA playbook: thresholds, time‑bound actions, and who escalates what, so head office only steps in when the regional chain has exhausted defined steps.

For serious RTM outages during peak periods, the most effective approach is a predefined escalation ladder where IT and the vendor are responsible for technical recovery, Sales leadership is accountable for commercial decisions and communication to the field and distributors, and a crisis coordinator manages cross‑functional updates. The RACI must be rehearsed, not invented mid‑crisis.

Tiered Escalation Path & RACI
Actors: Vendor Support, Internal IT, Sales Leadership, RTM Ops, Distributor Helpdesk, Finance, Comms.

Tier 1 – Detection & Initial Response (0–30 minutes)
- R: Monitoring tools / IT Service Desk and Vendor L1 support to detect and log incident; RTM Ops to confirm business impact (order capture failure, sync delays).
- A: IT Incident Manager
- C: RTM Ops Lead, Vendor PMO
- I: Sales Ops, Distributor Helpdesk.

Tier 2 – Major Incident Declaration (within 30–60 minutes)
Criteria: multiple regions unable to capture orders, or outage hits critical sales window. - R: IT Incident Manager to declare “major incident” and convene war room (IT + Vendor).
- A: CIO / Head of IT
- C: RTM Ops, Sales Ops, Vendor Support Lead.
- I: CSO, CFO, Country GM.

Sales Ops and RTM Ops together define immediate workarounds (manual order forms, Excel, WhatsApp) and instruct field teams via pre‑drafted playbooks.

Tier 3 – Business Communication & Distributor Handling
- R: Sales Leadership (CSO/Regional Heads) for messaging to field and distributors: what to do, expected recovery times, and how incentives/claims will be protected.
- A: CSO / Country GM
- C: RTM Ops (status), IT (ETA, scope), Finance (implications on billing and credit), Corporate Communications (tone, if needed).
- I: Distributor Helpdesks.

Distributor helpdesks are: - R for capturing distributor issues, guiding them through workarounds.
- A to the Head of Distribution/RTM Ops.
- C with Sales and IT for any localized decisions.

Root Cause Analysis & Prevention (Post‑Incident)
- R: Vendor and IT jointly for technical RCA and corrective actions.
- A: CIO for technical closure; Head of RTM Ops for process closure (e.g., better offline policies, revised SLAs).
- C: CSO, Finance (any financial remediation such as credit notes or incentive protections), Internal Audit.
- I: Distributors, via a simplified incident summary.

Before go‑live, codify this in a Major Incident SOP: - Named roles and contacts.
- Time‑boxed SLAs for each tier.
- Criteria for switching to manual processes and who authorizes it.
This minimizes blame‑shifting and speeds coordinated response when outages hit peak seasons.

When introducing new KPIs such as Perfect Execution Index and cost‑to‑serve per outlet, HR should be accountable for embedding them into performance and incentive frameworks, Sales should be accountable for coaching and target‑setting, and RTM Operations should be responsible for metric definitions, data integrity, and dashboards. This balance reduces resistance and confusion.

RACI – KPI Definition & Calculation Logic
Actors: RTM Ops / Analytics, Sales Leadership, Finance, HR, IT.

• R: RTM Ops / RTM Analytics for defining formulas, data sources, and thresholds (e.g., what counts towards PEI; cost drivers per outlet).
• A: Jointly by Head of RTM and Sales Director, with Finance sign‑off for financial KPIs.
• C: HR (implications on rewards), IT (data feasibility).
• I: Regional Sales Managers.

RACI – Incentive Design & Policy Updates
- R: HR and Sales Compensation team for mapping new KPIs into bonus/commission schemes and updating policy documents.
- A: HR Head with CSO / Sales Director
- C: Finance (cost of incentives, fairness), RTM Ops (ensuring KPIs are controllable by reps), Legal (employment law if needed).
- I: Regional Sales Managers and field reps.

RACI – Coaching, Performance Reviews, and Adoption
- R: Regional Sales Managers / ASMs for using new KPIs in one‑on‑ones, coaching, and performance appraisals.
- A: Sales Leadership
- C: HR (frameworks, training for managers), RTM Ops (dashboards and field‑friendly views), Training/L&D.
- I: Country GM.

RACI – Data Quality and System Performance for New KPIs
- R: RTM Ops & IT for ensuring data is timely and correct, and dashboards function.
- A: Head of RTM CoE; CIO for platform availability.
- C: Sales (feedback on usability), Finance (spot checks), Internal Audit (if used for pay).
- I: HR.

Best practice is a three‑step rollout: 1) “Dry run” KPIs visible but not tied to pay; RSMs coach with them.
2) Joint HR + Sales clinics to address perceived unfairness or data issues.
3) Only then, formal inclusion in incentives, with a clear RACI‑backed policy.

This staged approach, with HR visibly owning the fairness dimension, helps field teams accept new metrics as credible rather than punitive.

In markets with high outlet churn, a robust RACI for outlet census and beat redesign makes RTM Operations or a central RTM CoE Accountable for the overall process and standards, Sales teams Responsible for field-level validation and decisions, and distributor supervisors Responsible for proposing changes and ensuring local compliance. This turns route rationalization into a recurring, governed cycle instead of ad-hoc tweaks.

Most CPGs that handle churn well run quarterly or semi-annual outlet-census waves where distributor supervisors and sales reps are Responsible for capturing new, closed, and moved outlets, with geo-tags and classifications. Regional sales or RTM ops teams are Responsible for reviewing this input, flagging duplicates, and proposing beat changes based on drop size, strike rate, and cost-to-serve thresholds. The central RTM CoE is Accountable for approving final beat designs, updating the official outlet universe, and publishing effective dates for new routes into SFA and DMS.

Finance and commercial planning are Consulted when beats affect scheme eligibility, credit limits, or cost-to-serve. IT is Consulted for implementing bulk master-data updates and keeping a change log. This RACI ensures clear ownership of census execution (field and distributor), design decisions (regional sales/ops), and governance and sign-off (central RTM), avoiding the common failure mode where distributors unilaterally reshape routes to suit their convenience.

Under tight GST and e-invoicing scrutiny, most Indian FMCG companies assign Finance or Tax as accountable for RTM-related statutory data integrity, with IT responsible for system integration and monitoring. This makes statutory compliance a business-owned outcome, not something blamed on “the system.”

Finance/Tax is usually A for end-to-end correctness, timeliness, and completeness of GST, e-invoicing, and return data that flows via RTM. The Tax function is often R for defining tax logic, reconciliation rules, and responding to notices; Finance is R for periodic sign-offs and matching RTM data with ERP and filings. IT is R for building and maintaining integrations between RTM, ERP, and government portals, implementing alerts, and documenting interface behavior. Internal Audit or Compliance is C on design and periodic reviews.

• Tax logic and statutory rules in RTM: Tax = A/R, IT = R (config), Vendor = R (implementation), Finance = C.
• Integration uptime and data sync: IT = A/R, Vendor/SI = R, Finance/Tax = C with defined monitoring dashboards.
• Reconciliation & audit response: Finance = A, Tax = R, IT = C, RTM CoE = C for operational data.

Effective programs add explicit incident workflows: any sync failure or mismatch triggers an incident owned by Finance/Tax, with IT as technical lead, and a documented post-mortem that can be presented in audits to show governance, not negligence.

For RTM environments with frequent scheme and coverage iterations, a tiered RACI usually works best: Operations owns day-to-day configuration changes, while a cross-functional steering group is accountable for any configuration that materially shifts cost-to-serve or trade-spend. This helps balance agility with financial control.

Operations or Sales Ops is generally R for maintaining the configuration catalog: beats, visit frequencies, basic scheme parameters, user roles, and minor UI or workflow tweaks. Within predefined policy guardrails (e.g., discount caps, visit frequency ranges), Ops can implement changes autonomously. When proposed configuration changes exceed thresholds—new scheme types, major discount levels, changes in claim validation logic, or structural territory reassignments—they must be escalated to an RTM Steering Committee that includes Sales, Finance, and sometimes Supply Chain; this group is A for policy shifts.

• Routine config (within guardrails): Operations/RTM CoE = A/R, IT = R (technical), Sales & Finance = I.
• Significant scheme or coverage changes: RTM Steering Group (Sales + Finance + Ops) = A, Operations = R for design and implementation, IT = R, Country Sales = C, Finance = C.
• Guardrail and threshold management: Finance and Sales = A for defining limits; Operations = R for operationalizing them.

Codifying this boundary in a “config change policy” with examples prevents scope creep and reduces disputes over who authorized cost-driving changes.

Under board pressure for trade-spend ROI, companies usually make Finance accountable for final numbers on RTM analytics and promotion ROI dashboards, with Sales accountable for target narratives and operational plans. Analytics or Data teams are responsible for data pipelines and methodology. This division allows the CSO to present confidently, backed by Finance sign-off.

Finance is typically A for metric definitions (ROI, uplift, leakage, claim TAT), reconciliation with ERP, and sign-off of dashboards used for board reporting. Data/Analytics teams are R for model building, data quality checks, and calculation logic. Sales or Trade Marketing is R for interpreting insights, explaining variances, and building action plans. The CSO is A for the overall story presented to the board, relying on Finance’s attestation.

• Metric definition & changes: Finance = A, Sales/Trade Marketing = C, Data/Analytics = R.
• Dashboard build & data integrity: Data/Analytics = R, IT = R for infrastructure, Finance = C, Sales = C.
• Monthly/quarterly ROI report sign-off: Finance = A/R for numeric validation, Sales/CSO = A/R for narrative, IT/Data = C.

A simple approval workflow—draft dashboards from Analytics, validation by Finance, joint review with CSO—should be scheduled before each board cycle so last-minute disputes do not undermine credibility.

To tighten trade-promotion controls without a four-way bottleneck, most CPGs standardize scheme templates and make Trade Marketing responsible and usually accountable for scheme setup within pre-approved guardrails, with Sales and Finance providing tiered approvals only when configurations breach thresholds, and IT responsible for data integrity and logs rather than approvals.

In a practical model, Trade Marketing is responsible for configuring campaigns in the RTM system using Finance-approved discount types, payout methods, and eligibility rules. Sales leadership is accountable for commercial strategy—approving which customer groups, territories, and volumes to target. Finance is accountable for the financial framework: budget caps, allowable mechanics, evidence requirements, and claim validation rules; Finance is consulted for schemes that stay within these boundaries and provides explicit approval only for exceptions or high-value campaigns above a spend or margin threshold.

IT or RTM Operations is responsible for ensuring the system enforces the rulebook: mandatory fields, scan-based or digital proofs, automated accrual logic, and claim TAT tracking. In claim validation, Finance is accountable for final payout sign-off and sample-based audit, while RTM Operations is responsible for running automated validations, exception reports, and handling distributor queries. By codifying standard schemes and evidence rules into the platform, day-to-day Trade Marketing actions operate under Finance’s policy rather than requiring Finance’s micro-approval for each promotion.

An effective ROI-tracking RACI for RTM platforms makes Finance accountable for the ROI methodology and validation, Sales/RTM Operations responsible for input data quality and execution metrics, and the RTM CoE accountable

Finance typically defines the uplift measurement approach (baseline periods, control vs pilot territories, attribution rules for volume, margin, and leakage reduction) and is accountable for approving the calculation formulas, cost allocation logic, and statistical confidence thresholds. Sales and RTM Operations are responsible for ensuring accurate operational data: beat execution, scheme deployment, fill rates, numeric distribution, and claim settlement quality, as these feed directly into ROI metrics.

The RTM CoE or Sales Ops team is responsible for building and maintaining consolidated ROI reports across markets, pilots, and waves, and is accountable for explaining variances, outliers, and assumptions. IT is responsible for the data pipelines, integration quality, and the “single source of truth” data mart from which ROI calculations are drawn. The CFO is informed on a regular cadence via a standard “RTM investment performance” pack, with Finance and RTM CoE jointly accountable for the content; this separation lets Finance retain control of the method without owning every data-cleaning task.

For prescriptive AI and RTM copilots, a sound RACI makes Data Science/Analytics teams responsible for model configuration and monitoring, Sales leadership accountable for business rules and adoption, and an RTM CoE or Governance Council accountable for override policies and dispute resolution when field teams contest AI outputs.

Data Science or Analytics is responsible for selecting algorithms, defining features, tuning parameters, and implementing explainability and monitoring (drift, bias, performance). They are consulted by Sales to translate commercial strategies (e.g., focus SKUs, route priorities, promo bias) into model objectives and constraints. Sales leadership is accountable for approving which AI recommendations are binding vs advisory (e.g., mandatory beat adherence vs optional reorder suggestions) and for ensuring that AI business rules do not conflict with channel policies or trade agreements.

An RTM governance forum—often anchored by the RTM CoE—is accountable for defining override rights (which roles can override, under what conditions), escalation paths when field teams disagree with AI, and processes for reviewing override patterns to improve the model. IT is responsible for the technical deployment and data integrity. This structure keeps AI from becoming a “black box,” with clear human ownership of both recommendations and exceptions.

For a centralized RTM control tower, the effective pattern is to make regional sales managers responsible for data discipline in their territories, while the RTM CoE remains accountable for platform stability, metric definitions, and analytics quality. That separation keeps ownership close to the field but protects the integrity of the system.

RACI – Data Capture & Discipline (per region/territory)
Actors: Regional Sales Managers (RSMs), Area Sales Managers (ASMs), Field Reps, RTM CoE, IT.

• R (ensuring orders, visits, and stock data are captured correctly and on time): RSMs/ASMs
• A: Regional Sales Managers
• C: RTM CoE (data quality rules, training material), HR (if included in incentives)
• I: Country Sales Director.

RSMs should receive data quality scorecards (e.g., % outlets with missing stock, backdated orders, journey‑plan adherence) and be measured on them.

RACI – System Performance, Data Model, and Metrics
- R: RTM CoE (metric definitions, business logic, control tower dashboards), IT (infrastructure, uptime, data pipelines)
- A: Head of RTM CoE for analytics quality; CIO / IT Ops Head for platform performance
- C: Finance (for financial metrics), Sales Leadership (for KPIs and targets), Country IT
- I: Regional Sales Teams.

RACI – Exception Management & Escalations
- R:
- RTM CoE for identifying anomalies (OOS spikes, fill‑rate drops, data gaps) via control tower.
- RSMs for investigating field‑level root causes (non‑compliance, distributor behavior).
- A:
- RSMs for corrective actions within their territory (coaching, distributor follow‑up, route changes).
- Head of Sales when structural changes are needed (distributor change, coverage redesign).
- C: RTM Ops (process tweaks), IT (technical issues causing missing data), Supply Chain (stock allocation).
- I: Country GM.

RACI – Data Governance & MDM
- R: RTM CoE data steward(s) for outlet, SKU, territory structures and governance rules
- A: RTM CoE Head
- C: Country Sales/Operations (for structural changes), IT (for master data systems), Finance (where masters impact pricing and claims)
- I: RSMs/ASMs.

To formalize this, many CPGs: - Add data‑discipline KPIs to RSM scorecards (e.g., “Control Tower Data Quality Index”).
- Publish a short Control Tower Governance SOP stating that the RTM CoE never “fixes” field data silently; it flags issues and assigns them to the owning RSM for correction within defined SLAs.

When introducing prescriptive AI in RTM control towers, the workable pattern is: RTM Analytics is accountable for model quality and monitoring, Sales is accountable for business decisions to accept or override recommendations, and IT is accountable for the platform, data pipelines, and access controls. AI should advise, not silently decide.

RACI – AI Recommendation Design & Governance
Actors: RTM Analytics / Data Science, Sales Leadership, IT, Finance, RTM Ops.

• R: RTM Analytics for defining use‑cases (assortment, route changes), model features, thresholds, and explainability.
• A: Head of RTM Analytics / Commercial Excellence
• C: Sales (field practicality, guardrails), IT (data availability, performance), Finance (P&L impact metrics), RTM Ops (operational feasibility).
• I: Country GM.

RACI – Daily Use of AI Recommendations
(e.g., changing assortment in a beat, re‑routing for cost‑to‑serve) - R: Sales managers (RSM/ASM) for reviewing suggestions and triggering actions in their territories.
- A: Sales Leadership (CSO/Regional Sales Directors) for policy on when recommendations are mandatory, advisory, or ignorable.
- C: RTM Analytics (clarifications, scenario support), RTM Ops (implementation, e.g., updating journey plans or planograms), Finance (for major structural or price actions).
- I: IT.

RACI – Overrides & Exception Logging
- R: Sales managers for recording overrides with reason codes (e.g., local event, competitive action, distributor constraint).
- A: Sales Director for ensuring override discipline in line with policy.
- C: RTM Analytics (to refine models using override patterns), RTM Ops (checking if overrides indicate process gaps), IT (logging and access).
- I: Internal Audit for material revenue areas.

RACI – Monitoring Model Performance & Risk
- R: RTM Analytics for tracking uplift, hit rates, and bias; publishing dashboards comparing “accepted vs overridden vs ignored” recommendations and resulting performance.
- A: Head of RTM Analytics; CIO for technical risk (if using cloud AI services).
- C: Sales (interpretation and corrective actions), Finance (P&L verification), IT (data quality).
- I: Board or executive committee.

A short AI Governance Charter should state explicitly: - Which decisions remain fully human‑owned and cannot be auto‑executed.
- Thresholds where Sales must escalate to leadership before accepting AI‑driven changes likely to materially shift revenue or cost‑to‑serve.
- Who signs off on new models or major model changes (usually a joint Sales + RTM Analytics decision with CIO informed).

To minimize coordination overhead in RTM rollout training, an effective RACI makes internal L&D or Sales Ops Accountable for the training program, with the RTM vendor Responsible for content and product expertise, and Sales leadership and regional managers Responsible for attendance and reinforcement. Every session should have a single named session owner and a simple, pre-agreed escalation ladder.

In practice, Sales Ops or a central RTM CoE is Accountable for the training design, calendar, audience mapping, and adoption metrics. The vendor is Responsible for configuring training environments, delivering train-the-trainer sessions, and providing localized playbooks and short “how-to” videos. Internal L&D is often Responsible or Consulted for converting vendor material into company-standard formats, onboarding it into LMS, and tracking completion.

Sales leadership (CSO, national sales manager) are Consulted in deciding mandatory modules and linking completion to incentive eligibility, while regional sales managers are Responsible for ensuring their teams and distributor staff actually show up, complete pre-work, and use the app in the field. Escalations for low attendance or poor adoption should move from regional manager → national sales ops → CSO, with the vendor Informed and supplying remedial clinics or field rides, rather than being left to coordinate dozens of regional calendars directly.

For firms with past RTM failures, a concrete checkpoint-based RACI reassures leadership by tying each rollout milestone to specific functional sign-offs. A central Program Owner is accountable overall, but Sales, IT, and Finance each become accountable for defined gates such as pilot exit, go-lives, and adoption thresholds.

Typical milestone sign-offs include: pilot design approval, pilot exit, country-by-country go-live, and post-go-live adoption and stability. The RTM Program Manager or CoE is A for orchestrating these gates; Sales/RTM Ops is A for commercial readiness and field adoption thresholds; IT is A for integration stability and performance SLAs; Finance is A for data reconciliation and early ROI signals.

• Pilot design approval: Program Owner = A, Sales/RTM Ops = R, IT = R, Finance = C, Country lead = C.
• Pilot exit (e.g., minimum strike rate, claim TAT, no critical defects): Program Owner = A, Sales = R, IT = R, Finance = R for uplift checks.
• Country go-live: Country GM/CSO = A, Sales Ops = R, IT = R, Finance = C, HR = C for training completion.
• Adoption & stabilization (e.g., 80–90% active users, stable sync for 4–6 weeks): Program Owner = A, Sales = R, IT = R, Finance = C.

These checkpoints and owners should be codified in a one-page governance charter, reviewed at steering-committee meetings, and used as the backbone of communication to the board.

When multiple external partners support RTM programs, most CPGs designate a single Lead Partner or an internal Program Owner as accountable for end-to-end delivery, with other partners and internal teams responsible for their components. The objective is to create one “throat to choke” without hiding internal responsibilities.

Two patterns are common. In the first, a prime system integrator or platform vendor is A for delivery and support SLAs across all external work; other vendors subcontract or work under their coordination. Internal IT is R for architecture, security, and integration oversight; Sales Ops is R for process and adoption; Finance is C for ROI and controls. In the second pattern, an internal RTM Program Manager is A and orchestrates all external partners, with each external party R for its scope and a clear demarcation of responsibilities in a RACI and R&R matrix.

• Solution design & build: Lead Partner or Program Owner = A, Platform Vendor = R, SI = R, Internal IT = R, Sales Ops = C.
• Country rollout: Program Owner = A, Local Sales Ops = R, SI/Vendor = R for deployment, IT = R, RTM CoE = C.
• Support & incident management: Lead Partner or Internal IT = A, Platform Support = R, SI = R for integrations, Sales Ops = C.

Leading firms embed this structure contractually (prime vs sub relationships) and mirror it in internal governance decks so that escalation paths are unambiguous.

In most mature RTM programs, the single accountable program owner is either the Head of Distribution/RTM Operations or a dedicated RTM Transformation Lead reporting to the CSO. This role carries end-to-end accountability for rollout and steady-state governance, even though Sales, IT, and Finance each own specific responsibilities.

Sales/RTM Ops is usually R for coverage models, distributor processes, and field adoption; IT is R for platform stability, integrations, and security; Finance is R for trade-spend controls, claim validation processes, and financial reconciliation. However, when disputes arise—over secondary sales numbers, scheme leakage, or claim settlements—the RTM Program Owner is A for arbitrating data sources, coordinating root-cause analysis, and proposing process or system changes to the steering committee.

To make this stick, leading companies explicitly name the RTM Program Owner in governance charters, grant them authority over RTM change prioritization, and require that all major disputes (numbers or processes) be channelled through this role before reaching CSO or CFO. This concentrates accountability without weakening functional ownership.

The decision flow that avoids stall points in RTM contracting explicitly sequences business problem definition, IT feasibility, and Procurement commercialization, and assigns a single RTM sponsor as accountable across all stages. The sponsor is usually Head of Distribution/RTM CoE or Sales Ops, not Procurement or IT.

In a working pattern, Sales/RTM Operations is accountable for defining scope, must-have capabilities, and pilot outcomes; Finance is consulted on ROI logic and compliance sensitivities; IT is consulted on integration, security, and data residency constraints. Only after this business-and-IT frame is documented does Procurement become responsible for RFP, commercial negotiation, and vendor due diligence, with IT responsible for technical evaluation and security checks, and Finance responsible for TCO and contractual risk review.

To avoid “everyone waiting for everyone,” leading teams define explicit RACI per stage with time-bound SLAs. For example, during technical clearance, IT is accountable for issuing a written go/no-go on architecture within a fixed period, with business and Procurement consulted but not blocking. During SoW drafting, Procurement is responsible for document creation, IT is responsible for technical scope sections, Sales/RTM Operations is accountable for functional scope and acceptance criteria, and Finance is accountable for commercial terms, caps, and milestone structures. The steering committee (CSO + CFO + CIO) is informed at defined gates but not involved in line-item drafting.

When global HQ sponsors RTM modernization, effective RACI patterns separate global standards ownership from local configuration authority. Global COE or CSO is usually accountable for the reference RTM design and guardrails, while local Sales/RTM Operations are accountable for final configurations within those guardrails.

Pricing hierarchies, core outlet attributes, and scheme template types are typically owned globally: the global commercial or RTM CoE is accountable for defining standard entity models, field definitions, discount types, and approval thresholds. Local market Sales/RTM teams are responsible for filling in local content—price lists, customer group mappings, channel nuances—and accountable for ensuring they do not breach global policy on margin floors, discount caps, or target-setting rules.

Decision flow often uses a two-tier approval: global approves the framework and risk rules once; local approves market-specific setups routinely. For example, a local market can approve outlet segmentation rules as long as they use the global segmentation attributes and scoring model; any deviation (new segments, new discount mechanics) requires global consultation and, for high-risk changes, global approval. IT operates as responsible for enforcing configuration boundaries in the platform and maintaining separate environments (global template vs local instance), while Finance (global and local) is consulted to ensure tax, margin, and scheme accounting consistency.

Where past RTM tools failed on adoption, the RACI for training and behavior change must clearly make Sales leadership accountable for field compliance and usage, HR responsible for aligning incentives and performance management, and the RTM vendor responsible only for enablement content, training delivery, and product support.

Sales leadership (CSO, regional sales managers) is accountable for setting expectations that RTM usage is part of the job, defining KPIs such as call compliance, order capture via app, and photo-audit completion, and using these in reviews and performance decisions. They are responsible for coaching routines, ride-alongs, and reinforcing the “why” behind new workflows. HR is responsible for embedding RTM metrics into incentive plans, appraisal forms, and reward programs, ensuring that non-usage has consequences and good usage is visibly rewarded.

The RTM vendor is responsible for user training materials, train-the-trainer sessions, helpdesk processes, and feature optimizations to reduce friction. They can be held to adoption-enabling SLAs (e.g., response time, bug resolution) but must not be accountable for whether a sales manager enforces usage in weekly reviews. RTM Operations or a CoE can be accountable for tracking adoption dashboards and flagging non-compliant clusters, but the line of accountability for behavior change must remain squarely with Sales leadership, not outsourced to the vendor.

For RTM master data across van sales, general trade, and modern trade, a robust pattern is to assign a single RTM Master Data Owner (often in Sales Ops or RTM CoE) as accountable for outlet, SKU, and pricing hierarchies, while channel teams and external partners are responsible for requesting changes and consuming data according to governance rules.

The RTM Master Data Owner is accountable for defining data standards, naming conventions, deduplication rules, and approval workflows for new outlets, route changes, SKU launches, and price updates. They are also accountable for maintaining the “golden record” and for ensuring alignment with ERP and any MDM hub. IT is responsible for the technical MDM solution, integrations, and data-quality monitoring tools, but is not accountable for business definitions or approvals.

Channel managers (van sales, GT, MT) are responsible for submitting accurate master-data change requests (e.g., new outlets, classification updates), validating that data is correct in their channel views, and reporting anomalies. Finance is consulted on pricing and discount hierarchies, particularly where they impact margin or tax treatment. External partners (distributors, MT customers, eB2B platforms) are responsible for adhering to agreed interfaces and ID structures. This RACI avoids fragmented ownership by making one role accountable for cross-channel consistency while still leveraging channel expertise.

For RTM-linked distributor financing, the RACI that protects risk while using RTM data makes Finance and Risk accountable for final credit decisions and policy, Operations and Sales responsible for initiating and recommending limits based on RTM signals, and any finance partner or fintech responsible for executing approved disbursements under contract.

Finance and Risk define eligibility criteria, scoring models, exposure limits, documentation requirements, and delinquency responses, and are accountable for portfolio performance and regulatory compliance. RTM data (sell-through velocity, claim behavior, DSO, dispute patterns) feeds these models but does not replace Risk judgment. Operations and Sales are responsible for flagging potential candidates, triggering limit-review workflows in the RTM/ERP environment, and providing qualitative insights (ownership changes, market conditions) to complement quantitative data.

IT and RTM vendor are responsible for enabling secure data flows from RTM to credit assessment tools, logging all credit-related actions, and enforcing role-based access. Distributor managers and regional sales managers are consulted before major limit increases or suspensions but do not approve; this prevents them from overstepping into risk ownership. All credit approvals, limit changes, and exceptions are finally approved by Finance/Risk, ensuring that any losses or audit questions remain under Finance’s accountable domain.

For phased RTM rollouts, effective RACI at each phase gate uses objective readiness checkpoints where RTM Operations or CoE is accountable for go-live recommendations, Sales and Finance are responsible for specific adoption and accuracy metrics, and the steering committee is accountable for final decisions, explicitly documented.

Typical checkpoints per region include: training completion (percentage of field reps, distributor staff, and supervisors trained), minimum active usage (e.g., X% of orders captured via RTM, Y% beat compliance over a defined period), data quality (outlet master and SKU mapping completeness, low error rates), and financial accuracy (claim settlement accuracy vs old process, reconciliation between RTM and ERP within tolerance). RTM Operations is responsible for collating these metrics and is accountable for stating whether criteria are met.

Sales leadership is responsible for confirming field readiness, reporting any major objections or resistance, and ensuring supervisors can manage via the new dashboards. Finance is responsible for validating claim and invoice accuracy and is consulted on whether any remaining issues are tolerable. The steering committee (CSO/CFO/CIO) is accountable for go/no-go but only after reviewing a standard readiness scorecard; political pressure from regional leadership is deliberately separated from objective metrics by this structured gate process.

When an SI partner works alongside the RTM vendor, clarity comes from making the internal RTM CoE accountable for outcomes, the SI responsible for integration and configuration delivery, and the RTM vendor responsible for product behavior and defects—under a unified escalation ladder owned by the CoE.

In practice, the RTM vendor is responsible for core product defects, performance issues intrinsic to the application, and standard features; the SI is responsible for customizations, integrations, localizations, data migration, and environment management. IT is responsible for overall technical governance and non-functional requirements (security, SLAs), while the RTM CoE or Head of Distribution is accountable for end-to-end adoption, process fit, and timeline adherence.

Escalation ladders typically start with L1: SI project manager and internal RTM Ops for day-to-day issues; L2: RTM vendor success lead plus SI delivery head and internal IT lead for persistent defects or integration problems; L3: executive sponsors from CSO/CIO and senior vendor leadership when timelines or business continuity are at risk. Responsibility matrices explicitly tag each ticket type (functional defect, interface failure, performance problem, adoption issue) to a primary owner (vendor vs SI vs internal) to avoid the “three-way blame triangle.”

Among leading FMCG players in India and Southeast Asia, de facto RACI patterns for RTM governance concentrate accountability for business outcomes in Sales/RTM Operations, keep Finance accountable for financial control and ROI validation, assign IT accountable for architecture and integration stability, and use a cross-functional RTM CoE to coordinate vendor selection, pilots, and steady-state operations.

For vendor selection, CSO or Head of Distribution is typically accountable for defining business needs and selecting shortlists, with Procurement responsible for running RFPs and negotiations, IT responsible for technical due diligence, and Finance responsible for TCO and risk assessment. During pilot governance, RTM CoE is accountable for pilot design, metrics, and execution; Sales and Trade Marketing are responsible for field adoption and scheme execution; Finance is responsible for uplift and leakage measurement; IT is responsible for stable integrations and data flows.

In steady state, RTM Operations is accountable for operational performance (fill rate, coverage, claim TAT) using RTM tools, IT is accountable for uptime, security, and release management, and Finance is accountable for audit trails, reconciliation, and ROI reporting. Vendors are responsible for product and support SLAs but are not accountable for business KPIs. This pattern reflects a shift from one-off “IT projects” to ongoing commercial systems governed jointly by Sales, Finance, and IT under a formal CoE.

A best-practice end-to-end RACI for RTM modernization makes Sales/RTM Operations accountable for business outcomes and adoption, Finance accountable for financial risk and ROI validation, IT accountable for technical integrity, and a cross-functional RTM CoE responsible for orchestration across vendor selection, pilot, rollout, and run—closing the common “no-owner” gap.

In vendor shortlisting, Sales/RTM Operations is accountable for defining use cases and success criteria; Procurement is responsible for RFP and commercials; IT is responsible for integration/security checks; Finance is responsible for evaluating commercial viability. During pilot, RTM CoE is responsible for design and governance; Sales is responsible for field use and behavior change; Finance is responsible for uplift and leakage metrics; IT is responsible for environment stability; CSO is accountable for go/no-go using evidence from these teams.

For national rollout, RTM Operations is accountable for sequencing, region readiness, and KPIs like numeric distribution and fill rate; Sales leadership is accountable for enforcing usage; IT is accountable for scaling infrastructure; Finance is consulted on budget and risk. In steady state, RTM CoE is responsible for change requests and continuous improvement; IT is accountable for SLAs; Finance is accountable for reconciliations and trade-spend governance; CSO/CFO/CIO steering committee is accountable for major scope and budget decisions. Explicitly writing this across stages prevents diffusion of responsibility.

When layering reverse logistics and expiry‑risk dashboards onto an existing RTM stack, Supply Chain should be accountable for returns policies and approval, Finance for financial recognition and credit notes, and RTM Operations for workflow configuration, data capture, and dashboard quality. This keeps responsibilities anchored where they naturally sit today.

RACI – Process Design for Returns & Expiry Management
Actors: Supply Chain/Logistics, RTM Ops, Finance, Sales, ESG/CSR, IT.

• R: Supply Chain and RTM Ops jointly for defining reverse‑logistics flows: triggers, collection points, documentation, and segregation (saleable, rework, scrap).
• A: Head of Supply Chain
• C: Finance (valuation of returns, write‑off policies), Sales (impact on trade terms), ESG/CSR (disposal and waste‑management guidelines), IT (system feasibility).
• I: Country GM.

RACI – Returns Approval & Credit‑Note Processing
- R:
- Field / Distributors submit return requests via RTM, with evidence and expiry details.
- RTM Ops ensures requests follow process and are captured correctly.
- A:
- Supply Chain for physical acceptance decision (quantity, condition, logistics).
- Finance for credit‑note issuance and accounting treatment.
- C: Sales (commercial implications and exceptions), RTM Ops (system controls and thresholds), Internal Audit (spot checks).
- I: ESG/CSR for waste impact.

Often, thresholds apply: below a certain value or volume, approvals sit with Regional Supply Chain and Finance; above that, escalate to national roles.

RACI – Expiry‑Risk Dashboards & ESG Reporting
- R: RTM Ops / Analytics for configuring expiry‑risk dashboards (by SKU, region, distributor) and ESG metrics (waste volumes, recovery routes).
- A: Head of RTM CoE or Commercial Excellence; ESG/CSR Head for sustainability KPIs.
- C: Supply Chain (interpretation and actions like reallocation or markdowns), Finance (link to write‑offs and provisions), Sales (promo activations to clear stock).
- I: Country leadership, global sustainability teams.

RACI – Policy Enforcement & Continuous Improvement
- R: Supply Chain and Sales for acting on alerts (e.g., targeted promotions, redistribution, returns planning).
- A: Supply Chain Head for physical flows; Sales Director for commercial interventions.
- C: Finance (P&L impact), RTM Ops (process tweaks), ESG/CSR (waste reduction initiatives).
- I: Board or regional HQ via consolidated reports.

Adding a short Reverse Logistics & Expiry Governance Addendum to the RTM playbook, with these RACIs and thresholds, prevents ambiguity about who can approve returns and who owns ESG reporting.

For mid‑tier CPGs without a PMO, a lightweight RACI that groups work into four phases—selection, contracting, pilot, rollout—can keep RTM projects under control without overloading Sales and Ops. The key is to name one RTM Lead as day‑to‑day owner and keep documents to 1–2 pages per phase.

Roles to Define (often people wear multiple hats)
- RTM Lead (usually Head of Distribution or Sales Ops).
- Sales Leader (Sales Director/CSO).
- IT Lead.
- Finance Lead.
- HR/Training (optional but helpful).
- Procurement/Legal (may be combined).

Phase 1 – Vendor Shortlist & Selection
- R: RTM Lead (requirements, demos, reference checks).
- A: Sales Leader.
- C: IT (tech fit), Finance (ballpark budget), Procurement/Legal (basic terms).
- I: Country GM.

Phase 2 – Contract & Scope Finalization
- R: Procurement/Legal (SOW, price, basic SLAs).
- A: Finance Lead + Sales Leader (for spend and outcomes).
- C: IT (scope of integrations), RTM Lead (scope realism), Vendor.
- I: Country GM.

Phase 3 – Pilot Execution
- R: RTM Lead (pilot plan, KPIs, UAT, issue log).
- A: Sales Leader.
- C: IT Lead (environment, devices), Vendor (config, training), Finance (pilot costs, basic ROI), HR (support training calendar).
- I: Country GM, field managers.

Phase 4 – Rollout & Training
- R: RTM Lead (rollout waves, local champions, adoption tracking).
- A: Sales Leader.
- C: HR (training, incentives), IT (support and incident handling), Finance (change in processes, e.g., claims), Vendor (ongoing support).
- I: Country GM.

Two simple artifacts are enough: - A one‑page RACI by phase (table with tasks vs roles).
- A weekly action log owned by the RTM Lead (issue, owner, due date, status).

This avoids the overhead of a full PMO while still giving clarity on who does what, especially during selection and the first rollout wave.

In RTM programs that include distributor financing, responsibilities should be split so Treasury and Finance control credit terms and risk, while the RTM CoE is responsible for health‑index design, monitoring, and alerting. This prevents commercial teams from informally altering credit exposure while still using RTM insights to manage risk.

RACI – Credit Policy & Terms Definition
Actors: Treasury, Finance (Commercial/AR), RTM CoE, Sales, Legal, Partner Banks/Fintechs.

• R: Treasury and Finance for defining overall credit policy: eligibility criteria, exposure limits, pricing, collateral, and covenants.
• A: Treasurer / CFO
• C: RTM CoE (data fields and health metrics needed), Sales (practicality by channel), Legal (contracts), Banking/Fintech partners.
• I: Country GM.

RACI – Distributor Health Index & Early‑Warning Design
- R: RTM CoE / Analytics for building the health index (payment behavior, secondary sales trends, stock aging, claim behaviour) and early‑warning signals.
- A: Head of RTM CoE
- C: Treasury/Finance (validation of risk relevance), Sales (commercial view), IT (data availability).
- I: Risk Management, Country GM.

RACI – Credit Approvals & Adjustments
- R: Finance AR/Treasury teams for approving or adjusting credit limits based on both policy and RTM signals.
- A: Treasurer / Finance Controller (depending on size thresholds).
- C: Sales (relationship and volume impact), RTM CoE (interpretation of health index changes), Partner Banks (if joint approvals).
- I: RTM Ops, Country management.

RTM CoE is explicitly not Accountable for credit decisions; it provides structured input.

RACI – Monitoring, Alerts & Response
- R: RTM CoE for generating periodic dashboards and alerts (e.g., health index drops, rising DSO, abnormal claims).
- A: Finance Risk Owner for ensuring alerts trigger corrective actions.
- C: Treasury (funding exposure), Sales (actions with distributor: payment plans, order controls), RTM Ops (process follow‑through).
- I: Internal Audit.

RACI – Partner Management & Governance Reviews
- R: Treasury for bank/fintech relationships and program economics.
- A: CFO.
- C: RTM CoE (portfolio insights), Finance (losses, provisions), Legal (contracts), Sales (field feedback).
- I: Board or regional HQ.

Codifying this in a Distributor Financing Governance Note—with clear credit‑approval thresholds, escalation paths, and RTM data roles—gives both Finance and Sales comfort that the system will surface risk early without undermining growth.

In multi-country RTM programs, leading FMCG firms make a central Data or RTM CoE accountable for outlet and SKU master data governance, while Commercial and Operations teams are responsible for creating and maintaining local records under defined rules. This separates decision rights on the “golden record” from the mechanics of data capture.

Typically, a Master Data Owner (often under Sales Ops or a central Data Office) is A for standards, stewardship processes, and final conflict resolution. Country Sales or Trade Marketing is R for outlet creation and classification rules; Supply Chain or Category is R for SKU setup and lifecycle; IT is R for MDM tooling, validations, and sync with ERP. Disputes about duplicates, territory assignment, or SKU hierarchy flow to a small MDM council chaired by the Master Data Owner, with country Sales, Supply Chain, and Finance as C.

• Data standards & ownership policy: Master Data/RTM CoE = A, Sales, Supply Chain, IT, Finance = C.
• Outlet master (create/change/close): Country Sales Ops = R, Master Data Owner = A for approvals on exceptions, IT = R for technical validations.
• SKU master (create/modify/retire): Category/Supply Chain = R, Master Data Owner = A, Finance = C for pricing/valuation, IT = R for sync.

Organizations that avoid endless “who owns it” debates publish a one-page master data RACI, set clear SLAs for approvals, and enforce that only records approved through this flow are considered the single source of truth for analytics and control-tower reporting.

A practical RACI for RTM–ERP reconciliation makes Finance accountable for financial integrity and sign-off, IT accountable for data pipelines and controls, and Sales/RTM Operations responsible for day-to-day scheme and target execution within predefined guardrails. The governing principle is: Finance owns the rules and thresholds; IT owns the pipes and logs; the business operates within Finance-approved configurations without ticket-by-ticket approvals.

Most CPGs use three layers. At the design layer, Finance is accountable for COA mapping, revenue recognition rules, scheme accounting logic, and tolerance bands; IT is responsible for implementing these in integration, data models, and audit trails; RTM Operations and Sales are consulted to ensure rules align with field reality. At the operational layer, RTM Operations is responsible for daily reconciliation runs, exception review, and distributor-level issue resolution; Finance is accountable for closing-period sign-off and approving write-offs or overrides; IT is responsible for job execution, monitoring, and fixes when data or performance fails.

For schemes and targets, a common pattern is that Trade Marketing or Sales Ops is responsible for creating schemes and targets using Finance-approved templates and rate cards; Sales leadership is accountable for commercial impact; Finance is consulted only when a scheme breaks the approved template, budget, or risk thresholds. IT remains responsible for ensuring every transaction, change, and override is logged with user, timestamp, and source so Finance can audit without blocking every configuration change.

Under strict GST and e-invoicing regimes, the RACI typically makes Finance accountable for compliance and statutory filings, IT and the RTM vendor responsible for technical conformance and uptime, and RTM Operations responsible for process discipline and exception handling. The design principle is: Finance owns “what” must comply; IT and vendor own “how” it is implemented and monitored.

Finance is accountable for interpreting GST rules, defining invoice content requirements, retention periods, and acceptable tolerances between RTM, ERP, and government portals. IT is responsible for building and maintaining integrations with ERP and e-invoicing systems, ensuring data residency, security, and error handling, and the RTM vendor is responsible for implementing compliant invoice formats, tax calculations, and audit logs in the application.

RTM Operations is responsible for day-to-day compliance operations: ensuring field teams use approved workflows, monitoring reconciliation reports between RTM and ERP, and escalating anomalies (missing IRNs, mismatched tax values). Finance signs off periodically on compliance dashboards and is the owner of external audit responses and regulator interactions; IT and the vendor provide logs, evidence, and technical RCA but are not accountable for legal exposure. This structure allows Finance to retain control over submissions and attestations without micromanaging every system change.

A CFO can control RTM financial risk without becoming a bottleneck by structuring RACI so that Finance is accountable for business case validation, contract-risk review, and go-live financial readiness, while Sales/RTM Operations and IT are responsible for execution details and timelines. The pattern is: Finance approves frameworks and thresholds; others operate within them.

For business case validation, Finance is accountable for defining ROI methodology, validating assumptions (uplift, leakage reduction, cost savings), and confirming that KPIs and measurement plans are in place; Sales/RTM Operations is responsible for supplying realistic inputs and pilot design, with IT consulted on enabling costs. In contract sign-off, Procurement is responsible for drafting and negotiation; Finance is accountable for commercial terms, caps, payment milestones linked to adoption or KPI outcomes, and audit and data-ownership clauses; IT is responsible for technical and security clauses.

For go-live readiness, Sales/RTM Operations is responsible for adoption metrics and process readiness, IT is responsible for integration stability and data quality, and Finance is accountable for reconciliations between RTM and ERP, scheme-accounting integrity, and any compliance exposures (tax, audit trails). Finance’s approval becomes a clearly defined gate with objective criteria, not ad hoc sign-offs on every configuration, which protects the CFO from surprise exposures while avoiding day-to-day micromanagement.

For unified DMS + SFA rollouts, the most effective RACI pattern makes RTM/Distribution Operations accountable for change intake and impact assessment, while Finance and Procurement are accountable for financial and contractual approval of any scope or budget change. This gives commercial and ops teams speed on day‑to‑day decisions but forces any cost or contract impact through a predictable control gate.

Suggested RACI for Change Requests, Scope Creep, Budget Escalations
Actors: RTM Operations Lead (RTM Ops), Sales/Business Owner (Sales), Enterprise IT, Finance, Procurement, Vendor PMO.

1. Change request intake & triage
- R: RTM Ops
- A: RTM Ops
- C: Sales, Vendor PMO, IT
- I: Finance, Procurement
Scope: logging CRs, checking duplication, classifying as no‑impact / minor / major.

2. Impact analysis (process, timeline, and technical)
- R: Vendor PMO (effort, timeline, technical feasibility)
- A: RTM Ops (business impact) + IT (architecture impact)
- C: Sales, Finance
- I: Procurement
Rule of thumb: RTM Ops signs off that the change is genuinely needed for execution; IT signs off it will not break ERP/tax integrations.

3. Commercial impact & budget check
- R: Vendor PMO (quotes, rate cards)
- A: Finance (budget fit, ROI)
- C: Procurement (commercial terms), RTM Ops (benefit justification)
- I: Sales, IT
Finance should own the threshold logic (e.g., changes under 1–2% of TCV can be approved by RTM Ops + Finance controller; anything above goes to steering committee).

4. Contractual change control (SOW / PO / addendum)
- R: Procurement
- A: Procurement
- C: Legal, Finance, RTM Ops
- I: IT, Vendor PMO
Procurement anchors a standard change‑order template and ensures rate cards and caps are consistently applied.

5. Go / no‑go approval for major scope or budget changes
- R: RTM Ops (business case & urgency note)
- A: Steering Committee (CSO or Sales VP + CFO; CIO as veto on tech risk)
- C: Procurement, IT, Vendor PMO
- I: Regional Sales, Distributor stakeholders where relevant.

6. Implementation planning & communication
- R: Vendor PMO
- A: RTM Ops
- C: Sales, IT, Finance (if process changes affect claims or invoicing)
- I: Procurement.

To avoid slowdown, many CPGs define three bands of change with pre‑agreed RACI: - No‑impact / configuration changes (e.g., adding a SKU, tweaking a scheme rule): RTM Ops A, IT C, Finance/Procurement I only. - Minor effort, no recurring license change: RTM Ops A, Finance C for budget confirmation within a pre‑approved envelope, Procurement C for commercial hygiene. - Major scope or license impact: Steering committee A, Finance and Procurement A for finances and contracts, RTM Ops R for justification.

Document all of the above in a 2–3 page Change Control SOP attached to the contract: thresholds, RACI table, approval SLAs, and a simple change‑log template owned by RTM Ops. That combination usually gives Finance and Procurement confidence without forcing Operations to debate every minor configuration tweak.

In RTM projects integrating DMS/SFA with SAP or Oracle, enterprise IT should be accountable for integration architecture, security, and lifecycle maintenance, while the RTM vendor is responsible for functional mappings, adapters, and change implementation. The RACI must be explicit enough to satisfy CIO controls and audit expectations.

RACI – Integration Design
Actors: Enterprise IT (Apps & Integration), RTM Vendor, ERP COE, RTM Operations, InfoSec.

• R: Enterprise Integration Team for overall design (interfaces, middleware, error‑handling patterns)
• A: CIO / Head of Enterprise Architecture
• C: RTM Vendor (API capabilities, payload formats), ERP COE (SAP/Oracle specific constraints), RTM Ops (business process flows), InfoSec (security, data privacy)
• I: Finance (for financial postings), Audit.

RACI – Data Mapping and Field Definitions
- R: RTM Vendor + RTM Ops together for business‑level mapping (SKU, outlet, price, tax, scheme codes)
- A: ERP COE / Master Data Owner (to ensure consistency with global SAP/Oracle definitions)
- C: Enterprise IT (technical mapping templates), Finance (GL/CO mapping, tax codes)
- I: Country Sales/Operations.

Vendor usually provides mapping workbooks (Excel or similar) and sample payloads; IT validates them against corporate standards.

RACI – Build, Testing, and Cutover
- R: RTM Vendor for connector code, transformation logic in the RTM side; Enterprise IT for middleware configuration, jobs, and monitoring
- A: Enterprise IT Integration Lead
- C: ERP COE, RTM Ops (UAT), Finance (posting tests), InfoSec (pen tests, data‑flow review)
- I: CIO, CSO.

RACI – Ongoing Maintenance & Change Management
- R: Enterprise IT for operations (monitoring, restart, patching), RTM Vendor for bug fixes, version upgrades, and new endpoint support
- A: Enterprise IT Service Owner (integration)
- C: RTM Ops, ERP COE, Vendor Support
- I: Finance, Internal Audit.

To meet CIO risk controls, the following documentation is typically required: - Integration Design Document (IDD): data flows, systems, endpoints, volumes, SLAs, retry logic.
- Data Mapping Matrix: each field from RTM to SAP/Oracle with datatype, transformation, and owner.
- Runbook / SOP: monitoring tools, threshold alerts, resolution steps, RACI for incident tiers.
- Change Control Process: who approves new fields/interfaces, test evidence required, rollback plans.

Embedding these artifacts into the project SOW and IT’s service catalogue usually satisfies architecture boards and audit committees.

For GST‑compliant RTM in India, Legal and Tax should be accountable for interpreting statutory requirements, while IT is accountable for implementing those rules into the architecture and vendor selection. The RACI should prevent functional teams from improvising compliance decisions during rollout.

RACI – Solution Design for E‑Invoicing & GST Workflows
Actors: Tax, Legal, IT, RTM Operations, Finance, Vendor.

• R (business requirements: document flows, approval chains, retention rules): Tax (indirect tax team) with Finance
• A (final compliance interpretation): Head of Tax with support from Legal
• C: IT (feasibility, integration with GSTN/e‑invoice portals), RTM Ops (practical field processes), Vendor (standard capabilities, localization options)
• I: CSO, CFO.

IT is then: - R for translating Tax/Legal requirements into system designs and integration specs.
- A for technical compliance: encryption, data residency, logging, and uptime to meet statutory expectations.

RACI – Vendor Validation (compliance and technical)
- R: IT (security and integration due diligence), Procurement (commercial and documentation), RTM Ops (process fit)
- A: CIO (technical validation) + Head of Tax (GST/e‑invoicing compliance validation)
- C: Legal (contract clauses on data, liability, jurisdiction), Finance (implications for reconciliation, audits)
- I: Country leadership.

Legal’s role is not to design workflows but to: - Validate data‑processing terms, retention periods, indemnities, and roles as per law.
- Ensure contracts capture responsibilities for regulatory change updates.

RACI – Go‑Live Sign‑off
- R: IT (technical readiness, integration tests), RTM Ops (UAT on schemes, invoices, credit‑notes), Vendor (defect closure, statutory test cases)
- A: CFO or Finance Director, based on explicit sign‑off from:
- Head of Tax: GST treatment, e‑invoicing, and reporting flows are compliant.
- CIO: security and integration controls are acceptable.
- C: Legal (final legal risk check), CSO/Head of Sales (business continuity)
- I: Internal Audit.

To reduce firefighting, many Indian CPGs add two simple mechanisms: - A “Compliance Change Log” where Tax/Legal record regulatory updates and IT/RTM Ops document system responses and timelines.
- A quarterly Compliance Review where Tax, IT, and RTM Ops jointly review sample invoices, credit notes, and logs against GST rules.

This structure keeps interpretations centralized in Tax/Legal while making IT and RTM Ops clearly responsible for execution and daily exceptions.

For CPG companies in Africa, a workable master data RACI makes a central RTM or data-governance team Accountable for outlet and SKU standards, while regional sales or RTM operations teams are Responsible for local creation and maintenance, with distributors only proposing changes. This keeps a single source of truth for outlet IDs and SKU codes while using local knowledge to minimize duplicates and ghost outlets.

In practice, the central RTM CoE or Master Data team is Accountable for the data model, ID conventions, de-duplication rules, and final approval of any new outlet or SKU master record. Regional sales ops or RTM operations are Responsible for validating field inputs, running periodic de-dup checks, and enforcing that every beat or scheme uses only approved masters. Distributors and sub-distributors are typically Consulted: they submit outlet additions/closures and corrections through structured requests in DMS or SFA, but cannot directly create master records. IT and data-admin functions are Informed or Consulted for workflow automation and audit trails.

A simple pattern that reduces duplication is: distributor or rep proposes → regional ops validates and enriches (geo-tag, classification) → central MDM approves and creates ID → integration pushes to all systems. Outlet-census projects and large beat redesigns are run as time-bound campaigns where regional leaders are Responsible and central RTM CoE is Accountable for sign-off, with Finance and Commercial teams Consulted to protect scheme and territory integrity.

In RTM implementations subject to strict external audits, auditors typically expect documented decision flow and RACI that links every major RTM decision to named roles, timestamps, and approvals. Evidence clusters usually cover vendor selection, configuration and change management, and user/data-access rights, all with clear segregation of duties.

For vendor selection, auditors often look for signed steering-committee minutes, documented evaluation criteria, scoring sheets, and formal approvals showing who was Accountable (e.g., CSO or CFO) and who was Consulted (IT, Procurement, Internal Audit). For configuration and RTM process changes, auditors expect change-request forms, impact assessments, test results, and release notes logged in a change-management system, with clear separation between the person requesting the change, the person configuring it, and the person approving go-live. Linking these to ticket IDs and version history in DMS/SFA/TPM helps demonstrate control.

On data-access rights, auditors usually want user-access matrices, role definitions, and evidence of periodic access reviews signed by business owners and IT. Logs of admin actions, such as master-data edits, scheme configuration, and claim status overrides, are often sampled. Where RTM touches GST or e-invoicing in India, they also expect documented mappings between RTM, ERP, and tax systems and proof that changes have been tested end-to-end under controlled approvals.