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

# What can you automate with Gavel workflows?

> Explore the full range of use cases for Gavel document automation: internal drafting, client intake, client portals, decision trees, and paid workflows.

Gavel is designed to serve legal professionals across a wide range of practice settings and workflow types. Whether you want to speed up internal drafting, build a self-service tool for clients, or create a revenue-generating legal product, the same core platform supports all of it. The difference lies in how you configure access and what you connect as output.

The sections below describe the main categories of workflows you can build, with examples drawn from common legal practice areas.

***

## Use cases

<CardGroup cols={2}>
  <Card title="Internal document drafting" icon="building">
    Use Gavel within your organization to generate documents more efficiently. You and your colleagues complete the questionnaire, and Gavel produces a polished document instantly. This works especially well for high-volume, repetitive document types — demand letters, engagement letters, closing checklists, or standard contracts — where the facts change but the structure stays the same.

    **Examples:** NDA generator for your deal team, employment offer letter tool, standard lease generator for a property management practice.
  </Card>

  <Card title="Client intake and multi-user workflows" icon="users">
    Set up a workflow where a client fills out the questionnaire to provide their information, and you generate the documents in-house after reviewing the data. The client never sees the final document unless you share it with them — they just answer questions, and the information flows into your document automatically.

    **Examples:** Estate planning intake, personal injury intake, immigration questionnaire, corporate formation intake.
  </Card>

  <Card title="Client-facing portals" icon="globe">
    Publish workflows publicly or behind a login so clients can access and complete them directly, receiving generated documents on the output page without your involvement. This is the basis of a self-service legal portal.

    **Examples:** Simple will generator, tenant's rights letter tool, small claims demand letter, business formation wizard.
  </Card>

  <Card title="Decision trees and kickout pages" icon="arrows-split-up-and-left">
    Build logic-driven workflows that guide users through a decision tree rather than (or in addition to) producing documents. Use conditional logic and **Kickout Pages** to route users to different outcomes based on their answers — for example, telling an ineligible applicant they do not qualify, or directing a user to one of several document paths based on their situation.

    **Examples:** Benefit eligibility screener, jurisdiction selector, legal needs triage tool, intake qualification filter.
  </Card>

  <Card title="Paid legal products" icon="credit-card">
    Integrate Stripe into a workflow (or group of workflows) to collect payment before documents are generated. This lets you monetize automated documents as standalone products or as part of a subscription-based client portal.

    **Examples:** Paid will package, pay-per-document contract generator, subscription-based lease drafting tool.
  </Card>
</CardGroup>

***

## Choosing the right approach

The structure of a workflow is the same regardless of use case. What changes is who fills it out and how you configure access and output. Here is a quick guide to help you decide:

| Goal                                       | Configuration                                                                          |
| ------------------------------------------ | -------------------------------------------------------------------------------------- |
| Internal team use only                     | Restrict access to specific team members, or restrict based on email domain            |
| Gather client data, generate docs yourself | Multi-user workflow; client completes questionnaire, you generate docs                 |
| Let clients self-serve                     | Publish publicly or via direct link; client receives output docs directly              |
| Decision tree                              | Use Kickout Pages and conditional logic; output docs optional                          |
| Charge for document access                 | Add Stripe payment requirement at the start of questionnaire or before the output page |

<Tip>
  Start with a simple internal workflow to get comfortable with the process. Once you understand how questions map to document variables, you can quickly adapt the same workflow for client-facing use.
</Tip>

***

## Examples and inspiration

Gavel publishes case studies and real-world examples from legal professionals using the platform.

* View **case studies** at [gavel.io/category/case-studies](https://www.gavel.io/category/case-studies)

***

## Ready to build?

<CardGroup cols={2}>
  <Card title="Quickstart guide" icon="rocket" href="/workflows/quickstart">
    Follow the step-by-step guide to build and test your first workflow.
  </Card>

  <Card title="Question types" icon="circle-question" href="/workflows/question-types">
    See all available question types and when to use each one.
  </Card>
</CardGroup>