DCA Governance Framework · Implementation Plan

From no governance to full framework rollout

Document ID
STD-DCA-IMPL-001
Version
1.0
Status
Draft for approval
Owner
Head of Collections / Programme Lead
References
Framework index, Full plan (Markdown)

Purpose

This plan sets out how to implement the Standardised DCA Governance Framework when the organisation currently has no standardised DCA governance. It provides phased workstreams, dependencies, and a master checklist. Detailed step-by-step tables for each phase are in the bundled Markdown file.

Assumptions

Implementation approach: four phases

PhaseNameWhat it meansTypical duration
PolicyAgree policy in principleDraft and get in-principle sign-off on DCA Governance Policy and direction (Layer 1). Full formal approval can follow in parallel with other work.2-4 weeks
Internal assetsBuild in parallel (4 streams)Stream A: contracts and Layer 2 appendix. Stream B: delegated authority and Appendix A. Stream C: rhythm and packs (Layers 5, 3). Stream D: standard reporting pack and monthly engagement deck (Layer 3, monthly pack).4-10 weeks (parallel)
EngageProvide packs to DCAsPublish standard pack and monthly engagement pack to all DCAs; brief them; set go-live schedule and governance calendar.2-4 weeks
Roll outDCA rolloutEach DCA adopts new reporting, aligns contract, SLA, and assurance to the framework; track per-DCA completion.3-6 months (by DCA)

Duration depends on number of DCAs, legal and compliance capacity, and internal approvals.

Detailed phases (seven workstreams)

#WorkstreamFramework alignment
1Draft and agree policy (in principle, then formal)Layer 1
2Review current contractsLayer 2
3Review current delegated authorityLayer 1 Appendix A
4Review current monthly operating rhythm and packsLayer 5, Layer 3
5Build standard reportingLayer 3
6Provide new reporting and monthly engagement packs to DCAsLayer 3, Layer 5, monthly pack
7DCA rollout: new reporting and contract, SLA, assurance alignmentLayers 1-6, Appendix

Dependencies (high level)

Policy is agreed in principle first. Then the four internal streams (contracts, delegated authority, rhythm and packs, build standard) run in parallel. Once internal assets are ready, Engage (provide packs to DCAs), then Roll out per DCA.

DCA implementation phase dependencies
Flow: Policy (in principle) to internal assets (parallel) to Engage to Roll out.

Master project checklist

#GateOwnerDone
1DCA Governance Policy (Layer 1) and appendices approved and publishedHead of Collections
2Standard contract appendix and SLA standard (Layer 2) agreed; gap register and rollout plan in placeLegal / Collections
3Delegated authority (Layer 1 Appendix A) reviewed and aligned for all DCAsRisk / Collections
4Current operating rhythm and packs reviewed; target cadence and pack scope agreedCollections
5Standard monthly reporting pack and monthly engagement pack built and UAT completedCollections
6All DCAs provided with new pack template, instructions, and engagement deck; go-live schedule setCollections
7All DCAs rolled out: new reporting live, contracts, SLA, DA aligned (or exception documented), cadence in placeProgramme Lead
8Issue Log (Layer 4) and Escalation Framework (Layer 6) in use for all DCAsRisk / Collections
9Programme closure report and handover to BAUProgramme Lead

Full detail

Open Implementation-Plan-DCA-Governance-Framework.md in this folder for phase-by-phase steps, per-phase checklists, and the complete gate criteria.