Replacing Excel for Complaints Handling in IT Services

IT Services organisations may use Excel for complaints handling because it is quick to adapt and can hold the information the team needs without waiting for a new software project. In this setting, work is organised around clients, tickets, projects, devices, engineers and service commitments, often with several specialist systems already in use.

That flexibility is useful, but the spreadsheet can gradually become more than a file. It may start coordinating complaints that need to be acknowledged, assigned, investigated, responded to and closed with a clear record of actions. At the same time, ticketing, RMM, PSA, CRM and finance tools may cover standard functions while spreadsheets handle bespoke coordination, pricing or reporting.

This guide is about recognising that point and choosing the proportionate next step. The answer may be a better workbook, an existing software product, an extension to a system already in use, or a custom app built around the actual workflow.

How complaints handling is usually handled in Excel

A complaints tracker commonly records complainant or customer, date received, category, summary, owner, target dates, status, actions and outcome. Typical information can include complainant or customer, date received, category, summary, owner, status and outcome.

In it services, the workbook often sits inside a wider process rather than operating on its own. teams may work remotely, in an office or at customer sites while needing the same current information. Technical work, commercial information and customer communication can sit in different tools, with Excel used to bridge the gaps.

That surrounding work matters because a spreadsheet may be perfectly capable of storing the rows while still being a poor place to coordinate every decision, hand-off and update.

Where the spreadsheet starts to break down

The useful question is not whether Excel can technically hold more data. It is whether the team is doing increasing amounts of manual coordination around the workbook.

Common failure points for complaints handling include:

• correspondence and evidence are separated from the tracker
• ownership changes are difficult to follow
• target dates rely on manual checking
• sensitive details may be visible to everyone with the workbook
• management reports are prepared by categorising free text manually

The sector adds its own practical pressure. Technical notes, screenshots, device information, approvals, quotes or customer documents may need to stay linked to the relevant record. Views by customer, engineer, project, ticket type, asset or status can be more useful than one generic spreadsheet.

Signs you have outgrown Excel

A spreadsheet is more likely to be acting as an operational system when several of these are true:

• complaints are chased in recurring meetings
• staff search email for the latest correspondence
• different teams use different status wording
• overdue cases are found by manual review
• reporting categories are cleaned before every report
• one person has become the keeper of the workbook and the rules around it
• staff maintain side lists, emails or messages because the spreadsheet does not cover the whole workflow

These are not arbitrary limits. A workbook with many rows can be completely manageable, while a smaller file can be difficult if it has to coordinate several people, permissions, decisions and external systems.

When Excel is still suitable

Excel can be suitable for a very small number of cases handled by one person where access, evidence and workflow complexity are limited.

It is also worth improving the workbook before replacing it if the main problem is inconsistent structure. Controlled lists, clearer ownership fields, protected calculations, better naming and a single shared location can remove a surprising amount of friction.

Excel can remain valuable after part of the workflow moves into an app. Teams may still use it for flexible analysis, modelling, ad-hoc reporting or data exports where a grid and formulas are the right tool.

What a better workflow could look like

A replacement should not copy the spreadsheet cell by cell. It should make the real route through complaints handling clear and give each person the information and actions they need.

1. Register the complaint and source

Create one case with the information needed to understand what was raised and how it arrived. For it services, this should reflect that work is organised around clients, tickets, projects, devices, engineers and service commitments, often with several specialist systems already in use.

2. Assign ownership and next action

Make the responsible person and current next step visible from the start. The design should make sense for service desk staff, engineers, project managers, account managers, procurement teams and managers, rather than assuming one office-based owner.

3. Record investigation and correspondence

Keep notes, relevant documents and actions with the case rather than relying on inbox history. This is especially useful where technical work, commercial information and customer communication can sit in different tools, with Excel used to bridge the gaps.

4. Track deadlines and blockers

Surface cases needing attention without an administrator repeatedly checking dates. Where evidence is part of complaints handling, technical notes, screenshots, device information, approvals, quotes or customer documents may need to stay linked to the relevant record.

5. Close with a clear outcome

Record the response, outcome and relevant categories so later reporting uses the same case data. The resulting data should support the views people actually need: views by customer, engineer, project, ticket type, asset or status can be more useful than one generic spreadsheet.

What is different about complaints handling in it services

