Replace Change Spreadsheets and Email: A Practical Guide

Last Updated: October 18, 2026

Why Change Spreadsheets and Email Chains Break Down

Most organisations do not decide to replace change spreadsheets and email. The problem creeps up: one tab becomes twelve, the approval trail lives in an inbox, and nobody can say who signed off what last Tuesday. At ChangeGate, we see this constantly: the spreadsheet still opens, so nobody treats it as broken, even when the process around it has failed.

Signs your spreadsheet has become difficult to manage

Watch for these warning signs before they turn into an audit finding:

• More than one person edits the file, and nobody knows which copy is current

• Approval happens in an email thread, not in the record itself

• You keep a "final_v3" and a "final_v3_actual" version side by side

Two or three of these together mean the spreadsheet is no longer a control. It is a liability.

Limitations of spreadsheets for shared work

Spreadsheets were built for calculation, not governance: good with numbers, bad with accountability.

A shared spreadsheet has no permissions model beyond view, comment and edit, cannot enforce that the person who raised a change cannot also approve it, and has no audit log that survives a careless overwrite.

Email makes this worse. It has no status field, no owner and no deadline. NHS England's guidance on information governance makes the point that records must be accurate, complete and retrievable, which is hard to guarantee when your evidence is scattered across inboxes and file shares.

Watch Out The most common mistake we see is treating a shared spreadsheet as a system of record. Once two people edit it at once, the version you rely on in an audit may not be the version that was actually approved.

Replace or Improve? A Decision Framework for Change Spreadsheets

Not every spreadsheet needs replacing. Most teams look at tools before working out whether the spreadsheet was ever the right answer. Settle this framework first.

Score the spreadsheet, not the software

Score each of the six tests 0 (handles it well), 1 (copes with workarounds) or 2 (failing), then add them up.

A total of 0-3 means improve the sheet. A total of 4-7 means improve now and plan a replacement within the year. A total of 8-12 means replace it: the spreadsheet is no longer a control, it is a liability.

What "improve" actually looks like

If you score low, tighten the sheet in four ways:

1. Lock the structure. Protect the header row and column formats so nobody inserts a column that breaks the log.

2. Add a change log tab. One row per edit, with date, user, field changed, old value and new value. It is manual, but it is better than nothing.

3. Move approvals out of email. Even a simple form that writes to the sheet gives you a timestamp and a named approver.

4. Set a review date. Improving a spreadsheet buys time, not a permanent answer. Put a date in the diary to re-score it.

The cost comparison competitors skip

Replacement is rarely justified on licence cost alone. Compare properly:

• Spreadsheet maintenance: the hours spent rebuilding change history before each review, chasing approvals in email and reconciling versions. Usually the largest hidden cost, and it grows with every new site.

• Error and rework: a lost edit or an approval that cannot be evidenced. One failed audit finding usually costs more than a year of software.

• Software cost: ask for a quote rather than assuming a figure; pricing depends on user count and scope.

If maintenance and error costs over 12 months exceed software and migration cost, replace. If not, improve and re-score in six months.

Most teams that ask us whether to replace change spreadsheets already know the answer; they want permission to act.

Designing a Change Management Workflow That Replaces Email Requests

A change management workflow is the defined path a change takes from request to closure, with clear owners, approvals and evidence at each step, replacing the email thread with a single record.

Here is how we would build one, step by step:

1. Capture the request in one place. A form or record, not an email. Include what is changing, why, the risk and the proposed date.

2. Assign an owner. Every change has one accountable person.

3. Route for risk assessment. Low-risk changes get a lighter path than high-risk ones.

4. Send for approval to the right approver. Not the person who raised it.

5. Record the decision with a timestamp. Approve, reject or defer, with a reason.

6. Track implementation and closure. Link the evidence to the record.

The key shift is that the record, not the email, becomes the source of truth.

Managing multiple users, permissions and concurrent editing

Concurrent editing is where spreadsheets fail hardest. Two people open the same file, both save, and one set of edits vanishes. A proper system locks the record while it is being changed and keeps a full version history.

Permissions should follow roles, not individuals. Requesters raise changes. Approvers approve. Auditors read. Nobody approves their own change. That single rule closes a gap that email threads leave wide open.

The Change Approval Process: Who Approves What, and When

The change approval process decides which changes need sign-off, from whom, and by when. Get it wrong and you either bottleneck everything or approve nothing properly.

A workable model uses risk tiers:

• Standard changes: pre-approved, low risk, logged only

• Normal changes: one approver, usually the relevant manager

• Major changes: a change advisory group, with IT and operations sign-off

The rule that matters most is separation of duties. The person who raises a change should never be the person who approves it. Email cannot enforce that. A governed workflow can.

Book Demo →

Pro Tip Set a target approval time per tier and publish it. Most delays come from approvers not knowing a change is waiting on them, not from genuine disagreement. Automatic notifications fix that.

Change Management Templates Worth Keeping (and Which to Retire)

Some change management templates earn their place; others are habits dressed up as process.

Keep:

• A change request form with risk fields

• A risk assessment matrix

• A change advisory board agenda

Retire:

• The email approval chain (replace with a recorded approval step)

• The "reply all" status update (replace with a status field)

• The shared spreadsheet as the master log (replace with a system of record)

The test is simple. If a template exists only to move information between people, a workflow does it better. If it exists to force a decision, keep it.

Choosing Change Management Software: What to Assess Before You Switch

Change management software holds the change record, enforces the workflow and produces audit evidence automatically. Choosing well comes down to a short list of questions.

Assess these before you commit:

• Does it enforce separation of duties? No self-approval, ever.

• Does it keep a full audit log? Every edit, approver and timestamp.

