How Much Time and Money Does AI Save in Project Management?

How much time does AI actually save in project management?

Roughly three hours a week for managers generally, and nobody has published a credible figure for project managers specifically. That gap is worth knowing, because it is why the numbers on this topic vary by a factor of ten.

The most defensible survey found this run is Expleo's AI Pulse study, run in March 2026 among managers in Germany, the UK and France. According to the results reported from it, 27% of the managers surveyed reported a weekly time saving of three to three and a half hours from AI, with averages of 3.3 hours a week in Germany, 3.5 in the UK, and 3.2 each in France and Ireland. Managers rather than project managers, which makes it a floor rather than a precise answer for a PMO, and the underlying report was not available to read this run, so the sample and method are not something to lean on hard.

For project managers themselves, the closest real data is vertical. Mastt surveyed 108 construction project management professionals between March and June 2026 and published in July. Its respondents put reporting first among the places AI helps, at 84.3%, ahead of document management at 69.4%, and 9.3% said they are using AI agents today against 46.3% planning to start. Construction project management only, and Mastt sells software to that market, so read it as vendor research with a named sample and a stated field period.

Everything else circulating on this topic is an estimate with no method attached. Checking page one of this query on October 16, 2026, the figures on offer ran from about two hours a week to nineteen, most of them attributed to nobody, several of them mirrors of the same article, and two of them crediting a figure to Gartner that no Gartner document found this run contains. None carried a survey sample, a date and a definition of the task together.

Treat three hours a week as the number to plan against, with the caveat that it is an average across managers doing different work. The useful exercise is not finding a better survey. It is measuring your own reporting cycle, which the section below sets out. For the unqualified version of this question, how much time and money AI automation saves covers the wider evidence.

Where does the 80% figure come from, and should we believe it?

The 80% figure comes from a Gartner press release issued in March 2019, reported at the time by SiliconANGLE as a prediction that AI would eliminate about 80% of project management office tasks by 2030. Seven years old, written before the current generation of models existed, and quoted constantly without its date.

Worth reading what it actually said. According to the contemporaneous coverage, the release was about program and portfolio management, quoted the Gartner research vice president Daniel Stang, and gave data collection, reporting and tracking as its examples. That is a claim about administration rather than about management, and the shortened version that circulates now, "80% of project management tasks", drops the distinction that made it defensible. The wording varies between citations too, which is what happens to a figure that has been passed along for seven years.

Set against that, the dates settle it without anybody needing an opinion. A 2019 forecast about 2030 is not evidence about 2026 in either direction, and anybody quoting it as a current finding is quoting a prediction as a measurement.

The reason to spend a section on this is practical. The 80% figure is doing real damage to project budgets, because it sets an expectation that AI removes most of the job, and when a pilot saves three hours a week the project reads as a failure. Three hours a week per manager is a genuinely good return on a software subscription. It is a poor return on a six figure programme that promised transformation.

So the useful framing is the opposite of the headline. Ask which specific administrative cycles in your delivery process can be removed, price those, and leave the forecast out of the business case. Why AI automation projects fail covers what happens when the expectation is set by a press release.

Which project management tasks can AI actually take over?

The project management tasks AI can actually take over are the administrative cycle, not the judgement. The split below is the one that holds up against the evidence above.

Task	What AI does today	What stays with a person
Status reporting	Assembles the report from the systems that already hold the data	Deciding what the status actually is when the data disagrees
Chasing updates	Asks each owner, collects the reply, flags who has not answered	The conversation with the person who keeps missing dates
Meeting notes and actions	Transcribes, summarises, extracts commitments	Confirming what was actually agreed
Risk logs	Drafts entries from issue history and flags recurring themes	Judging which risk is the one that will hurt
Document assembly	Produces the first version of the plan, the change request, the closeout pack	Approving anything that commits the business
Schedule updates	Moves dependent dates when a task slips and shows the knock on	Deciding what to cut when the date cannot move
Resource conflicts	Spots two projects claiming the same person in the same week	The negotiation that resolves it
Reading the room	Nothing	All of it

Two patterns in that table. First, almost everything in the middle column is moving information between systems and people rather than thinking, which is why the savings are real and modest. Second, every row still has a person in it, which is why "AI project manager" is a category error rather than a product.

The money follows the first pattern. A delivery manager running six projects spends a predictable share of each week assembling status from four systems, chasing eleven people for updates and reformatting it for two different audiences. That cycle is measurable, repeats weekly, and is exactly the shape of work a built process handles well: a clear trigger, structured sources, a defined output and a person reviewing the result.

What does not work is pointing a model at the project and asking it to manage. Can AI take our meeting notes and handle the follow-ups? covers the adjacent case, where the notes are cheap and the follow up routing is the part worth building.

Can an AI agent run a project on its own?

No, an AI agent cannot run a project on its own, and there is a measurement for that rather than an opinion. TheAgentCompany benchmark, built at Carnegie Mellon with Duke and independent researchers, set 175 tasks inside a simulated software company and included project management as one of its six categories, alongside software development, data science, administration, HR and finance.

