Project Management
12-mins

Corrective Action in Project Management: How to Get Projects Back on Track

A 5% budget overrun caught in week two is a conversation. The same problem left until week eight is a crisis. Here's the five-step process for catching it early.
Written by:  
Jenna Green
Published:
October 26, 2026
Contents
Table of contents

Key takeaways

  • Corrective action fixes a gap that already exists between the plan and what is happening. Preventive action reduces the chance of a gap appearing. Defect repair fixes faulty work. You need all three, and they are handled differently.

  • Set numeric triggers before a project starts. Good starting points: a task 20% over its estimate, a project at 80% of budget with less than 70% of the work done, or anyone booked above 100% of capacity for two consecutive weeks.

  • Follow five steps: identify the deviation, find the root cause, choose the response, agree on it with your team and client, then make the change and check its impact.

  • Your billing model decides who pays for the overrun. On fixed fee it is you, on time and materials it is the client (until they stop trusting your invoices), and on a retainer it is whoever loses the monthly reconciliation argument.

  • Speed matters more than polish. In a study of 155 US defence contracts, cumulative cost performance moved by no more than 10% once a contract passed the halfway mark, so a problem you find late is a problem you mostly keep.

  • Log every corrective action. Six months on, that log is the best input you have for estimating the next project.

A 5% budget overrun caught in week two is a conversation. The same problem left until week eight is a crisis.

No project goes exactly to plan. A supplier misses a deadline by a week. Your lead developer gets pulled onto a client emergency. A phase quoted at 40 hours has burned 65 and still isn't finished. Any one of these is manageable. Leave all three unchecked for a month, and you have a project that's over budget, behind schedule and heading for an awkward conversation with the client.

Corrective action is how you respond. You notice when something starts to veer off course, understand the cause, agree on changes, and follow through. The concept is simple. Doing it consistently, on every project, before small problems get expensive, is the hard part.

At Magnetic, we build professional services automation software that agencies, consultancies and architecture and engineering firms use to run projects from pipeline to invoice. The firms we see recover well from setbacks share two things: current data and an agreed point at which someone must act on it. This guide covers both, plus the part most guides skip: how your billing model changes which fix is actually open to you.

What corrective action means in project management

Corrective action in project management is any deliberate change you make to bring project work back in line with the plan after it has drifted. PMI's PMBOK Guide defines it as "an intentional activity that realigns the performance of the project work with the project management plan."

It sits in the monitoring and controlling part of a project. You plan the work, do the work, track the work, and adjust when the numbers stop matching. Most firms are reasonable at the first three. The fourth is where things break down, because someone has to notice the problem, own it and act, usually while juggling four other projects.

Corrective actions that change the project's scope, budget or schedule baseline go through your change control process. Smaller ones, such as moving a task from one consultant to another, the project manager can handle directly. Knowing which is which before a problem lands saves a lot of arguing afterwards.

Corrective action vs preventive action vs defect repair

People use these three terms loosely, and the PMBOK Guide treats them as separate kinds of change. The difference matters because each one has a different owner and a different conversation with the client.

Compared onCorrective actionPreventive actionDefect repair
What it responds toA gap that already exists between plan and performanceA risk that has not happened yetA specific piece of work that does not meet the standard
TimingAfter the deviation appearsBefore anything goes wrongAfter the faulty work is found
Agency exampleMoving 20 hours of design work to a freelancer after the lead designer hits 130% capacityAdding a second review round to the plan for a client known to change direction lateRebuilding a landing page template that fails accessibility checks
Consultancy exampleSplitting a delayed workstream across two consultantsBooking a senior reviewer in advance for the final reportCorrecting a financial model with a formula error
A&E exampleRunning two documentation packages in parallel after a design phase overrunsBuilding structural sign-off into the schedule as a dependencyReissuing drawings with incorrect dimensions

Defect repair fixes the output. Corrective action fixes the project's direction. A repaired defect can still trigger corrective action if the rework pushes the timeline back by a week you didn't expect.

When to take corrective action: trigger thresholds for professional services firms

"Act early" is easy advice to agree with and hard to follow because nobody agrees on what "early" means. The fix is to decide your triggers before the project starts, so raising a problem is a matter of reading a number, not a judgement call that feels like an accusation.

The thresholds below are the starting points we suggest to professional services firms. They're deliberately simple. Tune them to your own history once you've logged a few months of corrective actions.

