Case study — 07
LoanEase CRM —
Employee Dashboard
Overview
The other side of the loan.
LoanEase began as a consumer-facing mobile app that lets customers compare loans, calculate EMIs, and apply with their chosen bank. But every application that comes in has to be processed — and that work falls to bank employees navigating a maze of legacy systems, email threads, and shared spreadsheets.
The LoanEase CRM is the employee-facing side of the same product: a unified lending workspace designed to give case reviewers, underwriters, and document officers a single place to see the full picture of every application — from submission to completion.
Applications list — 284 cases in pipeline
Applicant Overview — Emily Carter, £350k mortgage
The problem
Mortgage processing is fragmented by design.
A home mortgage involves identity checks, income verification, credit assessment, property valuation, solicitor coordination, underwriting decisions, and legal completion — often with different teams responsible for each stage. Without a unified tool, information lives in disconnected silos.
🗂 Information scattered across systems
Applicant data, uploaded documents, solicitor notes, and internal decisions live in different places — forcing employees to context-switch constantly and risk missing critical information.
⏳ Cases stall without clear next actions
Without a visible status trail, employees don't know what is blocking approval. A missing payslip or overdue valuation can sit unnoticed for days, slowing the applicant's journey.
📋 No audit trail for document decisions
When a reviewer accepts or rejects a document, that decision needs to be recorded with a reason, reviewer name, and timestamp — for compliance and accountability.
👥 Multiple stakeholders, no shared view
Solicitors, surveyors, underwriters and case officers all work on the same application but have no single shared view of where things stand — leading to duplicated communication.
"Bank employees should spend their time on judgement — not hunting for documents across ten different tabs."
Design principle — LoanEase CRMResearch context
Understanding how mortgages actually get processed.
To design a tool that would genuinely help employees, I mapped the real workflow behind a mortgage application. Secondary research into UK mortgage processing practices and observations from banking workflows gave me the six-stage lifecycle that became the skeleton of the CRM's information architecture.
Submission — Application arrives
Customer submits via the LoanEase mobile app. An ID is created (e.g. LE-2026-0148) and assigned to a case officer. Initial documents — passport, proof of address — are attached.
Identity & KYC — Who is this person?
The case officer reviews identity documents, runs sanctions and PEP screening, verifies address. This step must be confirmed before any financial assessment begins.
Income verification — Can they afford it?
Payslips, bank statements, and declared income are compared. Discrepancies trigger document requests. The affordability assessment runs in parallel with credit checks.
Property & legal — Is the property sound?
A surveyor valuates the property. A solicitor reviews title deeds and ownership history. Both must complete before underwriting can sign off.
Decision & offer — Approve or decline?
The underwriter reviews all completed checks and either approves the loan — generating a draft mortgage offer — or requests more evidence.
Completion & funding — Money moves.
Once the applicant signs the offer, funds are released to the solicitor's client account. The loan enters repayment servicing.
Design decisions
Structure that mirrors the actual workflow.
1. The dashboard as a triage view
The Portfolio Overview is designed for the first 30 seconds of a case officer's morning. Three headline metrics give immediate situational awareness. The Priority Queue surfaces the cases that genuinely need action today, sorted by due date and flagged by urgency.
Portfolio Overview — 128 open applications, priority queue, and pipeline by stage
2. The 16-tab case view — deep without being overwhelming
A mortgage case has 16 reviewable dimensions. The tabbed navigation lets reviewers move to exactly the section they need without losing the applicant context in the fixed header — Emily Carter · LE-2026-0148 · 4 of 7 checks complete.
Overview — 4/7 checks, next actions
Activity — chronological case log
Documents — 6 files, verification status
3. Verification checks — each step a dedicated screen
Every verification dimension has its own tab with three stat cards at the top, a detailed checklist in the main panel, and a reference sidebar. The consistent pattern means employees build a mental model of where to look on every screen.
Identity & KYC — screening clear, 2/2 docs
Income Verification — £78,000 p.a.
Credit & Affordability — £2,212/mo, 34% DTI
Property — £402,500 value, 86.96% LTV
Solicitor & Legal — Sarah Williams assigned
Conditions — 4/7 complete, 3 open actions
4. Gating the underwriting decision
The Decision tab won't allow approval until all required checks are resolved. This hard constraint is surfaced as a clear readiness panel showing exactly which checks are blocking — with a direct path to request outstanding evidence from the same screen.
Decision — Not ready, 3 checks open
Offer — draft preview, 6.5% APR, 30 years
Key screens
The complete lending lifecycle.
Beyond individual cases, the CRM covers portfolio-level views, team management, document review queues, and reporting — everything an operations team needs to run a mortgage lending division.
Post-approval: Completion & Servicing
Completion — £350k, Northbridge Legal
Repayment Servicing — £2,212/mo
Portfolio-level management
Customers — 237 total
Loans — 128 pipeline, 109 active
Team Tasks — 43 open, 8 due today
Document workflow & reporting
Document Request — 2 files, due 28 Sep
Reports — stage funnel, common blockers
Reports & Insights — September: 62 submitted → 36 approved → 22 completions. Common blockers surfaced at portfolio level.
Design outcomes
A tool that respects the complexity of the job.
The LoanEase CRM was designed to reduce the cognitive overhead of processing mortgage applications — not by simplifying the complexity, but by organising it in a way that makes the right next action always clear.
For case officers
The Priority Queue and persistent verification progress bar mean reviewers know exactly where each case stands without opening it. Next Actions on every overview tab removes the question "what do I do now?".
For underwriters
The Decision Readiness screen gates approval behind completed checks. Outstanding evidence can be requested directly from the same screen — no navigation away needed.
For document reviewers
The Application vs Evidence comparison table makes discrepancy detection immediate. Every decision is recorded with a reason and timestamp for compliance.
For operations leads
Reports & Insights surfaces systemic blockers. Missing payslips across 14 cases become a visible pattern — enabling resourcing decisions based on real data.
What I learned
Designing for complexity is itself a skill.
Internal tools deserve as much design rigour as consumer products
The temptation with B2B tools is to prioritise density over clarity. But expertise doesn't mean users enjoy friction. The consistent three-panel pattern and persistent applicant header reduced context-switches — which matters when you're processing 128 cases simultaneously.
Gating and progressive disclosure are UX features, not restrictions
The Underwriting Decision screen won't let a reviewer approve a case with open checks. Designed correctly, it feels like helpful structure, not a block. Surfacing what's missing and giving a direct path to resolve it turns a gate into a guide.
Status labels carry enormous weight in high-stakes environments
The difference between "In progress", "Awaiting", "Missing", "Pending", and "Blocked" is not semantic — each represents a different required action from a different person. Getting the status taxonomy right required understanding the process deeply before designing the interface.
Designing a dual product — the CRM makes the consumer app viable
The LoanEase mobile app and the CRM are two halves of the same product. Designing both taught me how UX decisions on one side create obligations on the other: a customer's document upload on mobile triggers a task in the employee's Document Review Queue.
Want to see the mobile app?
The customer-facing side of LoanEase — onboarding, loan comparison, EMI calculator, application tracker, and repayment management.