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.
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 organisations 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.
An original 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 organisation'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 running a multi-vendor program: three subcontracted delivery partners feeding one client program, all tracked in a single margin workbook maintained by the program's PMO analyst.
At program kickoff, the workbook holds one baseline per vendor workstream, each entered by a different vendor PM. The rate card the analyst copies in from each vendor is already a manual re-entry point — exactly the "same rates and hours are re-entered" signal in the table above — so record who owns each input from day one, not after the first mismatch.
When a fourth vendor is added mid-program, the workbook's formulas need extending to a new column set. This is where the scorecard's Logic dimension matters most: if only the original analyst can safely edit the formulas without breaking a rollup, score it a 2 and treat that as a real handover risk, not a scheduling inconvenience.
At the monthly portfolio review, the PMO needs one consolidated margin view across four vendors with different cost bases. If that consolidation is a manual copy-paste exercise every month, that is the Scale dimension's "large repeated data process is unstable" case from the signals table — score it honestly rather than absorbing the rework as normal.
At contract renewal, finance asks which vendor's data feeds which client invoice line. If the workbook cannot reconstruct that trail without asking the analyst directly, that is an Access-dimension gap, not just an inconvenience. Run a workbook audit before renewal so the scorecard reflects evidence, not impressions. None of this implies a structured tool removes the need for a named data owner at each vendor — only that it can make the ownership and consolidation visible instead of dependent on one person's workbook.
Putting those four moments on the scorecard side by side makes the total legible instead of anecdotal:
| Dimension | Evidence from the program above | Score |
|---|---|---|
| Ownership | Vendor rate re-entry has no single named owner | 1 |
| Version | One baseline per vendor workstream, not yet in conflict | 0 |
| Logic | Only the original analyst can safely extend the formulas | 2 |
| Access | Vendor-to-invoice trail depends on asking the analyst | 2 |
| Scale | Monthly four-vendor consolidation is manual copy-paste | 2 |
| Workflow | Plan and actuals still trace through to the workbook | 1 |
| Total | — | 8 of 12 |
An 8-of-12 total does not automatically trigger a purchase. It says where to investigate first: Logic, Access, and Scale each scored a material gap, so those three dimensions — not the workbook as a whole — are where evidence-gathering and a possible replacement business case should start.
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 organisation's records policy.
- Review whether control effort and decision quality actually improved.
A structured application can reduce copy handling and standardise 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 fixed-price resource-loading scenarios, a promoted delivery baseline, manual weekly actual-hours entry, current margin calculations, budget-consumption signals, and role-based views. It does not import timesheets, connect to external systems, or forecast final margin. 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.
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 implementation on 24 August 2026.