Case study · Education · Dubai, UAE
ITSECOPS designed and built a SharePoint hub-site intranet for a multi-campus education group in Dubai — one front door for staff policies, campus news and governed documents, replacing shared-drive chaos.
The client
An education group in Dubai operating multiple campuses, with policies and operational documents scattered across drives, email and legacy portals.
The challenge
Staff could not reliably find the current version of anything. Each campus had evolved its own filing culture, and onboarding new teachers took weeks of “ask around”.
What we did
- Designed a hub-site architecture: a group-wide hub with campus sites and department sites associated underneath.
- Built a governed document centre — policies with version history, review dates and a single canonical URL each.
- Created news and announcement flows targeted by campus and role.
- Applied the group’s branding and navigation so the intranet reads as one organization, not seven silos.
- Trained site owners and set governance rules for who may create sites and how permissions are granted.
Results
- One intranet front door for every campus.
- Policy lookups measured in seconds; version confusion eliminated.
- New-staff onboarding materials consolidated into a single site.
FAQ
How long does a SharePoint intranet project take?
A well-scoped hub-site intranet ships in 6–10 weeks including governance and training. Content migration is usually the long pole.
SharePoint or a third-party intranet product?
If you already pay for Microsoft 365, SharePoint hub sites cover most intranet needs without another subscription. Third-party layers earn their cost mainly for advanced employee-experience features.
How do you stop the new intranet becoming chaos again?
Governance: controlled site creation, named site owners, review dates on policy documents and a quarterly cleanup rhythm. We set that up before handover.