> For the complete documentation index, see [llms.txt](https://help.brieftech.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.brieftech.ai/get-started/review-an-ai-analysed-matter.md).

# Review an AI-Analysed Matter

A guided run through the Review stage — take a matter the AI has analysed and confirm, correct and refine its details until it's ready to index.

When you upload documents, BriefTech's AI reads each one and fills in a **Date** and a **Description** for every document. That's a strong first draft — but you're the lawyer, and the finished index has to be right. **Review** is the stage where you check the AI's work and correct anything that matters, before those details flow into your Document Index and court bundle.

In this tutorial we'll take a practice matter the AI has already analysed and work through a real review pass together: read what the AI produced, fix a date, sharpen a description, teach BriefTech your preferred wording so it rewrites the rest, and tidy the set with a label. By the end you'll have a fully reviewed matter and know how to run the same pass on a real case.

We'll work in a throwaway **practice matter** with BriefTech's built-in **sample files**, so nothing here touches a real case and you can archive the matter afterwards to clear it from your list. The whole run takes about ten minutes.

{% hint style="info" %}
**New to BriefTech?** Do [Your First Matter](/get-started/your-first-matter.md) first — it takes a matter from empty all the way to a downloaded bundle. This tutorial zooms in on just the Review stage and goes deeper.
{% endhint %}

***

## Before you start

By the end of this tutorial you'll have a **fully reviewed matter** — every AI-generated date and description checked, corrected where needed, refined to a consistent style, and ready to flow into a Document Index.

**You don't need any documents of your own.** We work in a throwaway **practice matter** with BriefTech's built-in **sample files**, so nothing here touches a real case and you can [archive](/how-to-guides/manage/organise-your-matters.md#archive-a-matter-you-have-finished-with) it afterwards. If you already have the practice matter from [Your First Matter](/get-started/your-first-matter.md), you can reuse it. The whole run takes about ten minutes.

***

## Step 1 — Open a practice matter with sample files

{% hint style="info" %}
**Already done** [**Your First Matter**](/get-started/your-first-matter.md)**?** Open that practice matter and skip to Step 2.
{% endhint %}

Otherwise, set one up:

1. On the **Matters** screen, click <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-f8cf6402521f2ea220af941844d9bda08c7ab3ad%2Fbtn-create-new-matter.svg?alt=media" alt="Create New Matter" data-size="line">, name it `Practice — Review`, and click <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-06da11e3f9e42d7aac2d2fd2965d857a8d44640c%2Fbtn-create-matter.svg?alt=media" alt="Create Matter" data-size="line">.
2. On the empty <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-30913153ebd9cc9194606c644922feb649ae10a5%2Ftab-files.svg?alt=media" alt="Files tab" data-size="line"> tab, click the link **Just exploring? Load sample files to try BriefTech now.**

BriefTech loads a set of around twenty mixed documents and, as each one finishes processing, the **Organise** agent automatically works out its date and description — no action needed from you. Give it a moment to finish.

***

## Step 2 — Read what the AI produced

Open the <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-8f18f06a78c4d0bf6e51eac54ec7d3e5d2cdb8a2%2Ftab-review.svg?alt=media" alt="Review tab" data-size="line"> tab. This is your review area: one row per document, with the AI's **Date** and **Description** filled in.

Take a moment to read down the list the way you would on a real matter. Most rows will be right or nearly right — that's the point of the AI. You're looking for the few that need a human: a date that looks wrong, or a description that's too vague.

{% hint style="info" %}
**Note:** Every field you can edit here, and exactly what each accepts, is listed in [Document metadata fields](/reference/document-metadata-fields.md). The AI agent behind these values is the **Organise** agent.
{% endhint %}

***

## Step 3 — Correct a date

The AI often finds more than one date in a document — the date on the letterhead, a date mentioned in the body, a date in the filename — and it has to pick one. Sometimes it picks the wrong one. When it does, you usually don't need to retype anything: the other dates it found are one click away.

1. Find a row whose **Date** looks off, and double-click its **Date** cell.
2. If the AI detected more than one date, a short list of the **candidate dates** it found appears. Click the correct one.
3. If the date you want isn't in the list — or the document had none — just type it in; the cell is a plain text date editor, not a calendar.

Date and Description cells have no Save button — picking a date, pressing Enter, or clicking outside the cell saves your change.

***

## Step 4 — Sharpen a description

Now let's improve a description by hand.

1. Double-click any **Description** cell. An inline editor opens.
2. Rewrite it the way you'd want it to read in the index, then click outside the cell.

The row updates at once and your text turns blue — it is now a **manual override**. Hover the cell and a <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-b3e446d64b7bf9b7ecf24f801ef6b0e5046cfa99%2Ficon-lock.svg?alt=media" alt="locked" data-size="line"> padlock shows it's locked. That's an important promise: **re-running the AI's analysis won't overwrite a value you've set by hand.** You can correct a document today and re-run analysis on the rest of the matter tomorrow without losing your edit.

{% hint style="warning" %}
**Clearing a cell doesn't blank it out.** If you delete your text and click away, BriefTech **unlocks** the cell and keeps your current text — it removes the padlock rather than leaving the field empty, and it won't bring the AI's original suggestion back either. For a fresh AI suggestion, hand the field back to it (Step 7).
{% endhint %}

***

## Step 5 — Teach BriefTech your style, then let it do the rest

Editing every description by hand would defeat the point. Instead, edit just a couple in the style you want, then have BriefTech rewrite the others to match — this is **Refine Descriptions**.

1. Edit **two or three** descriptions by hand (double-click, type, press Enter). These are your **examples**. Two or three beat one, especially if your documents are mixed (say, letters and invoices).
2. Tick the checkbox on your edited example rows **and** on a few un-edited rows you want rewritten (the **targets**).
3. In the toolbar, click <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-7ca852ba9ed8e5cd335486f6f5aafe2a31996043%2Fbtn-refine-descriptions.svg?alt=media" alt="Refine Descriptions" data-size="line">. BriefTech rewrites each target to match the style of your examples and leaves your edited rows untouched.

{% hint style="info" %}
**Button greyed out?** The button stays greyed out until your selection includes at least one example (a row you've edited) **and** at least one target (a row you haven't). Hover it for the reason. Full details and troubleshooting: [Refine descriptions from examples](/how-to-guides/review/refine-descriptions-from-examples.md).
{% endhint %}

***

## Step 6 — Translate a description

If your matter mixes languages, BriefTech can translate a description in place. Let's translate one.

1. Hover over a **Description** cell — a row of action icons appears.
2. Click the <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-17c9d403849250e5f95b2b7fa28c719dd8d2ba70%2Ficon-translate.svg?alt=media" alt="translate" data-size="line"> translate icon and pick a language: **English**, **Bahasa Malaysia**, **Chinese (Simplified)**, or **French**.

The description is replaced with the translation.

{% hint style="warning" %}
**Translating overwrites the description and can't be undone.** The translation replaces the current text in place — there's no undo back to the earlier version, so if you need it, copy it first. To move on you can retype the description or re-run the AI to generate a fresh one. Translate also works on a row you've edited by hand (a blue, locked row), and using it there unlocks the row.
{% endhint %}

***

## Step 7 — Hand a field back to the AI (optional)

You're always in control of the balance between your edits and the AI's suggestions. Let's hand some fields back.

1. Hover the description you locked in Step 4, click the <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-b3e446d64b7bf9b7ecf24f801ef6b0e5046cfa99%2Ficon-lock.svg?alt=media" alt="lock" data-size="line"> padlock to unlock it, then click the <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-d3979c11bfb80ae4047a5e662bd57d0e92067573%2Ficon-regenerate-description.svg?alt=media" alt="Regenerate AI description" data-size="line"> sparkle button. The AI writes a fresh description for that document.
2. Tick a few other rows, right-click one of them and choose <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-5801b5a18cacf0b98098fb21259c49a5f8d8f5ac%2Fbtn-regenerate-description-date.svg?alt=media" alt="Regenerate Description &#x26; Date" data-size="line">, then click **Continue** to confirm. BriefTech re-runs the Organise agent on just those documents in the background, keeping any value you've locked — their rows show a placeholder while it works and fill in when it's done.

***

## Step 8 — Tidy the set with a label

A quick organising touch while you're here. Labels help you filter and group documents later.

1. Tick the checkbox on a few related rows. Bulk-action buttons appear in the toolbar above the table.
2. Click <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-4630e5f670063ccc041d3526128ac3a57b214876%2Ficon-label.svg?alt=media" alt="Apply labels" data-size="line">. Your practice matter has no labels yet, so type a name such as `Correspondence` and click **Create "Correspondence"** — the new label is ticked for you.
3. Click <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-0334e74f602bb9f3c1d50edb1d54ae80adaaa59b%2Fbtn-apply-flat.svg?alt=media" alt="Apply" data-size="line">.

The label now shows in the **Labels** column of every row you ticked.

That's a bulk edit — the same pattern applies collections (<img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-1eaec3f82ef44c0803b583e3902c107b2468a79c%2Ficon-add-to-collection.svg?alt=media" alt="Manage collections" data-size="line">) and, via the toolbar **Tools** menu, spreadsheet edits of dates and descriptions. For the full set of bulk edits, see [Bulk-edit metadata](/how-to-guides/review/bulk-edit-metadata.md).

***

## What you've accomplished

You've taken an AI-analysed matter and made it yours: corrected a date from the candidates the AI found, sharpened a description into a locked override, refined the rest from your own examples, translated one, handed fields back to the AI, and labelled a group — with no Save button for any of your edits.

***

## Where to go next

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Index Documents</strong></td><td>Build the Document Index: the structured, ordered index that becomes the spine of your court bundle.</td><td><a href="/how-to-guides/index.md">Index Documents</a></td></tr><tr><td><strong>Review Documents</strong></td><td>The human-review pass: verify and correct what the AI produced before building the index.</td><td><a href="/how-to-guides/review.md">Review Documents</a></td></tr><tr><td><strong>Document metadata fields</strong></td><td>The document fields you can edit in the Review tab and their accepted values.</td><td><a href="/reference/document-metadata-fields.md">Document metadata fields</a></td></tr><tr><td><strong>Document classes</strong></td><td>The classes BriefTech's AI chooses from when it classifies a document, what each one covers, and how to filter a matter by class.</td><td><a href="/reference/document-classes.md">Document classes</a></td></tr><tr><td><strong>Refine descriptions using your own edits as examples</strong></td><td>Edit a few descriptions the way you want them, then have BriefTech rewrite the rest to match.</td><td><a href="/how-to-guides/review/refine-descriptions-from-examples.md">Refine descriptions using your own edits as examples</a></td></tr><tr><td><strong>Translate document descriptions</strong></td><td>Translate document descriptions into Bahasa Malaysia, Chinese (Simplified), French, or English.</td><td><a href="/how-to-guides/review/translate-document-descriptions.md">Translate document descriptions</a></td></tr><tr><td><strong>How AI analysis works: agents and playbooks</strong></td><td>What agents and playbooks are, and what they extract.</td><td><a href="/concepts/how-ai-analysis-works.md">How AI analysis works: agents and playbooks</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.brieftech.ai/get-started/review-an-ai-analysed-matter.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
