Strata management companies operate across dozens or hundreds of schemes, each with its own owners, tenants, contractors, and ongoing correspondence. Without a clear structure, Microsoft Teams quickly becomes cluttered and unusable, making it harder for strata managers to find scheme information, collaborate effectively, and protect sensitive owner and tenant data. This page explains how to structure Teams so it supports day‑to‑day operations, compliance, and growth across a multi‑scheme portfolio.
Strata companies manage dozens or hundreds of schemes, each with its own correspondence, maintenance issues, and stakeholders, and each requiring clear, auditable records. When every team member creates their own Teams and channels, information becomes fragmented, permissions are inconsistent, and critical communications about owners, tenants, and committees get lost in the noise. Without structure, Teams becomes unusable just when you need it most.
As teams grow and schemes change hands, new Teams and channels are created ad‑hoc, leading to duplicate spaces and inconsistent naming. Strata managers then waste time searching for the right place to discuss levy issues, maintenance requests, or AGM preparations.
Without governance, team membership and channel access are set manually and inconsistently, so some staff can see all schemes while others cannot access the ones they manage. This creates both operational friction and privacy risk when owner or tenant information is shared too broadly.
Strata managers must retain records for each scheme and be able to retrieve them for disputes, audits, or scheme handovers. A chaotic Teams environment makes it difficult to demonstrate what was communicated, when, and by whom, increasing legal and reputational risk.
Microsolve designs a Teams governance framework that defines when to create teams versus channels, who can create them, and how files are organised so that every scheme has a clear, consistent home for its communications and documents. This might include a team per region or portfolio, with channels per scheme, or a standard pattern that aligns with your management software and operating model. The goal is to make Teams easy to use, easy to govern, and easy to audit.
Define a standard pattern such as one team per region or portfolio and one channel per scheme, with consistent naming conventions so staff can quickly find the right place for scheme discussions and files.
Limit who can create new teams and channels, and provide simple request forms or templates so new schemes are onboarded consistently without creating duplicate or unnecessary spaces.
Organise files in predictable locations, such as a dedicated channel or SharePoint site per scheme, with clear folder structures for correspondence, maintenance, financials, and committee materials.
Assign team membership and channel access based on role and portfolio so strata managers, assistants, and support staff see only the schemes they are responsible for, reducing privacy risk and information overload.
Align Teams retention policies with your strata record‑keeping obligations so scheme communications are retained for the required period and disposed of appropriately when no longer needed.
Microsolve designs and configure the environment around the way your strata company actually works across schemes, portfolios, and regions. It's not a case of "turning on Teams". The starting point is understanding your current operating model, compliance obligations, and pain points, then building a Teams structure that reduces clutter, improves collaboration, and supports audit and dispute resolution.
We review your existing Teams, channels, and file structures, and speak with strata managers and support staff to understand where information gets lost and where permissions cause problems. This informs a governance model that fits your portfolio and operating style.
Microsolve designs the Teams architecture, including team patterns, channel standards, naming conventions, and permission models, and maps these to your scheme management workflows and compliance requirements. We also define retention and disposal rules that align with strata record‑keeping obligations.
We implement the new structure, migrate or reorganise existing content where appropriate, and provide simple guides and training so staff understand where to post, how to share files, and how to find scheme information quickly.
After go‑live, Microsolve provides ongoing monitoring, user support, and periodic reviews so the Teams environment remains aligned with portfolio changes, new compliance expectations, and staff feedback.
We recommend starting with a hands-on review with Microsolve to get an understanding of your current set up before setting out a clear and practical guide of your options, risks, and next steps.
A common approach is to create one team per region or portfolio and use channels per scheme, with consistent naming and file locations so staff can quickly find the right place for scheme communications. Microsolve designs this pattern around your operating model and portfolio structure.
In most strata companies, team and channel creation is limited to a small group of administrators or managers, with simple request forms or templates for new schemes or projects. This prevents uncontrolled sprawl while keeping the process practical for busy teams.
Microsolve configures role‑based access so staff only see the schemes and channels they are responsible for, and applies sensitivity labels and sharing policies to protect sensitive documents and conversations. This reduces the risk of accidental over‑sharing across schemes.
Yes, when Teams is structured and governed correctly, it can provide a clear, searchable record of scheme communications, decisions, and documents that supports disputes, audits, and scheme handovers. Retention policies and consistent file organisation are key to making this work in practice.
Microsolve defines standard onboarding and offboarding processes so new schemes are created consistently and departing schemes are archived or handed over with the right records intact. This keeps your Teams environment aligned with your current portfolio.