SignalStarting thresholdLikely root causeFirst response
Task hours vs estimateMore than 20% over estimate with work still openOptimistic estimate, unclear brief, or unlogged scope changeRe-estimate the remainder and check for scope additions
Budget burn vs work complete80% of budget spent with less than 70% of the work doneScope creep or the wrong mix of people on the workReview time logged against the agreed scope line by line
Forecast at completionForecast final cost more than 10% above budgetThe overrun points to an underlying problemDecide now whether to absorb, descope or raise a change request
Individual capacityAnyone above 100% booked for two consecutive weeksOverlapping projects allocated in isolationReallocate work or move a deadline before quality drops
Retainer burnHours used above the monthly allowance two months in a rowSmall requests nobody is documentingReconcile requests against the agreed scope with the client
Earned value (if you track it)Cost performance index (CPI) or schedule performance index (SPI) below 0.9Spending or progress running more than 10% behind planInvestigate the work packages driving the variance

Task hours vs estimateMore than 20% over estimate with work still openOptimistic estimate, unclear brief, or unlogged scope changeRe-estimate the remainder and check for scope additionsBudget burn vs work complete80% of budget spent with less than 70% of the work doneScope creep or the wrong mix of people on the workReview time logged against the agreed scope line by lineForecast at completionForecast final cost more than 10% above budgetOverrun is structural, not a blipDecide now whether to absorb, descope or raise a change requestIndividual capacityAnyone above 100% booked for two consecutive weeksOverlapping projects allocated in isolationReallocate work or move a deadline before quality dropsRetainer burnHours used above the monthly allowance two months in a rowSmall requests nobody is countingReconcile requests against the agreed scope with the clientEarned value (if you track it)Cost performance index (CPI) or schedule performance index (SPI) below 0.9Spending or progress running more than 10% behind planInvestigate the work packages driving the variance

CPI and SPI are earned value ratios: CPI compares the value of completed work to what it cost, and SPI compares it to what was planned to be done by now. A CPI of 0.9 means every £1 spent is producing 90p of planned work. Most agencies and consultancies don't run formal earned value, and the first five rows give you most of the same warning without it.

There’s genuine time pressure behind these triggers. A 1993 study by David Christensen and Scott Heise of 155 US Department of Defence contracts found that once a contract was more than 50% complete, the cumulative CPI did not change by more than 10%. Those were large defence programmes, not 12-week agency projects, so treat it as a direction, not a law. The direction is clear, though. The longer an overrun runs, the more of it is locked in, and the later you act, the fewer options you have left.

Most of these signals start small: a day behind here, a few hundred pounds over there. Scope creep in particular rarely announces itself. PMI's 2018 Pulse of the Profession found that 52% of projects completed in the previous 12 months experienced scope creep or uncontrolled scope changes, up from 43% five years earlier.

See when a project is going over budget

Track time and costs against your budget in Magnetic, so you know when to review scope or adjust the plan

Get started for free

Free for 14 days · No credit card required

How your billing model affects your corrective approach

Most corrective action advice assumes the same options are open on every project. In a professional services firm, they aren't. Who absorbs an overrun, and what you can reasonably ask the client to do about it, depends on how you bill.

Fixed fee.

The overrun is your cost. The client sees a price, not hours, so extra time comes straight out of your margin. Your corrective options are mostly internal: move work to someone with a lower cost rate, cut non-essential tasks you'd planned to include, or tighten review rounds. You can only go back to the client if the scope genuinely changed, which is why logging every client request against the original scope matters so much. "We underestimated" is your problem. "You added three pages" is a change request.

Time and materials.

The client pays for the hours, so an overrun looks like extra revenue. It usually isn't. Most time-and-materials work has a budget the client expects you to stay near, or a formal not-to-exceed cap. Cross it without warning, and you end up writing hours off at invoice to keep the relationship intact, which reduces your margin without ever showing up as an overrun in your project report. The corrective action here is mostly about forecasting: tell the client what the work will cost to finish and get approval before you cross the line, not after.

Retainer.

The risk on a retainer is slow leakage. Each request is small, nobody counts them, and three months later you've delivered a month of free work. Corrective action means reconciling hours used against the agreed scope each month, then having one of two conversations: increase the retainer to match reality, or set a firmer boundary and bill extras separately. For a quick read on how much unbilled work you're carrying, our over-servicing calculator does the math in a few minutes.

Phase or milestone fees.

Common in architecture and engineering, where the fee is split across stages. An overrun in one stage eats that stage's margin and tempts teams to borrow hours from the next. The corrective action is to compare fee earned against fee spent at the stage level, so you address a design-stage overrun in design and don't leave it to hide in the documentation phase.

Same deviation, four different conversations. Before you choose a response in step 3 below, check which of these you're in.

The five-step corrective action process

A repeatable process means you don't invent the response every time something goes wrong. It also takes the personal sting out of it. When you agree on the trigger and steps in advance, raising a problem becomes following the process, not pointing fingers.

Step 1: Identify the deviation

Many teams skip this step. A problem gets discussed in a stand-up, someone works around it, and nothing gets recorded. Two weeks later, the same problem returns.

Formal identification starts with a number crossing one of your triggers. Time tracking shows a 40-hour task at 35 hours with a lot left to do. The budget view shows 85% spent and 60% of the work complete. A task has sat "in progress" for twice its planned duration. Write down what crossed which threshold and when. Seeing it on Monday gives you options. Seeing it on Friday, after the client has asked what's going on, doesn't.

Step 2: Find the root cause

Before deciding what to do, work out what actually went wrong. Was the estimate too optimistic? Did the plan miss a dependency? Is one person carrying too much work across too many projects? Did the client add work nobody logged as a scope change?

The root cause decides the response. A bad estimate needs a plan adjustment. Scope creep needs a conversation with the client. An overloaded team member needs work moved to someone with capacity. Get this wrong, and you'll extend a deadline when the real issue was a senior developer stretched across four projects, and the deadline will slip again next month for the same reason. For deeper problems, a structured root-cause analysis using the 5 Whys or a fishbone diagram is worth the hour.

Step 3: Choose the response

Match the response to the cause and the size of the problem. The usual options:

  • Adjust the deadline to what's actually achievable
  • Move work to people with capacity
  • Deprioritise non-essential tasks to free up time
  • Agree a scope change or change request with the client
  • Bring in extra people, with care

That last one needs a warning. Fred Brooks put it bluntly in The Mythical Man-Month in 1975: "adding manpower to a late software project makes it later." New people need briefing, and briefing takes time from the people already on the project. Extra hands help most on work that's easy to hand over, like drafting or production, and least on work that depends on context.

Scale the response to the problem. A two-day slip on a six-month project needs a minor adjustment, not a replanning workshop.

Step 4: Agree the change with your team and the client

Tell the people affected what's changing and why before you make the change. Inside the firm, that's the team doing the work and whoever approves budget changes. Outside, it's the client.

Step 4 is also where you reset expectations. "We're moving the milestone by a week to protect quality" is a conversation you can have on your terms. "We missed the deadline, sorry" is a conversation someone else forces on you. A short written note helps, and if you send regular status reports, include the corrective action in the next one, with the reason stated plainly.

Step 5: Make the change and check it worked

Make the change, then watch what happens over the next week or two. If you moved tasks to a different team member, check after a few days that they're coping with the extra load. If you moved a deadline, check that the milestones downstream are still intact.

Set a review date when you agree on the action, and record the result: did the metric that triggered it come back inside its threshold? If it didn't, you either picked the wrong cause in step 2 or the action wasn't big enough. Either way, go back to step 2, not step 3.

Corrective action examples from agencies, consultancies and A&E firms

The three scenarios below are composites built from patterns we see across the firms that use Magnetic. Names and numbers are illustrative. The patterns are real and common.

Example 1: Resource bottleneck on a consulting project

A 35-person consultancy is six weeks into a six-month systems implementation for a client. The workload view shows one senior consultant booked at 140% across this project and two others. Implementation tasks are taking 30% longer than estimated, and the client has started asking why things are slowing down.

Root cause: we allocated the senior consultant to this project before confirming the other two. When the new projects started, no one checked her total workload.

Corrective action: move 20 hours a fortnight of documentation and testing work to a mid-level consultant with spare capacity. Keep the senior consultant on design decisions only. Adjust the sprint plan to allow for the handover. Flag the double allocation to the operations director so new projects get checked against existing bookings before anyone is assigned.

Outcome: the delay is held to one week instead of compounding across the rest of the project, and the senior consultant's load drops back to around 100%.

Example 2: Budget creep on an agency retainer

A marketing agency runs an £8,000 a month retainer for a financial services client. Actual costs have exceeded the retainer value for three months in a row, totalling £7,200. That's £2,400 a month, or 30% over, and almost a full month of free work across the quarter.

Root cause: the client has been adding small requests. An extra round of revisions, a new landing page, a few more social posts. Each one seemed too minor to flag, and none were logged against the retainer.

Corrective action: pull a report of all time logged against the retainer and map it to the agreed scope. Take the numbers to the client with two options: increase the retainer to match the real workload, or agree a firm boundary with extras quoted separately. From the following month, log every new request against the retainer balance as it arrives.

Outcome: the client agrees to a 20% increase. The agency recovers most of the margin and now sees retainer burn monthly instead of quarterly.

Example 3: Schedule overrun on a multi-phase A&E project

An architecture practice is managing a 14-month commercial fit-out. Detailed design is three weeks behind schedule. Construction documentation hasn't started, and the completion date is at risk.

Root cause: the structural engineers returned their comments late, forcing a partial redesign of two floor plates. The original schedule never included a dependency on structural sign-off.

Corrective action: run the structural and MEP documentation packages in parallel instead of one after the other. Bring in a contract drafter for four weeks to handle the extra volume. Move the documentation completion date back by one week, recovering two of the three lost weeks, and tell the client now about the revised date, with the plan attached.

Outcome: the project absorbs most of the delay. The client hears about a one-week change early, with an explanation and a plan, instead of a three-week surprise later. The practice adds structural sign-off as a named dependency in its fit-out project template, the preventive action that comes from this corrective one.

What waiting costs

Most writing about corrective action frames it as getting back on track. For firms that bill for their people's time, the bigger issue is money.

Take a £50,000 fixed-fee project. The 2026 SPI Professional Services Maturity Benchmark puts average project margin at 37.7%, so that project should return about £18,850. A 20% overrun nobody catches is £10,000 of free work, cutting the margin to £8,850, or 17.7%. More than half the expected profit is gone, and it only shows up when someone reviews the project at close.

Overruns at this scale are normal. The same SPI benchmark reports an average project overrun of 10.7% and 73.8% on-time delivery, meaning roughly one in four projects finishes late. Over a portfolio, that's a steady leak rather than an occasional crisis.

The return on doing this well is large. PMI's 2017 Pulse of the Profession found that organisations investing in proven project management practices waste 28 times less money, because more of their strategic initiatives finish successfully. Corrective action isn't the only practice in that bundle, but without it the rest of the monitoring is just watching.

To see how project overruns flow through to firm-level margin, our guide to real-time profitability dashboards covers what to track.

See which projects are over budget before they close

Magnetic's projects list with two alerts: tracked time has gone over its warning threshold, and net profit has gone over budget

A corrective action log template

A corrective action log records every deviation that crossed a trigger, what caused it, what you did and whether it worked. It's the single most useful document for getting better at estimating, because it tells you where your plans keep going wrong.

Copy these columns into a spreadsheet or your project management tool:

FieldWhat to recordExample
ID and date raisedA reference and the date the trigger was crossedCA-014, 3 March
Project and clientWhich project, which client, which billing modelBrand refresh, Acme Ltd, fixed fee
TriggerThe metric and the threshold it crossedDesign phase at 124% of estimated hours
Root causeWhat actually caused it, in one sentenceClient added two extra concepts at first review
Action agreedThe change you are makingChange request for two concepts, £3,200
OwnerOne named personProject manager
Approved byWho signed off, if approval was neededAccount director, client marketing lead
Client informedYes or no, and the dateYes, 4 March
Review dateWhen you will check whether it worked18 March
ResultBack inside threshold, or notInside threshold, change request approved
Lesson for estimatingWhat to change next timeQuote concept rounds as a separate line item

If you already run a RAID log for risks, assumptions, issues and dependencies, the corrective action log can sit beside the issues section. Issues record the problem. The corrective action log records what you did about it and whether it worked.

Making corrective action stick across teams

Most operations directors understand corrective action well. The difficulty is getting every project manager to apply it consistently. When each team uses its own approach, reporting becomes unreliable, and lessons from one project never reach the next.

Four things make the difference. Write the triggers down and apply them to every project, so a £10,000 engagement gets the same discipline as a £200,000 one. Decide who reviews a flag and who can approve each type of change, and keep the list short. Keep the log. And run a weekly 15-minute project review, because monthly reviews are too slow: a problem that could have been a conversation in week two becomes a crisis by week five.

Culture matters as much as process. If raising a problem feels like admitting failure, people hold back until the issue becomes impossible to ignore. Someone saying "this project is 15% over budget" in week three should be treated as useful information, not a performance issue.

