:Harvey:

Getting Started with Workflow Builder: 5 Workflows We Recommend

We’ve seen what’s possible when legal expertise meets Workflow Builder. Here are five workflows our internal teams built to show how you can go from idea to system—fast.

Jul 17, 2025

Harvey Logo

Harvey Team

Prompt to generate an NDA from template

Harvey’s Workflow Builder launched to all customers last month, providing an interactive platform for building custom workflows, alongside our growing library of pre-built options.

The early momentum has been exciting: customers have already created and published hundreds of workflows tailored to their internal processes, client-facing use cases, and jurisdictional nuances. These workflows solve a wide range of complex legal problems, proving just how flexible and powerful Workflow Builder is when paired with an organization’s unique expertise.

This breadth of opportunities with Workflow Builder often leads to a question: what are your favorite workflows to build?

To answer that question, we asked the experts from our Applied Legal Research (ALR) and Strategic Business Development Lead (SBDL) teams—former Big Law lawyers who partner with our product and engineering teams to help build Harvey—to provide examples of key patterns they’ve come across while building custom workflows with and for our customers.

We developed a list of the first five types of workflows to consider building. Each of these workflow ideas meets three key criteria:

  1. Simple: Ideas that present straightforward but powerful applications of Workflow Builder that anybody could use and reuse for their specific problem.
  2. General: Ideas that solve a type of problem and that could be changed to fit a range of use cases or solutions.
  3. Enduring: Workflow Builder will evolve a lot this quarter, with the addition of new agent types, interaction patterns, and controls. We wanted ideas that remain resonant over time and where new functionality creates upgrades, not obsolescence.

Each idea is presented as both a workflow type and a specific example implementation. The goal of this list is not to prescribe a specific set of to-do workflows but provide principles to reason about the problems that Workflow Builder is best suited to solve. By giving you the principles, we hope we can spark ideas that incorporate exactly what makes your organization different: your unique expertise, judgment, and how you solve problems.

Example 1: Writing from Precedent

Example 1: Writing from Precedent

Workflow Builder lets you maximize the value of your previous work product. Instead of starting from scratch, you can create custom workflows that draw on user input from freeform text and your own precedent documents.

Incorporating your precedents allows Harvey to ensure that your outputs align with your preferred style and standards—delivering results that look and feel exactly how you want. Moreover, writing using a precedent saves time and improves output quality by allowing Harvey to pick up on subtle stylistic cues and preferences without requiring the builder or the end-user to enumerate them.

This workflow has four blocks:

  1. Ask the user to describe the NDA that they would like Harvey to generate. This step enables the user to provide as much or as little guidance information as they’d like to include about their ideal NDA given the context, and their own expertise.
  2. Ask the user to upload a template to use while drafting, such as a similar NDA that a law firm generated in a similar context. This step further enables the user to personalize the output by selecting an NDA that they anticipate will be a good reference point for the NDA they would like Harvey to generate.
  3. Use a prompt to draft an NDA in accordance with the user’s description above and in view of the template NDA.
  4. Display the generated NDA to the user.

Example 2: Grounds for Resisting Discovery in NSW, Australia

Example 2: Grounds for Resisting Discovery in NSW, Australia

Workflow Builder provides the perfect framework for making custom workflows that adhere to the specific situational and jurisdictional details of your organization. In this example, the workflow analyzes discovery requests and generates a table of objections for proceedings before the NSW Supreme Court, including the strength of each objection.

With simple prompt tweaks, this workflow can be adapted to any jurisdiction, practice area, or objection format, making it a powerful template for litigation teams looking to embed local expertise into reusable tools.

The workflow has four blocks:

  1. Ask the user to upload the parties’ pleadings and the discovery request setting out categories of documents sought.
  2. Use a prompt to identify the grounds of objection available in proceedings before the Supreme Court of NSW. Notably, you could tailor this prompt to the specific jurisdiction and the specific type of litigation that you want the workflow to apply to (class actions, civil litigation, white collar, etc.).
  3. Use a prompt to generate a table containing all of all of the requested categories for production, all corresponding objections that could be made against each request, and the strength of said objections. As described above, you could tweak this prompt to fit the specific litigation use case and preferred format for the output.
  4. Display the available grounds of objection as well as the table of recommended objections for each discovery category and their respective strengths to the user.

