Objective:

• Reject a pending document
• Edit a pending document

Environment:

• PolicyStat
• PolicyStat Editor

Additional Information:

The Approval Workflow is a key concept in PolicyStat, and the role of Approvers are essential to the process. The interactive tutorial demonstrates how a document is rejected either with or without edits, and how the Approval Workflow restarts.

This article and tutorial addresses how to reject documents.

• For more about our communication and collaboration feature to discuss potential changes with others, see this article.
• For more about approving a document during an Approval Workflow please see this article.
• For more on the Administrative Override option available to Site Administrators, please view this article.

Reject/Edit a Pending Document (01:40)

Procedure:

Steps to Reject or Edit a Pending Document

1. Open the pending document
   
   - From the PolicyStat Home tab
   - Click the document's title if visible(1), or
   - Click the report header (2) if the title is not visible, or
   - Open using the link in the notification email
   
   
   
   
   Sample Notification email
   
   
2. Review the policy content. If you are uncertain about changes and would like to discuss with others, consider using the PolicyStat comments and collaboration feature to discuss with others. For more, see this article.
3. If you would prefer to reject or make edits the document, click the Edit link on the blue toolbar. This will create a new draft version of the document.
   
   
4. Either modify the content, or simply restart the Approval Workflow. If restarting the workflow without changing the content, provide a detailed description (3) as to why the current version is being rejected.
   
   

   NOTE: Any edits and/or comments will become part of the historical record of this version of the policy, and are visible to any user with editing/approving rights on the policy.

5. Click Start Approval Process (4).
   
   Restarting the Workflow sends it back to the very first Approver in the workflow.
   
   

This article applies to the following user roles: