A 2027 branch staffing plan copied from last year's template puts people in the wrong place at the wrong hour.
Picture 11:40 on a Friday. Six members and customers are waiting in the lobby. Two tellers are on the line, and the one banker who handles loan conversations is at lunch. Across town, a second branch has three staff and an empty lobby.
Friday, 11:40 a.m.
Friday, 11:40 a.m.
Same network, same hour. One schedule is short, the other is idle.
Neither branch has a staffing problem. Both have a planning problem. Their schedules came from habit, not from who walks through the door. Here is how to build your 2027 plan around real traffic data, in five steps, before January.
Last year’s schedule reflects last year’s assumptions. A lot moves in twelve months: a payday shifts, a competitor closes a branch nearby, and routine transactions keep moving to the app.
In the American Bankers Association’s 2025 survey, 54% of bank customers said they manage their accounts most often on a mobile app, and 9% said they mostly visit a branch. The ABA points to the branch as the channel for more complex transactions. That’s the work your schedule has to protect.
Staffing is the one decision that sets your cost and your member experience at the same time, and the cost keeps climbing. The FDIC reported that salaries and employee benefits at insured banks rose 5.1% year over year in the third quarter of 2025. Get the hours wrong and you pay twice: idle staff in the valleys, long waits at the peaks.
Branch workforce planning built on traffic data answers three questions for every branch:
When do people arrive, by day and by hour?
What do they come in for?
How long does each type of visit take?
Answer those, and the schedule follows from the answers instead of from habit.
Break it out by branch, day of the week and hour. Include walk-ins, scheduled appointments and wait times. A full year captures tax season, holidays and the slow weeks in between. If you only have three months of clean data, start there and mark the gaps.
Whether you're writing a credit union staffing plan or one for a community bank, plan these two kinds of demand separately. The second one is growing: in J.D. Power's 2025 advice study, 26% of bank customers said they're very interested in advice from their bank, up from 19% in 2021.
Mark the busiest and quietest hours at each branch. Say your Main Street branch sees 40 walk-ins between 11 a.m. and 2 p.m. on Friday, and 12 in the same window on Wednesday. Those two windows need different rosters, even if the branch is open the same hours both days.
Pick a maximum lobby wait time and build every hour of the schedule to hit it. Then move appointment scheduling into the valleys, so bankers aren't pulled off the floor at the peak. At the regional level, share staff between nearby branches whose peaks fall on different days.
A single annual schedule can't respond to what you learn in March. Commit to the first quarter in detail and set checkpoints for the rest.
A staffing plan is only as good as its last review. Run it on a fixed calendar:
Build the 2027 plan from twelve months of traffic data.
Roll out the new schedules and the appointment shift.
Change one thing per region and measure wait times against your standard.
Use two quarters of results to support the 2028 headcount request.
Branch leaders who walk into budget season with traffic data don't argue for headcount. They show it.
A schedule of roles and hours for each branch, built around when members and customers arrive, what they come in for and how long each visit takes.
Twelve months captures tax season, holidays and the slow weeks. Three months of clean data is enough to start, as long as you mark the gaps.
Every quarter: plan in Q4, implement in Q1, test in Q2, and use the results to prepare for budget season in Q3.
RelationshipOS brings lobby traffic, appointment scheduling, staff management and analytics into one place, so your 2027 branch staffing plan starts from what happened in your branches, not from what last year's template assumed.
Walk-ins per hour, example branch
Ready to turn your branch into a revenue engine? Let’s talk.
