Managing a project in Excel: real limits and when to change tools
Almost every project starts on a spreadsheet. The project manager opens it for the first estimate, the PMO updates it for consolidation, and the manager projects it in the meeting room. As long as there is only one project and there are few people involved, the sheet works: it is fast, flexible, requires no configuration and costs nothing. Problems never come from the sheet itself: they come when that sheet becomes the only place where the project state lives, as projects and people increase. This article is about recognizing that moment before it does damage.
What Excel does great
Before limits, honesty: Excel does some things better than any project control tool, and giving it up would be a mistake.
- Free structure: columns, rows and sheets adapt to any need in minutes.
- Immediate calculation: formulas and pivot tables answer timely questions without waiting for any software release.
- Zero configuration: It is already installed on every company computer and almost everyone knows how to use it well enough.
- Communication: to show a sequence of activities or a rough account, a well-made graph is worth more than a report.
The point isn't whether Excel works: it's what happens when the project stops fitting into one sheet and the state has to be rebuilt every time.
What breaks when projects and people increase
Divergent versions
The file runs in the mail or lives on a network folder. Two people open it, modify it, save it: "budget_v2_finale_BIS.xlsx" is born and from that moment on no one knows which version is the real one. It is worth knowing that concurrent editing exists in Excel: according to theMicrosoft documentation, multiple people can work on the same file, but only if the sheet is saved to OneDrive or SharePoint Online and opened with a recent version of Excel. A file that travels via email or on a shared server does not benefit from this function: and in most companies the project budget travels exactly like this.
Been rebuilt by hand
If every Monday someone opens multiple files, extracts the numbers and copies them into a summary sheet, the project status is not a data: it is a manual activity. It costs hours of work, introduces transcription errors and is already old by the time it is submitted. And since rebuilding costs effort, it is always done more rarely than it should be: the status is updated when there is a meeting, not when the facts change.
Silent errors
Excel has no structural constraints: anyone can overwrite a formula with a fixed value, break a reference or copy a row in the wrong place. The sheet does not protest and does not warn anyone: the error remains there until someone discovers it, usually at the end of the day. The technical limits, in truth, are generous — according to theMicrosoft documentationthe calculation precision reaches 15 significant figures and a sheet can exceed a million lines — but no technical limit protects against the wrong modification, which remains the real risk.
No trace of the decisions
Who changed that number, when and why? There is no answer in the sheet: there is no approved history of changes, and reconstructing the reason for a deviation becomes detective work. For credible project control, it is necessary to be able to trace each number back to the decision that produced it: this is the logic of [baseline management](/controlroom/guide/project-monitoring/), which we talk about in a dedicated chapter.
The signs that it's time for a change
The switching of instruments is not decided out of boredom: it is decided on the signals. Here are the six that matter.
| Signal | Why it's a problem | What to look for in the new tool |
|---|---|---|
| There are multiple "master" copies of the same file | Nobody knows which version is true | A single source of truth with controlled access |
| The progress is reconstructed manually every week | Wasted time, transcription errors, data already old | Updated data in one place and automatically generated reports |
| The deviations are discovered in the final balance | You don't correct what you don't see in time | Forecast and deviations calculated at each update |
| Changes have no author or date | Impossible to understand how we arrived at a number | Traceability of every change |
| Multi-project consolidation takes days | The wallet is governed with old data | Aggregated views by project and by portfolio |
| The file is a bundle of sheets and linked formulas | Every change risks breaking something invisible | Data structure with rules and validations |
In my opinion, the threshold for switching tools isn't the number of lines in the file: it's the number of hands touching it and how often someone reconstructs the state by hand. Only two indicators, but they are the ones that really count.
What to look for in a project control tool
If three or more signals concern you, the question becomes: what should the new tool do? A minimal checklist, in order of importance.
- Budget, staff and commitmentsin the same place: three distinct quantities, comparable line by line, as explained in the [guide to project budget tracking](/controlroom/guide/controllo-budget-progetti-in-tempo-real-2026/).
- Baseline and plan-final comparison: the approved plan remains fixed and any deviation can be seen without recalculating.
- Updated forecast: the projection at the end of the project, not the last photograph.
- Traceability: each modification with author, date and reason.
- Reports ready: The [progress report](/controlroom/project-progress-report/) does not have to be a separate job.
- Multi-project view: from single project to portfolio without copying files.
You don't need a huge platform: you need these six elements to live in one place, shared by those who have to decide.
A mistake to avoid: changing for fashion
Switching instruments is not a career promotion. If there is only one project, there are few people involved and you update the status in a few minutes, staying on Excel is the right choice: the spreadsheet remains the best tool for simulations, ad hoc analyzes and data that have nothing to do with project control. The opposite risk is to change the tool and continue working as before, with a new sheet of paper in new software.
In my opinion, a new tool is only useful if the way in which the data is created changes - a single source, updated by those who perform it - not if only the framework of the report changes. It's the difference between an investment and an expense.
The next step
If you recognize yourself in at least three signals in the table, the choice is no longer "if" to change, but "with what". The practical advice is to start with a [demo](/controlroom/demo/): a guided tour of ControlRoom shows how baselines, forecasts and reports appear when you no longer have to build them by hand, and can be booked for free from the dedicated page. If you first want to clarify the basics of budget control, the [guide to project budget tracking](/controlroom/guide/controllo-budget-progetti-in-tempo-real-2026/) is the right place to start.
For further information
If you want to try an individual workspace for plans, tasks, budget and costs, the ControlRoom Free guide shows the path from sign-up to your first AI review. Free does not include a structured risk register or collaboration by multiple users on the same project.