Aller au contenu
Coûts et Budget
13 min de lecture

ISO 27001 Budget Variance: How to Track and Control It

support@ismscalculator.com|

Analyst comparing planned and actual project costs

ISO 27001 budget variance is the gap between what you approved for the project and what you actually spent or are on track to spend. Measure it against a baseline you set after scope is fixed, review it on a schedule, and explain every material gap. The cause is almost always scope, starting maturity, or internal hours nobody priced. This guide shows how to set the baseline, calculate the variance, read it, and keep it small.

Ismscalculator
Build a Clearer ISO 27001 Budget
Estimate implementation costs using company size, industry, and security maturity, then compare your plan with the model reference.
Explore the cost calculator

TL;DR

  • Variance means actual cost minus the approved, time-phased baseline. Set that baseline only after scope is defined, or every number after it is unreliable.
  • Underspending is not automatically good news. It can mean required work slipped or the budget was padded.
  • The usual drivers are scope growth, weak starting maturity, unpriced internal labor, and audit-day assumptions that change with headcount or sites.
  • Write variance thresholds into your change-management plan, so a gap triggers a decision instead of a surprise.
  • Budget the whole three-year certification cycle, not only the first certificate.

Table of Contents

What budget variance means in an ISO 27001 project

Budget variance compares actual results with the approved cost baseline. For a certification project, the baseline is a time-phased plan: what you expect to spend on gap analysis, documentation, control work, training, tooling, internal audit and the certification audits, and in which months.

Two ideas matter here.

Variance is always measured against something fixed. Microsoft’s project guidance says to establish the cost baseline after defining scope and to assign costs to tasks or periods. It also says to track cost variance with earned-value measures. If you re-estimate every month and overwrite the original, you lose the ability to see drift.

Favorable is not the same as good. The FinOps Foundation defines favorable variance as spending below plan and unfavorable as spending above it. It also warns that a favorable variance can signal an inaccurate budget. For ISO 27001, spending less than planned can mean risk treatment work has been deferred, or that the original number was generous.

How to calculate it

Use two views: a simple one for leadership and an earned-value one for the project team.

The simple view

Variance = actual spend minus budget. Variance percentage = variance divided by budget.

A hypothetical example, with numbers chosen only to show the arithmetic: the Phase 2 documentation budget is $30,000 and you have spent $36,000. The variance is $6,000 over, or 20%. Whether that is a problem depends on how much of the phase is done.

The earned-value view

Microsoft’s definitions are the standard ones. Planned value is the budgeted cost of the work scheduled. Earned value is the budgeted cost of the work completed. Actual cost is what was spent producing that work. Cost variance is then CV = EV − AC, as set out in Microsoft’s variance tracking guidance.

Continue the hypothetical: you spent $36,000 on documentation, but only 60% of the planned documentation is done. Earned value is 60% of $30,000, or $18,000. CV = $18,000 − $36,000 = −$18,000. The simple view said you were $6,000 over. The earned-value view says you are far more over than that, because you are paying for work that is not finished.

Simple and earned-value budget variance comparison

That difference is the reason to track both. Raw spending against budget flatters a project that is behind.

What to put in the baseline

A variance report is only as honest as the baseline. Most overruns start as omissions. A complete ISO 27001 budget has these lines:

Budget line What it covers Often missed
Gap analysis and scoping Current state against the standard, scope statement Rework if scope changes later
Risk assessment and treatment Risk register, Statement of Applicability Time from system owners
Policies and documentation ISMS documents, procedures, records Review cycles and approvals
Control implementation Technical and organizational fixes Engineering hours, licenses
Training and awareness Staff training, implementer or internal auditor courses Per-seat course fees
Tooling Evidence collection, ticketing, monitoring Renewals in years two and three
Consultant support Advisory hours, if used Overage on open-ended retainers
Internal audit and management review Required every year Often assumed to be free
Certification audits Stage 1 and Stage 2 Travel and reduced-day assumptions
Surveillance and recertification Years two and three Left out of the first-year plan

Internal labor deserves its own row, even when no invoice is issued. When teams cut external spend, the hours move inside the company. Put an hourly cost on them, or the variance report will show a saving that is really a transfer.

For typical ranges by company size, our own pages are a reasonable starting point: the SMB cost drivers breakdown and our overview of certification cost. Treat any published range as a prior to adjust, not a quote. There is no flat price for ISO/IEC 27001 certification, and written quotes against a defined scope are what turn a range into a budget line.

Why actual spend drifts from the plan

Five causes explain most variance.

1. Scope changes

A wider scope means more controls, more documentation and more audit time. Every added system, team or location adds cost in several lines at once. Fix scope early and put any change through a formal request.

2. Starting maturity

A company that already runs access reviews, logging, vendor assessments and incident handling needs less remediation than one starting from scratch. If you assumed a mature baseline and discover gaps in the first assessment, remediation is where the overrun will land.

Existing attestations can also shorten the path. Some teams already run strong identity practices, such as a single sign-on setup guide describes, and those can be mapped to ISO 27001 controls rather than rebuilt. Our guide to mapping ISO 27001 controls to SOC 2 shows where the overlap sits. Count only the overlap you can evidence.

3. Headcount, sites and technical complexity

Certification bodies set audit effort in auditor-days, using tables tied to the number of people in scope, the number of sites and the complexity of the environment. When headcount grows between budgeting and audit, or you add an office, audit fees move with it. Re-run this line whenever those inputs change.

4. Unpriced internal time

Evidence gathering, interviews, control owners writing procedures and engineers fixing findings all take hours from people with other jobs. When these hours are missing from the baseline, the project either slips or borrows from operations. Neither shows up as a cash variance, which is why it surprises people.

5. Treating the certificate as the finish line

Certification runs on a three-year cycle: initial audits, then surveillance audits, then recertification. Internal audits and management reviews continue every year. A first-year-only budget guarantees an unfavorable variance in year two. Our three-year maintenance cost analysis lays the cycle out, and the enterprise cash flow view shows how it looks for larger scopes.

Reading a variance: a decision table

Numbers need interpretation. Here is how to read the four combinations of spend and progress.

Spend vs. plan Progress vs. plan Likely meaning Action
Over On or ahead Cost estimate too low, or rates changed Re-forecast, request baseline revision
Over Behind Rework, scope growth, or inefficiency Investigate cause, freeze scope
Under On or ahead Efficiency, or a generous budget Confirm, release contingency carefully
Under Behind Work deferred, owners unavailable Treat as a risk, not a saving

The fourth row is the dangerous one. A quiet project that has spent little can be a project that has not started the hard parts.

Set thresholds before you need them

Decide in advance what size of gap triggers action. Microsoft’s guidance recommends documenting variance thresholds in the change-management plan and using them to decide when a change request or a baseline revision is required, as described in its variance tracking process.

A workable pattern, which you should set to your own risk appetite:

  • Small gap: the project lead notes it in the monthly report and explains it.
  • Material gap: the steering group reviews the cause and approves either a corrective action or a revised forecast.
  • Large gap: a formal change request. The baseline is revised only through that request, never quietly.

Write the actual percentages into your plan, and have finance and the ISMS owner sign them. Keep the original baseline on file next to every revision so the history stays auditable.

A monthly routine that keeps variance small

The FinOps Foundation recommends tracking actuals, forecasting remaining spend, comparing the forecast with the budget, and investigating the cause of material variances, all covered in its budget management guidance. Applied to an ISO 27001 project, that becomes a short monthly loop.

  1. Log actuals by budget line. Invoices, license charges and tracked internal hours, mapped to the same lines as the baseline.
  2. Record progress. Percent complete per work package, agreed with the owner, not self-reported optimism.
  3. Calculate EV, AC and CV for each phase, and a total.
  4. Forecast the remainder. What will it cost to finish, given what you now know? Do not assume the rest will go exactly to plan.
  5. Compare forecast to budget and apply your thresholds.
  6. Write the cause for every material variance in one or two sentences. “Scope grew by one product line” is a cause. “Costs were higher” is not.
  7. Decide. Absorb, reallocate, request a change or cut scope.

