Blog

Getting Policy Storage Right in SharePoint

In Brief

  • One Hub for all policies from all departments 
  • Separate working documents from published policies 
  • Use metadata consistently across your publish documents 
  • Archive superseded policies 

Prefer to speak to us about getting policy storage right in SharePoint? Book a short call with one of our team to get answers to your questions.

So often we hear the question: “What’s the best way to store our policies in SharePoint?” 

To answer that, we first need to think about our audiences: 

  • Policy authors – the people responsible for creating and maintaining policies 
  • End-users – the employees who consume policies in their day-to-day work 
  • Heads of Compliance / Quality – the roles ensuring policies are consistent, up to date, and fit for purpose 

Each audience has different needs, but they all depend on one thing: trusted information. 

With our audiences in mind, the next step is to focus on outcomes. Ultimately, the goal is simple: reduce organisational risk through policy compliance. 

Too often, policies are treated as a tick-box exercise for ISO9001. That’s a low watermark. We should move beyond it and focus on the true value of compliance: guiding behaviour, setting standards, and building confidence, policy accessibility is a key part of that. 

SharePoint document libraries include a publishing function. Work in progress moves through minor versions (1.1, 1.2, etc) until it is published as a major version, such as 2.0. 

This works to an extent, but there are drawbacks: 

  • It’s difficult for those with full access to quickly see which version is viewable by end-users. 
  • Copilot or other AI agents may index the newest version available, meaning policy owners could get answers from unapproved drafts. 
  • Metadata stored at draft level may not be suitable for employees to see. 

Instead of relying on publishing within one library, take these steps: 

  • Create separate document libraries for your “Policy Masters” and your “Published Policies.”
  • Agree a workflow that keeps published policies up to date, whether manual or automated with Power Automate. 
  • Decide which metadata should be carried across during publishing, so employees only see what’s relevant. 

The starting point for many organisation is to have separate sites for each team, and the related policies stored in those sites. 

Don’t make employees guess whether an expenses policy sits with HR or Finance. Hunting around departments causes frustration and delays, the opposite of what policies are meant to achieve. 

Centralising policies into one repository removes this friction. It also reflects the reality that compliance and quality roles often span departments, so a single point of review is essential. 

Why we advise on a Centralised approach 

A central repository, read as a SharePoint site, does more than reduce confusion. It: 

  • Creates a single source of truth for employees and compliance teams 
  • Makes review and approval easier for cross-departmental roles 
  • Drives standardisation in formatting, metadata, and processes within SharePoint 

The result is a consistent experience for both end-users and administrators, and higher confidence that policies are accurate and up to date. 

For many policy authors, metadata feels like extra admin. It takes time to fill in, and without clear guidance it can seem unnecessary. That frustration often leads to metadata being skipped, which is exactly when findability starts to break down. 

When it comes to policies, metadata adds huge value. It: 

  • Makes policies easier to find through search, even when employees don’t know the exact title 
  • Helps filter results by type, audience, or subject area 
  • Enables pre-filtered search results, such as a department homepage showing all policies from the company handbook 

Considerations with SharePoint 

On the technical side, metadata is central to configuring a document library. Options include: 

  • A taxonomy in the centralised Term Store – ideal for structured, controlled values 
  • Enterprise Keywords – allowing flexible free-text tagging 
  • Choice fields or drop-downs – making metadata quick and consistent for authors 

Choosing the right approach ensures metadata is consistent, usable, and aligned to how your people actually search. Agree on which data can be appended to by policy authors, which are going to be more tightly managed. 

Few things damage trust in policies more than finding two documents that both look “current.” Employees end up second-guessing which one to use, or worse, following the wrong version altogether. 

This confusion often happens when old versions are saved in the same library with slightly different names, or when superseded documents are placed in a different library and accidentally picked up by employees. 

Why We Advise on Version Control  

A better approach is to use SharePoint’s built-in version history: 

  • For employees – it’s clear which is the current version, but they can also see previous versions and when they were published. That transparency builds confidence. 
  • For AI tools – only the current version should be indexed, ensuring responses are always based on approved content. 

We treat retired policies differently. Superseded documents should be moved into a dedicated archive library with limited access. This prevents confusion in the live repository while still providing a secure home for policies that may need occasional reference. 

Employees instinctively trust PDF as a final format. 

Word files often feel like work in progress and prompt unnecessary double-checking. 

Publishing in PDF reinforces confidence that the content is official and approved. With Policy Express, PDF conversion and publishing are automated — removing the manual step and ensuring employees always see the approved version in the right format. 

These best practices can be implemented out of the box in SharePoint, supported by manual processes. 

But processes that rely on people are always subject to variance. That’s why we built Policy Express — automating the administrative steps, providing a full audit trail, and giving employees complete confidence in the policies they use. 

Policy Express delivers all of this (and more) out of the box. Book a demo today to see it in action 

Your 3 Step Plan to your Trusted Policy Repository  

1. Review your current setup – identify where drafts, published policies, and retired policies are stored today.

2. Apply best practices – create a dedicated Policy Hub site in SharePoint. Within it, set up two document libraries: one for Masters and one for Published Policies. Apply permissions so regular end-users cannot access the Masters library, ensuring they only ever see approved, published versions.

3. Decide on automation – stick with manual processes in SharePoint, build your own workflows in Power Automate, or adopt Policy Express to automate workflows, maintain audit trails, and remove the admin burden. 

Author

Rupert Squires

Rupert Squires

Client Director

2 mins read

Ask how we can help you:

  • Implement a centralised, accessible policy library for your team.

  • Streamline approval and attestation processes for compliance.

  • Enable easy tracking, feedback, and timely reviews with Policy Express.

Questions? We reply within a working day.

Or Book a call to speak to an expert.

Pink Curly Arrow

View our other blog posts

Click through to see our other blog posts.

Managing Microsoft Office Templates in SharePoint

Managing Microsoft Office Templates in SharePoint

Utilising templates like Word Letterheads and PowerPoint Sales Proposals is essential for maintaining consistency in document creation. They help enforce branding guidelines, ensure legal compliance, and reduce friction for employees.

Approving Policies and Procedures in SharePoint

Approving Policies and Procedures in SharePoint

Within your organisation, a risk, a legal requirement or a standard has been identified, and it has been agreed that it should be addressed via a documented company policy. We can expand this approval requirement more broadly to Controlled Documents.

6 Strategies to Enhance Policy Awareness with SharePoint

6 Strategies to Enhance Policy Awareness with SharePoint

Policy awareness refers to the extent to which employees are informed about the existence and content of organisational policies and procedures.