Approval Queue Management for UK Mortgage Brokers: 6 Controls

Approval queue management is the organised handling of every item that must be reviewed before a mortgage case can move on: a payslip awaiting check, an unexplained deposit, an ID document, a lender request. A well-run queue gives each item an owner, a priority, an age and a recorded decision. This guide sets out six controls that a UK brokerage can apply, whatever its size.
TL;DR
- An approval queue holds work that has paused at a review gate. Managing it means prioritising, ageing and recording each item, not only clearing it.
- Give every case one named owner and a dated next action. A case with no next action is a defect.
- Sort items into three lanes: automatic pass, field-level review and full manual exception.
- Set due dates, reminders and escalation points, and measure how long files wait at each stage.
- Log what changed, who changed it, when and why, and keep retention rules written down.
Table of Contents
- What an approval queue is and why brokers need one
- Control 1: Define the stages and the gates
- Control 2: One owner and a dated next action
- Control 3: Prioritise and age every item
- Control 4: Automate checks, keep judgement with people
- Control 5: Set escalation targets and find the bottlenecks
- Control 6: Keep an audit trail and a retention policy
- A minimum set of fields for each queue item
- Our perspective
- Casefile for your approval queue
- Putting the controls in order
- FAQ
- Sources
What an approval queue is and why brokers need one
In workflow terms, a process reaches an approval gate and pauses. It creates a queue item containing the action and its context, routes the item to an eligible reviewer, and resumes, rejects or modifies the work once a decision is made. Curate-Me's documentation describes this sequence and adds that queue management supplies prioritisation, ageing visibility and auditability.
Two ideas are often confused. An approval workflow defines who reviews what and in which order. A review queue manages the backlog, its priority and its age, as Operion explains. A brokerage needs both: the workflow is the route, the queue is the day-to-day control of what is waiting on it.
For a mortgage broker the queue is rarely one list. It usually contains:
- client documents waiting to be checked (bank statements, payslips, tax forms, ID, proof of address);
- discrepancies waiting for an adviser's decision;
- internal sign-offs before a case is submitted;
- lender requests and conditions after submission.
The aim, in Operion's framing, is not a backlog of zero. It is the right attention on the right item at the right time. That is a useful standard for a small firm where a handful of people share every task.
Control 1: Define the stages and the gates
A queue only makes sense when the stages behind it are explicit. One mortgage workflow guide recommends seven stages, from first enquiry to post-settlement review, with an owner, a checklist and an expected duration for each of the six pipeline stages. The guide is written for the Australian market, but the structure transfers to a UK brokerage. Our own view of the early stages is set out in our mortgage onboarding workflow guide.
The same guide separates three kinds of approval, because each leaves different work outstanding:
- Pre-approval: an early indication, with verification still to do.
- Conditional approval: a decision subject to conditions that remain open.
- Formal approval: conditions met and the case ready to proceed.
A queue that treats all three as "approved" hides work. Label each case with the status it actually holds and list what remains.
It also helps to define who may approve what. Administrative preparation, document collection and follow-up can sit with a case processor working within procedures. Advice and loan structuring stay with the authorised adviser. The queue should reflect that split, so an adviser's time is spent on decisions and not on chasing a missing page of a statement.
Control 2: One owner and a dated next action
The most useful rule in any queue is single ownership. MortgageMatch's workflow guidance says one named person should own a case at any moment, and that ownership should genuinely transfer at handover, not be shared by assumption.
The same source recommends that every open case carries a dated next action instead of a bare status. "Awaiting documents" is a status. "Chase client for March payslip, Thursday" is a next action. A case with no next action should be treated as an error and corrected the same day.
For routing, there are four patterns in common use, all documented in Curate-Me's approval-routing guidance:
| Pattern | How it works | Suits |
|---|---|---|
| Direct assignment | Item goes to a named person | Cases with one adviser from start to finish |
| Role-based routing | Item goes to anyone holding a role | Document checks shared by processors |
| Round-robin | Items are spread evenly in turn | Steady volumes of routine checks |
| Escalation chain | Item moves up if not actioned | Overdue or high-risk items |
A small brokerage will usually combine direct assignment for the case and role-based routing for document review, so a holiday does not freeze a file.
Control 3: Prioritise and age every item
A queue sorted only by arrival time treats a routine address proof and a case about to breach a lender deadline alike. Prioritise by consequence instead.
A practical order, drawing on Brokers' BackOffice's processor guidance, is:
- Applications that have exceeded the lender's communicated timeframe.
- Applications with an outstanding action.
- New lender requests, which should receive an owner and a response deadline immediately.
- Everything else, by age.
Ageing matters because lender timescales set the pace you are working to. Aldermore's published UK service levels are a good example of the numbers a broker should have in mind: residential and standard buy-to-let applications average 27 working days from pre-underwrite to offer, DIP referrals are decided within 24 hours, pre-underwrite review takes 3 working days and underwriter review takes 2. Those figures are updated by the lender, so check the page for the current position, and compare them with the expectations of each lender you use.
If your document queue holds a file for longer than the lender's own review takes, the delay is yours. A checklist for the underwriting stages can help you work out what must be ready at each point in the timeline.
Record four dates on every submitted case instead of one generic "with lender" label:
- lodgement date;
- the lender's turnaround expectation;
- last update;
- next follow-up date.
Brokers' BackOffice recommends exactly this, and it turns a vague list into one you can sort by what is late.
Control 4: Automate checks, keep judgement with people
Most queue volume is routine checking: is the document present, legible, in date and consistent with what the client declared? That is where automation earns its place. The sensible split, set out in Edilec's routing guide, is to use automation for classification, extraction and detecting missing evidence, while authority stays in explicit rules and named roles. Material, low-confidence or conflicting cases go to a person. Unknown categories and failures go to a named operations queue and are never guessed at.