• Can it handle business, operational and IT change in one place? Fragmented tools recreate the problem.

Pricing depends on user count and scope, so ask for a quote.

This is where a unified platform earns its place.

ISO/IEC 27001 information security standard sets out the controls auditors expect, and a governed workflow maps to them far more cleanly than a spreadsheet ever will.

Migrating Spreadsheet Data and Retiring Email Threads

Migration is where good intentions die. This tool-neutral plan covers cleaning, mapping, testing, training and retiring the old spreadsheet, and keeping a trustworthy change history after the switch.

Phase 1, Prepare (two to four weeks before cut-off)

1. Freeze the old sheet. Set a cut-off date and stop new entries. Announce it to everyone who touches the file.

2. Clean before you move. Remove duplicates, close out stale changes, and fix inconsistent status values. Migration amplifies bad data; it does not fix it.

3. Map the fields. Match every column in the sheet to the new record structure. Where a column has no home, decide whether to drop it or hold it in a notes field. Do not leave this to the import tool.

4. Decide what history to carry. Closed changes older than your retention period can be archived rather than imported. Live changes must come across in full.

Phase 2, Test (one to two weeks before cut-off)

5. Import a sample first. Take 20-50 rows, mixing closed and live changes, and import them into a test environment. Check that every field landed and that the audit trail shows the original dates, not the import date.

6. Reconcile the count. After the full import, check that every row landed. A simple count by status is usually enough.

7. Test the workflow, not just the data. Raise a dummy change, route it for approval, approve it, and close it. Confirm the audit log records each step with a timestamp and a named user.

Phase 3, Switch (cut-off week)

8. Run both in parallel for one cycle. Keep the sheet read-only as a fallback. The parallel run is the step teams skip, and it is the one that prevents a data loss scare.

9. Train by role, not by tool. Requesters need to know how to raise a change, approvers how to approve and what to do when on leave, auditors how to pull evidence. A single all-staff session teaches nobody what they need.

10. Redirect new requests. Update the form, the intranet page and the email signature that points people at the old sheet. If the old route still works, people will use it.

Phase 4, Retire (one to three months after cut-off)

11. Archive the old sheet read-only. Do not delete it. If a question arises about a change made before migration, the archive is your evidence.

12. Close the email threads. Send a final message to each thread telling people where the record now lives, then archive the thread. Do not leave it open as a fallback.

13. Review after 30 days. Check for requests still arriving by email, approvers who have not logged in, and any change that stalled. Fix the cause, not the symptom.

Change tracking, change history and rollback after migration

After migration, the audit log becomes your safety net: every edit, approval and status change recorded with a timestamp and a named user, so you can see exactly what changed and roll it back.

Three rules make rollback work:

• Never overwrite a record. Supersede it with a new version so the history is preserved.

• Keep the pre-migration archive. The old sheet is your evidence for anything that happened before the switch.

• Test a rollback before you need one. Pick a dummy change, roll it back, and confirm the audit log shows both the original and the reversal.

Key Takeaway The goal of migration is not a clean import. It is a record you can trust, with a history you can prove, from the day you switch.

Security, Access Control and Audit Readiness

Security is the reason most organisations eventually replace change spreadsheets and email. A file share and an inbox are hard to control and harder to prove.

Access control should be role-based and reviewed. Who can raise, who can approve, who can read. NCSC guidance on access control recommends least privilege: give people the access they need to do their job and no more.

Audit readiness comes down to evidence: the change, risk assessment, approver, timestamp and outcome, linked together.

ChangeGate was built for exactly this: organisations of 50 to 2,500 people that need to govern change and prove it.

Frequently Asked Questions

How do you manage change requests without spreadsheets?

Move requests into a single system where each change is raised, assessed, approved and recorded in one place. Replace change spreadsheets with structured forms that capture risk, cost, affected systems and proposed dates, then route each request to the right approver automatically. The system holds the change history, so you no longer reconcile versions of a file or search inboxes for sign-off. Most teams start by moving one high-volume change type, such as IT infrastructure changes, then extend the workflow to operational and business change once the pattern is proven.

What is a change management workflow?

A change management workflow is the defined sequence a change follows from request to closure: submission, risk assessment, approval, scheduling, implementation, review and evidence capture. Each stage has an owner, entry criteria and a record of what happened. A workable workflow makes the approval path explicit, so a low-risk standard change moves quickly while a high-impact change gets deeper scrutiny. Documenting the workflow before selecting change management software keeps the tool aligned to how your teams actually work rather than forcing a process that people then work around.

What are the risks of managing change in spreadsheets?

Shared spreadsheets create duplicate data, unclear ownership and no reliable change history. A spreadsheet copy emailed between approvers can be edited by anyone with the file, so the record of who approved what and when is easily lost. Concurrent editing causes overwritten entries, and human error creeps in through manual data entry. For regulated work, this weakens audit readiness because there is no dependable audit log. These problems grow with scale: the more users and changes in flight, the harder it becomes to prove control.

How can teams replace email-based change approvals?

Route approvals through the system rather than through an email thread. Each request should generate a notification to the named approver with the full context attached: risk rating, affected services, rollback plan and proposed window. The approver records a decision inside the workflow, which timestamps it and writes it to the change history. This removes the need to search inboxes for consent and prevents approval by the person who raised the change. Start by listing every approval currently given by email, then map each to a defined role in the new process.

If your change record lives in a spreadsheet and your approvals live in an inbox, you already know the risk. ChangeGate replaces both with a single governed lifecycle: separation of duties, automatic audit evidence for ISO 27001, SOC 2 and TISAX, and clear visibility of every change in flight. Book a demo and see what a controlled workflow looks like in practice.

Book Demo