Standardising Technology Across Multiple Property Offices
Every branch does technology differently. The question is how you get one standard that also applies to the next office you open or acquire.
Multi-office property businesses rarely grow by design. Offices are opened, acquired or inherited, each arriving with its own devices, licences, suppliers and habits. One branch may have bought its laptops from a local retailer and set up Microsoft 365 itself. Another may have come with a managed services arrangement from a previous owner. A third may have been running on whatever worked at the time and has never been reviewed since.
The result is not one business with several offices but several businesses sharing a brand. Each office has its own security posture, its own way of onboarding staff, its own backup arrangement and its own understanding of what "good" looks like. When someone asks a simple question — "How many devices do we have?", "Who has access to what?", "Are all offices backed up?" — the answer usually requires a phone call to each branch and a spreadsheet assembled by hand.
The problem is not that any single office made a bad decision. It is that nobody ever owned the whole. Standardising technology across a multi-office property network is about creating one environment that every office shares, so that the business can be managed, secured and grown as a single entity rather than a loose collection of independent branches.
What inconsistency actually costs
The cost of inconsistent technology is not always visible, because it shows up in the things that take longer than they should, the questions that cannot be answered quickly, and the risks that exist without anyone being aware of them.
Security is only as strong as the weakest office
If one office has multi-factor authentication, conditional access and managed devices, and another does not, the business has a gap. An attacker does not need to defeat the strongest office — they only need to find the one that is still running on shared passwords and unmanaged laptops. In a multi-office network, every office is part of the same tenant, the same email system and often the same shared files. A compromise in one branch can reach the others.
Staff cannot move between offices easily
In a standardised environment, a property manager who transfers from one branch to another logs in to the same systems, sees the same file structure and follows the same processes. In an inconsistent one, every move is a fresh setup. New accounts, different folder structures, unfamiliar security settings and a different support contact. For a growing network where staff regularly move between offices or cover for each other during peak periods, that friction becomes a real operational cost.
Reporting has to be assembled by hand
When each office configures things differently, there is no single view of the business. A question as straightforward as "How many Microsoft 365 licences are we using across all branches?" can require logging in to each tenant, exporting a list and combining it in a spreadsheet. Security reporting is the same — there is no central position from which to see whether every office has the right controls in place. The business ends up relying on individual people at each branch to provide information that should be available at a glance.
Support is slower because every office is different
When a staff member in one office has a problem, the support path depends on which branch they are in. One office might call a local IT provider who knows that particular setup. Another might have no defined support path at all. Without a common environment, even a simple issue — a new user setup, a password reset, a printer configuration — takes longer to resolve because the person helping has to learn that office's specific arrangement before they can fix anything.
Licences are paid for and unused
Each office that buys its own licences independently tends to over-provision. A branch purchases a bundle of Microsoft 365 licences when it has more staff, then does not reduce them when headcount changes. Over time, across multiple offices, the business is paying for licences that no one is using — and because no one owns the whole, nobody is checking. The cost is quiet but continuous.
No way to answer a simple question about the whole business
"Are all our offices backing up their data?" "Does every branch have multi-factor authentication enforced?" "Who across the whole network still has access after leaving?" These are not unreasonable questions for a director or general manager to ask. In an unstandardised network, they are surprisingly difficult to answer. The information exists, but it is held by different people in different offices, in different formats, and some of it is not being tracked at all. The business cannot manage what it cannot see.
Why it happens
None of this happens because anyone made a deliberate decision to create inconsistency. It happens because each office solved its own problem at the time. A new branch needed laptops quickly, so someone bought what was available. An acquired office came with an existing IT provider, and changing it felt like more trouble than it was worth. A remote office had connectivity issues, so a local supplier was engaged to fix them. Each decision was reasonable in isolation.
The deeper issue is that nobody owned the whole. In a multi-office property business, technology decisions are often made at the branch level because there is no one person or team responsible for the network as a single environment. The office principal needed something to work, so they made it work. The head office was not consulted because there was no clear role for "consult head office about technology." Over time, each office's local solution became its permanent state.
Standardising felt like a project nobody had time for. It is not urgent in the way a broken email system or a failed inspection is urgent. It does not appear on any single day's priority list. It is the kind of work that is always important and never urgent, which means it is always deferred. The cost is distributed and quiet — a bit more time here, a slightly higher risk there, a licence that keeps billing — so it never reaches the threshold that forces action.
That is worth understanding, because it means the solution is not to blame the offices for being inconsistent. It is to recognise that consistency requires ownership. Someone has to be responsible for the technology standard across the whole network, and that standard has to be defined, documented and applied — not left to emerge on its own.
What a standard actually contains
A technology standard is not a vague aspiration. It is a defined set of decisions that every office shares, documented well enough that a new branch can be brought onto it without a conversation about what "good" means. For a multi-office property business, that standard needs to cover several concrete things.
Identity and access
Every staff member across every office signs in with a managed identity in the same Microsoft 365 tenant. Multi-factor authentication is enforced consistently — not left to each office to decide. Conditional access rules determine what can be accessed from which devices and locations. When someone joins, their accounts are created in the same place with the same permissions model. When they leave, access is removed from one position rather than chased across branches. In a property business where staff move between offices and where access to tenant applications and trust information must be tightly controlled, a single identity model is the foundation everything else rests on.
Device configuration and management
Every laptop, desktop and mobile device is enrolled in a mobile device management platform such as Microsoft Intune. That means devices are encrypted, configured to a common baseline, and can be remotely wiped if lost or stolen. A property manager who drops their phone at an inspection should not create a security incident that one office handles well and another does not. The standard defines what a managed device looks like — encryption on, password or PIN enforced, updates current — and no office is exempt. An unmanaged laptop bought by a branch and never enrolled is not a device on the network; it is a gap.
The Microsoft 365 baseline
The standard defines how Microsoft 365 is configured across the whole network. That includes the tenant settings themselves — how external sharing is controlled, what the default permissions are on new SharePoint sites, whether guests can be invited without approval — and the structure each office uses within it. A consistent SharePoint and Teams structure means a sales agent in one branch and a property manager in another store information the same way, under the same naming conventions, with the same access model. The standard also covers which Microsoft 365 plan each role receives, so a licence is assigned based on what someone actually needs rather than what their office happened to buy.
Security settings
Security is not something each office configures to its own preference. The standard defines the security baseline — which the Australian Signals Directorate publishes as the Essential Eight, a set of mitigation strategies that can serve as a common security standard across offices. That includes application control, application patching, operating system patching, macro restrictions, user application hardening, restricted administrative privileges, multi-factor authentication and regular backups. Every office meets the same baseline. An office that has not implemented these controls is not an office with a different approach; it is an office that is not yet at standard.
Backup and tested recovery
Every office's Microsoft 365 data — email, SharePoint, OneDrive, Teams — is backed up to a common backup platform, and recovery is tested, not assumed. The standard defines what is backed up, how often, where the backup lives and who can restore from it. It also defines what happens when an office needs to recover something: the process, the person responsible and the timeframe. A backup that has never been tested is a hope, not a control. In a property business where a lost email thread or a deleted SharePoint folder can mean a missing transaction record, recovery needs to work the same way in every office.
Onboarding and offboarding steps
The standard defines what happens when someone joins the business and what happens when they leave. Onboarding is a checklist, not a memory exercise: account creation, licence assignment, device enrolment, access to the right SharePoint sites and Teams, induction into the security baseline. Offboarding is the mirror: account disabled, access revoked, device retired, mailbox handled according to the standard, licences reclaimed. The steps are the same regardless of which office the person is in. That means a departing staff member in any branch is handled the same way — promptly and completely — rather than leaving an account active because no one in that office remembered to close it.
A defined support path
Every staff member in every office knows how to get help. There is one support contact, one way to log an issue and one set of expectations about response. That path does not change depending on which branch you sit in. When a property manager in a newly acquired office has a problem on the morning of an inspection, they do not need to find out who the previous owner used for IT support and whether that arrangement is still in place. They contact the standard support path, and the person on the other end already understands the environment because it is the same as every other office.
Standardising without stopping the business
Standardising a multi-office property network is never a single cutover. It is done office by office, and the standard is proven in one location before it is replicated anywhere else. That sequencing is not a preference. It is what protects the business from disrupting itself while it is trying to improve.
The first office is where the standard is built and tested. That office becomes the reference environment — the place where the identity model is configured, the device enrolment process is run end to end, the security baseline is applied and the backup is set up and tested. Anything that does not work is found here, in one office, rather than across the whole network at once. The first office also produces the documentation: what was done, in what order, what needed adjustment and what the final configuration looks like. That documentation is what makes the next office faster.
The reason this matters is that a multi-office cutover — changing every office at once — creates a single point of failure at a scale the business cannot absorb. If the identity migration has a problem, it affects every branch simultaneously. If a security setting breaks access to a property platform, it breaks it everywhere. The business goes from several offices working imperfectly to no offices working at all, and the people fixing it are trying to solve the same problem in multiple locations at the same time. Office by office means that when something unexpected happens, it happens in one place, and the fix is found before it is needed anywhere else.
It also means each office is only disrupted once. The transition for a single branch is manageable: devices are enrolled, accounts are restructured, security is applied, staff are briefed. The office is at standard. It does not need to be revisited. The next office then follows the same path, with the benefit of everything learned in the first one. By the time the third and fourth offices are done, the process is repeatable — the same steps, in the same order, with the same outcomes.
The offices that have not yet been standardised continue to operate. They are not left in a worse position than they were in before; they are simply not yet at standard. The business continues to function while the standard is rolled out, and each office that is brought onto it strengthens the network rather than disrupting it. The goal is a network where every office is at standard, reached through a sequence of manageable, one-office transitions rather than a single event that puts the whole business at risk.
The real prize: the next office
The immediate benefit of standardising is consistency — every office at the same security level, every staff member on the same systems, every question answerable from one position. But the larger benefit appears when the network grows. Once a standard exists, opening or acquiring an office becomes a repeatable process rather than a fresh project each time.
Consider what happens today when a multi-office property business acquires a new branch. The acquired office arrives with its own devices, its own Microsoft 365 tenant or lack of one, its own security posture and its own support relationships. Bringing it into the network means working out what it has, deciding what to keep and what to replace, migrating accounts, reconfiguring devices, applying security and establishing a support path. Each of those steps is figured out from scratch because there is no standard to apply. The work is different every time because the starting point is different every time, and the result is different every time.
With a standard in place, that changes. The new office is brought onto an existing environment. The identity model already exists. The device enrolment process already exists. The security baseline already exists. The backup platform already exists. The support path already exists. The work is not designing a solution; it is applying one. The new branch starts at the standard rather than being dragged up to it over months. Staff in the acquired office are briefed on a support path that is already running, not one that has to be negotiated. Their devices are enrolled into a management platform that is already configured. Their accounts are created in a tenant that is already secured.
That predictability matters for a growing network. It means the decision to open or acquire an office is a business decision, not a technology project. The technology is a known quantity — the same steps, the same outcome, the same standard. The time and effort that would have gone into figuring out the technology goes into the things that actually differ between offices: integrating the new branch's property data, briefing its staff, and bringing its client relationships into the network. The technology foundation is already settled.
It also means the standard gets stronger each time it is applied. Every new office is a chance to refine the process — to find a step that can be simplified, a configuration that can be improved, a piece of documentation that can be clearer. The first office built the standard. The second office proved it was repeatable. The third and fourth make it routine. By the time the network has grown through several offices, the standard is not a document someone wrote once; it is a living process the business knows how to run.
Franchise property networks
Franchise property networks face the same inconsistency problem with one added constraint: offices may be independently owned, so a standard has to be adoptable rather than merely mandated. The principles are the same, but the approach differs — a franchise network needs a standard that franchisees can see the value in adopting voluntarily, supported by clear documentation and a proven reference environment, rather than one imposed from above. See our approach to standardising technology across franchise networks for that audience.
How LOOKUP helps
LOOKUP works on the Microsoft 365 environment that surrounds the specialist systems a property business relies on. That means designing the tenant structure across the whole network, configuring identity and access so every office shares the same model, and enrolling all devices into a common management platform. The security baseline — aligned to the Essential Eight — is applied consistently so no office is weaker than another. Backup and tested recovery are provided through a common platform, and a single managed IT support model means every staff member in every office has the same path to help.
LOOKUP coordinates with property management platforms, CRMs and trust accounting systems rather than replacing them. The property software that runs listings, applications, maintenance and trust accounting remains the system of record for those functions. LOOKUP manages the environment around it — identity, email, devices, security, backup and support — so that the specialist platforms sit on a foundation that is consistent, secure and recoverable across every office.
For a multi-office property business, that means a single partner responsible for the technology standard across the whole network. The same identity model, the same security baseline, the same device configuration, the same backup and the same support path — whether an office has been part of the network for years or was acquired last week. If you are exploring technology for your real estate or property business, standardising across offices is one of the highest-leverage things you can do.
Frequently asked questions
Start with one office and build the full standard there — identity, devices, security, backup and support — before replicating it anywhere else, so any problems are found in one place rather than across the whole network. That first office becomes the reference environment, producing the documentation and the proven configuration that every subsequent office follows. By the time the second and third offices begin their transition, the process is repeatable rather than exploratory, and the standard has been tested under real conditions.
No, and moving every office at once creates a single point of failure at a scale the business cannot absorb, because a problem with the identity migration or a security setting affects all branches simultaneously rather than one. Office-by-office sequencing means each branch is only disrupted once, and anything unexpected is contained to a single location before the next office begins. The offices that have not yet been standardised continue to operate normally while the rollout proceeds.
An acquired office is brought onto the existing standard rather than assessed from scratch, because the identity model, device enrolment, security baseline, backup and support path already exist and simply need to be applied. The work shifts from designing a solution to executing one, which means the new branch starts at the standard instead of being dragged up to it over months. Staff in the acquired office are briefed on a support path that is already running, not one that has to be negotiated.
A standard can work across independently owned offices, but it has to be adoptable rather than mandated, because franchisees need to see the value in adopting voluntarily rather than having a standard imposed from above. Clear documentation and a proven reference environment matter more in a franchise context, where the standard has to earn adoption office by office. The principles are the same, but the approach relies on demonstration rather than direction.
No, standardising covers the environment around your property management platform — identity, email, devices, security, backup and support — not the specialist systems themselves, which remain the system of record for their functions. LOOKUP coordinates with property platforms, CRMs and trust accounting systems rather than replacing them, so the standard strengthens the foundation those systems sit on. The property software that runs listings, applications, maintenance and trust accounting continues to do exactly that.
Drift is prevented by ownership — someone has to be responsible for the technology standard across the whole network, and the standard has to be documented, applied to every new office, and maintained when changes are made. Without that ownership, each office will eventually solve its own problems in its own way, and the network returns to the inconsistency the standard was meant to fix. The standard is not a one-time project; it is an ongoing responsibility that needs a clear owner.
Sources & Further Reading
The following primary and authoritative sources support the research, guidance and industry context discussed on this page:
Australian Cyber Security Centre (ASD) — Essential Eight Mitigation Strategies — 2024
The ASD's published baseline set of mitigation strategies that can serve as a common security standard across offices, covering identity, access, patching, application control and multi-factor authentication.
View Source →Evidence Standard
LOOKUP references recognised industry, government, professional and technology sources when discussing research, regulation and industry trends. Research findings are paraphrased and linked to their original sources wherever practical. LOOKUP's professional observations and recommendations are presented separately from third-party research.
Get one standard across every office
If every branch does technology differently, the business is harder to secure, harder to support and harder to grow. A single technology standard changes that — and makes the next office you open or acquire a repeatable process rather than a fresh project. If you are building a technology roadmap for your property business, standardising across offices is where consistency starts.
Peter Kantarelis
Founder, LOOKUP — Business Technology Strategist
Peter Kantarelis is the Founder of LOOKUP and a business technology strategist helping Australian organisations modernise technology, strengthen cyber security and prepare for practical AI adoption. He regularly works with business owners and leadership teams to improve productivity, reduce operational risk and implement technology that delivers measurable business outcomes. The LOOKUP Business Modernisation Framework™ reflects more than 25 years of helping Australian businesses make better technology decisions.
View More Insights →