Projects rarely stall because of one big mistake. Far more often it is a series of small ambiguities: what exactly is in scope, who decides, and what happens when the plan changes.
Short answer
A project stays on track when the business case, what is and is not in scope, the budget assumptions and who approves are written down before work starts. A short, regular status report surfaces problems while they are still cheap.
1. The business case before the plan
Before timelines and budgets, write down why the project exists: what problem it solves, what value it brings and how you will know it succeeded. A good business case later works as a filter: every new request is checked against it. How we write a business case and business plan is described on our business and project development page.
2. A scope you can verify
List what the project delivers and what it does not. An “out of scope” list saves more time than any project management tool, because it prevents quiet additions that stretch timelines.
A scope template
For every project, write three short lists and have everyone who decides confirm them.
- In scope: exactly what we deliver, for example a five-page website, an enquiry form and tracking set up.
- Out of scope: what is not part of this project, for example translation into a third language or integration with accounting.
- Assumptions: what the plan rests on, for example that copy arrives by a set date and that decisions come within a few days.
3. A budget with contingency and assumptions
A realistic budget includes contingency for the unexpected and clearly written assumptions it rests on. When an assumption changes, you immediately know which part of the budget needs to be re-estimated.
Every phase should end with a decision and a document, so you always know where the project stands.
4. Clear roles
Decide who approves, who delivers and who is only kept informed. When external vendors are involved, their obligations, deadlines and acceptance criteria must be written down before work starts. If you are still choosing a vendor, it helps to have requirements and selection criteria written down before the first conversation.
5. A reporting rhythm
A short, regular report on what is done, what is late, which risks are growing and which decision is needed is worth more than a big report at the end. Problems found early are cheap.
A five-line status report
- Done: what has been completed since the last report.
- Late: what is late and why.
- Risks: which risks are growing and what we are doing about them.
- Decisions: which decision is needed and from whom.
- Next deadline: what comes next and by when.
6. Review after launch
Once the project is live, compare results with the business case. Record what worked and what you would do differently next time; it is the starting point for the next round of improvement.
In short
A business case, a verifiable scope, a budget with assumptions, clear roles and a steady reporting rhythm keep a project on track. If you are planning a digital, AI or IT project, see how we run it.

