Replacing Excel for Maintenance Requests in Education

Education organisations may use Excel for maintenance requests because it is quick to adapt and can hold the information the team needs without waiting for a new software project. In this setting, operational work can span departments, campuses or schools, with teaching, estates, finance and administration all using different parts of a process.

That flexibility is useful, but the spreadsheet can gradually become more than a file. It may start coordinating faults and maintenance needs that must be reported, assessed, assigned and resolved against the relevant asset or location. At the same time, student, finance, HR and estates systems may hold core information while spreadsheets cover local operational workflows between them.

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 maintenance requests is usually handled in Excel

A maintenance tracker typically records asset or location, fault description, priority, date raised, owner, status, target date and completion notes. Typical information can include asset or location, fault, priority, requester, owner, status and completion details.

In education, the workbook often sits inside a wider process rather than operating on its own. information may be updated across classrooms, offices, workshops, campuses or remote working locations. Ownership may move between departments and central support teams, making a single uncontrolled workbook difficult to govern.

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 maintenance requests include:

• faults arrive by phone, email and paper
• asset history is fragmented across tabs and files
• urgent work competes with routine requests without a clear queue
• photos and completion evidence sit elsewhere
• repeat faults are difficult to spot from free-text descriptions

The sector adds its own practical pressure. Forms, approvals, training evidence, purchasing documents or facilities information may need to remain linked to the record. Useful views can differ by department, campus, owner, category or status.

Signs you have outgrown Excel

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

• maintenance staff receive work from several channels
• the same fault is reported more than once
• people chase for status
• asset history has to be reconstructed manually
• open work is reviewed by filtering a spreadsheet
• 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 adequate for a small number of assets and low request volume where one person coordinates maintenance and history is not complex.

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 maintenance requests clear and give each person the information and actions they need.

1. Report the fault against an asset or place

Capture enough context to identify what needs attention and where it is. For education, this should reflect that operational work can span departments, campuses or schools, with teaching, estates, finance and administration all using different parts of a process.

2. Assess priority and route the work

Review urgency and assign the request to the person or team responsible. The design should make sense for administrators, department leads, estates teams, finance staff, managers and other employees, rather than assuming one office-based owner.

3. Track action and blockers

Keep the current status, notes and dependencies on the maintenance record. This is especially useful where ownership may move between departments and central support teams, making a single uncontrolled workbook difficult to govern.

4. Record completion and evidence

Capture what was done, when and by whom, with relevant files or photos where useful. Where evidence is part of maintenance requests, forms, approvals, training evidence, purchasing documents or facilities information may need to remain linked to the record.

5. Use the history for future decisions

Make previous requests easier to find by asset, location or issue instead of searching old sheets. The resulting data should support the views people actually need: useful views can differ by department, campus, owner, category or status.

What is different about maintenance requests in education

For maintenance requests in education, the important design problem is to raise faults against a clear asset or location, route them by urgency and ownership, and capture completion evidence. In this sector, work is shaped by academic terms, departments, campuses, staff roles and approval responsibilities that can differ from ordinary commercial organisations. That means the app cannot be designed from spreadsheet columns alone. It has to fit teaching staff, administrators, department leads, operations teams and finance staff, because a useful replacement needs to fit term-based working and delegated responsibilities without exposing unrelated student or staff information. A common failure pattern is that faults are logged in one place while photos, technician updates and asset context live elsewhere.

Failure patterns specific to this setup

• The replacement still fails if it does not keep asset or location, fault, priority, owner, status, action and completion evidence together while preserving the sector context needed for department, campus, term, responsible role, approval, supporting document and current status
• The replacement still fails if it does not test the workflow with teaching staff, administrators, department leads, operations teams and finance staff 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 maintenance requests 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 a useful replacement needs to fit term-based working and delegated responsibilities without exposing unrelated student or staff information

Practical details to design around

