> ## Documentation Index
> Fetch the complete documentation index at: https://docs.soc2doc.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Scenario advisor

> Before you make an operational change, ask the console whether it would break a commitment in your own SOC 2 report — answered from the report's own words.

You're about to give a vendor production access, or move a workload, or change how
access is granted. The question in the back of your mind is always the same: *will
this break something we committed to in our SOC 2?* The scenario advisor answers
it — checked against your own report, in the report's own words.

This is a console capability on the One Plan, separate from the free Commitment
Review.

## Ask it like a conversation

The advisor is a chat, not a form. You tell it what you're considering; it asks a
couple of quick questions, and then it checks.

<Steps>
  <Step title="Describe the change">
    Pick what you're planning — for example, giving a vendor production access — and
    answer a short back-and-forth: which vendor, what kind of access, from where,
    for how long.
  </Step>

  <Step title="Get a plain-English verdict">
    The advisor tells you what it found: potential conflicts with what you've
    committed to, obligations you'd need to meet, and areas your report is silent
    on — with the exact quoted language behind each one.
  </Step>
</Steps>

## Grounded in your report, never invented

<Note>
  The check is deterministic and anchored. Every finding points to the specific
  commitment or control it came from — the verbatim sentence and where it appears in
  your report. If your report is silent on something, the advisor says so rather than
  guessing.
</Note>

The advisor doesn't grade you and it doesn't hand you a generic checklist. It reads
what you already committed to and tells you where a proposed change would rub
against it — so you can decide before you act, not explain after an auditor asks.