FlowsBook a callSign inCreate free accountSign up
Workflows by industry

How banks watch rival branches opening and closing near their own

Competitor bank branch tracking, branch by branch: a baseline of every rival within reach, then two short lists each month, the newly found and the closed.

Part of the guide Workflow automation

By the xMap team · · 6 min read

Competitor bank branch tracking works best when it is organised around your own branches, not around a city. For each branch you run, keep a list of every rival branch within the distance customers will travel, and look again on a timetable. Each look produces two short lists: rival branches that were not there last time, and rival branches that have closed. A branch manager can act on both the same week.

This is for network planning teams, regional managers and marketing leads at retail banks, credit unions and microfinance networks. It covers why the two lists matter, how to set the distance, two ways to run the watch, an example, and the honest limits.

Why a closure matters as much as an opening

An opening near one of your branches is a threat to answer: a rival now offers the same counter service a few doors away. A closure is the opposite. Customers who used that counter for cash, for a signature or for advice now have a longer trip, and some will consider moving their account to whoever is nearest. That window is short. A bank that learns of the closure from a quarterly report has missed it; one that hears within the month can extend opening hours, send a mobile adviser or run a local campaign.

Rival moves also say something about the area. Two banks leaving one high street in a year is a signal to review your own branch there, in either direction: stay and be the last counter in town, or follow.

Set the distance by how customers reach you

A fixed radius treats a city-centre branch and a suburban one alike, and they are not. In a dense centre a rival 400 metres away is next door, and one 2 km away serves different streets. In a suburb people drive, and a rival ten minutes away by car competes directly.

  • City-centre branches: a walking distance, such as 500 metres to 1 km.
  • Suburban and small-town branches: a drive time, such as 10 minutes by car.
  • Rural branches: the next town in each direction, whatever the distance.

Decide also what counts as a rival. Full branches of other banks, certainly. Whether to include ATMs, exchange and remittance shops or lenders depends on what your branch sells. Keep the two apart in the report so that a new cash machine does not read like a new branch.

Two ways to run the watch

A monthly sweep of the whole network

The first design looks at every branch on a timetable. It suits a network of dozens or hundreds, where the planning team wants one report.

  1. A Schedule on the first working day of each month.
  2. My data brings in your branch table, one row per branch with its address or position.
  3. Nearby places, set to each incoming place, the type Bank, and your distance. It passes on each bank found with the branch of yours it is near, the distance between them and its brand.
  4. A Filter on the brand takes your own branches out of the list.
  5. The flow splits in two. One side goes through Only new, which lets through only places this flow has not found before. The other goes through What changed, set to watch for Closed, which lets through only places it knew that have since closed.
  6. An xMap LLM block writes one line for each: which of your branches it concerns and what the manager might do.
  7. An Email to the planning team, and a map.

The first real run is the baseline. Everything is new to the flow that day, so read that first list as the census of rivals around your network, not as a month of openings. From the second run on, the two lists are short.

An alert for a handful of key branches

The second design does not wait for the first of the month. The When something changes trigger checks around up to five places you pick, as often as every 15 minutes or as rarely as once a day, and starts the flow only when a check finds that a place of your chosen kind has appeared within the distance, or that one has closed. A quiet month runs nothing but the checks.

Use it for the branches where a rival move would change a decision: a flagship, a branch under review, a branch whose lease is up for renewal. One trigger watches for a single kind of change, so a branch that needs both openings and closures gets two small flows.

A worked example, with made-up figures

Take an invented credit union with 38 branches around Toronto. Its first run finds 212 rival bank branches within reach of its own, which becomes the baseline map. The second month's email is five lines long.

Your branchRivalWhat happenedDistance
DanforthBank ANewly found350 m
Scarborough EastBank BClosed600 m
Mississauga SouthBank CNewly found1.4 km
EtobicokeBank BClosed900 m
North York CentreBank DNewly found200 m

Invented names and figures, to show the shape of the monthly list.

Bank B closing two branches in a month is the story. The credit union adds a Demographics step for those two rows to see how many residents live within 1 km of each closed counter and how many are over sixty, a group that tends to use counters more. Population figures are available for Canada; they are not for the United Kingdom or the United States, where that step should be left out. The regional manager for the east gets both closures with those numbers and a suggestion to offer account-switching appointments at Scarborough East.

The limits to state in the report

  • Newly found does not always mean newly opened. A branch can enter the places database some time after its doors open, or be found for the first time because its listing was corrected. Where a place carries an opening date the flow can show it; many do not.
  • The database is refreshed monthly. Checking daily will not find news faster than the data arrives. Monthly sweeps match it well.
  • A move looks like one closure and one new branch. Read the two lists together before calling it a retreat.
  • Rebrands appear as changes of name. After a merger, add Name or address to what What changed watches, so a renamed branch is reported as renamed, not as new.
  • A public announcement comes first. Banks often announce closures weeks ahead. A News block on local feeds, or a page reader on a rival's branch-changes page, can catch the announcement; the places data confirms it later.

What reaches each manager

Send the planning team the whole list and each regional manager only their rows; a Split by territory step or a region column in your branch table does the sharing. The message for one row is three lines: the rival and its address, what happened and when it was noticed, and the branch of yours it is near with the distance. The template Rival bank branches that closed or moved is built for the closure side and is a quick way to begin; the wider pattern is described in the guide to location intelligence automation.

Questions

How quickly will I know when a rival branch opens?

Within about a month in most cases, because the places database behind the search is refreshed monthly. Add a news or web page watch step if you want to catch the announcement before the opening.

Can I track closures as well as openings?

Yes. What changed reports places the flow already knew that have since closed, and the When something changes trigger can start a flow when a place near one of your branches closes.

How do I stop my own branches appearing as rivals?

Filter the results on the brand or the name so that your own are removed before the new and closed lists are made.

Should ATMs count as competitor branches?

Track them separately. A cash machine changes convenience for customers but does not replace a counter, and mixing the two makes the monthly list hard to read.

What does the first run show?

Everything, because nothing has been seen before. Treat it as a census of rival branches around your network. Real changes show from the second run.

Templates that do this

Read next

More on workflows by industry · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.