Risks

Features

• Create and edit risks from Risks → New risk with client assignment.
• Severity and status lifecycle with activity history.
• Internal owner assignment and optional due date tracking.
• Client-linked views on portfolio and client detail pages.
• SLA timer evaluation based on assigned client policy and severity.
• Risk score summaries on client detail pages for open items.
• Filtering and search across the organization portfolio.
• Integration with reports—related open risks can appear in generated reports.
• Manual and platform-originated risk creation with source metadata.
• Dismiss workflow with rationale for accepted or invalid risks.
• Linkage to incidents when risks materialize into client impact.
• Dashboard and health engine integration for portfolio-level visibility.
• Role-based permissions for create, update, and close actions.
• Audit-friendly activity log on each risk record.

Step-by-step usage

1. Search existing risks for the client to avoid duplicates before creating a new record.
2. Open Risks → New risk and enter title, client, severity, and description.
3. Assign an internal owner responsible for mitigation and follow-up.
4. Set a due date if your delivery playbook requires time-bound response.
5. Move status to Acknowledged when work begins; add notes as mitigation progresses.
6. Monitor SLA timers on the risk detail page if the client has an assigned policy.
7. Set Mitigated when controls are in place; continue monitoring before final closure.
8. Resolve or Dismiss with documented rationale when the risk is no longer applicable.
9. Link related incidents if the risk materializes into active client impact.
10. Reference significant open risks in client reports when transparency is expected.
11. Review open risks weekly in operations meetings alongside incidents and SLA breaches.
12. Use Settings → Escalation rules for critical risks that breach response targets.

Best Practices

Risk registers fail when teams treat them as write-once archives. Successful agencies assign owners, set review cadence, and close loops in the same meeting where incidents are discussed.

• Define severity criteria in your internal playbook so the team applies labels consistently.
• Review open risks weekly in operations meetings alongside incidents and SLA breaches.
• Avoid duplicate records—search by client and title before creating new entries.
• Close risks with clear resolution notes suitable for audit or client review.
• Escalate critical risks through your defined path including Settings → Escalation rules.
• Link related incidents when a risk materializes into client impact.
• Use Acknowledged status promptly so SLA timers reflect active ownership.
• Dismiss only with written rationale when accepting exposure or invalidating the threat.
• Include open high-severity risks in published report key risks sections when appropriate.
• Revisit mitigated risks after thirty days to confirm controls remain effective.

Examples

Troubleshooting