Banks should treat branches as a relationship and revenue channel, not just a cost center. The article argues that branches still support customer acquisition, ongoing service, small business lending, and trust building, especially where customers prefer in-person advice or cash handling. The right decision is to evaluate branch value by customer segment, geography, and lending impact, rather than using branch count alone as the success metric.
How branch strategy changes when digital banking scales
As digital usage grows, branch strategy should shift from “how many locations can we afford?” to “which locations still create measurable customer and balance-sheet value?” That means separating branches that support acquisition, advice, and deposit gathering from those that mainly duplicate digital service. The decision should be built around segment demand, transaction mix, and local market economics, not a single enterprise-wide closure target.
Branches remain most defensible where they support behaviours that digital channels still do not fully replace: complex onboarding, relationship-led selling, cash handling, and trust-building for customers who prefer face-to-face service. That is especially true for small business and mass-affluent segments, where in-person advice can influence product uptake, retention, and cross-sell. A branch network is therefore part operating model, part distribution strategy.
What changes in practice is the unit of analysis. Instead of measuring only branch count, banks should look at contribution by geography, customer segment, and product line. A high-footfall branch with weak profitability may still be worth keeping if it supports local lending, business deposit flows, or strategic presence in a market where competitors are absent. Conversely, a lightly used branch with no clear acquisition or lending role is a stronger closure candidate.
What to measure before closing or keeping a branch
The most useful metrics are the ones that reveal what the branch actually does, not just how often it is visited. Banks should review new-account conversion, loan origination, deposit retention, service deflection to digital, cash transaction volume, and customer migration patterns after digital adoption. A branch that appears costly in isolation may still be economically justified if it reduces churn or improves lending outcomes.
Location context also matters. In some communities, branches serve as a resilience channel when digital access is limited, trust is low, or customers need cash and assisted service. In others, a branch may be retained primarily as a flagship or advisory hub rather than a high-volume transaction site. That distinction matters because the operating model, staffing, and hours should match the role the branch is meant to play.
If the bank is evaluating a close or consolidation, it should model second-order effects, not just immediate cost savings. Those include lost relationship depth, reduced small business origination, weaker local brand presence, and customer attrition to competitors. The question is not whether digital is “better,” but whether the branch still performs a function that digital cannot yet do at equal commercial value.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST CSF 2.0 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | GV.OV — Cybersecurity Oversight | Branch decisions require oversight of business and operational risk trade-offs. |
| GV.RM — Risk Management Strategy | The branch network decision is a portfolio trade-off between cost, reach, revenue and resilience. | |
| ID.BE — Business Environment | Branch value depends on customer segment, geography and product mix. | |
| Recommendation — Use oversight reviews to align branch footprint decisions with business objectives and risk appetite. Evaluate branch retention and consolidation through a formal risk and value management lens. Map each branch to the customer and business outcomes it actually supports. | ||
| CIS Controls v8 | 11 — Data Recovery | Branches support continuity for customers who still need assisted, local access during disruption. |
| Recommendation — Maintain local service continuity plans for critical customer-facing branches. | ||
Practitioner Guidance
Decision rule: Keep a branch open when it has demonstrable value in acquisition, lending, advice, or retention that cannot be replicated cheaply through digital channels; close it when usage is low, product impact is weak, and the local market does not justify a physical presence.
What to prioritise: Separate branches into operating roles such as transaction site, advice hub, small business engine, or brand presence, then assess each role with different metrics. A single profitability test is too blunt for deciding a network redesign.
What to verify: Confirm that digital adoption is not hiding unmet demand, especially among customers who still need cash handling, assisted onboarding, or in-person problem resolution. Also verify whether branch traffic supports lending or deposit growth, not just service volume.
Practitioner takeaway: The strongest branch networks are intentionally differentiated, with each location justified by a clear customer and revenue function rather than by habit or legacy footprint.
