A practical guide for Company Admins
Employee Policy Rollout Checklist
A policy rollout is more than sending a file. Your team needs the right document, a clear next step, and a way to ask questions. Use this checklist to plan the work, then use AcknowledgePoint to assign the published version and track who has acknowledged it.
Updated
Before you send: six things to check
Review this list with the people helping you. If an item is not ready, agree on who will finish it before the assignment goes out.
- The policy owner has reviewed the wording and confirmed the version to publish.
- The employee list, email addresses, departments, and locations are correct.
- Recipients can sign in, and someone is available to help with access.
- The assignment has the intended document, recipients, and due date.
- A named person will review pending and overdue work.
- The team knows where to find completed acknowledgement records.
1. Prepare one clear version
Start with the document itself. Give it a title employees will recognize, explain who it applies to, and describe what people need to do. Ask the person responsible for the policy to review it through your company's usual approval process before you publish it. A template is a starting point; check its wording against your own workplace.
- Confirm the document owner, title, type, and category.
- Remove unfinished notes and company-specific placeholders.
- Check the published version before creating an assignment. Draft documents are not ready to assign.
- For a revision, write a short explanation of what changed so employees know what deserves attention.
Help guide: Understand draft, published, and versioned content →
2. Check who needs the policy
Choose the audience based on the work people do. A company-wide handbook and a procedure for one location may need different recipient lists. Check the employee records before relying on department or location filters. A correct filter cannot fix an employee who is listed in the wrong department.
- Review employee names, work email addresses, departments, and locations.
- Include Company Admins when they also need to acknowledge the policy.
- Invite new users and check their access status. Resend an existing invitation if they need the setup link again.
- Agree on who will handle access questions and how to follow up with people who are away.
3. Review the assignment before sending
In Company Admin, open Assignments and choose Add Assignment. Select the published document, narrow the audience, and review the actual recipients. Set a due date that gives people time to read the document and ask questions. Explain separately when the policy takes effect if that date is different from the acknowledgement deadline.
- Compare the selected title and version with the document you intended to send.
- Check the recipient count and names, not just the audience filters.
- Review the Assigned column. If someone already has an assignment, check its version and status before deciding on the next action.
- Confirm the due date, then check Current Assignments after saving to make sure the expected records appear.
4. Give employees a simple next step
Tell employees why they received the policy, when to finish reviewing it, and who can answer questions about its meaning. In AcknowledgePoint, employees open My Documents, select their assigned document, read the displayed version, and complete the acknowledgement. Company Admins who receive assignments use My Acknowledgements.
- Explain that an invitation is for account setup. An assignment email means there is a document to review; it does not require another account.
- Ask employees to check the document title and version before acknowledging it.
- Provide a contact for policy questions and a separate path for sign-in or page errors.
- Plan any practical training separately. An acknowledgement records the review action; it does not show that a person can perform a task.
5. Follow up on the work that is still open
Choose a person to review progress before and after the due date. Use Current Assignments and the dashboard to find pending and overdue work for the policy you sent. Keep the document and audience filters consistent when comparing counts. A company-wide total can include assignments from other rollouts.
- Check whether an open item is an access problem, a missing link, or an unanswered policy question.
- Resend the assignment notification when someone needs the review link again. Avoid creating a duplicate assignment just to replace an email.
- Use an invitation resend for unfinished account setup; use an assignment notification for an existing document assignment.
- Check acknowledgement status after the employee finishes. Receiving an email alone does not mark the document acknowledged.
6. Keep the record and plan for changes
Use Ack Details to review a person's completed acknowledgements and download their history when needed. Check the person, document, version, and dates before sharing the record. Keep outstanding work separate from completed history so an unfinished assignment is not lost when the rollout is summarized.
- Confirm that the history belongs to the intended employee or Company Admin.
- Store downloaded records in your company's approved location and share them only with people who need them.
- Keep a follow-up list for unresolved assignments and a plan for new employees who join later.
- When the policy changes, review the published version and existing assignments again. An earlier acknowledgement does not mean someone has reviewed the new wording.
Putting the checklist to work
Example: a procedure for one warehouse
Your operations lead updates a receiving procedure. After the company reviews the wording, the administrator publishes the intended version and checks the warehouse employee list. The administrator reviews the selected recipients, sets a due date, and creates the assignment.
One employee has not finished account setup, so the administrator resends that person's invitation. Another has an active account but needs the document link again, so the administrator resends the assignment notification. The operations lead answers questions about the new steps. The administrator then checks completion and keeps any unresolved items on the follow-up list.
What should a rollout summary tell you?
You should be able to identify the document version, the intended audience, the due date, who has acknowledged it, and what still needs attention. Use those details to explain progress and hand off follow-up work. Keep the summary focused on the rollout instead of copying every dashboard number.
If you cannot explain a count, check the filters and individual assignments before sending another notification. A clear record starts with a clear question: which people still need to review this version?