For complaints handling in it services, the important design problem is to capture complaints, ownership, investigation, responses, actions and closure evidence in one controlled case record. In this sector, work is organised around customers, services, tickets, assets, changes and technical ownership, with many core records already present in service-management platforms. That means the app cannot be designed from spreadsheet columns alone. It has to fit service desk staff, engineers, account managers, operations teams and customer contacts, because the spreadsheet usually survives because a commercial, reporting or approval workflow sits awkwardly beside the technical service platform. A common failure pattern is that correspondence and actions scatter across inboxes while the spreadsheet contains only a status summary.

Failure patterns specific to this setup

• The replacement still fails if it does not keep complainant or customer reference, category, owner, chronology, evidence, actions, response and closure together while preserving the sector context needed for customer, service, asset or system, technical owner, priority, change or approval context and current status
• The replacement still fails if it does not test the workflow with service desk staff, engineers, account managers, operations teams and customer contacts rather than assuming the person who maintains the spreadsheet represents every user
• The replacement still fails if it does not make the live status and hand-off explicit so complaints handling does not continue in email, messages or a second spreadsheet after the app is introduced
• The replacement still fails if it does not confirm the interface reflects the operating reality that the spreadsheet usually survives because a commercial, reporting or approval workflow sits awkwardly beside the technical service platform

Practical details to design around

• Keep complainant or customer reference, category, owner, chronology, evidence, actions, response and closure together while preserving the sector context needed for customer, service, asset or system, technical owner, priority, change or approval context and current status.
• Test the workflow with service desk staff, engineers, account managers, operations teams and customer contacts rather than assuming the person who maintains the spreadsheet represents every user.
• Make the live status and hand-off explicit so complaints handling does not continue in email, messages or a second spreadsheet after the app is introduced.
• Confirm the interface reflects the operating reality that the spreadsheet usually survives because a commercial, reporting or approval workflow sits awkwardly beside the technical service platform.

Where the system boundary should sit

For complaints handling in it services, ITSM, monitoring, CRM, asset and billing systems should remain authoritative for tickets, configuration data and commercial records where they fit. customer or case masters should remain in CRM or specialist systems rather than be recreated solely for complaint tracking. The replacement should own the awkward workflow gap and the decisions around it, while referencing trusted identifiers from those systems instead of creating another master-data source.

Evidence and control design lens

For complaints handling in it services, the record matters because somebody may later need to understand what was checked, decided, approved or completed. The useful design work is therefore about current versions, ownership, evidence, follow-up actions and access, not simply replacing a spreadsheet grid with fields.

What good looks like

• Each complaint has one owner, current stage and clear next action.
• Correspondence, evidence and decisions stay with the case.
• Escalations and overdue cases are visible without a separate chase list.
• Management can analyse themes without exposing more case detail than necessary.

The process should also pass the combination-specific proof points below:

• Prove with real it services examples that a complaint can be received, investigated, responded to and closed with a complete chronology and visible actions.
• Confirm service desk staff, engineers, account managers, operations teams and customer contacts can complete their part without maintaining a parallel spreadsheet or private side list.
• Verify identifiers and downstream hand-offs respect the agreed system boundary rather than duplicating records owned elsewhere.
• Review exceptions from the pilot and add only those that occur often enough to justify product logic.

Questions to answer before replacing the spreadsheet

• How does a complaint enter the process and what information is mandatory?
• What stages, escalations or approvals represent real decisions?
• Who needs access to case detail and who only needs reporting?
• What information should be retained when a case is closed?

These questions should be answered with the real workbook, users and surrounding systems in front of you. They are more useful than choosing software from a feature list before the awkward parts of the workflow are understood.

A more specific hypothetical scenario

Consider a it services team where correspondence and actions scatter across inboxes while the spreadsheet contains only a status summary. A focused replacement is introduced for complaints handling. service desk staff, engineers, account managers, operations teams and customer contacts work from one current record containing complainant or customer reference, category, owner, chronology, evidence, actions, response and closure, with the relevant customer, service, asset or system, technical owner, priority, change or approval context and current status. The first release is considered useful only when a complaint can be received, investigated, responded to and closed with a complete chronology and visible actions. This is a hypothetical example, not a customer case study.

This scenario is illustrative and is not a customer case study.

