Create Conditional Columns in Review Tables
Reference responses in existing columns as context for responses in new columns to power workflows like conditional follow-up logic, targeted summary of entities, and transactional extraction.
Last updated: Apr 16, 2026
Overview
When building a review table, you can reference the output of one column in the prompt of another. This lets you create multi-step workflows where each column builds on the results of previous ones.
Use this feature to:
- Apply conditional logic based on prior answers (e.g., "if X exists, then describe it")
- Summarize information about a specific entity identified earlier
- Extract structured details based on a prior classification
Example Use Cases
Conditional Follow-Up
Use one column to detect a condition, and another to act on it only when the condition is met.
Column | Prompt |
|---|---|
Column 1 | Does an X clause exist? |
Column 2 | If an X clause exists per @Column 1, describe it. Otherwise, leave blank. |
Targeted Entity Summary
Focus a summary on a specific entity identified in a prior column.
Column | Prompt |
|---|---|
Column 1 | What is the name of the defendant? |
Column 2 | Summarize statements made by @Column 1. |
Classify Then Extract
Classify the document type first, then extract details relevant to that type.
Column | Prompt |
|---|---|
Column 1 | Classify the type of agreement. |
Column 2 | Based on the agreement type in @Column 1 if this is a power agreement, extract energy pricing structure, as described as fixed, indexed, or market-based. If this is a sub-engineering agreement, extract fee structure, as described as lump sum, time & materials, or cost-plus. |
How to Create a Conditional Column
- Open a review table with at least one existing column.
- Select + to add a new column.
- Write a question with conditional logic. Use the
@symbol to reference a prior column by name. - Select Run column.
The new conditional column is now dependent on the prior column.
If you later chose to re-run the prior column, you’ll receive a warning that the dependent column will become outdated as illustrated in the example image below.
Simply re-run an outdated column to refresh its answers.
Tips for Success
- Be explicit about when to leave a cell blank. If a condition is not met, say so clearly (e.g., "Otherwise, leave blank"). Without this, the column may generate a response even when there is nothing relevant to report.
- Break complex logic into multiple columns. If you need to classify, then filter, then extract — use three columns rather than one. Simpler prompts tend to produce more accurate and predictable results.