Mary Hain
Administrator

AI Response Assist is a generative AI capability within the Smart Assessment Engine that helps assessment responders draft answers faster — without replacing their judgment. When a responder invokes Draft Responses with AI, the skill searches prior Smart and Classic assessments and attached documents for relevant answers to each question in the current assessment. It returns up to three ranked suggestions per question, each linked to its source, so the responder can verify context before applying. It can be invoked on any GRC assessment that uses Smart Assessment Engine. 

 

Two pain points drive the value: the cycle-to-cycle drift problem — where answers change between assessment cycles, not because the control environment changed, but because the responder is answering from memory — and the evidence-hunting burden — where sourcing supporting documentation often takes longer than answering the question itself. AI Response Assist addresses both.

 

The feature operates within four boundaries that make it audit-safe: suggestions are private to each user, access-controlled to past assessments the responder can already read, bounded to the same scope item (the entity, control, vendor, or risk record the assessment covers), and never auto-applied without human review unless the responder explicitly enables the auto-apply option.


Watch the AI Response Assist video in the Now Assist for IRM playlist on YouTube to explore the full end-to-end capabilities. 

 

How it Works

The four-step responder experience

  1. Invoke — From inside an in-progress assessment, the responder clicks Draft Responses with AI. A modal appears with two source toggles (Past Assessments, Documents) and an optional Auto-apply checkbox. At least one source must be selected.
  2. Generate — The skill processes questions one at a time. A live counter shows progress (e.g., "18 of 20 processed"). The responder can continue working on the assessment while the generation runs. Sparkle icons appear on sections where suggestions are ready.
  3. Review — Each question with a suggestion shows up to three ranked AI Suggestions. Clicking View Sources reveals whether the suggestion came from a prior assessment (with the assessment name, scope item, and date) or from an attached document (with the document name and citation). The responder clicks Apply or Discard per the suggestion. User-entered content is never overridden.
  4. Submit — On submission, a summary shows the percentage of questions for which AI provided suggestions. Applied suggestions carry an AI-Assistance label that persists on the submitted record, creating an audit-defensible trail distinguishing AI-assisted answers from manually authored ones.

 

How the skill builds a suggestion — architecture overview

The generation pipeline runs two retrieval steps in parallel before synthesizing an answer:

  • Step 1a — RAG Search: Semantic matching of the current question text against prior Smart and Classic assessments within the same scope item (subject to access control).
  • Step 1b — Document Intelligence: Parsing of documents attached to the assessment, or surfaced via a document provider script, using the Now Assist Document Intelligence plugin.
  • Step 2 — AI Synthesis: The retrieval outputs are combined and passed to the AI model (Now LLM or a configured third-party), which returns up to three ranked suggestions for each supported question type (text, number, choice).

 

Cross-app search - out of the box

A key design feature: if the same entity, vendor, control, risk, or business process record is the scope item across multiple GRC workflows, AI Response Assist will surface answers across them without any configuration. A TPRM response for an application can inform a new Privacy Impact Assessment for the same application. A Control Attestation response can surface in a Risk Identification assessment for the same control. The scope item match is what enables cross-app retrieval — no scripting required for this out-of-the-box behavior.

 

Why it matters

Assessment programs are only as good as the consistency and defensibility of their answers. Three problems undermine that quality at scale:

  1. Cycle-to-cycle drift. Answers change between assessment cycles — not because the environment changed, but because the responder answered from memory. AI Response Assist anchors each new cycle to the organization's own prior responses, creating a rolling baseline of defensible answers.
  2. Evidence overhead. Sourcing supporting documentation often takes longer than answering the question. The Documents source toggle brings document intelligence directly into the generation step — analysts attach the relevant files once, and the AI extracts the answer.
  3. Scale without consistency. As assessment programs grow — more workflows, more vendors, more regulations — keeping answers consistent across teams and geographies becomes unmanageable. AI Response Assist is additive at the program level: it works across TPRM, IRM, BCM, Privacy, and Operational Resilience workflows with no cross-workflow configuration required.