• Keep asset or location, fault, priority, owner, status, action and completion evidence together while preserving the sector context needed for department, campus, term, responsible role, approval, supporting document and current status.
• Test the workflow with teaching staff, administrators, department leads, operations teams and finance staff rather than assuming the person who maintains the spreadsheet represents every user.
• Make the live status and hand-off explicit so maintenance requests does not continue in email, messages or a second spreadsheet after the app is introduced.
• Confirm the interface reflects the operating reality that a useful replacement needs to fit term-based working and delegated responsibilities without exposing unrelated student or staff information.

Where the system boundary should sit

For maintenance requests in education, student, HR, finance, timetable and learning systems should remain authoritative for the records they already own. planned maintenance and authoritative asset history should remain in CMMS or asset systems when those systems already provide it. 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.

Field-work design lens

For maintenance requests in education, the workflow has to survive contact with the real working environment. The office view can be excellent and the project can still fail if the person at the site, asset, customer or job cannot record the important update quickly. Mobile use, current context and the hand-off back to the office therefore belong in the core design.

What good looks like

• Faults are raised against a clear asset or location with the evidence needed to act.
• Priority and ownership are visible from request to completion.
• Field updates and completion notes happen against the live request.
• The workflow does not duplicate planned maintenance or asset data already held elsewhere.

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

• Prove with real education examples that a fault can be raised from the point of work and traced through assignment, attendance and closure.
• Confirm teaching staff, administrators, department leads, operations teams and finance staff 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

• What identifies the asset or location well enough for the maintainer to act?
• Which faults need urgency or escalation rules?
• What completion evidence is required?
• Is planned maintenance already owned by a CMMS or another system?

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 education team where faults are logged in one place while photos, technician updates and asset context live elsewhere. A focused replacement is introduced for maintenance requests. teaching staff, administrators, department leads, operations teams and finance staff work from one current record containing asset or location, fault, priority, owner, status, action and completion evidence, with the relevant department, campus, term, responsible role, approval, supporting document and current status. The first release is considered useful only when a fault can be raised from the point of work and traced through assignment, attendance and closure. 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 asset register if another system owns it.
• Do not rebuild preventive-maintenance scheduling unless it is part of the actual gap.
• Do not make field staff complete unnecessary data entry simply because the database can store it.
• 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 log faults, but the live status, field evidence and asset context usually depend on messages and manual updates around it.
Buy an off-the-shelf product	Established product and a defined implementation route	CMMS products are strong when planned maintenance, asset history and parts are central. They can be excessive where the real gap is a narrower bespoke request workflow.
Extend an existing core system	Keeps more data inside a platform the business already uses	An existing CMMS, facilities or asset platform should be used where it fits. The custom case is strongest when local request routing, forms or evidence sit outside that system because they do not map cleanly.
Build a custom app	Designed around the workflow the business actually follows	A focused app can close the maintenance-request gap without forcing the team to adopt a large maintenance suite for functionality it does not need.

For maintenance requests in education, the system boundary matters particularly strongly. For maintenance requests in education, student, HR, finance, timetable and learning systems should remain authoritative for the records they already own. planned maintenance and authoritative asset history should remain in CMMS or asset systems when those systems already provide it. 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 maintenance requests that people use repeatedly. Useful capabilities may include:

• asset or location reference
• request form
• priority and assignment
• status and blockers
• attachments
• completion history
• open and overdue views

For education, the design should also account for the way work is actually performed. Information may be updated across classrooms, offices, workshops, campuses or remote working locations. Access and screen design should reflect administrators, department leads, estates teams, finance staff, managers and other employees 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 education organisation coordinating work across several departments where fault reports arrive through several channels and an administrator updates a spreadsheet used for weekly maintenance review. 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 faults can enter one queue, stay linked to the relevant asset or location and keep their action history in one place. 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:

• clean the asset and location list
• identify current open maintenance work
• decide how much fault history is useful
• test urgent and routine request paths
• agree how repeat issues are recorded
• map the people and hand-offs involved in education
• 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.