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

# Contract Clause Extraction

> Automatically identify and extract key clauses from contracts so legal, procurement, and operations teams can review obligations and risks quickly.

### Overview

Contract Clause Extraction is a workflow that automatically identifies and extracts key clauses from contracts so legal, procurement, and operations teams can review obligations and risks quickly and consistently.

It supports first-pass contract review — clause identification, summarization, and risk spotting — in one streamlined workflow.

**What you get:** a structured table of extracted clauses and contract metadata you can review, edit, and export.

<Tip>
  To set up the workflow (creating sessions, uploading documents, running a workflow, and exporting), see [Setting Up a Workflow](/workflows/setting-up-a-workflow) for a comprehensive guide.

  This page focuses on what's specific to **Contract Clause Extraction**.
</Tip>

### When to use Contract Clause Extraction

Use this workflow when you need a consistent first-pass review of contracts, including:

* Parties and effective date validation
* Termination rights and notice periods
* Indemnification scope and carve-outs
* Confidentiality obligations
* Limitation of liability caps and exclusions
* Governing law and dispute jurisdiction
* Force majeure triggers and obligations
* Renewal / auto-renewal terms

### Step-by-step usage

<Steps>
  <Step title="Select the template">
    Navigate to **Workflows** > **Template gallery** and select **Contract Clause Extraction**.
  </Step>

  <Step title="Upload contract documents">
    Upload the contract documents (PDF only).
  </Step>

  <Step title="Upload related documents (optional)">
    Upload related documents (e.g., addendums, SOWs, MSAs, amendments) if they should be reviewed together.
  </Step>

  <Step title="Run the workflow">
    Click **Run** to begin extraction.
  </Step>

  <Step title="Review extracted fields">
    Review the extracted fields and edit anything that is incorrect.
  </Step>

  <Step title="Export results">
    Export results (CSV or Excel) for reporting or downstream processing.
  </Step>
</Steps>

### Inputs

* **Required:** access to [alk.wamiri.com](http://alk.wamiri.com)
* **Required:** stable internet connection
* **Required document type:** contract documents (**PDF only**)
* **Optional:** addendums/amendments/SOWs for full context

### What's specific to Contract Clause Extraction

1. **Columns are your clause checklist.**
   Contract review works best when your columns mirror the clauses your team must confirm for every agreement. Feel free to edit columns where necessary.
2. **Extracted clause text should be verified.**
   Always confirm clause language, thresholds, and exceptions against the source contract — especially around termination, indemnification, and liability.
3. **Use prompts to improve consistency.**
   If a clause is consistently missed or captured incorrectly, simplify the column name or add a short instruction that clarifies the expected output.

### Standard fields (default columns)

| Field                       | Description                                                                                                                   | Field Type | Task Type  |
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | ---------- | ---------- |
| **Contract Title**          | Name/title of the agreement (as shown in the document).                                                                       | Text       | Extraction |
| **Parties**                 | Legal names of the contracting parties (and roles, if stated e.g., "Client" and "Vendor").                                    | Text       | Extraction |
| **Effective Date**          | Effective date of the agreement (or commencement date if different).                                                          | Date       | Extraction |
| **Termination Clause**      | Termination rights, grounds (for convenience/for cause), notice requirements, and any post-termination obligations.           | Text       | Extraction |
| **Indemnification**         | Indemnity obligations (who indemnifies whom, scope, limitations, procedures, and carve-outs).                                 | Text       | Extraction |
| **Confidentiality**         | Confidentiality obligations, permitted disclosures, duration/survival, and handling requirements.                             | Text       | Extraction |
| **Limitation of Liability** | Liability cap, excluded damages, exceptions, and whether caps differ by claim type.                                           | Text       | Extraction |
| **Governing Law**           | Governing law and (if specified) venue/jurisdiction for disputes.                                                             | Text       | Extraction |
| **Force Majeure**           | Force majeure definition, notice obligations, performance impact, and termination rights triggered by extended force majeure. | Text       | Extraction |
| **Renewal Terms**           | Renewal/auto-renewal structure, renewal period, notice windows to prevent renewal, and pricing/term changes upon renewal.     | Text       | Extraction |

### Customising contract clause columns

You can tailor columns to match your contract review checklist.

* Add columns for any additional clauses you need (e.g., payment terms, IP ownership, data protection, assignment, subcontracting, SLA/service credits, dispute resolution, audit rights, non-solicit/non-compete, warranties, limitation exceptions).
* Rename columns to be explicit (for example, include expected format like "Liability cap (amount/percentage)").
* Keep column names clear and unambiguous to improve extraction quality.

### Important Notes

* Always validate critical terms (parties, effective date, termination, indemnification, limitation of liability) against the source contract.
* If a field is consistently wrong, simplify the column name or add a short instruction to the column prompt.
* If the contract has amendments/addendums, upload them to reduce conflicts and missing context.

## Related articles

* [Setting Up a Workflow](/workflows/setting-up-a-workflow)
* [How To Add Custom Columns](/workflows/setting-up-a-workflow#how-to-add-custom-columns)

## Need help?

If you run into issues, contact the Wamiri support team at [support@wamiri.com](mailto:support@wamiri.com). Include:

* What you were trying to do
* What happened instead
* Any error messages
* Steps to reproduce
* Screenshots or recordings (if available)
