How Does the Government Skills Compact Relate Wider AI Adoption Plans?

Most financial services firms are already running some form of AI Adoption Plan, covering tooling, data infrastructure and governance frameworks.

Workforce training is often included, but usually as a line item to be delivered after systems go live rather than as a condition of going live at all.

The AI Skills Compact changes that assumption. It positions workforce capability as a foundational requirement for safe and effective AI use, not a follow-up activity to be scheduled once the technology is in place.

Firms that fail to connect the two initiatives risk deploying AI tools into teams that cannot use them safely, effectively, or in a way that satisfies emerging regulatory expectations.

This article explains how the Skills Compact fits within a wider AI Adoption Plan, and what that means practically for planning, governance and budgeting.

Why workforce training and technology rollout get separated

AI Adoption Plans are typically built by technology, data and governance teams. Their natural focus is on tool selection, infrastructure, model risk and integration with existing systems.

Workforce training, by contrast, is often owned by HR or Learning and Development, and scheduled according to a separate calendar — frequently after a tool has already been selected, built or piloted.

This separation is administratively convenient, but it creates a gap. Decisions about what AI tools will do, and how quickly they will be rolled out, get made before anyone has assessed whether the workforce is ready to use them safely.

In a regulated environment, that gap is no longer just an operational inefficiency. It is a governance and compliance exposure.

Traditional approaches: technology first, training after

Historically, most technology rollouts in financial services have followed a consistent pattern: build or buy the system, test it, deploy it, and train staff shortly before or after go-live.

This sequencing works reasonably well for tools with predictable, bounded behaviour, where staff simply need to learn a new interface or process.

AI tools behave differently. Their outputs can vary, their failure modes are less predictable, and using them well requires staff to understand concepts such as model limitations, appropriate reliance, escalation triggers and data sensitivity.

When training is scheduled as a post-launch add-on, staff are often using AI-assisted tools in live operational or customer-facing situations before they have developed the judgement to know when to trust the output and when to intervene.

The Skills Compact's underlying logic is that this traditional sequencing is no longer sufficient for AI specifically, even where it remained workable for earlier generations of technology.

Where AI-enabled learning helps close the gap

One genuine advantage of recent AI-enabled learning tools is that they can accelerate workforce readiness in parallel with, rather than after, technology adoption timelines.

AI-assisted learning platforms can help identify individual and team-level knowledge gaps quickly, generate role-specific scenarios reflecting a firm's actual AI use cases, and adapt content as adoption plans evolve.

This can meaningfully shorten the time it takes to bring a workforce to a baseline level of AI literacy, which matters when technology and skills timelines need to run alongside each other rather than sequentially.

However, this capability supports the Skills Compact programme, it does not replace it. Structured governance — deciding what competency looks like, who signs off readiness, and how gaps are escalated — still has to sit with operations, risk and compliance leadership, not with a learning tool.

Aligning governance, budgeting and reporting

In practical terms, aligning the two initiatives means Skills Compact milestones should appear in the same governance forums that track AI Adoption Plan progress, rather than being reported separately or informally.

Budget and resourcing for workforce training needs to be planned alongside technology procurement from the outset, not requested as an afterthought once tooling costs have already been committed.

Risk and compliance teams should treat workforce readiness as a control that supports safe AI use, rather than viewing it purely as an HR initiative with no bearing on operational risk.

Ultimately, the question is not whether a firm has an AI Adoption Plan and separately has some workforce training activity underway. It is whether the two are explicitly connected, milestoned together, and owned by people who can be held accountable for both.

Example

A London-based bond trading desk plans to roll out an AI-assisted trade reconciliation tool as part of its wider AI Adoption Plan. The operations team originally scheduled staff training for the month after go-live.

When the firm's compliance function reviewed the plan against Skills Compact obligations, it required workforce training and competency sign-off to be completed before the tool went live, shifting the project timeline but reducing the risk of reconciliation errors going unchecked by undertrained staff.

The AI Adoption Plan's go-live date was adjusted to sit after workforce competency sign-off rather than before it, resulting in a smoother rollout with fewer early-stage reconciliation exceptions and a documented audit trail satisfying Skills Compact requirements.

FAQs

• Is the Skills Compact a separate deliverable from our AI Adoption Plan?

  No. It should be integrated into the AI Adoption Plan as an explicit workstream with its own milestones, resourcing and reporting, rather than run as an isolated HR project sitting outside the plan's governance structure.

• Should workforce training happen before or after AI tools go live?

  Wherever practical, workforce competency should be built ahead of or alongside deployment rather than strictly afterward. This reduces the operational and regulatory risk of staff using AI tools before they understand their limitations and appropriate use.

• Who should be responsible for aligning the two initiatives?

  Typically a cross-functional group spanning operations leadership, HR or Learning and Development, risk and compliance, and technology leadership. No single function can align the two initiatives alone, since each holds part of the required accountability.