Nobody decided to run a project without a scope. It just happened. Someone saw a demo, a manager approved a small purchase, a vendor started "configuring," and three months later there is a half-installed system, a growing list of invoices, and a steering meeting where nobody can quite say what was approved, by whom, or what finished looks like.
If that sounds familiar, the problem is not the technology. It is that the project never formally existed.
There is activity, but no agreement. The scope lives in email threads and in the vendor's statement of work. The budget is whatever has been spent so far plus whatever the next quote says. Several people are "involved," but nobody is accountable. And when something changes — a new requirement, a delay, a workaround on the floor — it simply happens, with no record of who decided or why.
It often surfaces at the worst moment: a finance review asking what the money bought, or an ISO 9001 auditor asking to see how a change to a production system was planned and controlled.
Small starts escape governance. Many digital projects begin below the threshold that triggers formal approval. By the time they are big enough to notice, they are already in motion, and nobody wants to stop and start over.
"IT project" versus "operations change." A new system on the floor changes how product is made, inspected or tracked. But if it is treated as an IT purchase, it bypasses the management-of-change discipline the plant would apply to a new machine or process.
Ownership is assumed, not assigned. Everyone assumes someone else is accountable. Responsibility is spread across IT, operations, quality and the vendor, which means it is effectively held by nobody.
Momentum feels like progress. Meetings, configurations and invoices create the feeling that the project is moving, even when there is no agreed destination.
Money without a baseline. Without an approved case, there is no way to say whether the project is over budget, under-delivering or succeeding. Spend continues because there is nothing to measure it against.
Decisions nobody can defend. When results disappoint, there is no record of what was agreed, so the conversation becomes blame instead of correction.
Audit exposure. ISO 9001 expects changes to the quality management system to be planned (clause 6.3), roles and authorities to be assigned (clause 5.3), documented information to be controlled (clause 7.5), and changes affecting production to be reviewed and controlled with records of who authorized them (clause 8.5.6). A production system that went live without any of that is a finding waiting to happen — and customers with supplier audits ask the same questions.
Floor trust. When a system appears without explanation and changes without notice, the floor learns to work around it.
"Paperwork will slow us down." A clear scope, budget and owner is not paperwork; it is the thing that lets a project finish. Unscoped projects rarely move faster — they just never end.
"It is too late to formalize it now." It is rarely too late. It is only more uncomfortable the longer it waits.
"ISO only cares about quality procedures." Any change that affects how conforming product is produced, controlled or recorded falls within the quality management system's concerns.
In a healthy project, anyone involved can point to one approved record: the problem, the scope, the expected benefit, the budget, the named owner, the people responsible and consulted, and the approvals. Changes are logged with who authorized them. The record is controlled like any other quality document. And the project has a finish line everyone agrees on.
To help plants get there, we built a free Project Approval & Charter Builder that turns what you already know into a charter and change record you can take to leadership. For the quality-system side, our sister brand ExceleorQMS focuses on keeping records audit-ready. Related reading: warning signs of a slipping ERP go-live and proving digital transformation ROI.
If your project is moving but nobody can say where to, read the stuck project situation, then tell us what's going on. We will reply from Info@exceleor.com.
If that sounds familiar, the problem is not the technology. It is that the project never formally existed.
What This Situation Actually Looks Like
There is activity, but no agreement. The scope lives in email threads and in the vendor's statement of work. The budget is whatever has been spent so far plus whatever the next quote says. Several people are "involved," but nobody is accountable. And when something changes — a new requirement, a delay, a workaround on the floor — it simply happens, with no record of who decided or why.
It often surfaces at the worst moment: a finance review asking what the money bought, or an ISO 9001 auditor asking to see how a change to a production system was planned and controlled.
Why It Happens
Small starts escape governance. Many digital projects begin below the threshold that triggers formal approval. By the time they are big enough to notice, they are already in motion, and nobody wants to stop and start over.
"IT project" versus "operations change." A new system on the floor changes how product is made, inspected or tracked. But if it is treated as an IT purchase, it bypasses the management-of-change discipline the plant would apply to a new machine or process.
Ownership is assumed, not assigned. Everyone assumes someone else is accountable. Responsibility is spread across IT, operations, quality and the vendor, which means it is effectively held by nobody.
Momentum feels like progress. Meetings, configurations and invoices create the feeling that the project is moving, even when there is no agreed destination.
Warning Signs
- Nobody can produce a single approved document describing scope and expected benefits.
- The budget has been increased informally, or never formally set.
- Different people give different answers about who owns the project.
- Changes to scope or timing are not recorded anywhere.
- The vendor's statement of work is the de facto project plan.
- Quality has not been involved in a change that affects production records.
What It Costs
Money without a baseline. Without an approved case, there is no way to say whether the project is over budget, under-delivering or succeeding. Spend continues because there is nothing to measure it against.
Decisions nobody can defend. When results disappoint, there is no record of what was agreed, so the conversation becomes blame instead of correction.
Audit exposure. ISO 9001 expects changes to the quality management system to be planned (clause 6.3), roles and authorities to be assigned (clause 5.3), documented information to be controlled (clause 7.5), and changes affecting production to be reviewed and controlled with records of who authorized them (clause 8.5.6). A production system that went live without any of that is a finding waiting to happen — and customers with supplier audits ask the same questions.
Floor trust. When a system appears without explanation and changes without notice, the floor learns to work around it.
Common Misconceptions
"Paperwork will slow us down." A clear scope, budget and owner is not paperwork; it is the thing that lets a project finish. Unscoped projects rarely move faster — they just never end.
"It is too late to formalize it now." It is rarely too late. It is only more uncomfortable the longer it waits.
"ISO only cares about quality procedures." Any change that affects how conforming product is produced, controlled or recorded falls within the quality management system's concerns.
Questions Leaders Should Be Asking
- What, exactly, was approved — and where is that written down?
- Who is the single accountable owner, and do they know it?
- What is the approved budget, and what has been spent against it?
- What problem is this solving, and how will we know it worked?
- How have changes been decided and recorded since the start?
- If an auditor asked about this change tomorrow, what would we show them?
What Good Looks Like
In a healthy project, anyone involved can point to one approved record: the problem, the scope, the expected benefit, the budget, the named owner, the people responsible and consulted, and the approvals. Changes are logged with who authorized them. The record is controlled like any other quality document. And the project has a finish line everyone agrees on.
To help plants get there, we built a free Project Approval & Charter Builder that turns what you already know into a charter and change record you can take to leadership. For the quality-system side, our sister brand ExceleorQMS focuses on keeping records audit-ready. Related reading: warning signs of a slipping ERP go-live and proving digital transformation ROI.
Frequently Asked Questions
Why do digital projects end up without a scope or owner?
They often start small, below formal approval thresholds, and are treated as IT purchases rather than operational changes — so ownership and scope are assumed rather than assigned.
Which ISO 9001 clauses relate to uncontrolled system changes?
Most commonly 6.3 (planning of changes), 5.3 (roles, responsibilities and authorities), 7.5 (documented information) and 8.5.6 (control of changes affecting production or service provision).
Is it too late to formalize a project that is already underway?
Almost never. Recording what was decided, confirming the owner and budget, and controlling future changes is valuable at any point in a project.
What is a project charter?
A single approved record that states the problem, scope, expected benefits, budget, accountable owner, key roles and approvals for a project.
Tell Us What's Going On
If your project is moving but nobody can say where to, read the stuck project situation, then tell us what's going on. We will reply from Info@exceleor.com.