> 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/readme.md). # Brief Tech Overview What BriefTech is, how it works, and where to start. BriefTech is an AI production infrastructure for dispute lawyers. It processes raw evidentiary files: PDFs, emails, spreadsheets — into court-ready work product: indexes, court bundles. ## The four-step pipeline Every matter in BriefTech follows the same pipeline: | Step | Tab | What happens | | -------------- | -------------- | ------------------------------------------------------------------------------------------------ | | **1 — Upload** | Files | Documents are converted to PDF, OCR'd where needed, and added to the search index automatically. | | **2 — Review** | Review | You correct document metadata: dates and descriptions. | | **3 — Index** | Index | You build the Document Index — ordered, structured, numbered. | | **4 — Export** | Index → Export | You generate a paginated PDF court bundle, or export the Document Index as DOCX/Excel. | BriefTech runs two workstreams in parallel throughout your matter: **AI analysis** — For the agents you switch on in a matter, BriefTech extracts key facts and classifies documents automatically. The output is a structured, reviewable layer of work your team didn't have to do manually. **Human review** — Your team works directly on the AI output: accepting, correcting, and refining until the work product is court-ready. Share a matter with colleagues who have a BriefTech account, assign permissions, and collaborate in real time. {% hint style="info" %} **In short:** The AI handles the extraction and classification. The lawyers own the judgment calls. {% endhint %} ## Key concepts | Concept | What it is | | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Matter** | A single case. All documents and exports for that case live here. | | **Document Index** | The structured, ordered index that becomes the spine of your court bundle. | | **Credits** | The unit BriefTech uses for billing, based on a document's page count. A document is charged once per matter, at 1 credit per 50 pages (minimum 1), the first time it is committed — for example by exporting it or adding it to a court bundle. Uploading, processing, and running AI agents are free. For exactly which actions charge, see [Credit costs and pricing](/reference/credit-costs-and-pricing.md). | | **Collection** | A named subset of documents within a matter, used to segment the document set. | | **Preset** | A built-in Document Index configuration (columns, serial numbers, bundle settings) applied in one click. | ## How this help centre is organised The help centre is split into four sections — pick the one that matches what you need right now: * **Get Started** — guided, end-to-end walkthroughs you follow once to learn the shape of the product. * **How-To Guides** — short, goal-oriented steps for getting a specific job done. Grouped into eight sections that follow the flow of a matter: Upload Files, Process Files, Organise Documents, Review Documents, Index Documents, Build Bundles, Export Files, Manage Account. * **Reference** — exact fields, limits, settings, and formats, as a single flat list. * **Concepts** — background reading about how and why BriefTech works the way it does. {% hint style="success" %} **New to BriefTech?** Start with the [tutorial](/get-started/your-first-matter.md) — about ten minutes, using sample files, no real case data needed. {% endhint %} The structure follows the [Diátaxis](https://diataxis.fr) framework: each page is written as exactly one kind of content (tutorial, how-to, reference, or concept), so you always know what you're getting. *** ## Need more help? Contact the BriefTech support team at . *** ## Where to go next
Your First MatterA guided, end-to-end first run — take a practice matter from sample files all the way to a downloaded court bundle.Your First Matter
How a matter moves through BriefTechThe staged pipeline and the two workstreams that run alongside it.How a matter moves through BriefTech
How AI analysis worksWhat agents and playbooks are, and what they extract.How AI analysis works: agents and playbooks
--- # 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/readme.md?ask=&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.