> 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/prepare-disclosure-list.md).

# Prepare a List of Documents for Disclosure

Turn a set of documents into a finished disclosure package — a ZIP with Word and Excel indexes and every file renamed by serial, date and description.

Welcome. In this tutorial we'll prepare a disclosure package — the kind you produce when you need to share a set of documents with the other side, a court, or a client. By the end you'll have a single ZIP archive containing:

* a **Word file** with the index table (one row per document: serial number, date, description),
* an **Excel file** listing the same documents as a spreadsheet, with its own fixed set of columns, and
* every **document file** renamed to `<serial>-<date>-<description>.<ext>`.

We'll follow the workflow from upload to export in order. The whole run takes around fifteen minutes.

{% hint style="info" %}
**Note:** This is a learning walkthrough with one fixed path. Once you've completed it, the **How-To Guides** show how to handle each task on real matters, and the **Reference** pages cover every available option in detail.
{% endhint %}

***

## Before you start

**Before you open BriefTech**, prepare a small set of practice documents on your computer — five to ten files is enough to see the full workflow. They can be PDFs, Word documents, emails, or any other supported file type mixed together.

***

## Step 1 — Create the matter and upload your documents

A **matter** is BriefTech's container for a single case or transaction.

1. Sign in to BriefTech. You'll land on the **Matters** screen.
2. 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">.
3. In **Input Matter Reference**, type `Practice — Disclosure List`.
4. 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">.

BriefTech opens the new matter on its <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, showing an empty upload zone.

Now upload your practice documents:

5. Drag your files into the upload zone, or click <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-8fb0db73f10e5ba0926bea47de89141576f6bf4f%2Fbtn-select-files.svg?alt=media" alt="Select files" data-size="line"> and pick them from your file picker.
6. BriefTech begins uploading and processing each file immediately.

{% hint style="success" %}
**Uploading a folder structure?** If your documents are organised in folders, you can drag the whole folder in — BriefTech remembers which folder each file came from.

1. Drag the whole folder into the upload zone.
2. Later, in the Document Index, select <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-b912cd1830c2b96fcb2e3a555cd9d809382cf685%2Fbtn-apply-preset.svg?alt=media" alt="Apply preset" data-size="line">, then **Generate index headings → Group by folder** to turn each folder into a **header** that groups the disclosure list by category.

See [Organise documents into folders](/how-to-guides/organise/organise-documents-into-folders.md) for the full guide.
{% endhint %}

{% hint style="info" %}
**Documents with processing issues:** If a document shows an error or warning icon, hover over it to read the message. For a persistent processing error, right-click the row and choose <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-d0e6b89a4a252f16acc7ad2ee31373e54f789ddd%2Fbtn-reprocess-selection.svg?alt=media" alt="Re-process Selection" data-size="line"> — see [Reprocess a failed document](/how-to-guides/process/reprocess-failed-document.md) for a full guide.
{% endhint %}

***

## Step 2 — Let BriefTech process the documents

BriefTech automatically extracts the date and a description from each document as it uploads. This runs in the background.

1. Click 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.
2. Watch the **Document Date** and **Document Description** columns fill in. A spinner on a row means that document is still being processed.

Wait until every row shows a date and a description before continuing.

{% hint style="info" %}
**How does BriefTech extract dates and descriptions?** Each document is processed by BriefTech's AI, which reads its text, looks at the page itself when an image of it is available, and identifies the most likely date and a short summary. To understand how this works — and what to do if results are consistently unexpected — see [How AI analysis works: agents and playbooks](/concepts/how-ai-analysis-works.md).
{% endhint %}

***

## Step 3 — Review and correct dates and descriptions

The index table is built from the **Document Date** and **Document Description** fields, and these same values appear in the renamed filenames. Reviewing them now ensures the disclosure package is accurate. The one exception is a document whose file name contains a date in a form BriefTech recognises, such as `2024-03-01`: the index and the renamed file use that date instead, so editing its **Document Date** here won't change either.

**Correct a date:**

1. Find a row whose **Document Date** looks wrong or is missing.
2. Double-click the **Document Date** cell to open the inline date editor. It is a free-text editor, not a calendar: if BriefTech found more than one date in the document, a list of those dates appears for you to pick from, or you can type a date directly.
3. Click outside the cell to confirm.

**Correct a description:**

