Offshore Competency Centre Creation Framework
Phased guidance for planning, transferring, stabilising, and improving offshore finance capability centres
This document is designed to help teams plan the move, select the right scope, prepare the operating model, execute knowledge transfer, and build a sustainable future-state service. Input to this document was provided by country CFO’s, Finance Process Owners and team members from the international finance team alongside documented lessons from pilot transfers in the UKI, CCC and GCC.
1. Core design principles
Start with the end state: define what the centre will do, what remains onshore, and how the service will be owned.
Move the right work first: prioritise transactional, repeatable, well-defined processes.
Standardise before you migrate: reduce local variation and define exception paths.
Stabilise before you optimise: do not redesign heavily during the initial transfer period.
Measure both quality and delivery: performance discussions should be fact-based.
Treat offshore as one team: relationship quality materially affects outcomes.
Make ownership explicit: unclear RACI and handoffs are a major failure point.
Plan for people impact beyond the directly affected team: adjacent functions will feel the change too.
Design for sustainability: talent, development, and leadership matter as much as cost.
Build for improvement: use progressive SLAs, scorecards, and feedback loops after go-live.
2. Stage overview
Stage
Focus
Gate question
Stage 1
Strategy, Case for Change and Sponsorship
Do we have an approved case for change, funding, sponsors, and a named accountable owner?
Stage 2
Process Selection and Wave Planning
Have we selected the right first-wave processes and documented what should be retained, deferred, or hybridised?
Stage 3
Current-State Assessment and Baseline
Do we understand the as-is process, baseline performance, dependencies, and key risks well enough to transfer safely?
Stage 4
Target Operating Model and Detailed Design
Is the future operating model designed, agreed, and measurable?
Stage 5
Readiness, Enablement and Transition Planning
Are all core enablers ready for training and transition?
Stage 6
Training, Knowledge Transfer and Handover
Has the offshore team demonstrated proficiency and formally taken ownership?
Stage 7
Go-Live, Hypercare and Stabilisation
Is service stable, controlled, and owned by the new team without excessive dependency on the old one?
Stage 8
Continuous Improvement and Future-State Maturity
Do we have an active improvement engine and a credible path to a more mature, flexible capability model?
3. Detailed framework by stage
Stage 1: Strategy, Case for Change and Sponsorship
Purpose: Establish why the centre is being created, what success looks like, and who will sponsor and govern the change.
Gate question: Do we have an approved case for change, funding, sponsors, and a named accountable owner?
Key steps
Define the business rationale and target outcomes such as capacity, quality, resilience, standardisation, efficiency, and scalability.
Understand the high level resource requirement to support the business case (number of heads moving)
Set the future-state vision for what the offshore centre will own, what will remain onshore, and how both teams will work together.
Agree the scope boundaries at a high level and confirm whether the move is finance-only or part of a wider shared-services model.
Build the business case, budget, and implementation funding.
Appoint executive sponsors, an onshore accountable owner, workstream leads, and decision forums.
Set clear success measures, milestones, and tolerances for risk, service disruption, and control impact.
Elements to consider at this stage
Lens
Key considerations
Process
- Define the outcomes the centre is expected to deliver.- Identify candidate processes at a high level and group them into likely waves.- Clarify whether the objective is lift-and-shift, improve-and-shift, or a blend.
People & Organisation
- Identify directly and indirectly impacted teams, not only the people whose roles may move.- Clarify who will lead the retained onshore team and how roles may change.- Plan for reskilling and future roles where possible rather than treating the programme only as a cost action.
Technology & Data
- Complete an early view of system feasibility, access constraints, and major technology dependencies.- Check whether ERP, billing, ticketing, reporting, and collaboration tools can support remote execution.
Risk, Control & Compliance
- Assess labour law, redundancy, SOX/control, audit, data handling, and local language constraints early.- Identify any activities that are too sensitive, judgement-based, or locally embedded for early migration.
Governance
- Establish steering committee, programme governance, escalation paths, and decision rights.- Define a named onshore owner for relationship management and end-to-end accountability.
Key deliverables
Approved business case and budget
Future-state vision statement
Initial scope and wave hypothesis
Programme governance and sponsor structure
Headline success measures
Exit criteria
Executive sponsorship is confirmed.
The case for change, target outcomes, and funding are approved.
There is a named owner for the retained service and the transition programme.
Common pitfalls
Starting without a business case or budget approval.
Treating the move purely as a headcount exercise.
Failing to define who owns the service end-to-end.
Stage 2: Process Selection and Wave Planning
Purpose: Choose the right work to move first and sequence migration in a way that protects service, controls, and stakeholder confidence.
Gate question: Have we selected the right first-wave processes and documented what should be retained, deferred, or hybridised?
Key steps
Assess each process against suitability criteria such as volume, repeatability, complexity, criticality, judgement, control sensitivity, and maturity.
Prioritise standard, transactional, repeatable work for the first wave.
Avoid or defer customer-facing, judgement-heavy, control-sensitive, or highly local activities until the model is proven.
Confirm upstream and downstream dependencies and how adjacent teams will be affected.
Create a phased migration roadmap rather than attempting a full transfer at once.
Elements to consider at this stage
Lens
Key considerations
Process
- Score each process for volume, repeatability, complexity, maturity, automation opportunity, and exception level.- Confirm defined inputs, outputs, and clear process steps; if work relies on interpretation, treat it as higher risk.- Use onshore process leads in selection decisions.
People & Organisation
- Assess business-facing touchpoints, customer sensitivity, and language dependence.- Consider talent availability in the offshore location for each process family.
Technology & Data
- Check whether process execution depends on local systems, poor workflow support, or weak data quality.- Assess whether automation or AI could improve suitability before migration.
Risk, Control & Compliance
- Review control-critical activities, segregation-of-duties implications, and audit requirements.- Use phased or hybrid models for high-criticality activities.
Governance
- Agree wave criteria and document why items are in scope, deferred, or retained onshore.- Define sign-off requirements from process owners, finance leadership, and controls stakeholders.
Key deliverables
Process inventory and suitability assessment
Wave plan with in-scope, deferred, and retained activities.
Dependency map
Selection rationale and stakeholder approvals
Exit criteria
First-wave processes are clearly defined and approved.
Higher-risk processes have mitigation plans, hybrid models, or a defer decision.
The sequence of transition is realistic and understood by all impacted teams.
Common pitfalls
Moving processes before inputs, outputs, and steps are clearly defined.
Including too many exceptions or judgement-based activities in the first wave.
Ignoring effects on adjacent teams.
Stage 3: Current-State Assessment and Baseline
Purpose: Build a fact base for transition by documenting how work is done today, where it varies, and what baseline performance must be protected or improved.
Gate question: Do we understand the as-is process, baseline performance, dependencies, and key risks well enough to transfer safely?
Key steps
Map processes end-to-end, including handoffs, controls, systems, and exception routes.
Document current SOPs, work instructions, business rules, and local knowledge.
Baseline volumes, throughput, service levels, error rates, rework, ageing, and FTE effort.
Identify process variation across teams, markets, and products.
Assess impacts on upstream/downstream functions and retained responsibilities.
Elements to consider at this stage
Lens
Key considerations
Process
- Map the as-is flow, decision points, approvals, exceptions, and escalation paths.- Identify where simplification and standardisation are needed before transfer.- Capture tacit knowledge held by individuals.
People & Organisation
- Identify role-by-role responsibilities, peaks, pinch points, and dependency on key individuals.- Assess the likely morale and engagement impact on both transferring and retained teams.
Technology & Data
- Document systems used, interfaces, access methods, reporting tools, and data quality issues.- Identify manual workarounds that could break when moved.
Risk, Control & Compliance
- List key controls, audit evidence requirements, and policy/regulatory considerations.- Confirm where local language or local market knowledge is essential.
Governance
- Agree a baseline pack and fact-based reporting that will later support objective performance discussions.
Key deliverables
As-is process maps.
SOPs and process notes
Baseline KPI/SLA pack for quality and delivery
Dependency and impact assessment
Knowledge capture log
Exit criteria
Process knowledge is documented well enough to train others.
Baseline performance and staffing assumptions are evidence-based.
Key dependencies, controls, and exception scenarios are understood.
Common pitfalls
Underestimating embedded local knowledge.
Missing process variation across markets or teams.
Starting transfer before documentation is complete.
Stage 4: Target Operating Model and Detailed Design
Purpose: Design how the future service will operate across onshore and offshore teams, with clear ownership, governance, controls, and ways of working.
Gate question: Is the future operating model designed, agreed, and measurable?
Key steps
Define the detailed target operating model and retained organisation.
Set service ownership, RACI, handoffs, decision rights, and escalation routes.
Design standard processes, controls, and exception handling.
Define the service catalogue, KPIs, SLAs, and reporting cadence.
Shape the offshore team structure, role profiles, and talent model.
Elements to consider at this stage
Lens
Key considerations
Process
- Standardise before migration wherever practical.- Create clear exception routes and avoid ambiguous handoffs.- Decide which processes should be lifted as-is for stability and which should be redesigned first.
People & Organisation
- Define offshore roles, retained onshore roles, reporting lines, and leadership accountabilities.- Plan career paths and development in both the offshore and retained teams.- Involve relevant onshore leaders in recruitment where appropriate.
Technology & Data
- Design access, workflow, reporting, collaboration, and ticketing support needed for the future model.- Plan data cleansing and standardisation to reduce friction after go-live.
Risk, Control & Compliance
- Embed control ownership, evidencing requirements, and segregation-of-duties rules in the design.- Confirm any legal, labour, privacy, or policy constraints.
Governance
- Define governance forums, performance reviews, service reviews, and escalation mechanisms.- Name an onshore relationship owner accountable for the service.
Key deliverables
Target operating model
RACI and retained-organisation design
Future-state process maps and exception routes
KPI/SLA framework
Offshore role profiles and recruitment plan
Exit criteria
The target operating model is signed off by process owners, finance leadership, and controls stakeholders.
Roles and accountabilities are explicit.
Service expectations can be measured objectively.
Common pitfalls
Leaving governance vague.
Assuming offshore and onshore teams will 'figure it out' informally.
Designing a model without accounting for talent retention and future development.
Stage 5: Readiness, Enablement and Transition Planning
Purpose: Put in place all prerequisites for a controlled migration, including people readiness, systems access, training, communications, and a realistic cutover plan.
Gate question: Are all core enablers ready for training and transition?
Key steps
Confirm systems, access, data, and infrastructure readiness.
Complete recruitment and onboarding of the offshore team.
Prepare the training curriculum, schedule, and materials.
Build the detailed migration plan, milestones, and cutover checklist.
Launch a structured communication and change plan for all stakeholders.
Prepare risk mitigations, contingency options, and hypercare support.
Elements to consider at this stage
Lens
Key considerations
Process
- Freeze the in-scope process design for transition purposes.- Document milestone-based handover criteria and readiness checkpoints.
People & Organisation
- Set role clarity for trainers, trainees, retained team, and leadership.- Plan how to support morale, trust, and adoption across locations.- Brief external stakeholders where the operating model change may affect them.
Technology & Data
- Validate logins, permissions, environments, connectivity, and collaboration tools before training starts.- Resolve data-quality and workflow issues that would otherwise undermine learning or execution.
Risk, Control & Compliance
- Confirm all control documentation, approval matrices, and compliance requirements are ready.- Create contingency plans for service interruption, attrition, or delayed readiness.
Governance
- Agree programme milestones, sign-offs, issue-management routes, and reporting cadence.- Confirm how decisions will be made if timelines slip or readiness gates are not met.
Key deliverables
Detailed transition plan
Communications and change plan.
Training curriculum and schedule
Access and technology readiness checklist
Risk register and contingency plan.
Hypercare plan
Exit criteria
All core enablers are in place before formal training begins.
Training materials, SOPs, and system access are complete.
Stakeholders understand the timeline, roles, and escalation routes.
Common pitfalls
Starting training without systems access or clean documentation.
Underestimating the communication and change effort.
Planning a big bang move where a phased approach would be safer.
Stage 6: Training, Knowledge Transfer and Handover
Purpose: Build offshore capability safely through structured learning, demonstrable proficiency, and controlled transfer of accountability.
Gate question: Has the offshore team demonstrated proficiency and formally taken ownership?
Key steps
Train offshore team members on the end-to-end process, not just isolated tasks.
Use a sequence of observe -> perform with supervision -> reverse shadow -> independent execution.
Define measurable proficiency checkpoints before trainer exit.
Transfer accountability in stages, with formal handover milestones and sign-offs.
Maintain strong communication, trust-building, and leadership support throughout.
Elements to consider at this stage
Lens
Key considerations
Process
- Train on process purpose, inputs, outputs, exceptions, controls, and customer or business impact.- Set measurable checkpoints such as first accurate completion, first fully independent week, or error-threshold achievement.- Start steady-state KPI/SLA measurement after training is complete, while still tracking training-readiness checkpoints during transfer.
People & Organisation
- Address resistance from both sending and receiving teams.- Consider language, culture, time zone, and training method.- Ensure trainers have time and recognition for knowledge-transfer responsibilities.
Technology & Data
- Use live systems or realistic training environments where possible.- Confirm trainees can access the same data, tools, and reports required for independent execution.
Risk, Control & Compliance
- Test understanding of controls, approvals, and evidence requirements as part of proficiency sign-off.- Avoid premature trainer withdrawal where knowledge gaps remain.
Governance
- Track completion against the training plan, milestone by milestone.- Use documented sign-offs for readiness, not informal assumptions.
Key deliverables
Training plan completion records
Competency matrix and proficiency sign-offs
Handover milestone log
Formal readiness approval for go-live.
Exit criteria
Offshore team members can execute agreed processes independently to the required standard.
Accountability has been transferred explicitly.
Onshore support expectations post-handover are documented.
Common pitfalls
Assuming attendance at training equals capability.
Rushing handover before reverse shadowing and readiness checks are complete.
Allowing trainers to continue making daily decisions after ownership has supposedly moved.
Stage 7: Go-Live, Hypercare and Stabilisation
Purpose: Protect service during the first months of operation while the offshore team takes full ownership and the new operating model settles.
Gate question: Is service stable, controlled, and owned by the new team without excessive dependency on the old one?
Key steps
Execute go-live against a controlled cutover plan.
Provide structured hypercare support, typically for 3 to 6 months depending on complexity and risk.
Run frequent operational reviews, issue triage, and escalation forums.
Track both quality and delivery measures and compare them to agreed baselines and targets.
Stabilise first; do not attempt broad optimisation during the initial transfer period.
Elements to consider at this stage
Lens
Key considerations
Process
- Operate the agreed process without introducing avoidable redesign during the early weeks.- Use issue logs to identify defects, unclear SOPs, and exception themes.
People & Organisation
- Maintain onshore support and accessible leadership during hypercare.- Continue reinforcing one-team behaviours and shared accountability.
Technology & Data
- Monitor system issues, access failures, reporting gaps, and data defects closely.- Use dashboards for real-time progress tracking where possible.
Risk, Control & Compliance
- Monitor control execution and evidence completeness from day one.- Escalate service or compliance risks quickly.
Governance
- Use daily or weekly reviews initially, then taper as stability improves.- Maintain clear decision-making on issue ownership and remediation.
Key deliverables
Go-live completion record.
Hypercare issue log and action tracker
Initial KPI/SLA dashboard
Stabilisation review and sign-off
Exit criteria
Service is stable and predictable.
Major defects and control issues are resolved or under managed action plans.
The offshore team owns day-to-day delivery, with onshore support reduced to the agreed model.
Common pitfalls
Underestimating post-transfer support needs.
Declaring success too early based only on volume throughput.
Measuring speed but not quality.
Stage 8: Continuous Improvement and Future-State Maturity
Purpose: Move from transferred service to a mature capability model that continually improves productivity, quality, flexibility, and talent depth.
Gate question: Do we have an active improvement engine and a credible path to a more mature, flexible capability model?
Key steps
Introduce progressive SLAs and productivity targets that evolve beyond day-one expectations.
Run regular scorecards, service reviews, and lessons-learned cycles.
Build a formal continuous-improvement backlog and delivery cadence.
Apply the sequence simplify -> standardise -> digitalise -> automate, then scale AI where appropriate.
Develop team capability, product knowledge, and career pathways to support retention and broader value-add.
Elements to consider at this stage
Lens
Key considerations
Process
- Review whether each process should remain as transferred or be redesigned for a better future state.- Expand the model carefully into adjacent or more specialist work as maturity grows.
People & Organisation
- Create ongoing training and development plans.- Strengthen onshore/offshore relationship networks and social cohesion.- Design teams for flexibility so they can support ad hoc or specialist work over time.
Technology & Data
- Improve data quality, documentation, and workflow visibility.- Identify automation and AI use cases that enhance scale and efficiency.
Risk, Control & Compliance
- Ensure process changes continue to preserve control integrity and auditability.- Periodically reassess risks as scope expands.
Governance
- Maintain named onshore ownership and consistent scorecards.- Document lessons learned and feed them back into process and operating model changes.
Key deliverables
Progressive SLA and productivity roadmap
Continuous-improvement backlog and ownership
Lessons-learned log
Future-state automation and AI opportunities list
Capability and talent development plan
Exit criteria
The centre is improving against a defined maturity path, not just holding day-one performance.
Improvement activity is governed, measured, and prioritised.
The operating model can flex as business needs change.
Common pitfalls
Leaving SLAs at initial transfer levels indefinitely.
Failing to capture lessons learned.
Pursuing automation before basic process simplification and standardisation are complete.
4. Appendix A: Process suitability guidance
Topic
Guidance
Likely first-wave candidates
Transactional billing; O2C collections for non-complex accounts; P2P; dashboard/reporting; data analysis; R2R with clear automation opportunity; expenses
Usually not first-wave candidates
Business partnering; operational business controllers; treasury; internal control/SOX; project management; customer-facing activities
Key suitability criteria
Volume; repeatability; clarity of inputs/outputs; complexity; judgement required; control sensitivity; process maturity; automation opportunity; dependency on local language or local knowledge; quality of supporting systems and data
Typical mitigations for lower suitability
Simplify and standardise first; document exceptions; improve workflow/system support; phase or hybridise high-criticality work; stabilise immature processes before transfer
5. Appendix B: Example KPI and SLA categories
Category
Example measures
Delivery
Volume processed, cycle time, backlog, ageing, on-time completion, service-level attainment
Quality
Error rate, rework rate, first-time-right, complaint volume, audit/control exceptions
Training readiness
Training completion, shadow/reverse-shadow completion, proficiency sign-offs, first independent week outcome
Operational health
Attrition, absenteeism, system incidents, open issues, dependency failures
Improvement
Productivity trend, automation adoption, standardisation completed, CI benefits delivered
6. Appendix C: Starter risk register
Risk
Typical trigger
Typical mitigation
Knowledge loss
Key tacit knowledge sits with individuals and is not documented
Capture SOPs and business rules early; use shadowing/reverse shadowing; stage trainer exit
Broken or fragmented process
Work is moved before simplification, standardisation, or exception design
Complete current-state assessment; standardise where possible; define handoffs and exceptions
Negative impact on retained team
Morale drops, roles become unclear, or leadership gaps emerge
Clarify retained roles; communicate early; plan reskilling and support
Technology not ready
Systems, access, ERP, billing, or ticketing tools cannot support remote delivery
Run readiness checks before training and go-live; fix critical issues first
Cross-functional disruption
Upstream or downstream teams are affected unexpectedly
Assess dependencies and impacts across teams; involve adjacent functions in design
Control/compliance weakness
SOX, segregation, audit evidence, or legal requirements are missed
Embed controls in the target operating model; involve risk/compliance stakeholders from the start
Communication barriers
Language, culture, or unclear messaging causes misunderstanding
Use structured communication plans; build trust; adapt training methods
Insufficient hypercare
Onshore support is withdrawn before the new team is stable
Plan 3 to 6 months of hypercare based on process risk and complexity