The Engineer's Migration from Spreadsheets to SaaS — What You Gain, What You Lose, and What to Watch For

Let’s start with an honest assessment of why spreadsheets remain the dominant calculation tool in electrical engineering — and why that is not entirely irrational.

A 2024 survey by the Institution of Engineers Australia found that 68% of practising electrical engineers use spreadsheets as their primary calculation tool. Among engineers with more than 15 years of experience, that figure rises to 81%. The reasons are consistent:

• Zero marginal cost. Every engineer already has Excel or Google Sheets. There is no procurement process, no subscription approval, no IT department involvement.
• Total flexibility. A spreadsheet can be adapted to any non-standard situation. Unusual installation methods, proprietary cable data, client-specific derating requirements — all can be handled without waiting for a software vendor to add a feature.
• Transparency. Every cell’s formula is visible. An experienced engineer can audit the entire calculation chain in minutes. There is no “black box.”
• Institutional knowledge. Many firms have spreadsheets refined over decades, incorporating lessons learned from specific projects. These tools encode expertise that is difficult to transfer to any external platform.

These are genuine advantages. Any SaaS platform that dismisses them as “legacy thinking” is not being honest with potential users.

The failure modes of spreadsheet-based engineering calculations are well-documented and consistent across industries:

Version control collapse

A study by the European Spreadsheet Risks Interest Group (EuSpRIG) found that 88% of spreadsheets with more than 150 rows contain at least one error. In engineering contexts, the most dangerous errors are not formula mistakes (which produce obviously wrong results) but version divergence — multiple copies of the “master” spreadsheet circulating with different corrections applied to each.

In a typical consulting firm, the cable sizing spreadsheet exists as: the original on the server, a copy on a senior engineer’s laptop with a correction to the grouping factor table, another copy on the project drive with client-specific amendments, and a fourth version emailed to a subconsultant. Within six months, no one is certain which version is authoritative.

Standards currency gap

When AS/NZS 3008.1.1:2017 replaced the 2009 edition, it modified Table 4 (current-carrying capacities for enclosed cables), Table 22 (ambient temperature derating), and several installation method classifications. Firms using spreadsheets had to manually update every affected cell, verify the updates, and ensure all copies were synchronised. Based on support queries to Standards Australia, many firms were still using 2009 data more than two years after the 2017 edition was published.

The same pattern repeated with BS 7671:2018 Amendment 2:2022, which introduced changes to maximum demand calculation methods (Appendix 15) and AFDD requirements. Spreadsheets built for the original 2018 edition required manual amendment — and many were not updated.

Audit trail absence

A spreadsheet records its current state, not its history. When a calculation is revised during detailed design, the previous version is overwritten unless the engineer manually saves a dated copy. Professional indemnity insurers increasingly ask: “Can you demonstrate what calculation was current at the time the design was issued?” Spreadsheets cannot reliably answer this question.

A well-designed SaaS calculation platform addresses the three failure modes above — and only those three. It does not make you a better engineer. It does not replace engineering judgement. It provides infrastructure that spreadsheets lack:

1. Single source of truth. One calculation engine, one set of standards data, one version. When the standard is updated, every user gets the update simultaneously. There are no divergent copies.
2. Immutable audit trail. Every calculation is timestamped, versioned, and stored. Revisions are tracked as discrete versions, not overwrites. When a PI insurer asks “what was the design basis on 15 March 2026?” the platform can answer definitively.
3. Standards currency guarantee. The vendor is responsible for updating tables and methods when standards are amended. The engineer is responsible for selecting the correct standard — but the data behind that selection is current.
4. Team consistency. Every engineer in the firm produces calculations using the same methodology, the same derating factors, the same standard references. The output is consistent regardless of who runs it.

These benefits compound with team size. A solo practitioner gains relatively little from points 1 and 4. A team of 20 engineers across multiple offices gains enormously.

SaaS platforms introduce constraints that spreadsheets do not have:

