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

# Legal User Flow: Practitioner Path Through the Workbench

> Follow the Legal practitioner journey from entry to continuation across the Spine Workbench, adapted for counsel and contracts managers.

The Legal user flow describes how practitioners move through the Spine Workbench to manage contracts, matters, and compliance. Continuity preserves context across sessions, so a contracts manager who pauses mid-redline returns to the exact same clause and notes.

<Steps>
  <Step title="Enter">
    Log in to SpineWorkspace and land on the Legal domain home. Your role determines the default tab: Contract Board for contracts managers, Matter List for counsel, or Compliance Calendar for legal ops.
  </Step>

  <Step title="Discover">
    Twin surfaces what needs attention: contracts approaching signature deadline, overdue matter tasks, or audit evidence gaps.
  </Step>

  <Step title="Understand">
    Drill into a contract or matter. Spine assembles context from Ironclad, DocuSign, Google Drive, and Salesforce so you see history, related documents, and stakeholder comments in one place.
  </Step>

  <Step title="Contextualize">
    Add redlines, attach precedents, or flag risks. Twin records your intent and links it to the contract or matter for future sessions.
  </Step>

  <Step title="Decide">
    Choose the next action: send for approval, escalate a risk, or schedule an audit. Twin may suggest options based on policy and past behavior.
  </Step>

  <Step title="Act">
    Execute the action through a governed capability. The system checks authorization, scope, and policy before writing back to the source system.
  </Step>

  <Step title="Review">
    Confirm the outcome: contract stage updated, matter assigned, audit evidence submitted. Receipts are stored for audit.
  </Step>

  <Step title="Continue">
    Hand off to a colleague or resume later. Context, memory, and notes persist across people, sessions, and agents.
  </Step>
</Steps>

<Warning>
  Actions that write to source systems may require human approval depending on the capability scope.
</Warning>

## Related

* [Human Workbench](/internal-docs/domains/legal/human-workbench)
* [AI Flow](/internal-docs/domains/legal/ai-flow)
* [Execution Flow](/internal-docs/domains/legal/execution-flow)
* [How It Works: Continuity](/how-it-works/continuity)