> For the complete documentation index, see [llms.txt](https://support.vlex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.vlex.com/vincent-by-vlex/vincent/core-workflows/tabular-review/manage-columns-in-tabular-review-name-question-source-and-format.md).

# Manage Columns in Tabular Review: Name, Question, Source, and Format

Learn how to rename a column, change the question it asks, set its Source and Format separately, and manage every column in Tabular Review from one view.

#### Summary

Learn how to rename a column, change the question it asks, set its Source and Format separately, and manage every column in a table in Tabular Review from one view.

### Why This is Important

The questions a review needs change as the review proceeds. A column asks the wrong thing, another needs to return a date rather than text, two need reordering so the table reads in the order a reviewer thinks. Doing that one column at a time, or rebuilding the table, is the work v2 removes.

### How to Manage Columns

1. Open **\[VERIFY — the column management view]**.
2. From here you can, for a single column or several at once:

   * Change the **name**
   * Change the **question** the column asks
   * Change the **Format**
   * **Reorder** columns
   * **Delete** columns

<figure><img src="https://1556743161-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MS8Dq_iqEIflAmbaOkI-887967055%2Fuploads%2FpVVXboEm4Qj8HV7JeqUe%2FScreenshot%202026-09-30%20at%204.06.29%E2%80%AFPM.png?alt=media&amp;token=2c81a5b6-1fe2-4e93-a6d4-94abe32e2020" alt="" width="249"><figcaption></figcaption></figure>

### Source and Format Are Set Separately

A column now has two settings that were previously conflated under a single label.

* **Source:** where the answer comes from: the document, the web, or manual entry.
* **Format:** what shape the answer takes: text, a date, a number, a true-or-false value.

{% hint style="warning" %}
These were two fields that both used to be called "type". If you have written internal guidance or training material referring to a column's "type", it needs updating to name which of the two it means.&#x20;
{% endhint %}

A column whose Source is manual entry is yours to fill in. It is how a reviewer's own knowledge goes into the table alongside the extracted columns, rather than into a separate spreadsheet.

### Sorting and Reordering

Sort and reorder from the column header itself.

<figure><img src="https://1556743161-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MS8Dq_iqEIflAmbaOkI-887967055%2Fuploads%2FBaX6qqNPpVRYrcpkysGS%2FScreenshot%202026-09-30%20at%204.09.06%E2%80%AFPM.png?alt=media&amp;token=ca53d3cb-801d-4ec3-b459-fc001294f7e7" alt="" width="179"><figcaption></figcaption></figure>

### Best Practices & Pro Tips

**Set Format before the review, not after.** Changing a format re-runs the column against the documents, so getting dates and numbers typed correctly at the start saves a re-run and keeps the export usable.

**Add a manual column for the reviewer's judgement.** A column for "assignable, yes, no, needs advice" turns the table into the place the review actually happens. Without it, the judgements go into a spreadsheet and the citations stay behind.