4. Find a row whose **Document Description** you want to improve.
5. Double-click the **Document Description** cell. An inline editor opens.
6. Edit the text, then click outside to confirm.

The value turns blue to show it is locked as your manual override. Re-running the AI's analysis won't overwrite a value you've set by hand.

{% hint style="success" %}
**Using the filename as the description:** If a document's existing filename is already the correct description, hover its **Document Description** cell and click the <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-34b8a19f87e0bfb744a6084aee42e8859d61b327%2Ficon-text-snippet.svg?alt=media" alt="Use file name as description" data-size="line"> icon to apply it directly. This icon shows only on hover, and only while the description hasn't been set by hand — once you've entered or accepted a description, it disappears.

A file name applied this way doesn't count as a hand edit: it doesn't turn blue, and re-running the AI's analysis — including <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"> — can replace it.
{% endhint %}

{% hint style="info" %}
**Verifying against the source document:** Click a document's row to open a side-panel preview without leaving 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.
{% endhint %}

{% hint style="success" %}
**Bring descriptions into a consistent style.** For many documents, use <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">:

1. Edit at least one description into the style you want (one example works; a few give better results).
2. Tick that row together with the documents you want to restyle.
3. Select <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"> in the toolbar.

BriefTech rewrites the unedited descriptions to match your examples. See [Refine descriptions using your own edits as examples](/how-to-guides/review/refine-descriptions-from-examples.md) for the full guide.
{% endhint %}

***

## Step 4 — Configure serial numbering, date format, and sort order

Serial numbers are assigned in the <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-320692e120077fab01f6944df1edd4eec4881a4c%2Ftab-index.svg?alt=media" alt="Index tab" data-size="line"> tab. BriefTech numbers documents from 1 by default (1, 2, 3, …). The serial numbers are plain sequential numbers and are not zero-padded. See [Serial numbers and date formats](/reference/serial-numbers-and-date-formats.md) for the full reference.

1. Click the <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-320692e120077fab01f6944df1edd4eec4881a4c%2Ftab-index.svg?alt=media" alt="Index tab" data-size="line"> tab.
2. To change where numbering starts, hover the **S/No.** column header and click the <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-67750f413ca1f83135a9a763cdb9d9fb5547e4e1%2Ficon-drive-file-rename-outline.svg?alt=media" alt="edit" data-size="line"> icon that appears to open its header editor, then set **Initial Serial Number**.
3. To change the date format, open the **Date** column's header editor the same way and choose a **Date Format Preset**. The options are labelled by example date (for example `01/01/2026`), not by format code.
4. To sort the list chronologically before numbering, select <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-b912cd1830c2b96fcb2e3a555cd9d809382cf685%2Fbtn-apply-preset.svg?alt=media" alt="Apply preset" data-size="line"> in the toolbar, hover over **Sort all sections**, and choose **Date**. See [Sort documents in the Document Index](/how-to-guides/index/sort-documents-in-index.md) for the full guide.

{% hint style="info" %}
**Adding headers to group documents.** To show groups under category headings (for example, "Correspondence", "Contracts", "Invoices"):

1. Hover over the row where a group should start — an **Add heading:** area appears.
2. Select <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-d8d2d1750e97e635403e5961cfa443f3d3db3baf%2Fbtn-heading.svg?alt=media" alt="Heading" data-size="line"> and enter a title.
3. Drag documents beneath the heading.

See [Manage headings in the Document Index](/how-to-guides/index/manage-index-headings.md) for the full guide.
{% endhint %}

Switch to <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-6fa665239290710351c4bd5664b5462cc2c59fea%2Fchip-preview-mode.svg?alt=media" alt="Preview" data-size="line"> mode to confirm that serial numbers, dates, and descriptions look correct before exporting.

***

## Step 5 — Export the complete disclosure package

BriefTech produces the Word index, the Excel index, and the renamed files in a single export.

