Publish a policy and check the reader outcome
Roll out the correct policy version and check access, acknowledgement and practical understanding as separate outcomes.
Part of Publish a policy readers can use
Publish a policy and check the reader outcome
Roll out the correct policy version and check access, acknowledgement and practical understanding as separate outcomes.
Before you start: Start with the intended existing policy Draft, or its already-Published version for the reader checks. Have the approved complete text, version, effective date, audience and acknowledgement requirement. Confirm the supporting files and the intended readers’ access before publication.
Steps
1. Open People → Policies → Company Policies and find the exact title and version. If already Published, skip editing and publication steps 2–4 and continue with the reader check in step 5.
2. For the intended existing Draft, use the row menu → Edit. Check Assign To, actual selected recipients, effective date, Require acknowledgement and Link from Files. Resolve the correct file edition and audience rather than using a similarly named document.
3. Put the complete approved text in Policy Content, preserving the intended settings. Review the beginning, middle and end, select Save once, then reopen the saved draft to compare its body and settings.
4. When ready for the agreed audience, choose the exact draft’s Publish action. Check the title and version in the confirmation, confirm once and reopen the Published record. Do not repeat publication on the retained published version.
5. The intended reader opens Pulse → Policies, checks Needs attention or All policies as appropriate and uses View on the correct version. They read the complete body and relevant supporting content. An owner’s access is not proof that another reader can open it.
6. If acknowledgement is required, the reader completes their own available acknowledgement action after reading. Review People → Policies → Acknowledgements for the exact policy/version and its targeted and pending receipts. Do not submit a receipt on someone else’s behalf.
7. When the policy teaches a practical procedure, ask the reader to apply it to a relevant work example. Check the actual result against the stated instruction and give a specific correction if needed. Keep this understanding check separate from the receipt count.
8. Follow up the real gap: inaccessible content with the content owner, an outstanding receipt with the intended reader, or a misunderstood step with focused explanation and another practice attempt. Do not broaden the audience or alter receipt settings merely to make a badge disappear.
Expected result
The intended policy version is available, required receipts can be reviewed and any practical learning gap has a specific next action.
Common pitfalls
- Two policy receipts can belong to one person. Check the unit behind the count before reporting completion.
- An old acknowledgement does not prove receipt of a newer edition, and a complete receipt percentage does not prove understanding.
- A linked filename is not the same as readable content. Files permissions still apply.
Continue learning
In this series: People operations — guide 6 of 6.
Turn what you learned into the way the team works.
Mark this lesson complete once the workflow exists in your workspace—not simply when you reach the bottom.