Be careful with the last option. Cutting cost by dropping risk treatment that your own risk assessment justified is not variance control, it is a nonconformity waiting for the auditor. Budget only the changes justified by risk treatment and your objectives, and when money is tight, cut by narrowing scope formally, not by skipping controls.

Variance for startups and finance firms

Startups usually have the least slack and the most unpriced internal time. A small team with no prior program often does much of the work itself, so the hours line decides whether the project hits its date. Price those hours, and plan for the pull on engineers. Our guide for SaaS and tech companies covers the specifics.

Finance firms tend to carry larger scopes, more third-party relationships and customer or regulator questions on top of the standard. Their variance usually comes from scope and vendor evidence, not from the audit fee. Link the ISO 27001 budget to your broader security spend, and our page on security budget percentage and three-year bands helps you frame it for finance.

Avoid the common budgeting mistakes

Most unfavorable variances trace back to a short list of planning errors: a baseline set before scope was agreed, no contingency, optimistic maturity assumptions, tooling priced for year one only, and no owner for the forecast. Our guide to common ISO 27001 budgeting mistakes and how to fix them goes through each. Fixing them before the project starts is cheaper than explaining the variance afterward.

Our perspective

We build ISMS Calculator because we think the biggest budget problem in ISO 27001 is not the price of the audit. It is that the estimate is a single number nobody can inspect.

A budget you can defend has visible assumptions: company size, industry, security maturity, scope. When one of those changes, the estimate should change in front of you, and you should be able to see why. That is how our calculator is designed to work, with editable assumptions, a traceable and versioned methodology, and saved scenarios you can compare against each other.

We also think variance should be discussed before it happens. Run a conservative, an expected and an ambitious scenario at the start. Then, when scope or headcount moves, you already know which scenario you are now in, and finance has seen the range, not a surprise.

The best use of an estimate is as the baseline you measure against. Build it carefully, version it, and keep it.

Martin

Build a baseline you can measure against

A variance process starts with a baseline you can defend. Our ISO 27001 cost calculator gives a real-time estimate from your company size, industry and security maturity, with model reference comparisons to check it against that reference. You can save several estimates and compare them, which is how you set a baseline and a contingency scenario side by side.

Ismscalculator

If you want to know your starting point first, the free 2-minute readiness check takes no signup for the initial calculation, and the full readiness assessment covers maturity across the four Annex A control themes. You can also read the cost model methodology to see how the figures are built.

FAQ

What is a normal budget variance for an ISO 27001 project?

There is no authoritative standard percentage, so set your own thresholds in the change-management plan and have finance agree to them. What matters more than the size is that every material gap has a written cause and a decision. Projects with fixed scope and a realistic maturity assumption usually have smaller gaps.

Is coming in under budget always a good sign?

No. Spending below plan is called favorable, but it can also mean required work was delayed or the budget was inflated. Check progress against the plan before you celebrate. If work is behind, an underspend is a risk to the schedule and to audit readiness.

How do I forecast variance before the project starts?

Build the baseline from a defined scope, then model at least three scenarios that change the inputs most likely to move: headcount, number of sites and starting maturity. Obtain written quotes from certification bodies against that scope. A calculator that lets you save and compare scenarios makes the range visible from day one.

Should internal hours be in the ISO 27001 budget?

Yes. Internal time is a real cost even when no invoice exists, and it often grows when you reduce external support. Track the hours by work package and give them an agreed hourly rate, so a cash saving is not mistaken for an overall one.

What should I do when scope grows mid-project?

Raise a change request, re-estimate every affected line (controls, documentation, training and audit days), and revise the baseline only after approval. Keep the original baseline on file. This keeps the variance report honest and gives you an audit trail for the decision.

Sources

Prêt à estimer vos coûts ISO 27001 ?

Utilisez notre calculateur gratuit pour obtenir une estimation personnalisée des coûts, de l'effort et du calendrier basée sur votre profil d'entreprise.

Calculez votre estimation — gratuit
Retour à tous les articles