Insights

Gap analysis: how to do one, with a template and example

How to compare where you are with where you need to be and turn the difference into a prioritised plan, with a copyable template and a hypothetical ERP readiness example.

By Christopher Fagan, Managing Partner, PEF Consulting Partners

£13bnlargest programme delivered
19 yrssenior systems delivery
5 continentsdelivered across
£25msaving on a single programme

Delivered for and alongside

ShellBPCapitaBaringaOfgemSmart DCCInsightsFlui TechnologiesExxonMobilVodafoneConstellation SoftwareDeloittePwCEYNational GridElexon

Gap analysis is a structured comparison of where an organisation is today with where it needs to be, followed by a plan to close the difference. You describe the current state, define the target state in measurable terms, name each gap specifically, and assign actions, owners and priorities so the result can be delivered rather than filed.

It is one of the most used tools in consulting and one of the most often wasted. The comparison is the easy part. The value comes from being honest about today, precise about the target, and ruthless about which gaps matter enough to close first.

Current state and future state: the core idea

Every version of the method has three parts. The current state is how things actually work today, backed by evidence. The future state, often called the target state, is what must be true at a defined point, set by strategy, regulation, a standard or a new operating model. The gap is the specific difference between the two.

The discipline lies in the word specific. “Our data is poor” is not a gap. “Active customer records with no valid billing address will be rejected by the new system, and nobody owns fixing them” is a gap, because it tells you what to fix, roughly how big the job is and what happens if you leave it.

A gap can run the other way too. Sometimes the current state already exceeds what is needed, and the right action is to stop spending effort there. Record those areas as well, because they free up capacity for the gaps that matter.

Where it comes from

There is no single inventor. Measuring the distance between current performance and an objective has been part of business planning and quality management for decades, and consultancies adopted it as a standard first step in transformation work.

One well documented strand is the gaps model of service quality published by Parasuraman, Zeithaml and Berry in 1985. It treated service quality as the gap between what customers expect and what they experience, and traced that back to four gaps inside the organisation. UK public sector business cases build the same logic into the strategic case of the five case model, which has to make the case for change from current arrangements.

How to do a gap analysis, step by step

  1. Set the purpose and scope. Name the decision it supports, such as whether to start an ERP implementation or whether you can report under a new standard, and say which areas are in and out of scope.
  2. Define the future state first. Describe it in measurable terms and say where it comes from: a strategy, a regulation, a standard, a target operating model or a design. If nobody can agree the target, settle that before going any further.
  3. Assess the current state with evidence. Workshops tell you what people believe. Sample real transactions, look at the data, read the controls and watch the process being done.
  4. Describe each gap precisely. State what is missing, how big it is and what happens if it stays open.
  5. Prioritise. Score each gap on impact and on the effort or time needed to close it, and separate the gaps that must close before a deadline from the ones that would be nice to close.
  6. Turn gaps into actions. Give each action one owner, a date and its dependencies, and group related actions into workstreams.
  7. Measure again. Repeat the assessment at agreed points. A gap is closed when the evidence says so, not when the action is ticked off.

Gap analysis template

Copy the table below into a spreadsheet and add one row per area. The first row explains what belongs in each column and the second shows a completed entry; delete both once you start.

AreaCurrent stateTarget stateGapActionOwnerPriority
The process, capability, requirement or system being assessedWhat happens today, with the evidenceWhat must be true, by when, and where that requirement comes fromThe specific difference, sized where possibleWhat will close it, and any dependenciesOne named personHigh, medium or low, with the reason
Supplier onboardingNew suppliers set up by email; bank details checked by the same person who enters themOnline request with approval and an independent bank detail checkNo approval workflow; no separation of duties on bank detailsConfigure the workflow; move bank checks to a second teamHead of procurementHigh: payment fraud exposure

Keep the evidence behind each current state entry where the team can find it. When a sponsor challenges a priority, evidence settles the argument faster than opinion.

Gap analysis example: ERP readiness at a hypothetical distributor

This example is hypothetical. A wholesale distributor plans to replace an old accounting package and a separate stock system with a single ERP platform, and the board wants to know whether the business is ready to start. The future state comes from the business case and the outline design: one set of master data, standard order to cash and procure to pay processes, and a month end close in five working days.

AreaCurrent stateTarget stateGapActionOwnerPriority
Master dataCustomer and item records in two systems, many duplicates, no ownerOne cleansed record per customer and item, with named data ownersNo data ownership; duplicates not yet sizedAppoint data owners; profile and cleanse before design endsFinance directorHigh
ProcessesEach depot runs order processing its own wayOne standard order to cash process with agreed exceptionsNo agreed standard; depot managers not yet involvedProcess workshops with depot managers; sign off before buildOperations directorHigh
PeopleKey users fully loaded with their day jobsNamed key users with protected time through testing and go liveNo backfill budgetedBackfill plan and budget agreed by the boardManaging directorHigh
ReportingSpreadsheet reports built from exportsStandard reports and dashboards from the ERPReport requirements not definedAgree the twenty most used reports and their definitionsFinancial controllerMedium
IntegrationsWeb shop and carrier links built by a contractor, undocumentedSupported integrations with clear ownershipNo documentation; contractor availability uncertainDocument current interfaces nowIT managerMedium
GovernanceDecisions made informally by the ownerSteering group with clear decision rightsNo sponsor time set aside; no decision logSet up the steering group and a decision logManaging directorHigh

The result is not a pass or a fail. It tells the board the business can start, but only once three high priority gaps are closed: data ownership, an agreed standard process and protected time for key users. Those become conditions for signing the implementation contract, rather than problems discovered halfway through the build.

