assess.one – AI-powered business operations platform

Workflow Template

Risk Assessment Workflow

Captures business risks via an intake form, tracks them through assessment, treatment approval (for High/Extreme ratings), treatment execution, monitoring, and closure, with status tracking and notifications throughout.

This workflow is designed for risk, compliance, and operations teams who need a consistent way to capture, assess, and resolve business risks without relying on spreadsheets or email chains. It automates the full lifecycle from intake through assessment, treatment approval for High and Extreme rated risks, treatment execution, monitoring, and closure, with status updates and notifications at each stage. The result is a single traceable record per risk, with a reference number and timeline, that shows exactly where each risk stands and who is responsible for the next step.

Business Outcomes

  • Faster risk intake and acknowledgement with a public form and automatic reference numbers
  • Clearer accountability through tasks assigned directly to risk owners, action owners, and senior management
  • Reduced delay on High and Extreme risks through a dedicated approval and revision cycle
  • Improved visibility into risk status with dashboards showing records by status such as Identified, Under Assessment, or Monitoring
  • More consistent treatment tracking with likelihood, impact, rating, and residual risk captured directly on the record

Workflow Steps

Steps

  1. 1
    Create Risk Recordcreate record

    Registers the submitted risk as a new record.

  2. 2
    Set Status to Identifiedupdate record

    Marks the risk status as Identified.

  3. 3
    Send Acknowledgement Emailsend email

    Emails the submitter confirming receipt with their reference number.

  4. 4
    Set Status to Under Assessmentupdate record

    Marks the risk status as Under Assessment.

  5. 5
    Risk Owner: Assess Riskcreate task

    Assigns the risk owner a task to record likelihood, impact, rating, and treatment details, due in 5 days.

  6. 6
    Save Assessment to Recordupdate record

    Persists the likelihood, impact, risk rating, and treatment details to the risk record.

  7. 7
    Route on Risk Rating

    Routes High/Extreme risks to senior management approval; Low/Medium risks proceed directly.

    risk_rating: "High"→Senior Management: Approve Treatment Plan
    risk_rating: "Extreme"→Senior Management: Approve Treatment Plan
    risk_rating: "Low"→Set Status to Treatment Underway
    risk_rating: "Medium"→Set Status to Treatment Underway
    Default→Set Status to Treatment Underway
  8. 8
    Senior Management: Approve Treatment Planrequest approval

    Requests senior management approval of the treatment plan for a High or Extreme rated risk.

  9. 9
    Route on Approval Outcome

    Routes to treatment underway if approved, or to revision if rejected.

    approval_status: "approved"→Set Status to Treatment Underway
    approval_status: "rejected"→Risk Owner: Revise Treatment Plan
    Default→End
  10. 10
    Risk Owner: Revise Treatment Plancreate task

    Assigns the risk owner a task to record a revised treatment plan, due in 3 days.

  11. 11
    Save Revised Treatment Planupdate record

    Persists the revised treatment plan to the risk record's treatment actions field.

  12. 12
    Resubmit for Approvalrestart from step

    Closes this iteration and restarts a new approval cycle with the revised treatment plan.

  13. 13
    Set Status to Treatment Underwayupdate record

    Marks the risk status as Treatment Underway.

  14. 14
    Action Owner: Complete Treatmentcreate task

    Assigns the action owner a task with no due date to record completed treatment actions and the residual risk rating.

  15. 15
    Save Treatment Completionupdate record

    Persists the completed treatment actions and residual risk rating to the risk record.

  16. 16
    Set Status to Monitoringupdate record

    Marks the risk status as Monitoring.

  17. 17
    Risk Owner: Close Riskcreate task

    Assigns the risk owner a task with no due date to close the risk once it no longer needs monitoring, recording closure notes.

  18. 18
    Save Closure Notesupdate record

    Persists the closure notes to the risk record.

  19. 19
    Set Status to Closedupdate record

    Marks the risk status as Closed.

  20. 20
    Send Closure Emailsend email

    Emails the submitter to notify them the risk has been closed.

Fields

Show all 20 fields

FormRisk Assessment Submission

  • Submitter Name*· Text
  • Submitter Email*· Email
  • Business Area*· Text
  • Risk Title*· Text
  • Risk Category*· Choice
  • Risk Description*· Long text
  • Causes*· Long text
  • Consequences*· Long text
  • Existing Controls· Long text

TaskRisk Owner: Assess Risk

  • Likelihood*· Choice
  • Impact*· Choice
  • Risk Rating*· Choice
  • Treatment Actions*· Long text
  • Action Owner*· Text
  • Target Date*· Date

TaskRisk Owner: Revise Treatment Plan

  • Revised Treatment Plan*· Long text