UK trade press has reported AI-assisted case checking arriving inside mortgage case workflows, flagging missing documents, data mismatches and exceptions with an audit trail for each check. Brokers should expect that kind of pre-screening to become normal, because it moves discrepancies off the adviser's desk before a lender sees them.
Three lanes
Parseur's human-in-the-loop guide recommends three lanes, which map neatly onto a brokerage:
| Lane | Brokerage example | Who acts |
|---|---|---|
| Straight-through | Complete, consistent payslip matching the declared salary | Nobody; recorded automatically |
| Field-level review | One figure unclear, such as a net pay amount | Processor checks the single field |
| Full manual exception | Wage deposits do not match, or signs of tampering | Adviser decides, with notes |
The same guide says an exception should show the source document beside the extracted fields, mark which fields are flagged and state why review was triggered. Reviewer actions should be structured: accept, edit, mark missing, escalate or request information. Free-text outcomes are hard to count and hard to audit.
What to automate, and what to keep manual, is covered in more detail in our mortgage broker automation guide.
Control 5: Set escalation targets and find the bottlenecks

A queue without time limits is a list. Approval systems that work attach a due date, a reminder and an escalation to every item. As an example, Gloo's approvals documentation sets a default of 72 hours, a reminder after 24 hours and a further 72-hour escalation window where no custom service level is defined. You would set shorter periods for a client document than for an internal sign-off, but the structure is the point: due, remind, escalate.
To find where files stall, TrackMyTrail recommends recording entry and exit times for each stage, the owner of the next action and the reason for waiting, then comparing actual time with expected duration. After a month the pattern is usually plain. Common causes in document queues are:
- clients who upload partial statements;
- items waiting on a single reviewer;
- discrepancies with no agreed decision-maker;
- files sent backward by a missing document with no return path.
That last point deserves its own rule. When a missing document or unresolved condition sends a file back a stage, define where it re-enters, so it does not drop out of sight. Revisit the workflow too when a lender changes its policy.
A weekly file-health check keeps the system honest. Brokers' BackOffice's version asks, for each active file, whether it has:
- a next step;
- a responsible person;
- an expected age;
- complete supporting documents;
- a lender follow-up date;
- approval conditions tracked separately.
Any file that fails one of those questions goes to the top of Monday's queue.
Control 6: Keep an audit trail and a retention policy
Every decision in the queue should leave a record. Parseur recommends logging what changed, who changed it, when and why, and notes that the log doubles as training evidence for new staff. Gloo's approach goes a step further by recording the outcome, status, decision-maker and audit evidence together, and refusing approvers who lack access or eligibility. For a brokerage, the equivalent is that only authorised users can approve, and that the approval and its reason are stored with the document.
Retention needs a written policy as well. ICAEW's document-retention guidance says a policy should cover storage, access rights, retention periods and secure destruction, and be reviewed regularly for legal compliance and staff adherence. For mortgage firms, confirm the specific record-keeping periods that apply to your permissions with your compliance adviser or the FCA Handbook, and write them into that policy.
Supporting checks feed the same trail. If your queue includes identity and anti-money-laundering evidence, see our guides to AML document checks and identity document verification.
A minimum set of fields for each queue item
Whatever tool you use, each item should carry the same fields. This list is a practical minimum, assembled from the controls above:
| Field | Purpose |
|---|---|
| Case and applicant | Identifies the file, including joint or multiple applicants |
| Item type | Document check, discrepancy, sign-off or lender request |
| Owner | One named person |
| Next action and date | Prevents ambiguous status |
| Lane | Straight-through, field-level or manual exception |
| Age and due date | Drives priority and escalation |
| Reason flagged | Explains why review was triggered |
| Outcome | Accept, edit, mark missing, escalate or request information |
| Decision log | Who, when and why |
If your current spreadsheet or CRM lacks more than two of these, that is the first place to improve.
Our perspective
We build Casefile for UK mortgage brokers, and the queue problem we see most often is not volume. It is that discrepancies reach the adviser late, with no context, after the client has already stopped responding.
Our approach is to move the checking to the front of the queue. Documents are collected through a document list that builds itself from the client's payment type, cross-checked on arrival, and flagged for undeclared commitments or mismatched wage deposits before they go near a lender. The adviser sees an exception with the reason attached, not a folder to open and read.
We designed the platform around clear audit trails, UK-only data residency and no manual or offshore data handling, because a queue is only as trustworthy as the record behind each decision. It carries your own branding, so clients see your firm throughout, and it is built to need minimal technical learning, which matters most in small brokerages where the same people review, chase and advise.
The result we aim for is fewer lender queries and fewer days lost between collection and submission. Our guide to reducing lender queries shows the checks we put first.
Darren
Casefile for your approval queue
Casefile automates document collection and review for UK mortgage brokerages. It cross-checks bank statements, payslips, tax forms, ID and utility bills, flags discrepancies and undeclared commitments, matches wage deposits, detects tampering and manages the document approval queue under your own branding. Applicant documents stay in the UK.

See how it fits your process on the Casefile site, or read how Casefile handles your documents for the data and privacy detail. For the collection step alone, our guide to automated document collection is a good start.
Putting the controls in order
You do not need to introduce all six at once. A sensible sequence for a small firm:
- Add an owner and dated next action to every open case this week.
- Add the four lender dates to submitted cases.
- Split incoming document checks into the three lanes.
- Set due dates and a reminder for every queue item type.
- Start the weekly file-health check.
- Write down the audit and retention rules, and review them regularly.
For teams looking at the wider home-buying sequence around a mortgage case, a home buying workflow guide shows how the client's other deadlines interact with yours.
FAQ
What is approval queue management?
It is the practice of organising items that need review before work can continue, so each has an owner, a priority, an age and a recorded outcome. It goes beyond approving items one at a time by showing what is waiting, for how long and why.
How is a review queue different from an approval workflow?
An approval workflow defines who reviews what and in which order. A review queue manages the live backlog, including priority and ageing. A brokerage needs the workflow to set the route and the queue to keep items moving along it.
How should a small brokerage prioritise cases?
Put cases that have passed a lender's communicated timeframe first, then cases with an outstanding action, then new lender requests with an owner and deadline, then the rest by age. Check the lender's published turnaround times so you know what "late" means.
Can automation replace manual document review?
It can handle classification, extraction and detection of missing or inconsistent evidence, which removes most routine checking. Material, low-confidence or conflicting cases should still go to a named reviewer, and each decision should be logged.
Sources
- Approval Queues, Curate-Me Docs
- Review Queues, Operion
- Mortgage Pipeline and Workflow Management, TrackMyTrail
- Mortgage broker workflow management, MortgageMatch
- Loan Processor Productivity Insights, Brokers' BackOffice
- Our Latest Mortgage Turnaround Times, Aldermore Bank
- AI Approval Routing Automation, Edilec
- AI compliance checks in a mortgage case workflow, Mortgage Soup
- Human-in-the-Loop Workflow, Parseur
- Approvals and Human-in-the-Loop, Gloo
- Document retention, ICAEW
- Mortgage underwriting process checklist
- Home buying workflow guide, Offer Smart
Recommended
- Document Version Control for UK Mortgage Brokers
- Mortgage Onboarding Workflow: 6 Stages for UK Brokers
- AML Document Checks for UK Mortgage Brokers: A 5-Step Guide
- Mortgage Fraud Red Flags: A Broker's Checklist for 2026
This article was generated with AI, and whilst it is our expectation that the article is accurate, it should not be taken as advice.