In ServiceNow Integrated Risk Management, expiration is the key time-based event that prompts notifications for audit tasks. This keeps task owners and stakeholders informed as deadlines slip, while changes like 50% completion, reassignment, or due-date edits don’t automatically fire the alert. This is about staying aligned with overdue status.

Multiple Choice

Which baseline criterion triggers notifications for audit tasks when they expire?

In IRM, notifications for audit tasks are driven by specific events, and a time-based event is expiration. When an audit task reaches its expiration, that event matches the expiration baseline criterion and triggers the configured notification to the task owner and stakeholders. This ensures timely awareness and follow-up when the task can no longer be completed within its original timeframe. Other scenarios don’t align with expiry: triggering at 50% completion is about progress, not overdue status; reassignment concerns ownership changes; a change to the due date only fires if the due date itself is altered, not when the task becomes overdue. So, expiring is the trigger that best matches the requirement.

In ServiceNow Integrated Risk Management (IRM), keeping audit tasks on track is more than a chore—it's a risk-control habit. Organizations rely on timely alerts to prevent drift, missed deadlines, and the cascading consequences that can follow. So, how do these notifications actually get triggered? The short answer: expiration. But there’s a bit more texture to that story, including why expiration matters, how it fits into baseline criteria, and what you can do to make the notifications meaningful rather than noise.

Let me explain the core idea behind baseline criteria in IRM. Think of a baseline criterion as a rule that tells the system when something should happen. It’s like setting up a calendar with the right reminders, except the calendar is smart, dynamic, and tied to risk governance. For audit tasks, these criteria determine when stakeholders should be alerted, escalated, or asked to take action. The beauty of this approach is that the triggers aren’t tied to opinions or guesswork—they’re anchored to events the system can observe consistently. When the event happens, the preconfigured notification fires off to the right people: task owners, process owners, risk managers, auditors, and sometimes even external readers if your governance model requires it.

Expiration as the time-based trigger is particularly intuitive for audit tasks. Why? Because audits are time-bound activities. There’s a window to complete evidence collection, analysis, and documentation before the task becomes overdue. When the clock ticks to expiration, you’ve effectively crossed from “in progress” to “overdue by policy.” That boundary is precisely what the notification is designed to highlight. It’s not about micro-managing every moment; it’s about signaling that the window for completing work under the original schedule has closed, and proactive follow-up is warranted.

Contrast this with other potential triggers and you’ll see why expiration is the natural fit for audit task alerts. A 50% completion trigger, for example, emphasizes progress—nice for visibility, but it says little about whether the task is still on track to be finished within the defined timeframe. Reassignment alerts might be important when ownership changes, but they don’t automatically flag overdue risk unless you couple them with a time-based rule. A due date change is inherently reactive—it responds to a change in schedule, not to the task falling behind. In practice, the expiration-based notification aligns with the risk-management objective: ensure timely completion and accountability before delays propagate.

How it actually works in IRM

  • Event-driven notifications: When an audit task hits its expiration, the system recognizes the event and checks the notification rules tied to that baseline criterion. If the policy says “notify owners and stakeholders at expiration,” the message goes out automatically.

  • Stakeholder scope: Notifications can target task owners, control owners, risk champions, and anyone else you designate as a recipient. You can tailor the message to reflect the task’s status, the evidence needed, and the recommended next steps.

  • Content that makes a difference: A good expiration alert isn’t just “This task expired.” It includes context: which control, which risk scenario, how long it was overdue, what evidence remains to be collected, and the recommended escalation path. It’s practical, not punitive.

  • Actionable follow-up: The notification should prompt a concrete action—review the overdue task, assign it to the right owner, attach missing evidence, or open a remediation plan. The best systems offer quick links, so you don’t have to hunts for the right record.

