Workflows

Multi-step automations for repeatable legal work. Inputs go in, structured outputs come out — drafts, reports, emails, comparisons.

Where a Risk Playbook reviews an existing contract, a Workflow takes raw materials (notes, transcripts, contracts) and produces an output. Each workflow is a pipeline of steps with inputs, prompts, model settings, and an output format.

Built-in workflows

QuickContract ships with six built-in workflows:

• Turn sales call into MSA — meeting transcript + commercial terms → first-draft Master Services Agreement
• Review vendor agreement — vendor contract → structured risk report with recommendations
• Prepare client summary — contracts + meetings → client-facing update
• Extract renewal obligations — contract → list of dates, notice windows, and owner actions
• Draft negotiation email — deal context → professional negotiation email with asks and fallback positions
• Compare deals — two or more deal options → side-by-side comparison across business value, risk, and obligations

Built-in workflows can’t be edited — click Duplicate to make a custom copy you can change.

Running a workflow

Open Workflows in the sidebar. Each workflow shows its name, description, and a small Run button on the right. Click Run on any workflow to open the runner page.

The runner shows:

• The workflow’s required sources (e.g. "Call notes", "Commercial terms")
• Input slots — paste text, upload a file, select a contract, or fill a structured form (varies by workflow)
• Optional jurisdiction notes, model override, output format settings

Click Run and the steps execute in sequence. Each step’s progress is shown. The final output appears at the bottom — could be a contract draft, a report, or an email body.

Workflow shape

Every workflow has the same shape:

• Inputs — what the user provides (call notes, deal terms, a contract to review)
• Required sources — types of data the workflow needs (meeting, contract, person, company, file, notes)
• Steps — a list of prompted AI calls. Each step can reference outputs from previous steps via {{stepOutput.previous_step_id}}.
• Model settings — default task, optional model override, temperature
• Output format — report, contract, email, or comparison. Drives how the final output is rendered.
• Playbook dependencies (optional) — references to playbooks/rules the workflow uses
• Jurisdiction notes — any jurisdiction-specific guidance the AI should apply

Customizing a workflow

From the Workflows page, click any built-in workflow then click Duplicate. The copy lands in your Custom filter with “ (Copy)” appended to the name.

You can then edit:

• Name, icon (lucide name like file-signature or any short text), description
• Each step’s prompt, output format, max tokens
• Required sources and inputs
• Model override (e.g. force a specific provider/model) and temperature
• Output destination (download, contract, email)
• Jurisdiction notes
• Playbook dependencies

Click Save to persist your changes. Custom workflows can be deleted; built-ins cannot.

Workflows vs Risk Playbooks vs Review Tables

You want to…	Use
Find issues in a contract you already have	Risk Playbook
Generate a new contract from notes/transcripts	Workflow (Sales Call → MSA)
Get a structured comparison or summary	Workflow
Apply a clause-level fix to existing language	Risk Playbook (apply fix)
Bulk-extract terms across many contracts	Review Table
Open conversation with grounded context	Legal Advisor with pinned items