• Reduced flexibility. If the platform does not support your specific installation method, cable type, or non-standard derating requirement, you cannot simply add a row to a table. You must request the feature and wait for the vendor to implement it — or maintain a parallel spreadsheet for edge cases.
• Vendor dependency. If the vendor goes out of business, raises prices beyond your budget, or discontinues the product, your calculation archive becomes inaccessible unless the platform exports to an open format. This is a real risk with SaaS tools in niche engineering markets.
• Ongoing cost. A spreadsheet has zero marginal cost after creation. SaaS platforms require monthly or annual subscriptions. For a solo practitioner doing 20 cable sizing calculations per year, $29/month may not be justifiable on pure economics.
• Internet dependency. Most SaaS platforms require an internet connection. On remote construction sites, offshore platforms, or in developing regions, this is a genuine constraint.
• Black box perception. Even when the calculation methodology is fully documented, some engineers are uncomfortable relying on a tool where they cannot inspect every formula cell. This is a legitimate professional concern, not resistance to change.

Any vendor that does not acknowledge these limitations is selling you a product, not giving you honest advice.

Based on the evidence, here is when each tool is the rational choice:

Spreadsheets are rational when:

• You are a solo practitioner or a team of 1–2
• You work with a single standard that changes infrequently
• Your projects are similar enough that one well-tested template covers 90%+ of cases
• Your professional indemnity insurer does not require formal calculation audit trails
• You have the discipline to maintain version control manually (and you actually do)

SaaS is rational when:

• Your team exceeds 3 engineers
• You work across multiple standards (AS/NZS, BS, IEC, NEC)
• Standards updates are frequent and affect your calculations
• Your PI insurer requires or rewards auditable calculation records
• You need consistent output formatting for client deliverables
• New graduate engineers join regularly and need to produce compliant calculations quickly

Both are rational when:

• SaaS handles 80% of standard calculations; spreadsheets handle edge cases the platform does not support
• This hybrid approach is more common than vendors admit and is entirely reasonable

The strongest argument for SaaS is not efficiency — it is liability management.

When a cable sizing error leads to a fire, the investigation will examine the calculation that justified the cable selection. If the calculation was performed in a spreadsheet, the engineer must demonstrate that: (a) the spreadsheet was correctly formulated, (b) the standards data was current, (c) the correct version was used, and (d) no one modified the spreadsheet after the design was issued.

With a SaaS platform, the vendor shares some of that burden. The calculation engine was validated by the vendor. The standards data was maintained by the vendor. The audit trail was created automatically. The engineer is still responsible for the inputs and engineering judgement — but the infrastructure is defensible.

This does not mean SaaS provides legal immunity. It means the defence is more straightforward. Several professional indemnity insurers in Australia and the UK now offer reduced premiums for firms that use auditable calculation platforms, reflecting the reduced claims risk.

Note: ECalPro is a SaaS platform and therefore has an inherent bias in this comparison. We have attempted to present the evidence fairly, but readers should weight this analysis accordingly. The spreadsheet advantages described above are real, and we do not claim that SaaS is universally superior.

If you decide that SaaS is the right choice for your practice, the migration should be systematic, not abrupt:

1. Audit your current spreadsheets. Document which calculations you perform, how often, and which standards each references. Identify the 80% that a SaaS platform can handle immediately.
2. Run parallel calculations. For the first 20–30 projects, run both the spreadsheet and the SaaS tool. Compare results. Investigate any discrepancies — they may reveal errors in either tool.
3. Verify standards data. Spot-check the SaaS platform’s tables against your physical copy of the standard. Check at least 10 values per standard for current-carrying capacity, derating factors, and voltage drop constants.
4. Test the export. Ensure you can export your calculations to PDF, Excel, or another open format. Your data must survive the platform — if the vendor disappears, you need your calculation archive.
5. Keep your spreadsheets. Maintain them for edge cases the platform does not handle. There is no shame in using the best tool for each situation.

Standards referenced: AS/NZS 3008.1.1:2017, BS 7671:2018+A2:2022, IEC 60364-5-52:2009+A1:2011, NEC/NFPA 70:2023.