Practical tips for configuring expiration-based alerts

  • Define clear expiration semantics: Make sure your organization agrees on what “expiration” means for audit tasks. Is it a hard cutoff, or a soft SLA with a grace period? A common pattern is to differentiate between a primary expiration and a final overdue state, each with its own notification cadence.

  • Align with risk appetite: If your risk tolerance is high, you might want earlier nudges (for example: a week before expiration) to give teams breathing room. If risk is tightly regulated, stricter alerts closer to the deadline can be appropriate.

  • Keep recipients relevant: It’s tempting to blast everyone, but that creates fatigue. Target owners, responsible control owners, and the risk leads who can actually move the task forward. You can segment audiences by task type, risk domain, or business unit.

  • Use meaningful content: Include the control reference, the key risk it mitigates, the evidence needed, due dates, and the next escalation step. A well-crafted message reduces back-and-forth and speeds up resolution.

  • Leverage dashboards and summaries: Pair notifications with a dashboard that shows overdue tasks by age, owner, or risk level. A visual snapshot helps leadership and teams quickly grasp where attention is needed.

  • Test with care: Run a controlled test to verify that expiration events trigger notifications as intended. Check that recipients receive the right messages and that the links take them to the correct records.

Common scenarios and how expiration notifications improve them

  • Late compliance checks: An audit task tied to a control’s period end might slip if evidence gathering gets bogged down. Expiration alerts spotlight the lag, prompting a rapid check-in with the process owner and a plan to gather the missing documents.

  • Evidence misplacement: Sometimes the missing pieces aren’t visible in the system until it’s almost too late. Expiration notifications can trigger a reminder to upload attachments, screenshots, or logs, keeping the audit chain intact.

  • Ownership churn: People change roles; someone new inherits the task. An expiration-based alert still lands in the right inbox, ensuring the newcomer is aware of the due status and what’s needed to complete the job.

  • Regulatory alignment: For industries with strict reporting windows, expiration alerts help maintain traceability and demonstrate timely action when controls are tested or remediated.

A few caveats to keep in mind

  • Alert fatigue is real. If every task in the system vetoes you with an expiration alert, teams will start muting notifications. The antidote is thoughtful throttling: tiered alerts (earlier nudges, then sharper reminders), smart grouping, and occasional reviews of who actually needs to be notified.

  • The timing must be practical. Expiration triggers should reflect operational realities. If some tasks routinely take longer due to dependencies outside the control of the task owner, you might need a built-in buffer or a separate “extension” workflow that still notifies the right people without shouting urgent warnings prematurely.

  • Data quality matters. If records aren’t up to date, expiration alerts can misfire. Make sure task statuses, due dates, and ownership are maintained consistently. A quick quarterly health check on task data can save hours of barking up the wrong tree later.

Real-world vibes: painting a clearer picture

Imagine a mid-sized financial services firm that relies on IRM to keep its control environment honest. Each audit task is mapped to a specific control with defined evidence requirements. As the calendar flips to the expiration date, the system sends a concise alert to the task owner, the control owner, and the risk manager. The note isn’t a siren; it’s a nudge with purpose: “Here’s what’s missing, here’s what to gather, and here’s who to loop in if you need a hand.” If the task still isn’t complete after expiration, a second wave of alerts — possibly with an escalation path to the process owner or an auditable remediation plan — ensures accountability without turning into a paper chase.

In another scenario, a multinational retailer uses expiration-based notifications to keep compliance tasks in check across time zones. Regional teams receive time-appropriate reminders, and the central risk office can monitor overdue patterns across regions. The result? Faster remediation cycles, better evidence quality, and a clearer picture of where risk sits in the organization.

A final note on the big picture

Expiration as a baseline criterion isn’t just a ticking clock. It’s a design choice that anchors risk governance in timely action. When you tie notifications to a concrete, time-bound event, you create a predictable rhythm for audits: a cadence that helps teams stay aligned with policy expectations, regulators’ needs, and internal risk appetite. It’s about turning vigilance into a practical, everyday habit—one reminder at a time.

If you’re building or refining an IRM program, start with expiration as your go-to trigger for audit task alerts. Map out who should be in the loop, what information is indispensable in the alert, and how you’ll measure whether the notifications actually help close gaps faster. After all, the goal isn’t just to send notices—it’s to foster a culture where timely action becomes second nature, and risk stays well in check.