Approval delays in spreadsheets rarely have a single cause.
A request may appear to be waiting in a workbook, but the real blockage can be unclear ownership, missing information, an off-sheet conversation, or a decision rule that only one person understands. The spreadsheet can be one contributor to the delay, particularly when it is being used to coordinate recurring work. It is not always the only bottleneck.
For operations and commercial managers, the useful question is not simply whether Excel is at fault. It is: where does an approval wait, who is expected to move it, and what information or evidence is missing when it stops?
What an approval delay looks like in practice
An approval may be marked as "pending" for several reasons:
- the current decision owner is not clear
- the request arrived without the information needed for a decision
- the latest question or decision sits in email or chat rather than the workbook
- different people are looking at different copies, tabs or attachments
- a status field has not been updated after an off-sheet conversation
- an exception needs judgement that is not captured in the normal process
- nobody can quickly show what has already happened and what is still required
These problems can occur in purchasing, job changes, stock decisions, customer exceptions, internal sign-off and other repeatable operational processes.
A spreadsheet remains useful for modelling, forecasting, flexible calculations and exploratory work. A recurring approval process has a different job. It needs to move requests between people, make the current state visible and retain a dependable record of decisions.
If a workbook must answer "what is waiting, with whom, since when and why?", it is supporting an operational queue rather than only recording data.
The main causes of approval delays in spreadsheets
Unclear ownership
A request can sit untouched when it is assigned to a team, department or shared mailbox rather than a named decision owner. Delays also arise when colleagues are unsure who should act after a request changes or needs clarification.
Diagnostic check: Take a sample of recent requests. At every point, can you identify the person responsible for the next decision?
A named owner does not remove every delay, but it makes waiting visible instead of leaving responsibility assumed.
Incomplete requests and clarification loops
Some approval delays begin before the request reaches an approver. Missing documents, unclear rationale, incomplete job details or inconsistent data can create a chain of questions before anyone can decide.
The spreadsheet may show a request as submitted even though the practical work is still waiting for information.
Diagnostic check: Review delayed requests and note whether the first delay occurred before the approver had enough context to act.
Hidden queues across email, chat and files
A spreadsheet may be the official tracker while the real process happens elsewhere. Questions appear in Teams, approval is given by email, and supporting evidence sits in a shared folder. Staff then have to search across channels to understand the live position.
This does not mean those tools are inherently unsuitable. It means the approval state is fragmented when nobody can see the authoritative next action in one place.
Diagnostic check: Trace one request from submission to decision. List every place where someone had to look, ask or update information.
Version and file confusion
Version history and collaborative editing can reduce the need to email attachments, but confusion can still arise when a process relies on copied files, exported tabs or several working versions. A reviewer may act on an older version, or a completed decision may not be reflected in the file others are using.
Diagnostic check: Can staff identify the current request record without opening multiple files or asking which version is correct?
Status fields that no longer reflect reality
A status column is useful only when it matches what has actually happened. If people make decisions in conversations and update the sheet later, the tracker can become a retrospective record rather than a live queue.
That makes it harder for managers to tell whether a request is genuinely waiting, already decided or blocked by missing information.
Diagnostic check: Compare the spreadsheet status for a small sample of requests with the most recent real action or decision.
Hidden decision rules and single-person dependency
Some approval paths depend on one experienced person knowing which exception applies, what evidence is sufficient or who should be consulted. That knowledge may be held in habit, comments, formulas or informal conversations.
This can be manageable in a small, stable process. It becomes more fragile when that person is unavailable, workload changes or other staff need to take over.
Diagnostic check: Could another appropriate colleague explain why a request is waiting and progress it using the same rules?
Missing decision evidence
An approval is more than a final yes or no. For an operational process, it can also require a clear record of the request, the decision-maker, the decision, the relevant context and the time it was recorded.
When evidence is scattered between spreadsheet comments, forwarded emails and chat messages, staff may spend time reconstructing what happened instead of progressing the next request.
Diagnostic check: For a completed approval, can you find the decision history without manually searching through messages and attachments?
A simple way to identify the real blockage
Use a recent approval that was awkward or slow. Follow the actual path it took rather than the path the spreadsheet suggests it should have taken.
Record:
- when the request was first ready for review
- each point where it waited
- who was expected to act next
- whether the required information was available
- where questions and decisions were made
- whether the spreadsheet status matched the real position
This is a diagnostic exercise, not a workflow redesign. The aim is to separate different sources of delay.
| Delay symptom | Likely cause to investigate | Question to ask |
|---|---|---|
| Nobody acts on a request | Unclear ownership | Who is responsible for the next decision? |
| Requests repeatedly return for questions | Incomplete intake | What information was unavailable at first review? |
| Staff chase through several channels | Hidden queues | Where is the authoritative current status? |
| Colleagues disagree about the latest file | Version confusion | Is there one current record for the request? |
| The tracker says pending after a decision | Stale status | Does the recorded status match the last action? |
| Work pauses when one person is unavailable | Hidden logic or dependency | Can another person apply the same decision rule? |
| Evidence takes time to find | Missing decision trail | Can the history be viewed without manual reconstruction? |
What the diagnosis can tell you
Not every delayed spreadsheet process needs replacing.
If the process is occasional, straightforward and handled by a small group with clear ownership, a spreadsheet may remain a practical tool. The issue may be a specific gap in request information, status discipline or responsibility.
Recurring delays deserve closer attention when the same patterns continue:
- staff regularly need to chase for an update
- requests are rerouted after submission because the right path was unclear
- decisions happen outside the main tracker
- managers cannot see the age, owner or blocker for live requests without asking around
- exceptions depend on personal knowledge rather than visible rules
- decision evidence has to be assembled after the event
These are signs that the process is doing more coordination work than a shared workbook can comfortably carry. They do not prove that the spreadsheet alone caused the problem. They do show where process design, ownership and control need attention.
When a managed approvals application may fit
A managed approvals application can be appropriate when approval is part of a wider operational workflow rather than an isolated sign-off.
For example, a request may need information from a job, order, project or inspection record; it may require different actions from different roles; or the decision may trigger follow-on work. In those situations, the value is not simply replacing a spreadsheet. It is giving the process a clearer operating structure.
A managed application can provide a dedicated place for requests, decision status, routing, role-based access and recorded history. That can help a team make the live queue easier to understand while reducing reliance on manually reconciling files and side-channel conversations.
Explore managed approvals applications for spreadsheet-led processes.
Spreadsheet Upgrade builds and manages custom web applications for UK SMEs whose business-critical operational processes have outgrown workbook coordination. A Free Fit Check can help you assess whether the recurring issue is a fixable process habit or a sign that the approval workflow needs a more structured replacement.
Start with a Free Fit Check
If approval delays keep returning in the same places, start by reviewing one real process and the points where work waits.