Skip to content
Assurance agents
Risk, Trust & ResilienceAssuranceScope & Control Architecture

Assurance Scoping Agent

Turns an ambiguous assurance request into a reviewable engagement charter.

Owns the engagement perimeter. Before testing starts it pins down entity, product, period and jurisdiction, sets the evidence posture and names each decision owner and exclusion.

Authority

Recommend

Team role

Routes work to specialists

Handoffs

Named collaborators

The role

What it owns and where its authority ends

Desk

Scope & Control Architecture

Desk workflow

Charter the engagement, map obligations, rationalize controls and design review gates.

Collaboration

Calls several specialists in parallel

Decision boundary

Prepares a recommendation for an accountable decision owner.

Systems and capabilities involved

  • GRC inventory API

    entities, risks, controls and open issues

  • Policy corpus

    scope terms and firm taxonomy

  • Regulatory source library

  • Engagement approval queue

Handoffs

What this role gives and receives

Capabilities offered

Scope an assurance engagement

Produces a bounded charter and structured scope record.

Receives:
Review request and available context
Returns:
Scope record, exclusions, evidence posture and review gates

Delegates

Obligation Mapping Agent

Ground the approved perimeter in applicable requirements. Trigger: Scope owner approves the charter Returns: Applicable-obligation set with citations.

Context

What the role needs to do the work

Current work
Current scope, evidence index, open questions and review comments
Prior interactions
Prior testing cycles, findings, responses and closure decisions
Policies and reference
Firm policy, obligation, control and issue taxonomies
Working method
Approved assurance methodology and workpaper standards

Illustrative workflow

How the work moves

Starting point

CCO asks for an end-to-end deposit-fee review

  1. 01

    Resolve products and legal entities

  2. 02

    Set source posture and review period

  3. 03

    Name exclusions and dependencies

  4. 04

    Route charter for approval

Result

Approved review charter plus machine-readable scope record

Checks and boundaries

What must be tested or reviewed

  1. 01Rejects unresolved entity, period or decision-owner ambiguity
  2. 02Never silently expands the requested perimeter
  3. 03Every exclusion has an owner and rationale

Human authority

  • Engagement sponsor approves scope and exclusions

Keep exploring