Free Notion Template for HR Policy Library 2026: Version-Controlled, Audit-Ready

Your HR policy library is scattered across a shared drive no one maintains, a SharePoint folder with three versions of the same document, and a spreadsheet that was last touched in 2024. When an employee asks which disciplinary procedure is current, you are checking file metadata instead of running your department. This template gives you one database where every policy has a version number, an owner, a next-review date, and a live status — so when your CEO or an auditor asks, you open one filtered view and answer in under a minute. If you are looking for a general HR dashboard or an onboarding tracker, this is not that.

What this template does

It replaces the manual process of hunting across drives to confirm which version of a policy is active, who approved it, and when it expires. On day one you open the template and see a pre-built table with 14 field columns and three filtered views — Active Policies, Due for Review, and Archived. After one week of data entry you have a single source of truth that surfaces every policy whose review date falls within the next 30 days, so your Monday morning check takes four minutes instead of forty. The database is sized to handle a typical SME or mid-market HR function: up to 80 discrete policies across six to eight policy categories without any Notion performance issues.

Template structure

Policy Library (Main Database)

• Policy Name (Title): The exact official name of the document. Example: Disciplinary and Grievance Procedure v3.2. If this field is blank, the record is invisible in filtered views and will not appear in the Due for Review export.

• Policy Category (Select): Employment Contracts / Health & Safety / Data & Privacy / Performance & Conduct / Leave & Absence / Equality & Diversity / Compensation & Benefits / IT & Security. Assign this on creation. It drives the Category grouped view used during annual audits. A miscategorised policy will surface in the wrong audit grouping.

• Status (Status): Draft / In Review / Approved / Live / Scheduled for Archive / Archived. Change to In Review the moment you send the document to a legal reviewer or senior stakeholder — not after they respond. Change to Live only when the signed approval memo exists in the Approval Document field. Leaving a policy at Approved when it is already distributed is the most common cause of audit discrepancies in this database.

• Version Number (Text): Semantic version string. Example: 3.2. Increment the minor number (3.1 → 3.2) for wording clarifications. Increment the major number (3.0 → 4.0) for structural or legal changes. Never overwrite a version number — archive the old record and create a new one. If this field is blank, the Audit Export view flags the record in red via conditional formatting.

• Policy Owner (Person): The named HR team member or department head accountable for keeping this policy current. Example: Sarah Okonkwo. This is not the author — it is the person who will receive the automated Notion reminder when the review date is approaching. If no owner is assigned, reminders do not fire and the policy will silently expire.

• Effective Date (Date): The date the current version became active across the organisation. Example: 2025-11-01. Used in the formula that calculates Days Since Last Review. Leave it blank only for policies still in Draft status.

• Next Review Date (Date): The calendar date by which the policy must be reviewed and reconfirmed or updated. Example: 2026-10-31. This field powers the Due for Review filtered view, which shows every policy with a Next Review Date within the next 30 days. If this field is empty, the policy never appears in that view and will be missed.

• Review Frequency (Select): 6 months / 12 months / 24 months / Triggered by legislation. Use Triggered by legislation for any policy directly governed by statute (e.g., data retention, right-to-work checks) so it does not get a fixed cycle. Assign this on creation so when you archive a record and create the next version, you can copy this value without making a judgment call under time pressure.

• Days Since Last Review (Formula): Auto-calculated. Formula: dateBetween(now(), prop("Effective Date"), "days"). Read-only. Example output: 247. Any value above 365 highlights in the Audit Export view. Do not edit this field manually — it recalculates every time you open the page.

• Linked Policy Document (URL): Direct link to the master document in your HRIS, SharePoint, or Google Drive. Example: https://drive.google.com/file/d/1aBcDefGh. This is the single source of truth URL you share with employees. If the document moves and this link is not updated, staff will reach a broken link and HR will field avoidable queries.

• Approval Document (Files & Media): Upload the signed approval memo, board minute, or email chain confirming sign-off. Example: a PDF named Disciplinary_v3.2_Approval_2025-10-28.pdf. Do not change Status to Live until this file is uploaded. During an employment tribunal or regulatory audit, this attachment is your evidence that due process was followed.

• Legislation Reference (Text): The specific Act, Regulation, or statutory guidance the policy must comply with. Example: Equality Act 2010, s.26. One reference per line if multiple apply. Leaving this blank is acceptable for internal operational policies but is a red flag for any policy under Data & Privacy or Health & Safety.

• Applies To (Multi-select): All employees / Managers only / UK only / Remote workers / Fixed-term contracts / Agency workers. Example: a Flexible Working policy might be All employees and UK only. This field drives the Scope filter used when answering employee queries about whether a policy applies to them.

• Notes (Text): Free text for anything that does not fit elsewhere. Example: Pending legal review of IR35 changes — do not promote to staff until cleared. This is the only unstructured field in the database. Do not use it to track version history — that belongs in a new record.

Views included

• All Policies (Default Table): Every record, sorted by Next Review Date ascending. Your starting point for any policy search.
• Due for Review (Filtered): Shows only records where Next Review Date is within the next 30 days and Status is Live or Approved. This is the view you screenshot and paste into your weekly HR team meeting agenda.
• Audit Export (Gallery or Table): Filters out Archived and Draft records. Shows Policy Name, Version Number, Status, Policy Owner, Effective Date, and Approval Document. Sorted by Category. Export as PDF or share the Notion link with your auditor.
• Archived (Filtered): Status is Archived. Sorted by Effective Date descending. Gives you a complete version history without cluttering the active views.

How to use it week by week

1. Day one — import your existing policies. Open the All Policies view. Create one record per policy. Copy the official name from your current file, set the Status to whatever it actually is today (be honest — many will be Draft or unknown), and paste the document link into Linked Policy Document. Do not fill in every field on day one. Priority order: Policy Name, Status, Policy Owner, Next Review Date. The rest can follow.

2. Every Monday morning — run the Due for Review check. Open the Due for Review filtered view. Any policy appearing here needs action this week. For each one: confirm with the Policy Owner that a review is underway, update the Status from Live to In Review, and add a note in the Notes field with the target completion date. Screenshot this view and paste it into your Monday HR team standup notes.

3. **When