TaskAction Owner: Complete Treatment

  • Treatment Actions Completed*· Long text
  • Residual Risk Rating*· Choice

TaskRisk Owner: Close Risk

  • Closure Notes*· Long text

Other fields

  • Risk Status· Choice
  • Submitter Name*
  • Submitter Email*
  • Business Area*
  • Risk Title*
  • Risk Category*
  • Risk Description*

Forms

Risk Assessment Submission

9 fields

Data Views

Risk Register

risk_title, risk_category, risk_rating, residual_risk_rating +2 more

Dashboard Widgets

Risks by Status

Recommended integrations

Setup the following integrations to extend workflow capability.

  • Send email in the workflow

    AWS SES logoAWS SES
riskassessmentcontrolstreatmentreviewgovernance

Similar Workflows

Similar Categories

FAQs

Why should we automate risk assessment instead of managing it through spreadsheets and email?

Manual risk tracking often relies on someone chasing status updates across spreadsheets, inboxes, and meeting notes, which makes it easy to lose track of where a risk stands. This workflow keeps every risk as a single record with a reference number, a current status, and a timeline of what has happened, so anyone checking progress can see it without asking around. Tasks are assigned directly to the risk owner, action owner, or senior management at each stage, reducing the coordination effort needed to move a risk forward.

What is the business case for using this template rather than building a custom process?

The template is ready to use, so a workspace can publish it and start running live risk assessments in minutes rather than commissioning a development project. Because the workflow already covers intake, assessment, approval routing, treatment, monitoring, and closure, teams avoid the cost and delay of designing that logic from scratch. Adjustments can still be made later by describing the change in plain English or editing steps directly in the workflow editor.

Who is involved in assessing and approving a risk, and what do they each do?

The risk owner records likelihood, impact, risk rating, and treatment details during assessment, and later completes treatment and closes the risk once monitoring is no longer needed. For risks rated High or Extreme, senior management is asked to approve the treatment plan before work proceeds. The action owner is responsible for completing treatment actions and recording the residual risk rating once treatment is underway.

What happens if senior management rejects a treatment plan?

If the approval outcome is rejected, the workflow routes the risk owner to a task where they record a revised treatment plan, due in 3 days. That revised plan is saved to the risk record's treatment actions field, and the workflow then resubmits it for a new approval cycle. This continues the process without requiring the risk to be re-entered or restarted from intake.

How does the workflow decide whether a risk needs senior management approval?

After the risk owner completes the assessment task, the workflow routes based on the risk rating that was recorded. Risks rated High or Extreme are sent to a senior management approval task before treatment can begin, while risks rated Low or Medium proceed directly to the Treatment Underway status. This routing happens automatically based on the rating entered on the assessment task.

Can the intake form or task fields be changed to match our internal risk categories or terminology?

Yes, the workflow can be adjusted by describing the change in plain English or by editing the relevant step directly in the workflow editor. This includes changing fields on the intake form, such as Business Area or Risk Category, or adjusting what the risk owner, action owner, or senior management are asked to record on their tasks. Earlier versions of the workflow are kept, so changes can be reviewed against what was previously in place.

How does the submitter stay informed about their risk without needing a login?

Submitters take part entirely through a public request form and emailed notifications, with no account required. They receive an acknowledgement email with their reference number after submitting, and a closure email once the risk has been resolved and closed. Both emails are sent automatically as part of the workflow's built-in email capability.

What information is retained on the risk record for later reference?

The record keeps the intake details, the assessment fields such as likelihood, impact, and risk rating, the treatment actions and target dates, any revised treatment plans, treatment completion notes, the residual risk rating, and closure notes. Each of these is saved because the relevant task is one the workflow waits for, meaning entries are persisted to the record rather than left only on the task. The record's timeline also shows the sequence of status changes, from Identified through to Closed.

Does this workflow help with compliance or audit requirements?

The workflow records statuses, the values staff enter at each stage, and a timeline of what happened on each risk record, which can support internal review and reporting. Each business should confirm its own compliance and record-keeping obligations, as the workflow itself does not determine or certify compliance. The structured record and timeline are intended to make information easier to retrieve when needed, rather than to represent a compliance outcome.

How long does treatment and monitoring typically stay open on a risk?

There is no fixed due date on the treatment completion or closure tasks, since these depend on how long treatment actions and monitoring take in practice. The action owner completes treatment and records a residual risk rating when ready, after which the status moves to Monitoring. The risk owner then closes the risk, recording closure notes, once it no longer needs to be monitored, and this timing is left to their judgment rather than a preset deadline.

Ready to use this workflow?

Create a free account and customise this workflow for your business.

Risk Assessment Workflow | assess.one