Spreadsheet Dependency: Could Your Business Run Without One Expert?

Business Continuity • Process Management • ERP

Could Your Business Run Tomorrow If Your Spreadsheet Expert Took Leave?

Every business has that one person who knows which spreadsheet to open, which tab to check, which formula to repair and which number to trust.

They may manage the monthly sales report, calculate commissions, track inventory, prepare cash-flow forecasts or consolidate figures from several departments. The spreadsheet works because they understand how it works.

But what happens when that person takes leave, resigns or is simply unavailable when the business needs an urgent report?

The issue is not that spreadsheets are inherently unreliable. It is that important business knowledge can become hidden inside undocumented formulas, personal workarounds and processes only one employee understands.

1. The spreadsheet works. But does the business understand it?

Consider an illustrative UAE distribution company, Gulfline Trading. Every month, its finance and sales teams use a spreadsheet to calculate product margins, sales commissions and branch performance.

The workbook has several tabs. One imports sales data, another adjusts costs, a third calculates margins and a final tab prepares the management summary.

It has been used for years. The numbers usually look correct, and management relies on the report during monthly reviews.

But there is a problem: only one employee knows that:

• One tab must be refreshed before the other tabs are updated.
• A particular column needs to be manually adjusted for returned goods.
• The commission calculation uses an exception for certain product categories.
• A hidden worksheet contains the exchange rates used in the margin calculation.
• The final report must be copied into another workbook before it can be shared.

None of these steps is documented properly. Other employees know how to enter data, but they do not understand the full calculation.

When the employee is unavailable, the monthly report is delayed. Nobody is confident enough to change the formulas or confirm whether the results are correct.

The real risk: the business does not simply depend on a spreadsheet. It depends on one person’s knowledge of the spreadsheet.

2. What makes a spreadsheet a business continuity risk?

A spreadsheet becomes a continuity concern when an important business process depends on information, calculations or instructions that are difficult for another authorised employee to understand and reproduce.

A. Undocumented formulas

A formula may calculate a margin, tax amount, commission or stock requirement correctly. But if nobody knows what the formula represents, which inputs it uses or why a particular adjustment exists, the result becomes difficult to verify.

For example, a formula might calculate a product’s contribution margin using selling price, purchase cost, freight and a manually entered adjustment. If that adjustment is not explained, another employee may remove it or apply it twice.

B. Hidden assumptions and fixed values

Some spreadsheets contain values embedded directly inside formulas. Others use hidden worksheets, named ranges or separate workbooks that hold important assumptions.

Examples include:

• Commission percentages that change depending on sales targets.
• Exchange rates used to convert purchase costs.
• Minimum stock quantities based on management decisions.
• Discount limits that are not recorded anywhere else.
• Manual adjustments for returns, damaged stock or special customers.

If these assumptions are not visible and documented, employees may not know when they should change or who is authorised to approve a change.

C. Linked files and manual steps

A workbook may depend on several other files. It may also require a user to download data from one system, copy it into another workbook, refresh a query, run a macro and manually transfer the result.

When the process depends on a particular sequence, a missed step can affect the final output. If the supporting file is renamed, moved or replaced, the process may stop working as expected.

D. No clear version ownership

Different employees may maintain separate copies of the same workbook. One person updates the formulas while another continues using an older version. A report may be circulated without anyone knowing which file was used to prepare it.

Version history and controlled access can help, but the business still needs a clear rule about which workbook is approved and who is allowed to change it.

E. No independent review

When the person who created a spreadsheet is also the only person who checks it, errors can remain unnoticed. Important calculations should have appropriate review and testing based on the workbook’s business impact.

3. What happens when the spreadsheet expert is unavailable?

Let’s return to Gulfline Trading. Its spreadsheet expert takes an unexpected two-week leave during the month-end reporting period.

The finance team needs to prepare the management report, while sales managers are waiting for commission figures.

The company still has the spreadsheet. It has the data. It has employees who understand the business. What it lacks is a documented, repeatable way to complete the process.

