Managing Branches and Departments in One Company

A multi-branch company faces a tension it cannot avoid: the identity must be uniform while the data must be local. Logo, colours, information order and title conventions are the same everywhere, while address, phone, opening hours, map location and staff belong to each branch individually. The most expensive error here is displaying head-office details on every employee's card, so a client in Dammam opens the card of someone they met there, finds a Riyadh address and number, and calls the wrong place or drives somewhere irrelevant.

Draw the structure before building anything

Half the problems in branch management come from a structure that accumulated rather than being planned: a branch was added, then a department, then another branch copied from the first along with its mistakes.

Sit down for an hour and sketch it: how many branches, what departments in each, who manages which, and who needs permission to edit what.

That simple sketch usually reveals things that were never explicit: a department serving two branches, a manager overseeing locations in two cities, or a department that exists in one branch and not another.

The working rule: the digital structure must match operational reality, not the org chart in an HR file. If the Jeddah manager effectively handles Makkah matters too, let the permissions say so.

What is shared and what is local

Shared at company level: logo, colours and typefaces, title conventions, the company description, general policies, and the template every page uses.

Photo by Steph Quernemoen on Unsplash

Local to each branch: address and map location, phone, opening hours, staff list, the services actually available at that branch, and local offers.

That last point deserves attention. Not every service exists at every branch. A branch that does not offer something should not display it, or it will receive customers asking for what it does not have — one of the biggest sources of frustration in multi-branch businesses.

Opening hours: the most volatile data and the most neglected

In Saudi Arabia specifically, opening hours are not fixed data but a seasonal variable.

Ramadan changes every branch's hours. Both Eids have their own schedules. National holidays alter closing times. Branches inside malls follow mall hours rather than company hours. A branch in a residential district may open early while one in a business district opens late.

Managing that manually through printed signs on ten doors always ends the same way: two or three branches carrying outdated hours, and customers arriving to find doors closed.

The arrangement that works: each branch is responsible for its own hours, with management reviewing before major seasons. Setting hours and linking them to Maps is covered in opening hours and Google Maps.

Permissions: three layers

The distribution that works in most multi-branch companies:

Head office controls identity, templates and policies, creates and closes branches, and sees everyone's figures.

Branch manager edits their branch's details — hours, phone, local offers — manages their branch's staff, and sees only their branch's numbers.

Employee edits their own details only: photo, bio, direct number.

This resolves the standing tension: head office does not want anyone changing the logo, and a branch manager does not want to wait a week to correct their own phone number.

The common error is concentrating every permission at head office "for discipline". The effect is the reverse: data goes stale because whoever notices an error cannot fix it, and whoever can fix it never notices.

The permission model is detailed in permissions and user management.

Departments within a branch

In larger companies each branch subdivides: sales, customer service, maintenance, accounts.

The practical benefit of representing departments digitally is not only organisational but directional: a customer looking for after-sales support should not land on a sales representative, and vice versa.

The useful arrangement gives each department a page showing its role, how to reach it, and who works in it. Customers reach the right person first time, instead of a chain of transferred calls that usually ends in them giving up.

Note that departments do not always parallel branches. Maintenance may serve every branch from one centre while sales exists in each. The digital structure should reflect that rather than imposing a symmetry that does not exist.

Getting the customer to the right branch

This is the benefit customers feel directly.

A map location per branch, not one written address. They tap and drive.

A number per branch, not one central number that transfers. Repeated transfers are the largest source of irritation in dealing with multi-branch companies.

A clear branch list for anyone arriving at the general page, ordered by city.

Each employee's card showing their own branch — the most important of the four. Someone met at the Khobar branch should have Khobar on their card.

Opening a new branch, or closing one

Opening: create the branch page a week before it opens, not after. A branch that opens with no digital presence loses its most valuable weeks — the ones where people who saw the signage go looking for it.

Photo by S O C I A L . C U T on Unsplash

Closing or relocating: do not delete the old branch page. Turn it into a page pointing to the new location with its address. Someone reaching the old link finds a way forward instead of a missing page, which converts a problem into a service.

That second point is widely overlooked, and the result is customers reaching dead pages or driving to closed premises.

Local offers: controlled freedom

A recurring question in multi-branch companies: may a branch manager launch offers of their own?

Forbidding it outright misses real opportunities. Branch managers know their local market: that a particular district gets busy after Isha, that a nearby school finishes at a specific time, that a competitor opened next door last week. None of that reaches head office in time.

Permitting it without limit produces a worse mess: two branches in one city running different offers on the same product, so the customer at the more expensive one feels cheated when they find out — and they will find out.

The balanced arrangement: an approved framework with freedom inside it. For example, a branch manager may run an offer up to a set discount percentage, for no more than two weeks, on items from an approved list, without referring upwards. Anything beyond that needs approval.

You get local responsiveness without losing consistency. Building offers is covered in digital coupons and offers for shops.

Staff moving between branches

A routine occurrence in multi-branch companies, and usually handled badly.

Someone who transferred from Riyadh to Jeddah keeps a card showing the Riyadh address and number, sometimes for months. Clients opening it call the wrong branch, that branch transfers them, and the result is a poor experience caused by one un-updated field.

The fix is procedural: make updating the branch part of the transfer process itself, alongside handing back equipment and changing email. It takes seconds if it is on the checklist, and never happens if it is not.

The harder case is someone serving two branches. The answer is not to pick one arbitrarily but to show the branch where they spend most of their time, noting that they cover both.

Measuring branch performance

Separated figures per branch reveal what financial reports alone do not.

A branch with high page opens and low sales shows interest that is not converting into visits: the location may be hard to reach, the hours unsuitable, or what is offered may not match expectations.

A branch whose page is never opened has a visibility problem rather than a performance one: people do not know it exists.

A large gap between two comparable branches deserves a direct question to the weaker branch's manager, and the answer is usually simple and operational.

The rule: compare a branch to itself over time first, then to branches similar in size and setting. Comparing a mall branch to one on a side street compares nothing.

Getting started

Start with one branch and set everything up properly: data, permissions, staff. Then copy the pattern to the rest.

That is considerably faster than creating ten at once and then discovering a structural error you have to correct ten times.

Then test it yourself: open every branch page on your phone, press the call button, open the map. Faults surface in two minutes and appear in no report.

With AurCard you manage branches and departments from one account: a shared identity, per-branch data, and permissions that let a branch manager update what belongs to them.