Replace a project margin spreadsheet when its control burden or operational risk exceeds its value: teams reconcile duplicate copies, formulas are difficult to review, sensitive rates need finer access, baseline history is unreliable, or repeated multi-project reporting depends on manual consolidation. Confirm the replacement supports the real workflow, then migrate in stages rather than assuming software alone fixes process problems.
Terms used in this guide. cost: the expense included in the stated project model; margin: revenue left after the included costs; margin percentage = that amount / revenue × 100; baseline: the approved original plan kept for comparison; forecast: recorded actuals plus the remaining plan, a calculation and not a prediction.
In plain words
A spreadsheet is fine while the work is small and one person looks after it. It is time to move on when copies multiply, formulas are hard to check, you need to control who sees pay rates, or someone spends days each month combining sheets by hand. Size alone is not the test: a larger or shared workbook can be fine with a named owner, controls and a reconciliation, while a small one can still need replacing if it holds pay data it should not or its errors go unnoticed.
Who this helps: Finance leaders, PMO staff and managers who run margin tracking in spreadsheets.
Questions this guide answers:
- When should you stop using Excel for project margin?
- What are the signs a spreadsheet is no longer enough?
- How do you move from a spreadsheet to project margin software?
Margin words: gross, contribution, managed margin, budget, forecast and the roles named here are defined once in the margin vocabulary.
A familiar picture: seven copies of the margin file
The PMO manager opens the shared drive and finds seven versions of the margin workbook. Month-end consolidation takes two days because each copy was built on a different baseline. Nobody can say which one the quote used. That is what a workbook that has outgrown its role looks like. The rest of this guide shows how to confirm it with evidence and move calmly.
When is a spreadsheet still a suitable tool?
A spreadsheet can be appropriate for a focused calculation with a trained owner, limited users, transparent formulas, controlled inputs, a reliable version, and proportionate review. It is flexible, inspectable, and familiar. Replacing it merely because a newer tool exists is not a business case—see the project margin management guide for the definition and workflow a replacement still has to serve.
ICAEW advises organizations to assess spreadsheet dependence and apply controls according to risk. Its suitability principle says a database may fit large quantities of similar data and dedicated software may fit an established process, while also asking whether users can understand and maintain the spreadsheet for current and future needs.
Which signals suggest the workbook has outgrown its role?
| Observed signal | Why it matters | Evidence to collect |
|---|---|---|
| Several "final" copies circulate | Reviewers may use different baselines or actuals. | Monthly count of active copies and reconciliation time. |
| The same rates and hours are re-entered | Duplicate input increases mismatch risk. | Input map showing source, re-entry points, and owners. |
| Formula logic depends on one person | Maintenance and review become fragile. | Documented formulas, peer-review findings, and handover test. |
| Users need different rate visibility | A shared workbook may expose or over-restrict sensitive detail. | Role-to-data access matrix and actual sharing method. |
| Baseline changes are hard to reconstruct | Current variance can lose its reference point. | Version history, approval records, and change log gaps. |
| Portfolio reporting requires manual consolidation | The process consumes time and can apply inconsistent definitions. | Close calendar, adjustments, mapping exceptions, and elapsed effort. |
One signal is not an automatic replacement decision. A control improvement may be enough. Repeated signals across projects, especially when they affect financial or client decisions, strengthen the case for a structured workflow.
A replacement decision scorecard
Score each dimension 0 for controlled, 1 for recurring friction, or 2 for a material control gap. Document evidence beside the score; do not use the total as an automated purchasing rule.
| Dimension | 0: controlled | 1: recurring friction | 2: material gap |
|---|---|---|---|
| Ownership | Named owner and reviewer | Backup unclear | No accountable owner |
| Version | One governed current file | Copies reconciled manually | Baseline cannot be established |
| Logic | Simple and peer reviewed | Complex sections need one expert | Results cannot be reproduced |
| Access | Access matches role need | Manual sharing exceptions | Sensitive data is inappropriately exposed |
| Scale | Focused project model | Repeated consolidation | Large repeated data process is unstable |
| Workflow | Plan and actuals remain traceable | Frequent hand-off corrections | Approved plan and delivery data disconnect |
A higher total means investigation is more urgent, not that a particular product is correct. Define mandatory capabilities, acceptable residual risks, migration cost, control ownership, and a test plan before selecting a replacement.
Add a costed baseline to the decision: measure hours spent collecting inputs, reconciling versions, correcting mappings, reviewing formulas, and producing portfolio outputs for several cycles. Compare that observed burden with implementation, training, subscription, migration, and continuing-control costs. Avoid unsupported savings claims; a replacement is justified only when its expected benefits and residual risks fit the organization's evidence and priorities.
What should a replacement actually improve?
- one governed record of the approved price and resource baseline;
- structured actuals at the detail and period the review needs;
- consistent formulas and cost definitions;
- role-appropriate visibility for sensitive data;
- traceable changes and named decision ownership;
- repeatable project and portfolio views without silent remapping.
Do not require features unrelated to the process, and do not assume "automation" where source data still needs a human owner. The future-state map should say exactly which entries remain manual.
How does the scorecard play out on a multi-vendor program?
Consider a systems integrator consolidating four delivery partners in one workbook. Score the observed control, not the inconvenience alone. In this illustration the PMO analyst is accountable but has no trained backup; the baseline is identifiable; complex formulas depend on one expert; permissions have been tested; consolidation is manual but reconciled; and handoff corrections recur.
| Dimension | Evidence | Score |
|---|---|---|
| Ownership | Accountable owner; backup unclear | 1 |
| Version | One governed baseline | 0 |
| Logic | Complex sections depend on one expert | 1 |
| Access | Sharing matches tested role needs | 0 |
| Scale | Repeated manual consolidation with reconciliation | 1 |
| Workflow | Recurring handoff corrections | 1 |
| Total | Investigation aid, not a purchase threshold | 4 of 12 |
If results cannot be reproduced, Logic becomes 2. If sensitive rates are inappropriately exposed, Access becomes 2. A missing vendor-to-invoice trail concerns lineage and workflow; it is not automatically an access failure. Investigate the evidence and cost of remediation before deciding whether to improve the workbook or replace it.
Moving from spreadsheets to project margin software
Margin often slips after the deal is won because the spreadsheet that priced the work is not the one delivery uses: the agreed team, hours and rates stop being the reference. Whether you choose an Excel alternative or improve the workbook, close that gap first.
- Fix the baseline at the win. Keep the agreed price, team, hours, rates and target margin as the approved pricing baseline that delivery is measured against.
- Record delivery against it. Approved time, expenses and change requests on the same cost basis, so actual and forecast margin always compare with what was sold.
- Review the gap every week. Read margin variance in points with its drivers and act while there is time. Retire the workbook once old and new results reconcile on a pilot project.
The six controls below make that move safely.
How should the transition be controlled?
- Inventory active workbooks, owners, consumers, formulas, data, and sensitivities.
- Agree the margin definition, baseline rule, access matrix, and cut-off process.
- Select a small representative project and reconcile old and new results.
- Resolve differences before migrating more projects.
- Freeze or archive the retired workbook according to the organization's records policy.
- Review whether control effort and decision quality actually improved.
A structured application can reduce copy handling and standardize a workflow, but it cannot define scope, approve commercial changes, verify source data, or guarantee project profit. Migration can also reproduce old errors if formulas and assumptions are transferred without review.
Where Managed Margin fits
Managed Margin supports pricing strategies for fixed-price and time-and-materials work, a finalized baseline, handover, approved weekly timesheets, expenses, change requests, and baseline, actual and forecast margin with role-based views. It does not import timesheets or accounting data. Compare the current Managed Margin workflow with your mandatory capability map rather than assuming fit.
If the spreadsheet remains appropriate, use the project margin spreadsheet structure and workbook audit checklist to improve control.
- What Is Managed Margin? Meaning, Formula and Software
- How to Share Project Margin With Sales Without Showing Salaries
At the office: Greta counts the signs
An illustrative story with invented figures, to show how the idea works in a real office.
Greta, a PMO manager, lists what is happening. There are seven versions of the margin file. Month-end consolidation takes two days. A sales colleague accidentally saw salary data. A formula error was found only after a client meeting.
She scores each sign from 0 to 2 and the total is high. She does not rush: she first audits the file, then writes down what a replacement must do, then tests two options on a real project.
The move is a controlled project of its own, and the old file stays read-only until the new numbers match.
Who decides to replace the spreadsheet?
| Step | Owner | Checkpoint |
|---|---|---|
| Count the signs | PMO manager | Copies in circulation, reconciliation time, repeated errors |
| Score the friction | PMO manager and finance | Each dimension 0, 1 or 2 with evidence; the total is not an automatic rule |
| Plan the move | Operations manager | Workbooks inventoried; margin definition and baseline rule agreed |
| Run a pilot | Project manager | One representative project is run in both systems and compared |
Frequently asked questions
When is a spreadsheet still suitable?
When volume, risk and users are small and controls are adequate.
When should you replace a project margin spreadsheet?
When several “final” copies circulate, reconciliation takes longer each month, errors repeat, or the plan used to price a job is not the one delivery uses. Score those signs with evidence, then pilot the replacement on one project.
Continue the sequence: guides to read next
- How to Structure a Project Margin Spreadsheet: making the sheet as good as it can be
- How to Audit a Project Margin Spreadsheet: the audit behind the decision
- Project Margin Management Software: How to Evaluate It: evaluating the replacement
Sources and methodology
- ICAEW, Twenty Principles for Good Spreadsheet Practice. Used for risk-based spreadsheet governance, suitability, competence, structure, review, version control, and access principles.
- The scorecard is an original Managed Margin decision aid, not an industry benchmark. Product scope was reviewed against the current Managed Margin application on 26 September 2026.