This is why key-person dependency should be treated as an operational risk, not simply an employee availability issue.

4. How dependent is your business on its spreadsheets?

Not every spreadsheet needs to be replaced. A personal calculation sheet or a one-time analysis may be perfectly reasonable.

The first step is to identify the workbooks that support important business activities and assess how difficult they would be for another employee to operate.

A practical spreadsheet dependency matrix

Questions to ask your team

• Which spreadsheets are required every day, week or month?
• Which reports are used to approve payments, purchases or sales decisions?
• Which workbooks contain calculations that affect financial results?
• Does anyone else understand the formulas and assumptions?
• Can another employee complete the process without calling the workbook owner?
• Are the source files, refresh steps and output checks documented?
• What happens if the workbook becomes corrupted or the owner is unavailable?

A useful continuity test: ask an authorised backup employee to complete the process using the available instructions, without help from the primary owner. Record where they get stuck. Those gaps reveal the real dependency.

5. Document the knowledge before it disappears

One of the simplest ways to reduce spreadsheet dependency is to make the process understandable to someone other than its creator.

For important workbooks, documentation should explain more than the file name and the person who created it.

Create a workbook information sheet

Every business-critical workbook should have a clear record of:

• Purpose: what business activity the workbook supports.
• Owner: who is responsible for its accuracy and maintenance.
• Backup owner: who can operate it when the primary owner is unavailable.
• Data sources: which systems, reports or files provide the inputs.
• Update frequency: when and how the information is refreshed.
• Formula logic: what the important calculations mean.
• Assumptions: which rates, thresholds and exceptions are used.
• Outputs: who uses the results and for which decisions.
• Version history: when important changes were made and who approved them.

Explain the formulas that matter

It is not necessary to write a long explanation for every simple formula. Focus on calculations that influence business decisions or downstream processes.

For example, a margin workbook might document:

• Which selling price is used in the calculation.
• Whether the cost includes freight and other landed costs.
• How discounts and returns are treated.
• Whether the margin is calculated before or after specific expenses.
• Who approves changes to the calculation.

Document the process from beginning to end

A formula guide alone is not enough if employees do not know how to run the process. Include the sequence of activities:

1. Where to obtain the source data.
2. How to prepare and validate the inputs.
3. Which sheets, queries or macros must be refreshed.
4. Which checks must be completed before accepting the output.
5. Where the final report should be saved and who should receive it.
6. What to do if a calculation or source file fails.

This turns individual knowledge into an organisational procedure.

6. Put basic spreadsheet controls in place

Even when a spreadsheet remains the right tool, it should not depend on memory and informal instructions.

For important workbooks, establish controls around:

These practices align with the ICAEW’s Twenty Principles for Good Spreadsheet Practice, which cover spreadsheet planning, design, documentation, testing, controls and version management.

7. Build process continuity—not just spreadsheet backups

A backup copy protects a file. It does not automatically protect the business process that depends on it.

Continuity requires the business to make sure another authorised employee can perform the task, understand the output and respond when something goes wrong.

8. When should a spreadsheet become part of an ERP process?

Some spreadsheets are useful and should remain spreadsheets. They are flexible tools for analysis, modelling, temporary calculations and specialised tasks.

But when a workbook becomes the unofficial system for an important business process, it may be time to consider a more structured solution.

The key consideration is whether the spreadsheet is simply helping someone analyse information or whether it has become the place where the business actually records, controls and approves its work.

When multiple people depend on the same workbook for recurring transactions, stock decisions, approvals or financial records, a shared system can reduce manual handovers and make the process easier to govern.

9. How ERPNext can reduce individual knowledge dependency

Moving a process into ERPNext does not automatically remove every risk. The business still needs documented procedures, trained users, appropriate access and clear ownership.

However, a properly designed ERP process can move important information and rules away from a personal workbook and into a shared operational environment.

Shared transaction records

