Policies

The group's policies in one register: what is missing against the catalogue, how good each one is (a grade from A to D), what the law has changed since it was written, and who has been issued and acknowledged it. SharePoint is the master copy and the nightly autopilot reads it; this page is where a person reviews what the autopilot proposes, accepts or rejects a redraft, and publishes a version to staff. The Overview board leads with what to do next; Register, Coverage, Review mode and Law changes are one click away under Views.

You enter

A new policy: drafted from the catalogue's brief with + New policy, or created for tonight's autopilot to draft.
The decisions a redraft raises (Review mode, worst first): accept or reject each proposal, the company facts the draft could not find, and the policy's owner.
Publish — each ready redraft becomes its next version and goes to its audience to read and acknowledge on their portal. Nothing reaches staff until a person publishes, unless your account's hold window lets the autopilot issue it.
Not for us, on a catalogue policy the group does not need.

Saral fills in

The register from the SharePoint folder: every file listed, its text read, its subject and category recognised, a redraft written from the original and graded against the benchmark.
Coverage: which policies the catalogue, the law and the schemes you hold expect, and which are missing, thin or weak but asked for.
Law changes: the dated changes each policy must reflect, from the benchmark's checks and the law feed.
Who has acknowledged each published version, and a weekly chase of whoever has not.

It produces

Published policy versions typeset on the letterhead, read and acknowledged on /me/policies, and appended to the accreditation evidence pack.
The Overview, Register and Coverage as Preview, PDF or Excel; the activity log of everything the autopilot did, with Stop and Undo.

What this page is for

A policy set is only worth having if it is complete, current and acknowledged — and most groups cannot say which of theirs are any of those. This page answers all three from evidence: coverage against the catalogue and the schemes you hold, a grade for each policy from a read of its text, the dated law changes it has not caught up with, and the acknowledgement register for every published version. The person's job is to decide, not to draft: accept or reject what the autopilot proposes, answer the questions it could not, and publish. A policy's status is never a tick box; missing means no document covers it, weak means the grade says so, and acknowledged means a named person did so on a dated version.

SharePoint is the master copy

The policies folder on SharePoint is read every night, and on page open when the last listing is over an hour old. Each file becomes a row on the register, its text is read, and from that text a redraft is written in plain, benchmark-shaped language and graded. A file changed in SharePoint is noticed, and Review N changes runs the chain again — redraft, grade, proposal — without touching the published version. A policy edited in both places waits for a person to choose. Open in SharePoint sits on every document, and the folder itself is set once on the settings tab.

Grade, improve, publish

A grade from A to D says how far a policy is from the benchmark for its subject; Improve writes a proposal with the company's own facts, two at a time in the background, and nothing changes until a person reviews and accepts it. Review mode is the quickest way through: one decision at a time, worst first. Publish is the headline act — each ready redraft becomes its next version, typeset on the letterhead, and goes to its audience to read and acknowledge on their portal; the row says Publishing until the server confirms. A policy missing from the set is drafted from the catalogue's brief, with the company facts, and waits for review; the legal ones can be queued for tonight's autopilot instead.

The autopilot and the hold window

The autopilot drafts, grades and redrafts overnight, and — within the hold window — issues the next version itself unless a person stops it. Everything it does is one dated line on the activity log, with Stop while it is still held and Undo after, so an automatic change is never silent. Needs you lists only what software cannot decide: a fact the records did not hold, a conflict between SharePoint and Saral, a failure. With the hold window off, every draft waits for a person. Monday reminders chase owners of a policy due for review and staff who have not acknowledged a version.

Where the settings live

HR → Settings → Policies owns the SharePoint folder, the Monday reminders, the hold window and the target grade — the Views menu shows them read-only and links there. Who is asked to acknowledge a policy follows its audience; a policy's owner is set on the policy, or in bulk with Correct owners by category. The Employee Handbook and Accreditations have their own pages and settings tabs; a policy published here is what the handbook's chapters link to and the evidence pack appends.

Next screen: /hr/handbook

Not what you needed? Inside Saral, ask Kuku (Alt+K) — if it cannot answer, “Ask a human” sends the question to Saral support with the chat attached.