The Branch, the Brand and the Back-End: Short-Link Rules for UK Multi-Site Teams

Picture a clinic group with forty sites, a bakery franchise with twelve owners, or a retailer with branches from Bristol to Glasgow. They all share one cuturl.co.uk domain. On the same Tuesday, head office launches a brand campaign, a regional manager pushes a recruitment drive, and a branch manager wants a link for a half-term offer. If nobody has agreed how slugs are built, whose name goes where and who can press publish, the short domain turns into a very tidy-looking mess. The fix is not a shinier dashboard. It is a small operating model that treats the domain like shared property.

Start with the branch code, not the campaign name

The temptation is to name links after the campaign: /autumn-offer, /jab-season, /recruitment. Within a week you have three versions of each and no idea which branch they belong to. A better default is to reserve the first part of the slug for the site or region code, then add the campaign and a time marker. Something like /ncl-jabs-nov26 tells you the Newcastle site, the campaign and the period. It is still short enough to say out loud, and it cannot be confused with a head-office link.

Keep the code list in one place and make it boring. Three-letter site codes are usually enough. Regions can have their own prefix, such as /r-north- or /r-wales-. Head office campaigns can start with /hq-. The exact convention matters less than the fact that it is written down, shared and checked before anyone creates a link. Avoid generic slugs such as /offer or /book. They are the link equivalent of an unlabelled Tupperware in the office fridge: everyone assumes someone else owns it.

Permission boundaries that match the org chart

A shared domain needs clear roles. Head office should own the domain, the redirect infrastructure and the top-level naming rules. Regional managers should be able to create and edit links inside their own prefix, because waiting for head office to approve a local clinic campaign is how people end up using a personal bit.ly account instead. Branch staff should work from approved templates or a small set of pre-built links. They should not be able to edit national campaigns, change destinations or delete anything.

Make deletion a rare permission. Pausing a link is usually enough, and it leaves an audit trail. Set a default expiry on local links, such as ninety days, with an option to extend. Require a destination check for any custom URL, especially if it leaves the main brand site. A regional manager in Cardiff should be able to launch a local campaign without emailing head office, but they should not be able to change the national brand link or overwrite a slug that belongs to another region. That is not bureaucracy. It is the difference between local speed and a brand incident.

A reporting spine that rolls up

The reporting problem usually starts before the report. If one branch uses /jabs, another uses /flu-jab and a third uses /autumn-clinic, head office cannot compare them without a manual cleanup. Attach four pieces of metadata to each short link: site_id, region, campaign_family and channel. Store them in the link record itself, not only in UTM parameters at the destination. The short link should carry its own identity. Then a report can group by branch, roll up to region and summarise at head office without guessing.

Use separate links per channel, even when the destination is the same. A link shared in a leaflet, a link in a paid social post and a link in an email should not be collapsed into one number just because they point to the same page. Otherwise a busy branch looks quiet and a quiet branch looks busy. The roll-up should follow the hierarchy: branch first, region second, head office third. Keep the definitions stable across the year. If campaign_family means one thing in March, it should mean the same thing in November.

Build a small registry, not a spreadsheet swamp

A shared spreadsheet is fine if it is treated as the source of truth rather than a side project. List the site codes, region codes, current campaigns, link owners and expiry dates. Lock the columns that should not drift. Add a simple status column: live, paused, expired. The registry does not need to be glamorous. It needs to be the place people check before they create a link called /final-offer-2.

The ten-minute monthly tidy

Once a month, check for links that have expired but still appear in old emails, links with missing metadata, duplicate slugs across regions and redirects that land on a 404. Look for branch links using the head-office prefix and head-office links using a branch code. Fix the naming before the next campaign lands. This is unglamorous work, but it is the sort of thing that keeps a multi-site short-link estate from turning into a maze.

What good looks like

Good looks like a branch manager creating a link in two minutes, a regional manager seeing their own numbers without waiting for a head-office export, and head office trusting the total. Nobody overwrites anybody else. The domain stays short, the reporting stays honest, and the local teams keep the freedom to act. One domain, many kitchens: the trick is agreeing where each kitchen is allowed to put its knives.