Our free ERP readiness assessment covers the same ground as a quick self check. An independent ERP readiness review adds the evidence, the sizing and a view on which gaps the system integrator should close and which the business must close itself.

Business, compliance and skills gaps

The method stays the same; the subject changes. A business gap analysis looks at performance or capability across the organisation: revenue, cost, service levels, controls, systems or the operating model as a whole. It works best when it is tied to a decision, such as a budget round or a restructuring, rather than run as a general health check.

Compliance versions are common ahead of new rules. For sustainability reporting, the target state comes from the standard, and the work is establishing what data, processes and controls exist today, which is the heart of CSRD readiness. If you are not sure the rules apply to you, our CSRD checker answers that first.

A skills gap analysis compares the skills and roles a team has with the ones it will need, usually because the strategy, technology or regulation is changing. It works best as part of strategic workforce planning, so that each gap leads to a decision to build, buy, borrow or redesign roles rather than a training wish list. Digital capability can be assessed the same way, and a digital maturity assessment gives you a structured current state to start from.

When to use it, and when not to

Use it before a significant commitment, such as signing an implementation contract, starting a transformation or accepting a reporting deadline, when you need to know how big the job is and what to fix first. It is also useful once a strategy has been agreed, to translate the ambition into a work plan, and in due diligence, where the difference between how a business runs today and how a buyer needs it to run shapes the value creation plan.

Do not use it while the target is still being argued about; settle the strategy first, or you will be measuring against a moving line. Do not use it to explain why something went wrong, which is a job for root cause analysis. And do not use it as a shopping list: if every gap ends in a purchase, the analysis has been written backwards from a solution.

Common mistakes

  • A flattering current state. Self assessment in workshops tends to overstate maturity. Test it against data and real transactions.
  • A vague future state. “Better reporting” is not a target. “Management accounts issued on working day five” is.
  • Gaps written as solutions. “We need a new system” is a conclusion. The gap is what the current system cannot do that the business needs.
  • No sizing. A gap without a size cannot be prioritised or costed.
  • Everything is high priority. If thirty gaps are all high priority, none of them is. Force a ranking.
  • A one off exercise. The analysis earns its keep only if it is measured again and the actions are tracked to closure.
  • Done to the team, not with it. A gap list handed over by outsiders rarely gets owned. The people who will close the gaps should help find them.

Turning the gaps into a delivery plan

A finished analysis is a plan in waiting. The high priority gaps become workstreams with owners, the dependencies set the sequence, and the measures you used to describe the target become the measures you report against. If you cannot draw a line from each gap to the plan, the analysis is not finished.

This is the point where many organisations stall, and where PEF is most useful: we build the plan with your team and stay to deliver it, rather than handing over a report and leaving. In 19 years of delivery, Christopher Fagan, our Managing Partner, has taken SAP S/4HANA, Oracle, Unit4, NetSuite, Microsoft Dynamics, Sage and Access finance systems through to go live, so our ERP readiness work goes straight to the gaps that sink implementations. His University of Oxford ESG qualification underpins our sustainability reporting readiness work.

Common questions

What is a gap analysis?

A gap analysis compares an organisation’s current state with the future state it needs to reach, sets out the specific gaps between the two and plans the actions to close each one. It is used before major investments, ahead of new regulation, after a strategy is agreed and in due diligence, and is only useful if each gap has an owner, a priority and a date.

How do you do a gap analysis?

Set the purpose and scope, then define the future state in measurable terms before assessing the current state with evidence rather than opinion. Describe each gap precisely, including its size and the consequence of leaving it open. Prioritise by impact and effort, assign actions with owners and dates, and measure again at agreed points until the evidence shows each gap has closed.

What should a gap analysis template include?

A practical template has seven columns: the area being assessed, the current state with evidence, the target state and where it comes from, the gap described specifically, the action that will close it, one named owner, and a priority with the reason for it. Many teams add columns for due date, dependencies and status so the same sheet can track delivery.

What is a skills gap analysis?

A skills gap analysis compares the skills, roles and capacity a team has today with those it will need to deliver a strategy, a new system or a regulatory change. Each gap is sized and prioritised, then addressed by training people, hiring, borrowing expertise or redesigning roles. It works best as part of a wider workforce plan rather than as a list of training courses.

What is the difference between a gap analysis and a root cause analysis?

A gap analysis looks forward: it compares where you are with where you need to be and plans how to close the difference. A root cause analysis looks back: it starts from a problem or failure and works out why it happened so it does not recur. Transformation work often uses both, with root causes explaining why some gaps have stayed open.

Related reading: Root cause analysis explained, What is an operating model?, ERP readiness assessment, CSRD readiness explained and Strategic workforce planning.

Need an honest view of the gap?

We assess the current state with evidence, agree the target with you and turn the gaps into a plan your team can deliver. Talk to us about a readiness review.

Book a confidential conversation

Sources: A. Parasuraman, Valarie A. Zeithaml and Leonard L. Berry, A Conceptual Model of Service Quality and Its Implications for Future Research, Journal of Marketing, 1985

PEF TRACK RECORD£13bnLargestprogramme led5Continentsdelivered across19 yrsSystems delivery£25mLargestsingle saving
CF

Written by Christopher Fagan

Managing Partner, PEF Consulting Partners

Christopher has led systems and transformation delivery for 19 years, including the National Grid separation, the £9bn Energy Bills Support Scheme and the BP Pulse EV charging rollout.