Branch Performance Dashboards

The problem

The MIS team reports on the bank's loan and deposit portfolios every day. Before the dashboards, comparing 23 branches meant pulling extracts, lining up today against the previous reporting day by hand, and answering the same questions for different people in slightly different formats.

That works, but it's slow, it's easy to get wrong, and nobody sees the picture until someone has assembled it.

What I built

• A branch leaderboard that updates from the daily loan and deposit data and ranks every branch on assets and deposits, with the change against the previous reporting day beside each one.
• A retail dashboard focused on the portfolios the retail side cares about, and a bank-wide dashboard that rolls everything up.
• Trend views for the loan and deposit books, so a jump or a dip shows up as a shape you can see rather than a number you have to notice.
• A repeatable way of handling ad-hoc requests: filter and segment portfolio data into customer lists for relationship officers instead of rebuilding each one from scratch.

Decisions that mattered

• Compare to the previous reporting day, not the previous calendar day. Weekends and holidays otherwise produce fake swings.
• Rank and show the delta together. A rank alone hides how close the race is; a delta alone hides where you stand.
• Keep one source extract feeding every view, so the retail and bank-wide numbers can never disagree with each other.

What changed

Branch performance became something people could look up rather than request. The daily report went from an assembly job to a check, and my time went to the questions the dashboards raised instead of the ones they now answer on their own.