Review Table Agent Actions: Bulk Edits, Metadata Import, & More

What’s New

Review tables are now agent-operable across nearly every action you can take, on any subset of the table: a single cell, a row, a column, a filtered set, or the whole table. Describe the change you want in Assistant, and Harvey identifies the matching cells, rows, or columns and applies it directly.

This covers editing cells, importing metadata, grouping files, adding or removing rows and columns, and workflow actions like assigning, flagging, verifying, and commenting — see the full list of supported actions below.

Why It Matters

Working on a review table one cell or row at a time can get slow and error-prone as the table grows. With this update, you can describe a change once and Harvey applies it everywhere it matches. And it's not just edits: you can organize your table and manage the review workflow the same way, from grouping amendments with their originals to assigning rows and flagging items for follow-up.

How to Use

1. Go to Assistant.
2. Attach your review table by selecting Files → Add review table, or ask Harvey to find it for you.
3. With the table attached as a knowledge source, describe the change you want in plain language. Harvey identifies the matching cells, rows, or columns and applies it.

Examples of Supported Actions

• Edit or lock/unlock cells: "Update every 'Counterparty' cell that says 'Acme Corp' to 'Acme Corporation, Inc" or "Lock every cell in the 'Counterparty' column."
• Import metadata: "Add the metadata from this Relativity export [CSV]" or "Create an 'Internal Risk Rating' column and populate it per this definition."
• Edit a single column: "Make Governing Law a classification with US / UK / Other and re-run."
• Group or ungroup: "Group original credit agreements with their respective amendments."

  • Harvey groups using any content already on the table, such as file names or extracted answers. To group based on attributes it hasn't extracted yet, attach the underlying files as knowledge sources alongside the review table and ask Assistant to group using those attributes.
• Add or delete rows: "Add any files in my vault that aren't yet in this review table" or "Remove any rows that aren't commercial contracts."

  • New rows can only derive from the same source as your review table. For instance, you cannot add files from your computer onto a Vault-backed review table. When adding files, for Vault-based tables, attach that Vault as a knowledge source first.
  • Deleting a row removes it from the table only; the underlying file isn't deleted.
• Reorder or delete columns: "Put all the date columns next to each other" or "Delete File Name, Parties, and Effective Date."
• Assign: "Assign all finance-related rows to a specific user; split the rest equally to other users with access to this vault."

  • You can assign rows to any user with edit access to the table.
• Flag: "Flag every row where Termination for Convenience is 'Yes' in red."
• Verify: "Mark complaint_44.pdf as verified across all its columns."
• Comment: "Comment 'Escalate to senior reviewer' on every red-flagged row."

Notes & Limitations

• Agent actions require you to have edit access to the review table. Users with view-only access cannot invoke them.
• You can work on only one review table per Assistant thread. Start a new thread to work on a different table.
• A bulk action cannot be undone after it’s applied.

FAQs

Q: What information does Harvey use to find the right table?

Harvey uses the table name, created date, last-updated/last-run time, status, # rows/files, # columns, column names + types, and vault.

It does not use cell contents, citations, cell status (comment, verified, flagged), file names, or row assignees. It also doesn’t use who created it, who shared it, and last-viewed date; you can't find tables by person.

Q: Does Harvey read the cell contents to find a table?

No, only table-level details and column names at search time. Cell contents are read only after you add the table as a knowledge source to your Assistant query.

Q: Will editing and then re-running a column affect cells I've already verified?

No, verified cells are preserved by default unless you specify otherwise.

Q: Can I edit my table as Harvey is performing an edit or re-run action on it?

Yes, you can keep working. Re-runs happen in the background and the rest of the table stays usable. What becomes the final response comes down to two rules:

• Immediate edits win at the moment they're made. Editing a cell, flagging, verifying, commenting, assigning, and deleting columns/rows take effect right away. On the same cell, the action performed the latest, by human or agent, wins.
• A re-run replaces the cells it regenerates, when it finishes. Re-runs write fresh values into every cell in scope and clears prior edits, flags, comments, and verifications on those cells. Consequently, a manual edit made to a cell currently being re-run gets overwritten once the re-run completes. An exception to this rule is that verified cells are preserved by default and skipped by a re-run (unless you explicitly re-run all cells). Verify a cell first if you want to protect it from a concurrent or later re-run.