global field operations support team ministry support and integration consolidation pilot engagement...

Global Field Operations Support Team Ministry Support and Integration

Consolidation Pilot

Engagement with the SO PartnersJuly 2015

Ministry Support and Integration

Outline of Consolidation Pilot

1. Description of a consolidation model

2. Objectives for the Pilot

3. Honduras and the Central Province of Sri Lanka

4. Pilot Design

5. Timeline for the Pilot

6. Stakeholder Engagement


Purpose of the Consolidation Model

Contextually appropriate programme by a National office that Contextually appropriate programme by a National office that

utilises multiple funding types and sources in one program utilises multiple funding types and sources in one program

design, one budget, one report and one evaluation, allowing for design, one budget, one report and one evaluation, allowing for

greater efficiencies and leading to increased impact on the well greater efficiencies and leading to increased impact on the well

being of children.being of children.


Description of the Consolidated Model• A fully integrated programme of multiple types and funding sources

• Simultaneous and full application of the following change processes across a number of programmes in a National Office: • LEAP 3• Shared and efficient use of core number of high-caliber

management and technical staff• Common and efficient business processes in DME, finance,

sponsorship management, procurement, etc.

• Each Technical Programme across the Area Programmes has one consolidated:

• Design• Budget for which SOs commit funding with exceptions to grant

funding• Report with disaggregated data for specific donor/SO

contributions

• Contextualised by the National Office


Unpacking the Non-Negotiables


Consolidation Pilot Objectives

1. Identify the effectiveness measures of contribution to CWB (both at individual RC and at community levels) in comparison to the baseline

2. Determine the efficiency measures of the consolidated model, in terms of cost and time in comparison to the baseline

3. Determine if the pilot can meet the common fiduciary requirements including sponsorship customer relations and reporting as per the requirements

4. Determine what conditions can the consolidated model be applied in other National offices


Consolidation Pilot Selection CriteriaCriteria Criteria ReasonReason

Demonstrated DME, Sponsorship and Technical capacity

• Responsibly transition to LEAP 3• Strong monitoring system is required to

disaggregate data and report for contributing SO’s

• Capacity is required to adapt the consolidated model to one’s context

• Deployment of Horizon 3

Readiness for LEAP 3 • LEAP 3 enables scale-up of technical programmes

• Allows for immediate start of the pilot in FY16

Number of SOs involved • Engagement of SO’s representing various sizes and geographic regions is important to fully understand the implications for the SO’s

Number of funding streams

• Various funding streams are able to leverage one another and is part of the proposed model

Size of the NO • Certain size of the NO allows for lessons from the pilot to be generalized across the Partnership

Willingness of the NO and RO leadership

• NO ownership and RO support is critical as consolidated model is a major commitment

Ministry Support and Integration 8

Introduction - Honduras

Ministry Support and Integration 9

Introduction – Sri Lanka


Process Redesign : Commitments and Funding (Honduras)Support OfficeCommitments at Cluster level

Sponsorship & PNS (unrestricted) at Cluster-level based on total RC & PNS investment

National OfficeDevelop one high-level TP design and budget for each Cluster for both TA’s together

10

Review and agree to the TP designs and budgets

NO’s undesignated reserves MYPBAS by Funding Type

TP budgets will include all Cluster costs and all relevant NO technical and programme support costs Separate plan and budget

for AP costs


Process Redesign : Commitments and Funding (Sri Lanka)Support OfficeCommitments at Cluster level

Sponsorship & PNS (unrestricted) at Cluster-level* based on total RC & PNS investment

National OfficeDevelop one high-level design and budget per each of 4 TPs in alignment with their strategic priorities

11

* Cluster-level for WV Lanka

Review and agree to the TP commitments, designs and budgets

NO’s undesignated reserves MYPBAS by Funding Type

TP budgets will include all Cluster costs and all relevant NO technical and programme support costs Separate plan and budget

for AP costs

Allocate SO commitments to the TPs


Key Differences between LEAP 3 and Consolidation Model

12

Current ADP area

Multiple ADPs in a

cluster

At the AP level based on RC in the AP and unrestricted PNSAt the Cluster level based on total RC and unrestricted PNS

Design per TP and plan per APs (current # of ADPs)

Designs per TP and plan per APs (at the cluster level)

Report per TP with break-down of monitoring data for each AP

Report per TP with break-down of monitoring for each SO investment

Concept Concept of APof AP

SO SO FundingFunding

# of # of DesignDesign

s / s / PlansPlans

# of # of ReportReport

ss

LEAP 3

C.M.C.M.


Time-line for the Pilot

Time Activities

Pre-Pilot (End of Sept 15)

• TA’s Finalized• Technical and DME expertise in place• Pilot – project plan in place• Formation of Pilot Coordination Committee in

each site• Baseline of current level of staffing, support

costs and business processes• Review and revision of key business processes• Development of TP Designs

Pilot Preparation (Oct to Dec 15)

• F2F meeting of PSTs• Finalization and approval of designs including the

engagement of PST & sign off by the SOs. • Finalization of staffing and structural implications• Putting in place processes and templates to

capture learning

(Pilot Implementation)Beginning Jan 16

• Implementation of pilot• Ongoing reporting to EGOLT & SO CEO forum• Capturing of lessons and recommendations

Pilot Review(Oct 16)

• Reporting to MRC and finalize recommendations• Reporting to the SO CEOs• Decision on continuation of pilot


Stakeholder Role/EngagementStakeholderStakeholder RoleRole

National office • Lead the pilot• Review of structure and business processes• Design of TA and TP• Implementation of the pilot

Regional office • Technical Support

Support offices • Technical support • Co-creation in the pilot design & implementation• Exercise of decision rights as per Partnership standards.• Monitoring of customer service & reporting• Contribute to the lessons learned

GC Pilot Secretariat • Pilot design• Project plan• Support in the review of business process improvement• Capture of lessons learned• Stakeholder coordination• Ensure Partnership support for the pilot• Pilot review

Steering Committee • Contribute to the pilot design, implementation and lessons learned

• Share the learning with others

EGOLT • Provide overall accountability


Key Asks

1. Your agreement for engagement in the pilot design and implementation

2. Your support for the proposed approach to how planning, funding and reporting will work in the consolidation pilot

15

global field operations support team ministry support and integration consolidation pilot engagement...

Documents