1. In the <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-320692e120077fab01f6944df1edd4eec4881a4c%2Ftab-index.svg?alt=media" alt="Index tab" data-size="line"> tab, click <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-298440d7fe88cf38c80144c49e84fc629f762518%2Fbtn-download-files.svg?alt=media" alt="Download Files" data-size="line"> in the toolbar. The **Download Files** panel opens on the right.
2. Under **Export Type**, tick **All Files**. This produces a ZIP archive containing the renamed document files together with the Word and Excel index tables.
3. Under **File Naming Convention**, select **Serial Number + Date + Description**.
4. Leave **File Type**, **Word Separator in File Names**, and **Folder Export** at their defaults for now.
5. Click <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-faa8e13bf4e50e240ff9bb371fb29c2aaa59248b%2Fbtn-export.svg?alt=media" alt="Export" data-size="line">. If any documents are being exported for the first time, BriefTech will show a confirmation dialog listing the credit cost — review it and confirm to proceed.
6. BriefTech queues the job and shows **Export started!**. The job keeps running if you move elsewhere.
   * When it finishes, BriefTech emails you a link to download the ZIP.
   * The finished ZIP is also listed in the **Download Files** panel when you return to the **Index** tab.
   * If you stay on the Index tab, BriefTech shows **Your export is ready to download!** when it's ready.
   * While the job runs, the <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-a2c6e257a40e2d93f4e0f813e521b1bd444d9f0c%2Ficon-pending-actions.svg?alt=media" alt="background jobs" data-size="line"> icon in the top bar pulses; click it to open **Background Jobs** and check the job's status. See [Background Jobs](/reference/background-jobs.md) if the job appears stuck.
7. Click the <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-d47c0bf09b2f73cb89b87ad94a6dbff03a65bda4%2Ficon-cloud-download.svg?alt=media" alt="download" data-size="line"> download icon once the job completes.

{% hint style="warning" %}
**Exporting spends credits.** Credits are charged at 1 credit per 50 pages (minimum 1 credit per document); documents you have exported before are free to re-export.
{% endhint %}

{% hint style="success" %}
**Customising the export:** This tutorial uses the defaults, which include a **File Type** of **Searchable PDF**. To export files in their original format or preserve your folder structure inside the ZIP, see [Export formats and options](/reference/export-formats-and-options.md) for the full settings reference.
{% endhint %}

Open the ZIP and check that it contains:

* a Word file with the index table,
* an Excel file listing the documents as a spreadsheet, and
* each document file named in the format `1-2024.01.15-email from alice to bob.pdf` (or similar).

***

## What you've accomplished

You took an empty matter and:

* uploaded a set of documents and let BriefTech extract dates and descriptions automatically,
* reviewed and corrected the metadata so the list is accurate,
* configured serial numbering, date format, and sort order in the Document Index, and
* exported a single ZIP containing the Word index, the Excel index, and every document renamed by serial number, date, and description — ready to share as a complete disclosure package.

***

## 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>Export the Document Index as a Word or Excel file</strong></td><td>Export your Document Index as a Word or Excel file.</td><td><a href="/how-to-guides/export/export-index-word-pdf-excel.md">Export the Document Index as a Word or Excel file</a></td></tr><tr><td><strong>Sort documents in the Document Index</strong></td><td>Sort documents within Document Index sections by date, file name, or description.</td><td><a href="/how-to-guides/index/sort-documents-in-index.md">Sort documents in the Document Index</a></td></tr><tr><td><strong>Manage headings in the Document Index</strong></td><td>Add, rename, move, sort, indent, and delete headings in the Document Index, or generate them automatically from your folder structure.</td><td><a href="/how-to-guides/index/manage-index-headings.md">Manage headings in the Document Index</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>Serial numbers and date formats</strong></td><td>Serial numbering options, date format presets, and sort order for the Document Index.</td><td><a href="/reference/serial-numbers-and-date-formats.md">Serial numbers and date formats</a></td></tr><tr><td><strong>Export formats and options</strong></td><td>Output formats and the settings for exporting the Document Index.</td><td><a href="/reference/export-formats-and-options.md">Export formats and options</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>Background Jobs</strong></td><td>Status indicators, columns, and row actions in the Background Jobs dialog.</td><td><a href="/reference/background-jobs.md">Background Jobs</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><tr><td><strong>The document lifecycle: from upload to ready</strong></td><td>What happens to a file between upload and the moment it can be used.</td><td><a href="/concepts/the-document-lifecycle.md">The document lifecycle: from upload to ready</a></td></tr><tr><td><strong>How credits work</strong></td><td>What credits measure and how your balance is calculated.</td><td><a href="/concepts/how-credits-work.md">How credits work</a></td></tr><tr><td><strong>Credit costs and pricing</strong></td><td>What charges credits, what is free, how the charge is calculated, and what credits cost to buy.</td><td><a href="/reference/credit-costs-and-pricing.md">Credit costs and pricing</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/prepare-disclosure-list.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.