According to the paper, the best baseline agent completed about 24% of those tasks autonomously in the first version, and the revision of September 2025 reports Gemini 2.5 Pro at 30.3%. The authors describe simpler tasks as often solved and longer horizon work as still out of reach, which is the shape of project management work: the individual steps are easy and the sequencing across weeks is the job.

What that means for a PMO considering an agent is narrow. A tightly scoped agent that assembles the Thursday status pack from four systems, flags the three owners who have not replied and drafts the summary for review is doing work the benchmarks support. An agent given the project and told to run it is doing work the benchmarks say fails roughly seven times in ten.

The design that works, here as everywhere, puts the model on the reading, classifying and drafting, the system on the fetching, writing and logging, and a person on whatever got flagged as uncertain. The flagged pile is the whole safety mechanism, and its size week to week is also your best signal that something upstream has changed.

How do we work out what it is worth on our own projects?

Work out what it is worth on your own projects by measuring the reporting cycle before you buy anything, because that number is both the business case and the thing nobody has.

Four steps. Count the hours. For one month, have each delivery manager log the time spent assembling status, chasing updates and reformatting reports for different audiences, separately from the time spent on the projects themselves. Most teams find the administrative share larger than they expected and concentrated on two or three people.

Multiply by loaded cost. Salary plus payroll tax, benefits and overhead, divided by working hours. That gives the annual cost of the cycle, which is the figure a quote has to beat.

Then subtract what stays. If the report still needs a human read before it goes to a client, the saving is the assembly time rather than the whole cycle. Honest subtraction at this stage is what keeps the project from being judged against a number nobody could have hit.

Then check the inputs. If the status data lives in four systems and two of them are maintained by hand, the automation project is partly a data project. That is worth knowing before anybody quotes you, not in month three. Is our data good enough for AI? covers how to check, and how to measure AI automation savings sets out the arithmetic in detail, including how to avoid counting the same hour twice.

One thing worth measuring that most teams miss: the delay cost. A status problem discovered on Thursday rather than the following Tuesday is often worth more than the hours saved assembling the report, because the decision happens four days earlier. Harder to price and frequently the larger number.

What does AI change about a project manager's job?

AI changes a project manager's job by moving it toward the parts that were always the job. The administrative cycle shrinks, and what is left is the negotiation, the judgement about which risk matters and the conversation with the person who keeps missing dates.

That is a better job and it is also a harder one, which is why adoption is uneven. A manager whose week was two fifths reporting has a week with more room in it and no fewer problems, and the first few weeks of that feel like exposure rather than relief. Teams that handle this well say out loud what the time is for before they free it up.

The capacity question is the one owners should be asking. Three hours a week per delivery manager across a team of six is most of a day and a half, and the useful version of that is taking on more work with the same team rather than counting a saving. For an owner led business, that usually looks like running a seventh project or shortening the gap between winning the work and starting it.

What it does not change is accountability. A report assembled by a system is still signed by a person, and a schedule moved automatically is still somebody's commitment to a client. Every sensible design keeps a person between the automated output and anything that leaves the business, which is less about the technology than about the fact that your client hears a promise from you rather than from a workflow.

For a worked example of the shape, the Universidad Maimonides case study covers fifty to a hundred data files per batch becoming records built automatically, about fifteen hours a week back, running on our infrastructure ever since.

Frequently asked questions

How much does it cost to automate project reporting?

Cost is driven by how many systems the report has to read, how clean the data in them is, how much judgement sits in the summary and who operates the thing afterwards. A report assembled from two mainstream systems with structured data is a small build. A report pulling from four systems where two are maintained by hand is a larger one, because the cleanup is part of the work. The number to establish first is your own: the hours the reporting cycle eats each week, multiplied by loaded hourly cost, annualised. We scope each engagement on the call rather than publishing a rate.

How does AI status reporting actually work?

A trigger starts it, usually a schedule. The system reads the project data from wherever it lives, which is the part that takes the engineering. A model drafts the narrative from the structured facts rather than inventing them, each number carries its source so a reader can check it, and anything the model is unsure about is flagged rather than guessed. A person reviews it before it goes to a client. The build is mostly connections and rules, and the model is a small part of it.

Is an AI project management tool better than automating what we already have?

Different purchases. A tool with AI features in it suits a team willing to move its projects into that tool and work the way the tool works, and for many teams that is the right answer. Automating what you already have suits a team whose project data is spread across software they are not going to replace. The question to settle first is whether the reporting pain comes from the tooling or from the fact that the data lives in four places, because new software does not fix the second one.

Can our project reporting be automated, or is it too bespoke?

If the report is assembled from data that exists somewhere in a system, usually yes, including when the current version is built by hand in a spreadsheet every Thursday. The test is whether a competent new starter could be taught to produce it in a week from written instructions. What does not automate is the part where somebody decides the project is amber rather than green despite what the numbers say, and that judgement is a smaller share of the cycle than most managers assume.

Does AI reduce the need for project managers?

The measured evidence points at hours rather than headcount. The savings land on administration, which is a share of every manager's week rather than a whole role, and the work left over is the part that needed a person in the first place. Research published by the Federal Reserve Bank of Dallas in September 2026 found that firms more exposed to AI reducing job postings by roughly 5% to 6% by the middle of 2024 and 8% to 9% by early 2026, which is a labour market adjusting at the margin rather than replacing a profession.