Employee Handbook

The handbook every employee acknowledges, kept as one document and shown as chapters: each chapter against the benchmark (present, thin or missing), the law it must reflect, the policy it links to, and who has signed the current version. The autopilot drafts missing and out-of-date chapters from your company settings and issues the next version within its hold window; a person corrects it, and nothing more is required. Employees read and acknowledge it on their portal, and the gate decides what stays open until they do.

You enter

A chapter's wording, edited in place — or a benchmark chapter accepted from the AI draft, after you have read it.
The title, and the short note of what changed when a version is sent for acknowledgment.
Stop on a draft the autopilot is holding; Undo on a change it made; the facts a draft could not find in the records.

Saral fills in

The chapters, split from the saved text by its headings, and each benchmark chapter's status: present, thin or missing, with the reason and the law it has not caught up with.
The link from a chapter to the published policy it names, and a drift warning when that policy was republished after the handbook version.
Drafts for the missing, thin, out-of-date and drifted chapters, from the company's own settings and policies, each held for the hold window before it goes in.
Who has acknowledged the current version and who is still to chase.

It produces

A numbered version, as a PDF on the letterhead and as a booklet, sent to every employee to acknowledge on /me/handbook; the acknowledgement register as Preview, PDF or Excel.
The coverage checklist and the difference between any two issued versions.

What this page is for

An employee handbook is where the group's rules reach the people they bind, and it is only evidence if it is complete, current and acknowledged. This page keeps one handbook per account as a single document — so the PDF, the booklet, the portal and the version archive never disagree — and shows it as chapters so each can be measured against the benchmark, linked to the policy it summarises and drafted on its own. A chapter is present, thin or missing because the text says so; a version is acknowledged because a named employee did so on a date; the law is reflected because a dated check passed. None of it is a tick box.

Chapters, the benchmark and the law

The handbook is split into chapters by its numbered headings; add headings to split a single block. The benchmark is the set of chapters a UK construction employer's handbook is expected to carry, and each is matched to your chapters by the rules, with the AI asked only about the ones the rules could not place. A chapter that merely restates a published policy is better as a short summary with the policy's code in the text — the rail then links it and warns when the policy is republished after the handbook version, which is what Drifted from policy counts. Law to reflect is the dated changes the chapter must catch up with, from the benchmark's own checks and the accepted lines of the law feed.

The autopilot drafts, a person corrects

Every night the autopilot drafts the chapters that are missing, thin, out of date or drifted, from the company's settings and published policies, and holds each for the hold window — shown on the panel with the day it goes into the draft and the day the version issues, and a Stop. With the hold window off, every draft waits for a person. A draft whose blanks the records could not fill goes to Needs you instead. Everything the autopilot did is one dated line with Undo where the chapter can still be put back. The forms on this page exist for corrections and are never required.

Issuing a version and the gate

Send for acknowledgment issues the next numbered version with a short note of what changed; every employee is asked to read and acknowledge it on their portal, and the rail shows signed x of y with a Chase that emails only those still outstanding, the PDF attached. The acknowledgement gate decides what happens meanwhile: by default the rest of the portal locks 14 days after a version is issued until it is acknowledged, unless your account changed it to a different grace period or to reminders only. Check-in, attendance and timesheets always stay open. The first save stamps version 1 before anything is issued; issued means published, and nobody can have signed an unissued version.

Where the settings live

HR → Settings → Employee Handbook owns the autopilot (nightly drafting, the hold window, whether it issues by itself, the Monday chase) and the acknowledgement gate (hard gate or reminders only, and the grace days). The autopilot panel and the rail show those values read-only and link there. The policies a chapter links to are owned on Policies; who counts as an employee for the handbook follows the worker's type on their record.

Next screen: /hr/training

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.