Example 3: Analyze Draft DPA and Compare against Preferred Terms

Example 3: Analyze Draft DPA and Compare against Preferred Terms

Workflow Builder allows you to tag the contents of previous input blocks in your prompts with an @-mention, directing Harvey to focus on the right context at each step. This improves prompt clarity, readability, and precision throughout the workflow. In this example, @-mentions are used to compare an uploaded draft DPA against a preferred version, enabling Harvey to flag potential issues and suggest targeted revisions.

The workflow has five blocks:

  1. Ask the user to upload a preferred DPA that Harvey should use as a positive reference.
  2. Ask the user to upload the DPA currently being drafted/negotiated.
  3. Use a prompt to thoroughly analyze the Draft DPA and flag potential concerns given context about the company’s locality, industry, and any additional details that you’d like to include about unique circumstances that the workflow should account for.
  4. Use a prompt to compare and contrast the preferred DPA and the draft DPA in a table. The prompt can be tailored with organization-specific details, such as the countries where the organization operates, the types of data involved, or the key priorities during DPA negotiations.
  5. Display the analysis of the draft DPA and the table comparing and contrasting the draft DPA and the preferred DPA to the user for quick reference in continuing the negotiation.

Example 4: Draft Internal Litigation Hold

Example 4: Draft Internal Litigation Hold

Workflow Builder lets you connect multiple prompt blocks within a single workflow, allowing intermediate steps (such as document categorization or context building) to run behind the scenes.

For example, one prompt block might identify all categories of documents relevant to a litigation hold while a second uses those categories to draft the notice itself. The output of the first block is passed internally to the second, so users only see the final, polished result. This “prompt chaining” approach ensures each step builds on the last—leading to smarter, more accurate outputs, without cluttering the user experience with unnecessary details.

The workflow has five blocks:

  1. Ask the user to upload the complaint(s) that are the subject of the litigation hold.
  2. Ask the user to identify who the litigation hold will be addressed to and from.
  3. Use a prompt to identify all categories of documents that may be subject to a litigation hold notice.
  4. Use a prompt to prepare the internal litigation notice using the above-generated categories of documents and party names. Notably, this block could be customized to conform to your organization’s specific style and tone of litigation hold notices, such as by swapping in preferred language for the spoliation warning.
  5. Display the internal hold litigation to the user.

Example 5: Make Supply Agreement More Favorable to Buyer

Example 5: Make Supply Agreement more Favorable to Buyer

Custom workflows can work directly with the user. Users can be prompted to answer questions or provide key information that will make sure Harvey has the necessary context to give thoughtful, comprehensive responses that match up with a user’s situation. Workflows can also proceed down branching paths depending on user responses. This iterative process can gather requisite information from a user to produce finely tuned outputs.

The workflow has eight blocks:

  1. Ask the user to upload the supply agreement currently being negotiated.
  2. Ask the user to upload a preferred supply agreement (one they’ve drafted before) that Harvey can look to as a reference.
  3. Ask the user how much leverage they have in the current negotiation, which will influence the type and scope of suggestions that Harvey will propose. This could be tweaked to include firm-specific preferences such as additional questions, additional tiers of leverage, or any other conditions that the workflow should consider to result in suggestions that match up with your day-to-day internal processes.
  4. Branch the workflow based on whether the Buyer has high or low leverage in the negotiation.

If the user selected high leverage above…

  1. Run a prompt block that generates buyer-friendly suggestions that will bring the Supply Agreement being drafted at least as favorable to the buyer as the provided favorable supply agreement.
  2. Display the proposed changes to the user.

If the user selected low leverage above…

  1. Run a prompt block that generates selective buyer-friendly suggestions to make the supply agreement being drafted more favorable to the buyer while also keeping in mind that the buyer has low leverage in this negotiation.
  2. Display the proposed changes to the user.

What Will You Build?

These examples illustrate just a small slice of what’s possible with Workflow Builder. You can start simple and add complexity as needed, all the while incorporating your organization’s proprietary knowledge and unique ways of working.

If your team can define the process, you can turn it into a workflow. And the more those workflows reflect how you think and work, the more powerful they become.

Ready to build? Contact your Harvey team to enable Workflow Builder or request a demo to learn more.