Every policy approved before it goes out
Send finished policies to the person who signs them off: a manager, the board, a policy owner or external legal counsel. They open each document, approve or reject it, and the decision is recorded against the exact version you sent.
The approver needs no account, only the link in one email and a one-time code. Until a policy is approved, it cannot be made active or sent to anyone.
Try a look:
A status for every step
With approvals on, a policy moves from Draft to Ready for approval, then In approval while the approver looks at it, and Active once it is approved. A rejected policy is Not approved until you fix it and send it again. A policy in any of these statuses is never sent in a cycle.
Send policies for approval
One request, one approver, as many policies as you need. The dialog walks you through it in three steps, and the screens below are the app's own.
- 1
Mark the policies ready
When a policy is done, set it to Ready for approval on the policy page, or mark several at once with Bulk edit.
- 2
Pick the policies
Open the Approval requests tab and choose New approval request. Every policy shows its version and where the document is, so you can check what goes out.
- 3
Choose one approver
Someone in your recipient directory, or anyone else by name and email: a board member, a manager, external legal counsel. It cannot be you.
- 4
Review and send
See the email and the page the approver will get, then send. The policies move to In approval and are locked until the approver decides.
What the approver gets
One email in your organization's branding, a one-time code, and a page with each policy to open and decide on. The page is in your logo and color, the same as the confirmation page your employees use. Switch the look at the top of the page to see it change.
A record of every decision
The Approval requests tab on the Policies page lists every request, Open, Completed or Cancelled. Open one to see who it went to, what was sent and what was decided. While it is open you can resend the invitation, copy the approver's link, or cancel the request.
Built so the approval holds up later
An approval is only worth something if it is clear what was approved, by whom and when.
The approver decides on what you sent
The version, the document and its details are kept with the request when you send it. A policy that changes afterwards is taken out of the request and goes back to Draft, so nobody approves one text and publishes another.
No account for the approver
One email with a link. The approver gets a one-time code at the address the request went to, and sees the policies only after typing it in. The email itself names no policies, so a forwarded email reveals nothing.
One decision per policy
Each policy is approved or rejected on its own, and a reason is required to reject. Every decision is saved at once with the time and the verified email, and cannot be changed afterwards.
Approving sends nothing
An approved policy becomes Active in Policy Confirm. It reaches employees only when you add it to a cycle, so the approver signs off the content and you decide the timing.
You hear back in the app
A notification in Policy Confirm when a policy is not approved, and when every policy in the request has been decided. A rejected policy gets the reason under its Comments.
The history stays
Each request keeps who approved which version and when. The approval history on a policy is kept even if you turn approvals off later.
Approval is the step before distribution. Cycles, deadlines, reminders and the confirmation record are described under How it works.
Frequently asked questions
What are policy approvals in Policy Confirm?
An optional step before a policy goes live. With approvals on, a policy can only be made active after an approver has approved its current version. You send the policies to one approver, they review each document and approve or reject it, and the decision is recorded with the version, the time and their verified email.
Does the approver need a Policy Confirm account?
No. The approver gets one email with a link, and a one-time code at the email address the request was sent to. After the code they see the policies, open each document and decide. They can stop and come back later with the same link to finish.
Who can be the approver?
Anyone with an email address: a person in your recipient directory, or someone else by name and email, such as a board member or external legal counsel. A request has one approver, and you cannot approve your own request.
What happens when a policy is rejected?
The policy becomes Not approved, and the approver's reason is added to the policy's Comments, marked as an approval rejection. You get a notification in Policy Confirm. Fix the policy, mark it Ready for approval again and send a new request.
Does an approved policy go out to employees straight away?
No. Approving makes the policy Active in Policy Confirm and sends nothing to employees. You decide when it goes out, by adding it to a cycle.
Does a new version of an active policy need approval?
Yes, with approvals on. Move the policy to Draft, add the new version under a new version number and send it for approval. The approved version number always stays with the approved document.
What happens to policies that are already active?
They stay active. From then on, a policy that is not active needs an approval before it can be made active, and a new version of an active policy needs one too. A tab called Approval requests on the Policies page lists every request.
Get every policy signed off before it goes out
Free for up to 10 recipients. Mark your policies ready and send your first request in a few minutes.