What not to build

• Do not duplicate the customer record if another system owns it.
• Do not expose detailed complaint content to users who only need aggregate reporting.
• Do not encode every exceptional escalation before the normal case lifecycle is stable.
• Do not duplicate a function already handled well by an existing system merely to make the new app look more complete.
• Do not move every old spreadsheet column into the new system unless it has a clear operational purpose.

Comparing the realistic replacement options

The cheapest-looking option is not always the lowest-cost operating model. Compare the amount of coordination, configuration, duplicated entry and compromise each option leaves behind.

Option	Why it can look attractive	The tradeoff to examine
Keep or improve Excel	Familiar, flexible and already paid for	Excel can hold a complaint register, but correspondence, ownership and review history usually spread across inboxes and folders.
Buy an off-the-shelf product	Established product and a defined implementation route	Case-management products are attractive when the process follows a standard model. They can be cumbersome when the organisation has a focused complaint workflow tied to other internal records.
Extend an existing core system	Keeps more data inside a platform the business already uses	CRM or service-desk systems may already own customer interactions. Extending them is preferable when they can represent the complaint process cleanly and with the right access controls.
Build a custom app	Designed around the workflow the business actually follows	A custom app can keep the case workflow, evidence and reporting focused on the organisation’s exact process while referencing customer or service data from elsewhere.

For complaints handling in it services, the system boundary matters particularly strongly. For complaints handling in it services, ITSM, monitoring, CRM, asset and billing systems should remain authoritative for tickets, configuration data and commercial records where they fit. customer or case masters should remain in CRM or specialist systems rather than be recreated solely for complaint tracking. The replacement should own the awkward workflow gap and the decisions around it, while referencing trusted identifiers from those systems instead of creating another master-data source.

A specialist product or existing module is still the right answer when the workflow genuinely fits it. The custom-app case becomes stronger when the spreadsheet exists precisely because the surrounding software cannot represent the organisation's rules, calculations, approvals, hand-offs, evidence or reporting without workarounds. In that situation, buying another generic product can leave the business paying for software while Excel continues beside it.

The Spreadsheet Assessment is the lower-commitment way to test that fit before agreeing a build. The recommendation can still be to keep Excel or use existing software if that is genuinely the better route, but the assessment is designed to identify whether the spreadsheet is filling a business-specific gap that deserves its own app.

What to include in a replacement system

A sensible first version should concentrate on the parts of complaints handling that people use repeatedly. Useful capabilities may include:

• case register
• ownership
• controlled status and categories
• correspondence and attachments
• target dates
• access controls
• outcome reporting

For it services, the design should also account for the way work is actually performed. Teams may work remotely, in an office or at customer sites while needing the same current information. Access and screen design should reflect service desk staff, engineers, project managers, account managers, procurement teams and managers rather than assuming every user needs the same view.

Features should earn their place. If a rare exception can remain manual without creating risk or confusion, it may be better to leave it out of the first release and keep the core workflow simple.

Hypothetical example

Consider a hypothetical IT services provider coordinating technical and commercial work across several customers where complaints are logged in Excel while correspondence remains in individual inboxes and managers rely on manual chase lists. The spreadsheet is useful because it fills a gap, but staff have to keep the file synchronised with the work happening around it.

A replacement could change that flow so the complaint, owner, actions, correspondence and outcome can remain connected in one controlled case record. The exact screens and rules would depend on the organisation, but the important shift is that the record becomes part of the workflow rather than a document someone has to update after the workflow has happened.

This is an illustrative scenario, not a customer case study and not a claim about a particular organisation.

Migration checklist

Before replacing the spreadsheet, work through the details that make the current process function:

• identify open cases
• agree categories and statuses
• decide which historic cases need migration
• review who should access each type of information
• test reporting from closed cases
• map the people and hand-offs involved in it services
• identify information that already comes from another system and should not be re-entered unnecessarily
• preserve important calculations and business rules with representative test cases
• decide what old data genuinely needs to move and what can remain archived
• agree a clear cut-over point so the spreadsheet and app do not become competing operational records

The Spreadsheet Assessment is designed to work through this kind of detail before a build is agreed. It looks at the spreadsheet together with the process around it so the recommendation can distinguish between what should stay, what should change and what a first useful version would need.