Instead of maintaining separate spreadsheets for customer orders, purchase activity, stock movements and invoices, the relevant teams can work with shared ERP records. This gives authorised employees a common place to review the current status of transactions.

Role-based access and responsibilities

ERPNext supports role-based permissions for documents and actions such as reading, creating, writing and submitting records. This helps define which users can perform particular activities and which users can review or approve them.

For example, a sales employee may create a quotation, while a manager has additional approval authority. Access should be designed around the company’s actual responsibilities rather than giving every user unrestricted access.

See ERPNext Role Based Permissions.

Standardised workflows

Where a business process needs approval stages, ERPNext workflows can define states, transitions and the roles responsible for moving a document forward.

This reduces dependence on one employee remembering who needs to approve a transaction or which email should be forwarded next. The workflow must still be configured and maintained according to the approved process.

See ERPNext Workflows.

Shared reports

ERPNext provides standard reports and tools such as Report Builder. These can help authorised users access information from shared business records rather than relying on one person to consolidate multiple files manually.

Reports should be configured with the correct filters, permissions and business definitions. A report is only useful when users understand what its figures represent.

Change history and traceability

ERPNext document versioning can track changes to configured documents, helping authorised users review what changed and when. This can support accountability for important records.

It is not a substitute for a full process document or an approval policy, but it adds a useful layer of traceability.

See ERPNext Document Versioning and Frappe Audit Trail.

The objective is not to eliminate spreadsheets.

It is to make sure that important business processes do not depend on an undocumented workbook or one employee’s memory when a shared, controlled process would be more appropriate.

10. A practical 30-day plan to reduce spreadsheet dependency

A business does not need to replace every spreadsheet at once. Start with the workbooks that create the greatest operational or financial dependency.

Week 1: Identify critical spreadsheets

• Ask departments which workbooks they use regularly.
• Identify spreadsheets that affect finance, inventory, sales or management decisions.
• Record the primary owner and backup owner.
• Identify workbooks with macros, linked files or complex formulas.

Week 2: Understand and document

• Review important formulas and assumptions.
• Identify data sources and manual steps.
• Document the process from input to final output.
• Record access, version and approval arrangements.

Week 3: Test continuity

• Ask a backup employee to complete the process independently.
• Review the accuracy of the results.
• Identify missing instructions or access permissions.
• Correct unclear formulas and unsupported workarounds.

Week 4: Decide what to improve

• Keep simple analytical spreadsheets with appropriate controls.
• Standardise important recurring workbooks.
• Move suitable shared transaction processes into the ERP.
• Assign owners for documentation, training and future reviews.

11. The real test: can someone else do the work?

Return to Gulfline Trading. The company does not begin by deleting its spreadsheets or forcing every calculation into the ERP.

It first identifies the workbooks that support important decisions. The team documents their purpose, formulas, data sources and update steps. A second employee learns how to operate the monthly reporting process. Critical sales, purchasing and stock transactions are reviewed to determine which should be recorded in a shared ERP workflow.

Now, when the spreadsheet expert takes leave, the business has a documented process and another authorised person who can complete the essential work.

That is the outcome worth aiming for.

A business should value the expertise of its employees without allowing essential operational knowledge to remain locked inside one person’s files and memory.

Good business continuity means the work can continue, even when the person who originally built the process is unavailable.

Frequently asked questions

Make your business processes independent of individual workarounds

At Craft Interactive, we help businesses review manual processes, identify operational dependencies and explore how ERP systems can create more structured, shared workflows.

If important business information is spread across personal spreadsheets, undocumented calculations and manual handovers, it may be time to review how those processes are managed.

Talk to Craft Interactive

Further reading

• ICAEW: Twenty Principles for Good Spreadsheet Practice
• Microsoft Support: Trace Formula Relationships
• Microsoft Support: Show Changes in Excel
• ERPNext: Role Based Permissions
• ERPNext: Workflows
• ERPNext: Document Versioning
• Frappe: Audit Trail