One Intranet for Six Content Worlds: How a Large Care Organisation Finally Got Its Internal Information Under Control

Board governance papers. HR policies. IT support. Training resources. Community news. Staff forms. They all existed. None of them lived in the same place, and nobody without institutional knowledge could reliably find any of it.

This is a use case about a large community care and social services organisation, one of the bigger players in its region, delivering support across children and families, older people, specialist intervention, and communities facing disadvantage. It runs a network of centres and programmes staffed by care professionals, social workers, therapists, educators, and the corporate teams who hold it all together.

The organisation had a workforce problem that is surprisingly common in the sector: a significant proportion of staff spend their days with service users rather than at a desk. For those people, a complicated internal system is not a minor inconvenience, it is a reason not to use it at all. And the system they had was, in practice, a collection of disconnected shared drives, email chains, and separately-maintained folders that had each grown up according to their own logic.

Nothing was dramatically wrong. It was just that nothing was easy, and easy matters a great deal when the people trying to find information have other things on their mind.

The Problem Had Several Layers

The surface problem, information spread across too many places, was the visible symptom. Underneath it were a few specific things that made the situation harder to resolve than a simple migration.

First, the content types were genuinely different in what they required. Board and committee papers needed restricted access, only the right people should see governance material. HR content needed to reach everyone but required its own structure. IT support material needed to be findable in a hurry, not browsed through a library of documentation. Training resources needed to be accessible without going through a coordinator. These are not the same requirements, and a system that suits one does not automatically suit the others.

Second, the staff directory and organisational chart were already maintained in the corporate directory. Duplicating that information into an intranet would mean maintaining two copies, and two copies means one of them is always out of date. For an organisation of this size with staff moving between roles and programmes regularly, a stale directory is not just unhelpful, it is actively misleading.

Third, and the client was direct about this, they did not want to depend on a development partner for routine content changes. Publishing a notice, updating a banner, adding a quick link: these are things the organisation's own communications and HR teams need to be able to do themselves, immediately, without raising a ticket or waiting for a developer's schedule to free up.

And fourth: there was no option to go dark while the platform was built. Existing content was in daily use by frontline staff. Any transition had to happen without disrupting access to the information people were relying on.

"We needed somewhere that worked equally well for our board, our corporate teams and our frontline staff, and we needed to be able to keep it current ourselves. Delivering it in phases meant our people were never left without what they needed, and we now manage the day-to-day content without having to ask anyone."

The Approach: Three Phases, No Disruption

The project ran over twelve months across three delivery phases. Rather than building everything and launching it all at once, which would have required a hard cutover and a period where staff had to find their way around an entirely new system, the approach delivered one complete, usable area at a time while existing systems continued running alongside.

Each phase gave staff something real to use. Each phase taught the team something about how people were actually navigating the portal. And by the time the third phase completed, the transition was largely done without anyone having experienced it as a disruption.

• 3 Delivery phases completed with no disruption to live content throughout
• 6 Major content areas unified, governance, HR, news, IT, community and learning
• 4 Permission groups configured to match the sensitivity of each content area

What Was Built, Area by Area

The home page is the front door: announcements, admin-controlled banners, an events calendar, a community feed, and quick links. Building these features around specific organisational needs often requires custom application development. . It is designed for people who visit briefly and need to leave with something, not for browsing. That distinction shaped the navigation throughout. Frontline staff who spend five minutes a week on the intranet need a different experience from the HR manager who lives in it.

Governance Hub

Board papers, committee documentation, and governance policies in dedicated libraries with restricted access. Material is organised and controlled rather than circulating by email, which is both more convenient and more accountable for an organisation answerable to a board and to funders.

HR Area

HR news, quick links, and a staff directory and organisational chart powered directly by Azure Active Directory, with Azure integration services helping connect employee information to the intranet.  When someone joins, moves, or leaves, the intranet reflects it automatically, no page update, no maintenance task, no stale entries.

News Hub

A newsroom for full articles and a bulletin format for short updates, with featured items promoted to the home page. Two formats gave the communications team the right tool for the job, brief notices no longer had to be dressed up as articles to be published.

IT Self-Service Portal

Help desk, enterprise IT, cybersecurity, data, and project management, each with FAQs, quick links and a document library. Structured around the questions the IT team was actually receiving, so staff can resolve common issues themselves without raising a ticket.

Community Section

The meeting point for HR, corporate communications, and early intervention services, the areas where internal operations and frontline work connect most directly.

Learning Hub

Learning roadmap, leadership development, academic sponsorship, and a self-service resource centre. Staff find and pursue development opportunities themselves, without going through a coordinator. For an organisation that invests seriously in its people, removing the friction between intent and access matters.

The Practical Tools That Earned Their Place

Two additional features were built into the platform that sound minor but turned out to be among the most appreciated outcomes.

A meeting room booking system synced with individual Outlook calendars, so a booking made in the intranet appears in the right diaries automatically. This type of integration can be supported through Microsoft 365 solutions that connect everyday business tools. Double-bookings, and the chasing that followed them, stopped.

A staff suggestion scheme gave people a direct route to management that did not previously exist. In a large, distributed organisation where frontline staff are often physically and operationally separated from central teams, having a structured channel for upward communication is not a trivial thing.

The Self-Service Requirement, Treated as Non-Negotiable

The requirement that shaped more of the build than any other was this: the client's own teams had to be able to manage routine content themselves.

Every banner and quick link across every page is driven by SharePoint lists maintained by the client's administrators. Adding a link, updating a notice, changing a banner image, none of this requires a developer, a support ticket, or waiting. It requires logging in and editing a list.

This sounds like a technical detail. For a communications or HR team trying to publish time-sensitive information, it is the difference between an intranet that is current and useful versus one that always lags a few weeks behind what it should say.

What Actually Changed

For frontline staff, the group least likely to persevere with a confusing system, having a single, predictable starting point made the difference between using the intranet and ignoring it. That is not a small outcome. An intranet that frontline care workers actually use is a different proposition from one that corporate teams navigate while everyone else works around it.

The staff directory and organisational chart have been quietly significant. Because they draw directly from the corporate directory, they are always current. In an organisation of this size and spread, being able to find the right colleague reliably saves a great deal of collective time, and removes the low-level uncertainty that comes from not knowing whether the contact information you have is still accurate.

Governance material is now handled as it should be. Board and committee documentation sits in properly controlled libraries, accessible only to those entitled to see it, rather than circulating by email. That is an improvement in both convenience and accountability.

The IT self-service portal absorbed a meaningful share of routine support demand. Staff resolving familiar problems themselves means the IT team spends more time on the work that genuinely needs them, not on questions that a well-structured FAQ section answers perfectly well.

The Outcome the Client Values Most

Independence. Because the content administrators control banners and quick links through SharePoint lists they manage themselves, the communications and HR teams change content when it needs changing, immediately and without cost. The intranet became something the organisation runs rather than something it pays to have changed, which is exactly what was asked for at the start.

Conclusion

The lesson this project reinforces is one that comes up consistently in large-scale intranet work: the platform decision is the smaller part of the problem. The harder parts are phasing the delivery so existing work is never disrupted, designing for the people who spend the least time at a computer rather than the people who spend the most, and building a self-service layer that gives the organisation genuine day-to-day control. Get those right and the technology takes care of itself.

Building an Intranet for a Large, Diverse Organisation?

Dotsquares has delivered SharePoint Online intranets for community care organisations, non-profits, and large distributed workforces, phased, self-managed, and designed around how people actually work. Talk to our team about your project.

Talk to Our Team