> For the complete documentation index, see [llms.txt](https://docs.corpdev.ai/corpdev.ai-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.corpdev.ai/corpdev.ai-docs/compare-documents-with-tabular-reviews.md).

# Compare documents with tabular reviews

A tabular review puts files in rows and questions in columns. Use it to compare contract provisions, extract financial facts or assemble a diligence evidence table. It is available in workspaces with **Reviews** enabled and requires permission to run analysis.

## Create a review

1. Open **Source Files** and choose the folder or files you want to review.
2. Open **Reviews**, then create a **New Review**. The adjacent dropdown can start a review for the current folder.
3. Enter a descriptive **Review Name** and choose the scope. Check the included files, subfolders and exclusions; the scope determines what gets analyzed.
4. Apply a saved column template if appropriate, or start blank.
5. Choose the extraction mode. **Agent** can search each document repeatedly and fill columns together. **Standard** performs an independent extraction per cell.
6. Select **Create Review**.

## Define useful columns

Add a **Column** for each question. Ask for one clearly defined fact or assessment per column. Include the desired units, date format or classification where relevant.

For a contract review, examples include “Contracting parties,” “Termination notice in days” and “Does the agreement contain a change-of-control consent requirement? Cite the relevant clause.” Ask for “not found” or an empty result when evidence is absent rather than an invented answer.

Use questions appropriate to the documents. A financial statement and an executed contract need different extraction criteria.

## Run and verify

Select **Run All** after files are processed and columns are ready, or run a particular column. Progress and error counts show what has completed. A run in progress can continue filling cells; do not mistake a blank pending cell for a negative finding.

Open a result's verification panel to inspect supporting text and the source. Correct or verify answers using the available controls. Review material exceptions and low-confidence results before treating the table as a diligence conclusion.

Changing scope or questions can change which results remain useful. Recheck the included file count after edits and run the required pending work.

## Filter and export

Use document search, column filters and sorting to inspect the table. **Export** offers CSV, Excel and JSON. **Exports contain the full review; the current filters and sort are not applied.** Check the downloaded data before sending it to anyone who should receive only a subset.

If a run cannot start, check that at least one column exists and the selected files have finished processing. For partial failures, inspect affected files and retry the relevant work after resolving the cause.