Business Analysis & Data Analytics · Case Study 02

Digital Loan Application
and Approval System

From manual application handling to a traceable digital loan journey: requirements, process redesign, sprint planning, and operational reporting.

120Simulated applications
12User stories
3Planned sprints
64Planned story points
Featured case study

A clearer journey from application to decision

A portfolio case study that connects business needs to practical delivery and reporting outputs.

The scope covers application capture, mandatory-field validation, document readiness, assignment, manual review, decision recording, notifications, audit history, and operational KPIs.

Simulated portfolio case study. The proposed system and its benefits are designed outcomes, not a deployed bank platform or measured production results.
Business problem

Disconnected manual tracking

  • Paper applications and repeated document follow-up.
  • Unclear case ownership and review priorities.
  • Inconsistent status and decision records.
  • Limited visibility into pending applications.
Proposed direction

Centralized, traceable workflow

  • Structured intake with completeness checks.
  • Document checklist and missing-information loop.
  • Assigned review queue with recorded decisions.
  • Status history, notifications and KPI reporting.
Process analysis

As-Is → To-Be workflow redesign

The final swimlane diagrams show the current manual process and the proposed digital workflow, including missing-information loops and approval or decline paths.

As-Is · manual application process · Applicant, Loan Operations, Loan Officer / Lending Manager Click to enlarge
To-Be · digital application process · Applicant, Digital Loan System, Loan Officer / Lending Manager Click to enlarge
Requirements engineering

From business need to acceptance criteria

The BRD defines the business scope, functional requirements, business rules, and acceptance criteria. The story register translates these into a prioritized backlog.

BRD referenceRequirement summaryRelated stories
FR-01Create, save and submit applicationsUS-01 / US-02
FR-02Validate mandatory details before submissionUS-03
FR-03Document checklist and readinessUS-04
FR-04Assign and reassign loan officersUS-06 / US-07
FR-05Request information and record decision reasonsUS-05 / US-08
FR-06View application and ownership historyUS-11
FR-07Operational KPI reportingUS-12

Acceptance criteria example · US-08

As a loan officer, I want to record an approval or decline decision so that the application has a clear outcome.

  • The decision requires a valid reason category.
  • The system records the decision date and user.

Stakeholder register

StakeholderResponsibilityInfluenceInterest
Lending Business Owner / ManagementApprove business goals, prioritize requirements, and review outcomesHighHigh
Loan Operations TeamRegister applications, track documents, and follow up on missing informationHighHigh
Loan OfficersValidate information, assess applications, and record decisionsHighHigh
Lending ManagerAssign applications, resolve escalations, and monitor turnaround timeHighHigh
Risk / Credit Policy RepresentativeValidate rule definitions and review exceptions for the project scenarioHighMedium
Customer Service TeamRespond to enquiries, explain next steps, and coordinate applicant communicationMediumHigh
Loan ApplicantsProvide accurate information and complete requested actionsMediumHigh
Business AnalystGather requirements, document the BRD, write user stories, and map workflowsHighHigh
Data AnalystClean data, analyze outcomes, and prepare Excel and Power BI reportingMediumHigh
System AdministratorMaintain user access, support configuration, and monitor system issuesMediumMedium
Agile delivery design

Jira backlog structured for execution

Eight epics and 12 user stories are organized into three planned sprints. Story points, priorities and acceptance criteria follow the project story register.

Sprint 1

Intake & validation

18 story points · 4 stories

  • US-01 · Create loan application (5)
  • US-02 · Submit loan application (5)
  • US-03 · Validate mandatory fields (3)
  • US-04 · View required documents (5)

Planned backlog · To Do

Sprint 2

Review & decisioning

23 story points · 4 stories

  • US-05 · Request missing information (5)
  • US-06 · Assign applications to loan officers (5)
  • US-07 · View assigned review queue (5)
  • US-08 · Record loan decision (8)

Planned backlog · To Do

Sprint 3

Visibility & reporting

23 story points · 4 stories

  • US-09 · Review application exceptions (5)
  • US-10 · Notify applicants of status updates (5)
  • US-11 · View application audit history (5)
  • US-12 · View operational KPI reporting (8)

Planned backlog · To Do

Jira board · Sprints 2 and 3 · Actual backlog screenshot; Sprint 1 is documented in the plan above and the summary PDF Click to enlarge
Data work

Cleaning, validation, modeling, and SQL analysis

Data-quality checks

The supplied analysis dataset contains 120 applications and nine fields. Application IDs are unique; required values are present. The cleaning script documents type conversion, validation and controlled categories.

The supplied raw and clean CSV files contain the same records. This case does not claim a measured reduction in duplicates or errors.

Field groupExample fields
IdentifiersApplication_ID, Customer_ID
Application detailsSubmitted_Date, Requested_Amount_JOD, Term_Months
Profile and statusEmployment_Type, Current_Status
Operational trackingTurnaround_Days, Current_or_Decision_Reason

SQL analysis · 10 business questions

  1. Executive KPIs
  2. Application status distribution
  3. Decision outcomes and reasons
  4. Requested amount by employment type
  5. Approval rate by employment type
  6. Requested amount bands
  7. Loan-term analysis
  8. Queue-aging exceptions
  9. Monthly volume and outcomes
  10. Month-over-month application change

Power BI reporting model

Date Table
Date · Month Year · Month Sort
1 → *Single-direction date filter
Loan_Applications_Clean
Submitted_Date

Recorded duration is the supplied Turnaround_Days field. It includes open and closed cases and is not a pure decision-time measure.

Excel analysis

A workbook built around business questions

Excel · loan application dashboard · Preview of the supplied final Excel analysis PDF Click to enlarge

The workbook includes applicant, status, decision, queue, loan-term and monthly trend analysis. Open the PDF to inspect all analysis pages.

Reporting & decision support

Power BI dashboard and KPI layer

Power BI · final dashboard · 120 applications · 42 approved · 35.0% approval share · 495,500 JOD requested Click to enlarge
Interactive portfolio preview

Explore the simulated applications

This page filters the same 120-row CSV used in the project. It is a website preview, separate from Power BI Desktop.

120Applications
42Approved applications
35.0%Approved / filtered applications
495,500Requested amount (JOD)

Project impact & value designed

What the solution is designed to improve

Process visibility

Explicit ownership, information requests, and decision states make the next action easier to identify.

Designed benefit; not production-measured.

Traceable requirements

BRD requirements connect to user stories, acceptance criteria, workflow steps, and planned sprints.

Evidence: BRD, story register and Jira plan.

Operational insight

43 applications are Under Review or awaiting more information in the simulated dataset. Reporting makes this queue visible.

26 Under Review + 17 More Information Required.

Links & artifacts

Inspect the actual project outputs

Business Case

Business need, scope, risks and expected benefits.

Stakeholders

Roles, needs, responsibilities, influence and interest.

BRD

Business and functional requirements, rules and acceptance criteria.

User Stories

12 prioritized stories across three sprints.

Jira

Epic structure, sprint plan, stories and implementation tasks.

Excel Analysis

Workbook and full eight-page analysis export.

Power BI

Final dashboard PDF and editable report.