Search "scope creep statistics" and the first figure you meet is usually seventy-two per cent, credited to the Project Management Institute. It appears in guides, in slide decks, in the opening line of articles that go on to sell a project-management tool. We traced it as part of a wider verification pass, and it is not PMI's number. It does not appear in the Pulse of the Profession series at all. Where it originated we could not establish; where it is repeated, each page is citing another page.
The real figure is on page seven of a report that is free to download, and it is worth reading in full once, because the details are more interesting than the headline.
What PMI actually found
Pulse of the Profession 2018, subtitled Success in Disruptive Times, reports that 52% of the projects completed in the past twelve months experienced scope creep or uncontrolled changes to the project's scope. The report calls that a significant increase from the forty-three per cent reported five years earlier.
The survey population, from the report's own front matter: 5,402 professionals in total, made up of 4,455 project management practitioners, 447 senior executives and 800 directors of project management offices, across industries including government, information technology, telecom, energy, manufacturing, healthcare and construction, in North America, Asia Pacific, Europe, the Middle East and Africa, Latin America and the Caribbean.
Two more figures from the same page. Organisations PMI classes as champions (80% or more of projects on time, on budget and meeting intent) reported scope creep on about a third of projects, 33%, while underperformers reported 69%. And the share of projects respondents called highly complex rose from 35% in 2013 to 41% in 2018, which the report links to the scope problem.
The report's definition, for the record: the uncontrolled expansion of product or project scope without adjustments to time, cost, and resources.
Why it does not describe your studio
Read the population again. These are people running projects inside large organisations, with executive sponsors, project management offices and formal change-control processes. The scope creep they are measuring is a requirements document drifting inside a company, over a horizon of months, with money that belongs to the organisation.
A freelance brand project has none of that machinery. The "project" is one person and one client. Scope creep arrives as a Thursday email asking for a fourth logo variant, and it costs the freelancer directly, out of a fixed fee, in hours nobody is tracking. Whether the corporate rate is fifty-two per cent or seventy-two tells you nothing about how often that email arrives, or what it costs when it does. It is weather in a different country.
This is not an argument that scope creep is rare in freelance work. It is plainly common; every freelancer has a story. It is an argument that no published statistic measures it, and that a figure borrowed from project management and presented as if it did is doing rhetorical work, not informing you.
The number you can actually have
The only scope-creep figure that describes your practice is one you collect. It takes a spreadsheet and about a minute per event.
Every time a request arrives outside the agreed scope, log it: the date, what was asked, roughly what it would cost in hours, and what you did (absorbed it, absorbed it and said so, or quoted it). After a year you will know your own rate, in requests per project and in hours given away, and you will know which kind of client and which kind of project produces it. That figure is worth more than anything PMI publishes, because it is about you.
It also changes behaviour, in a way a statistic never does. A freelancer who has written down eleven absorbed requests in a quarter, totalling twenty-two hours, stops absorbing the twelfth.
What actually reduces it
Not a statistic, and not a framework. Four sentences in the proposal, written before the project starts: a scope line that names what is included and, specifically, what is not; a revision cap that defines what a round is; a change-order note ready to send the same day a request arrives; and a kickoff warning that you will send one. The scope-creep post has all four written out, and the change-order template is the third of them with the blanks left in.
The reason those work where "communicate early" does not is countable scope. "A website" settles nothing when the client asks for one more page. "Five page templates" settles it, because the request is now arithmetic: a sixth template, priced, with a new date. That is also why the proposals North drafts count everything countable inside each option, so the week-six conversation has a number to be about.
Keep the PMI figure for context if you like. Keep your own log for decisions.
Common questions
- What percentage of projects experience scope creep?
- The verified figure is 52%, from PMI's Pulse of the Profession 2018, measuring projects completed in the previous twelve months as reported by 5,402 project professionals across industries such as government, IT, telecom, energy, manufacturing, healthcare and construction. The same report says that was up from forty-three per cent five years earlier, and that organisations it classes as champions reported 33% against 69% for underperformers. Nothing in it is specific to creative or freelance work.
Sources checked 2026-08-29