How a workflow is structured
Every Gavel workflow has two sides that work together.The questionnaire
A step-by-step web form you build in Gavel’s no-code editor. Each question has a unique variable name. The person filling out the workflow — you, a colleague, or a client — answers the questions on screen.
Output documents
One or more Word (.docx) or PDF templates you connect to the workflow. You tag each template with variable names that match your questions. When the questionnaire is submitted, Gavel merges the answers into the templates automatically.
The two-step build process
Building a workflow follows a consistent two-step pattern regardless of complexity.Set up the questionnaire
Add questions that capture all the data your documents need. Each question type — text, date, yes/no, single select, and more — maps to a unique variable name. You can organize questions across multiple pages and sections, add conditional logic to show or hide questions based on prior answers, and include instructional blocks or kickout pages for decision-making flows.
Connect your output documents
Upload your Word or PDF templates and tag them with the variable names from your questionnaire. For Word documents, you insert variable tags directly in the document using Gavel’s Word Add-in. For fillable PDFs, you map fields in Gavel’s PDF Tagger. You can add conditional clauses, calculations, and loops to control exactly how the answers appear in the finished document.
You can connect multiple output documents to a single workflow. For example, a contract workflow might generate a main agreement, an exhibit, and a signature page all from one questionnaire.
Common use cases
Gavel workflows are flexible enough to serve very different purposes depending on how you configure sharing and access.| Use case | Description |
|---|---|
| Internal drafting | You and your team fill out the questionnaire to generate documents without sending anything to a client. |
| Client intake (multi-user) | A client fills out the questionnaire to provide their information; you review the data and generate documents in-house. |
| Client-facing portal | Clients access and complete the workflow directly, receiving generated documents on the output page. |
| Expert systems | Logic-driven workflows that guide users to a decision or recommendation rather than (or in addition to) producing documents. |
| Paid workflows | Add a Stripe payment gate before documents are generated to monetize your automated legal products. |
What you can build
Legal professionals use Gavel for a wide range of document types: estate planning documents, business formation packages, lease agreements, demand letters, client intake forms, compliance checklists, and more. Because Gavel works with standard Word and PDF templates, any document you currently draft manually can become an automated workflow.Quickstart guide
Build and test your first workflow step by step.
What can you build?
Explore use cases and examples across practice areas.