The mistakes we see most often:

  • Waiting for a problem to sort itself out. It almost never does.
  • Fixing the symptom. If you extend a deadline without understanding why the project missed its target, you risk pushing back the next phase as well.
  • Changing the plan without telling anyone, which costs trust even when the change was right.
  • Overreacting. If a non-critical task runs a day late, it’s usually not worth a full replanning session.
  • Working from last week's numbers. By the time you review a Friday spreadsheet, the picture has changed.

What your tools need to show you

Corrective action is only as good as the information behind it. If project data lives in spreadsheets updated once a week, every decision is based on numbers that may already be wrong. Whatever you use, it needs to show you four things without anyone assembling them manually: time logged against estimates as work happens, budget spent next to work completed in the same view, who is booked on what and how close they are to capacity, and project, people and financial data in one report.

Magnetic is a professional services automation platform built for agencies, consultancies and A&E firms. It connects project management, resource management, time tracking and financial reporting in one system, so the data you need for each step of corrective action is already in one place.

For corrective action specifically, three parts do most of the work. Budget-vs-actual alerts flag a project heading over budget while there's still time to adjust scope or reassign tasks. The live workload view shows who is free, stretched, or about to be overbooked by day, week, or month, and automatically flags someone when they're overbooked or two deadlines collide. Over-servicing dashboards show where unbilled work is building up at the company, client, and project level, where retainer and fixed-fee leakage first shows. Because time, budgets, and invoicing live in the same system, you can trace an overrun back to the tasks and timesheets behind it, making step 2 practical, not theoretical.

Exonic Solutions, a software consultancy with fewer than 50 people, replaced several disconnected tools with Magnetic and reported an 80% improvement in project visibility and a 45% reduction in admin time. Chapu Chartered Accountants, a 60-person firm, went live on Magnetic in one week and reported a 70% efficiency improvement.

Magnetic offers a 14-day free trial with no credit card required, and paid plans start at £9 per user per month billed annually.

References

  1. Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK Guide).
  2. Project Management Institute. Pulse of the Profession 2017. 2017.
  3. Project Management Institute. Pulse of the Profession 2018. 2018.
  4. SPI Research, via Deltek. 2026 Professional Services Maturity Benchmark findings. 2026.
  5. Christensen, D. and Heise, S. Cost Performance Index Stability. National Contract Management Journal, 1993.
  6. Brooks, F. The Mythical Man-Month. 1975. Summary: Brooks's law.
Try it yourself
Free for 14 days. No credit card required.
Get started for free
See it with our team
A 30-minute demo of Magnetic.
Book a demo

FAQs

Is corrective action the same as a change request?

Not always. If a corrective action changes the project's agreed scope, budget, or schedule baseline, it goes through change control as a change request. A corrective action that stays within the baseline, such as moving a task between two team members, can be handled by the project manager without a change request.

Do you need client approval for corrective action on a fixed-fee project?

Only if the action changes what the client receives, when they receive it, or what they pay. Internal fixes, like reallocating work or adding review rounds, are your call. If the overrun comes from the client introducing extra scope, that's grounds for a change request, and you need their agreement before the extra work goes ahead.

What's the difference between a corrective action plan and a project recovery plan?

A corrective action plan responds to a specific deviation: one overrun, one bottleneck, one missed milestone. A recovery plan is a wider reset for a project that has failed several thresholds at once and can't meet its original goals, and it usually involves rebaselining scope, budget and dates with the client.

How does corrective action work on agile projects?

In agile delivery, sprint reviews and retrospectives give you a built-in point to act from. The triggers shift from budget lines to velocity and burn-down: a sprint that delivers well under its planned points two sprints running, or a release burn-up that shows the date slipping. The five steps stay the same; the cycle is just shorter.

How do you tell a client their project has gone off track?

Early, in writing, with a plan. State what has changed, why, what you propose to do and what it means for dates or cost. Clients take bad news far better when it arrives with a proposed fix than when they discover the problem themselves.

How long should you monitor after taking corrective action?

Long enough to see whether the metric that triggered it returns to its original threshold, usually one to two weeks on a typical services project. Set the review date when you agree on the action, so the check actually happens.

Jenna Green

Head of Growth

at Magnetic

Jenna Green leads marketing at Magnetic. She's worked across agencies, startups, and B2B SaaS, giving her first-hand experience of the operational challenges service firms face.

LinkedIn