Banking Branch Technology Refresh: A Practical Guide

A banking IT infrastructure rollout works inside constraints retail never meets: security vetting for every person who touches a branch, change windows negotiated with risk teams, devices that hold customer data at every desk, and a regulatory environment where "the branch opened late" is an incident, not an anecdote. Refreshing technology across a branch network is deployment with the tolerances turned down.

What makes branches different

People must be cleared. Field engineers need police checks, inductions and sometimes bank-specific credentials before they enter a branch outside public areas. Mobilising a refresh means mobilising a vetted workforce, and vetting has lead times a schedule must respect.

Change is controlled. Banks run formal change management; every branch visit maps to an approved change with a window, a plan and a rollback. The rollout's wave plan and the bank's change calendar are one document, or the program stalls at the CAB.

Assets carry data and risk. A teller workstation is a data-bearing asset with a custody requirement. Every device movement gets serialised tracking; every retired device travels a certified destruction chain ending in a certificate the bank's risk function can file. "It's on a truck somewhere" is not a status.

The branch must open. Cutovers run overnight with rollback rehearsed. A branch unable to serve customers at 9:30 am escalates through channels no project wants to meet, so the downtime disciplines apply at full strength: deep staging, timed playbooks, parallel-run for anything critical.

The refresh pattern that works

Pilot in low-profile branches across formats. Waves grouped by region and change-window availability. Kits staged per branch, imaged with the bank's build, serial-matched to the register before dispatch. Overnight installs with evidence packs: photos, test results, asset reconciliation. Old fleet out the same night into certified custody. Hypercare through the first trading days per wave.

The pattern is standard multi-site method, executed with banking's paperwork and banking's stakes. That combination, industrial pace with auditable custody, is the entire trick.

Proof it scales

NAB relies on IMI for technology rollouts and onsite support across its nationwide branch network. Their words: "IMI always go above and beyond to deliver service." The case study and our banking industry page carry the detail.

The planning questions to settle early

How long does your vetting pipeline take, and who owns it? Which change windows exist per region, and how many branches fit each? What custody evidence does risk require for retired assets? Settle these three before scheduling anything, and the rest of the program behaves like deployment. Leave them late and they become the program.

Refreshing a branch network? Speak to an expert.