zgbrenner builds Gary a cautious intake table for U.S. lawyers

A new built-in template turns a pile of uploaded matter documents into a structured, attorney-reviewable grid - without pretending it knows more than it does.

intakesummarization

zgbrenner took Gary's existing spreadsheet-style review feature, renamed it to the plainer "Review Table," and added a template aimed squarely at legal intake. Point it at a matter's documents and it fills eight columns: document name, type, date, people and parties, a plain-English summary, key issues, a suggested legal task, and a flag for whether an attorney needs to look.

The interesting part is the restraint. The prompts behind every column are tuned to refuse guessing - missing dates and parties come back as "Unknown" rather than invented, the tool won't make definitive privilege calls, and the attorney-review flag defaults to Yes whenever a document touches rights, deadlines, filings, or sensitive data. A persistent banner labels the whole thing a draft, every cell stays editable, and the suggested-task column is deliberately informational for now - it points, it doesn't act.

So what Legal-ops leads evaluating AI for document triage should look here for a model of how to make extraction useful without inviting a hallucinated fact into the file.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from zgbrenner/gary, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
06f80d85 feat: add Matter Document Review template and lawyer-friendly Review Table Claude 2026-05-19 ↗ GitHub
commit body
Lightweight improvements to make uploaded matter documents easier to
understand at a glance.

- Rebrand the user-visible "Tabular Review / Tabular Reviews" copy to
  "Review Table / Review Tables" across the sidebar, project tabs,
  modal headers, breadcrumbs, page titles, owner-only-action messages,
  and the workflow-builder helper text. Internal type names and routes
  are unchanged.
- Rewrite both empty states to match the lawyer-friendly direction:
  title "Start a Review Table", body about Gary organizing uploaded
  documents into a table with dates, document types, people,
  summaries, and follow-up issues, primary button "Create Review
  Table", and a secondary note "Review all extracted information
  before relying on it."
- Add a built-in tabular workflow "Matter Document Review" with eight
  default U.S. legal review columns: Document Name, Document Type,
  Date, People / Parties, Short Summary, Key Issues, Suggested Saved
  Legal Task, and Needs Attorney Review. Column prompts are cautious:
  use only the uploaded content, do not invent, write "Unknown" when
  missing, default "Needs Attorney Review" to Yes when uncertain or
  when the document touches legal rights / privilege / deadlines /
  filings / settlement / sensitive data. The Suggested Saved Legal
  Task column tags map to the eight built-in Saved Legal Tasks.
- Pre-select Matter Document Review when launching the create-review
  modal from inside a matter, and pin it to the top of the tabular
  template dropdown.
- Surface a plain-English failure on create ("Gary could not create
  the Review Table. Check your AI connection and try again.")
  via a dismissible inline banner in the project Review Tables tab.
- Add a persistent attorney-review reminder banner above every Review
  Table: "Draft for attorney review. Review all extracted information
  before relying on it. Do not treat any cell as verified fact, legal
  advice, or a definitive privilege call."
- Document the Review Table flow in the U.S. lawyer setup guide and
  add a terminology-map entry for Matter Document Review.
- Add focused tests covering the new workflow's columns, tags,
  cautious prompts, and the absence of legacy "Tabular Review" /
  "Workflow Template" copy in built-in workflows.

Row-to-Saved-Legal-Task launching from a row is intentionally deferred
to a follow-up PR; the Suggested Saved Legal Task column is purely
informational today and is documented as such in the setup guide.

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-572.md from inside the repo you want the changes in.

⬇ Download capture-thread-572.md