Skip to main content

Approvals workflow

This workflow outlines how approvals are created, reviewed, and completed in Hyperproof.

  1. Configure approvals on Hyperproof objects, including tasks, repeating tasks, Risk assessments and evaluations, and policies. See Creating a task with an approval, Creating a repeating task with an approval, Initiating a policy approval, and Creating a risk assessment.

  2. Trigger the approval process by setting a task or risk evaluation to Submitted or moving a policy to the Approval stage. Users assigned to approve tasks, risk evaluations, or policies receive a notification when it's time to review them. See Policy approvals, and Risk evaluation approvals.

  3. Review the proof attached to the task, the risk evaluation updates, or the policy document. See Completing an approval, Completing a risk evaluation approval, and Approving or requesting a change to a policy.

  4. If a task, risk evaluation, or policy hasn't been approved and the approver has requested changes, the assignee must make the updates and resubmit it for approval. See Managing a task approval marked Change requested, Managing a risk evaluation approval marked Change requested, and Managing a policy approval marked Change requested.

  5. When an object is approved, Hyperproof's response varies by object:

    • Tasks require no further action.

    • Risk evaluation status is updated to Approved. If the approval option Automatically update risk is on, the risk is updated with the changes entered in the evaluation. If it is off, the assignee must manually trigger the risk update. See Updating a risk with approved evaluation data.

    • Policy approvals are closed, but policies must be moved to the Effective stage manually. See Managing a policy approval marked Approved.

  6. Review approval history as needed on the Work items > Approvals tab. See Viewing closed or canceled approvals.

Did this answer your question?