How it works
From a blank page to a reading record, in eight steps.
The life of a policy in Policy Core, in the order it happens.
Create the policy
Give it a title, an optional reference, a category, a review period and an owner. Start empty, with common headings, or from a copy of another policy.
Build and write it
Add sections, subsections, paragraphs and items, then write each part in the editor. Attach the forms and appendices that belong with it, written here or uploaded.
(opens a larger view)The outline of a draft. (Sample data. Select the picture to enlarge it.) Choose who has to read it
Everyone, teams, job titles or named people. You see how many people that is, and who, before you publish.
Publish
The draft tells you what is missing. When it is ready, publishing says what will happen: the version number, how many people, and whether anyone must read again. People are asked to read it straight away.
People read and confirm
Staff open the policy from their list, read it, answer any questions, and confirm. A wrong answer keeps the others and shows the writer's hint.
(opens a larger view)The confirm panel for staff. (Sample data. Select the picture to enlarge it.) Follow up
See who has read the version in force and who has not, send a reminder if you choose to, record a reading made on paper, and print evidence.
Change it when you need to
Start a new version. It begins as a copy only managers can see, and the published one stays in force until you publish the new one. You decide whether everyone must read it again.
Review it on time
Each policy has a review date. Managers see what is due and can mark a policy reviewed with no change, which is recorded.
Try the steps yourself.
The demonstration has invented people and policies, so you can write, publish and read without risk.