The trust mechanics matter as much as the speed. Suggestions are private per user, access-controlled, and scope-bounded — the AI does not surface answers from assessments the responder cannot read, and it does not blend answers across unrelated scope items. AI-Assistance labels persist on every submitted answer, so auditors can see exactly which answers had AI involvement and trace each suggestion back to its source.

 

For organizations running Control Attestation, Risk Identification, TPRM Vendor Assessments, Business Impact Assessments, and Privacy Impact Assessments on recurring cycles — the use cases where the same question recurs against the same entity each period — AI Response Assist delivers maximum value. The prior cycle becomes the accelerant for the next.

 

FAQ: AI Response Assist

Semantic Search Scope

  • Does semantic matching search across all templates and categories, or only within the same template or category? The default logic searches across all templates in all categories — any past assessment the user has read access to that contains all scope items of the current assessment. At the category level, customers can create scripted extension points to override this logic and define which past assessments the AI searches.
  • What exactly is compared when the AI decides a past assessment qualifies? Does 'superset' mean every scope item on the current assessment must appear on the past one? Yes. Matching is on the exact sys_id of each scope item — no traversal of related records and no parent/child resolution. The current assessment's scope set is collected as raw scope_item sys_ids. Superset means every scope item on the current assessment must also appear on the past one; the past assessment may have additional scope items
  • Can AI Response Assist pull answers from a different GRC app — for example, using a TPRM response to inform a new Privacy Impact Assessment for the same entity? Yes. This requires no configuration as long as the scope item is the same entity record. Cross-app retrieval is out of the box. If the scope item differs, it is configurable at the category level using scripted extension points
  • Is a Template Category required for the feature to function? Yes. The AI response-enabled field lives at the category level. Without category-level enablement, the Draft Responses with AI button does not appear, regardless of whether the platform-level skill is active.

Access Control

  • Is retrieval limited to past responses that the current responder has read access to? How is that access determined? Yes — if the responder has read access to a past assessment, it is considered. Access is determined by standard platform access controls on the assessment record. This behavior is not configurable.
  • Does access span across risk areas, or is it limited to the same risk area? Access spans across risk areas by default. This is configurable using scripted extension points at the category level.

 

Multiple Responders (Delegation and Collaboration)

  • When multiple responders are involved — delegation, collaboration, sectional contributors — who can invoke Draft Responses with AI? Any collaborator with edit access can invoke Draft Responses with AI. Suggestions are generated only for the questions that the collaborator can edit. A sectional collaborator sees AI suggestions only for the sections they are assigned to.
  • Are AI suggestions shared between collaborators? No. AI suggestions are private to each individual user. No one can see another person's suggestions. Because different users have access to different past assessments and documents, suggestions will differ across users. Only admins can see AI usage data in platform data tables.
  • Who is recorded as the author when a suggestion is applied? The answered_by value remains the responder who clicked Apply — not the AI. The AI is never recorded as the author of any answer.

 

Document Sources

  • Can responders pull from personal SharePoint or OneDrive— or only from documents attached to the assessment? By default, responders see only documents attached to the assessment instance. Responders can always attach additional documents from SharePoint or OneDrive using the standard Attachments section. Automated document surfacing from external systems is configurable via scripted extension points (document provider scripts at the category level).
  • Do the 20 MB and 200 page limits apply per file or cumulatively across all documents in a single generation? Per document. Each document in the picker is limited to 20 MB and 200 pages. A responder can select up to 5 documents per generation run.
  • Where are document provider scripts configured? As scripted extension points at the Template Category level, using the sn_smart_ai_assist.SmartAsmtResponseAssistExtensionPoint extension point.

 

Some useful resources

Visit the ServiceNow product documentation or join the conversation on the ServiceNow GRC Community.

Version history
Last update:
2 hours ago
Updated by: