Start from what applicants were promised. If the website says a decision within a day, every held application must reach a loan officer in time to meet that, including weekend applications. Staff each channel against its promise, name a disbursement approver before each payment cut-off, and plan extra cover for the weeks after a campaign or rate change.
What does a lending rota cover?
A lending agent takes applications, requests documents, runs affordability and policy checks, and drafts offers and declines. It holds what needs an officer: offers and declines for a person to send, applications with unverified or inconsistent income, signs that the applicant may be struggling, and every disbursement. Applicants are waiting for all of these, often having been told how long they will wait.
The head of lending owns the rota. Marketing should share its campaign calendar, because demand follows it. The guide to AI agent skills by role covers what loan officers need to know. For the terms, see what a reviewer rota is and what an AI agent reviewer is.
What are the steps?
- Agent, depth 1: reports held applications by channel, hour and day. Online, branch, broker; weekend applications separately.
- Person (head of lending): lists the promises. Decision times published or agreed for each channel and product.
- Person (head of lending): sets response targets from the promises. Leave a margin: if the promise is one day, the target for officers is less.
- Person (head of lending): staffs each channel. Officers who know broker cases are not interchangeable with those who know online personal loans; the rota names who covers which.
- Agent, depth 3: requests documents within bounds. Standard requests go out without waiting.
- Agent, depth 2: drafts offers and declines. With figures, sources and reasons.
- Person (loan officer): decides each held application. Send, edit, decline with reasons, or refer.
- Person (disbursement approver): releases funds before cut-off. Depth 4, named for every payment cut-off in the day.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Intake | Takes applications and checks completeness | 1 | Nothing routine |
| Document requests | Sends standard requests | 3 | Non-standard requests |
| Offers | Drafts with figures and sources | 2 | Sending or editing |
| Declines | Drafts with reasons | 2 | The decision and the wording |
| Possible difficulty | Flags and holds | 2 | Careful handling and recording |
| Disbursement | Prepares and holds | 4 | Release before cut-off |
How should weekends and peaks be handled?
Online applications arrive at weekends; many lending teams do not work then. If the promise is a decision within a day, a Saturday application either needs a weekend officer or a promise that says "next working day". Choose one and make the website match the rota.
Peaks follow campaigns and rate changes. A promotion launched on Monday fills the queue by Wednesday. Agree with marketing that campaign dates reach the head of lending in time to adjust the rota, and keep a list of trained officers from other teams who can be borrowed. They must be trained in reviewing agent work, not just in lending, or they will approve drafts on trust.
How should the disbursement line be staffed?
Disbursement is the one step where a late decision costs the applicant money, not just time: a house purchase or a supplier payment may depend on funds arriving that day. List the payment cut-offs the lender uses, and name an approver for each, with a deputy. The approver checks that every condition of the offer has been met before release, not just that the offer was approved.
Which controls matter, and what evidence do they leave?
- Promises are met. Evidence: time from application to decision, by channel, against the promise.
- Declines carry specific reasons. In many markets a declined applicant is owed them, including where a model is used. Evidence: the reasons on each decline verdict.
- Declared income is marked as declared. Evidence: provenance on each figure the decision relied on.
- Disbursement has a named approver. Evidence: the release verdict with name and time.
- Difficulty flags have a response. Evidence: the action recorded against each flag.
What should be measured?
- Decisions within the promise, by channel and day of week.
- Disbursements missing the intended cut-off.
- Declines with reasons rewritten at review.
- Applications held for income verification, and how long they waited.
- Borrowed officers' decisions sampled for quality during peaks.
Where does it usually go wrong?
The promise and the rota disagree. The website says one day, the rota is Monday to Friday. Applicants notice.
Peaks surprise the team. Lending demand is rarely random; it follows the organisation's own campaigns. The surprise is a communication failure.
Disbursement waits on one person. If only the team leader can release funds and they are in a meeting at cut-off, money arrives a day late. Name a deputy for every cut-off.
Speed pressure on declines. Under a promise clock, decline reasons become generic. Keep enough experienced officers on the rota to write them properly.
IT and operations teams staff their queues with the same method and different clocks; compare the rotas for the IT team and the operations team. For the reviewer's role in general, see what an agent reviewer is.
Questions people ask
Should loan officers work across all channels?
Ideally, over time. In the short term, assign them to the channels they know and cross-train in quiet periods. A broker case decided by someone unfamiliar with broker processes tends to bounce back.
Can the agent send offers itself to speed up decisions?
Only if that capability has been certified on the lender's own cases and set within its bounds. Most lenders keep offers at depth 2 until they have that evidence.
How should the rota cover branch applications?
Branch staff often take the application; the decision may sit centrally. The rota should name the central officer for each branch region, so branch staff know who will decide.