Multi-office businesses need each site to manage its own equipment while head office can still see the whole estate. Hierarchical locations with departmental separation give you both. The thing that most often breaks is the transfer between offices, which loses history if it isn't recorded as one.
Every multi-site business I've worked in ran the same system, which was eleven systems.
Head office had a list. Each office had its own spreadsheet. None of them agreed, and roughly once a year somebody would try to consolidate them by email and give up around the fourth attachment.
Why the single flat register gets abandoned
The instinct is to fix fragmentation with one central list. It doesn't work, and the reason is mundane rather than political.
An office manager in Leeds doesn't want to scroll past four thousand items in Manchester to find a monitor. Made to, they build a local spreadsheet — and now you have the fragmentation you started with, plus a central system nobody updates.
Separation isn't a nice-to-have in a multi-site organisation. It's the condition for anyone using the thing.
Hierarchy, done once, properly
|
Level |
Example |
Who works at this level |
|---|---|---|
|
Region |
North |
Group reporting and insurance |
|
Office |
Leeds |
The local manager, day to day |
|
Floor or area |
Second floor |
Counts and desk moves |
|
Room |
Meeting room 2 |
Finding the thing |
Filtering by a parent shows everything beneath it, so head office gets a roll-up without anyone collecting anything, and Leeds gets a list that fits on a screen.
Worth spending an afternoon on this at the start. Restructuring a location hierarchy after two thousand items are filed into it is tedious in a way that's hard to convey.
The transfer that breaks the chain
This is where multi-site registers actually go wrong, and it's specific.
Equipment moves between offices. It leaves one site's list, spends a week in transit, and either never appears on the destination list or turns up as a brand new record with no history — no purchase date, no warranty, none of the three repairs it's already had.
Recorded as a transfer with a destination, it stays one continuous record and the in-transit state is visible rather than ambiguous. That's the whole fix, and it costs one action.
*A transfer keeps one record and one history, rather than a deletion at one end and a creation at the other.*
Office moves are an opportunity, not a disaster
A relocation is the single best chance you'll get to correct the register, because every item is being physically handled anyway.
Scan as it's packed, scan as it's unpacked. You finish the move with an accurate register instead of the usual six months of drift, and the count you've been postponing is done as a by-product.
Most organisations do the opposite — suspend the register during the move because it's chaotic, and never quite restore it.
Devolving without losing oversight
- Local managers issue and receive. Head office approving a monitor is a bottleneck that produces workarounds.
- Counts are scoped per site, so they're an afternoon rather than a project, and they rotate through the year.
- Reporting rolls up centrally — value by site, holdings by department, a group-wide count for insurance.
- One process, documented once. New offices inherit it instead of inventing a spreadsheet.
Opening a new site
A new office set up without the process starts a spreadsheet on day one, and you'll be unpicking it in two years.
Making registration part of the opening checklist — locations created, equipment registered on arrival, a named local person who can issue — takes about an hour and prevents the divergence entirely. It's the cheapest intervention in this article and the one most often skipped, because opening an office is busy and this doesn't feel urgent.
|
Opening task |
Cost |
What it prevents |
|---|---|---|
|
Create the location hierarchy |
10 minutes |
Equipment filed nowhere sensible |
|
Register equipment as it arrives |
As it happens |
Reconstructing from invoices in a year |
|
Name a local recorder |
A conversation |
Records made remotely by people who weren't there |
|
Run a count at week four |
An hour |
Discovering what the fit-out actually left behind |
Key takeaways
- A single flat register gets abandoned locally, which recreates the fragmentation you were fixing.
- Build the location hierarchy once, properly — restructuring later is genuinely painful.
- Record inter-office moves as transfers; delete-and-recreate loses purchase basis, warranty and repair history.
- An office move is the best opportunity you'll get to correct the register, not a reason to suspend it.
- Put registration in the new-office opening checklist; an hour there prevents years of divergence.
Frequently asked questions
Can each office see only its own equipment?
Yes. Departments and hierarchical locations let each site manage and view its own register inside one organisation, while head office retains a consolidated view across all of them.
How do we handle equipment moving between offices?
As a transfer with a destination, so the item keeps one continuous history and its in-transit state is visible. Deleting from one site and adding at another loses the purchase basis, warranty and repair history.
Can we produce a group-wide asset count?
Yes. Counts are scoped per site so they stay manageable, and the results roll up. Insurance and group audit get a consolidated figure without anyone collating spreadsheets by email.
Does every office need its own administrator?
Someone local who can issue and receive equipment, yes — otherwise records are made remotely by people who weren't there. Unlimited users on every plan means that doesn't carry a per-seat cost.
What's the best time to clean up a multi-office register?
During an office move or a fit-out, when everything is being handled anyway. Scanning as equipment is packed and unpacked produces an accurate register as a by-product of work you're already doing.
How should we structure locations across regions?
Region, office, floor, room. Four levels covers almost every multi-site business, and filtering by a parent shows everything beneath it. Deeper hierarchies slow every entry down for little benefit.