Reporting an issue from Business Continuity Workspace

concept brazil Updated Nov 6, 2026 2 min read grc-iss-rep-frm-bcmws-w-ai.md
Raw file servicenow.com

Associate issues with plans or events in Business Continuity Workspace to report compliance gaps and control deficiencies.

During business continuity management (BCM) events, teams identify gaps between documented controls and actual operations. GRC issue reporting formalizes these findings into actionable work items that your compliance team can track, analyze, and resolve.

How issue reporting works

When you discover a control deficiency, non-compliance, or gap during a BCM event, report it directly using ServiceNow Otto for IRM AI-guided workflows. ServiceNow Otto for IRM prompts you for essential context and automatically:

  • Classifies the issue by risk severity
  • Assigns it to the compliance team
  • Tracks its progress through analysis, response, review, and closure

Roles required for reporting issues in a BCM instance

Users with the sn_bcm.viewer or sn_bcm.manager role and the sn_grc_genai.issue_aiagent_user role can invoke issue AI agents.

Why report issues

Structured issue reporting creates an audit trail that demonstrates your organization's commitment to governance and continuous control improvement. Structured issue reporting prevents compliance gaps from going unaddressed and helps leadership understand risk exposure across business units.

Issue workflow states

Reported issues progress through the workflow states:

  • New: Issue submitted and awaiting triage
  • Analyze: Compliance team validates scope and risk rating
  • Respond: Remediation actions assigned and tracked
  • Review: Completion and control effectiveness verified
  • Closed: Issue resolved and approved for closure

An issue that you report through ServiceNow Otto for IRM isn't automatically classified as a BCM issue, and isn't automatically linked to the plan, event, or exercise it relates to. ServiceNow Otto for IRM classifies the issue based on the description you provide and marks the issue source as Ad-Hoc.

[Omitted image "ai-issue-not-classified-as-bcm.png"] Alt text: Issue reported showing a classification and an issue source of Ad-Hoc.

If the issue relates to business continuity, in the Classification field, select Business continuity management, and link the issue to the relevant plan, event, or exercise manually. For the steps, see Add or create an issue from a plan or Add or create an issue from an exercise.

Related topics

Report an issue

Managing issues from Business Continuity Workspace

Add or create an issue from a plan

Add or create an issue from an exercise

Keywords GRCbusiness continuityissue trackingcomplianceOtto AI
Search documentation
Search document titles and file paths on the brazil branch