How a matter moves through BriefTech
The staged pipeline and the two workstreams that run alongside it.
BriefTech organises everything around a single, repeatable pipeline for a matter. Almost every feature belongs to one stage of that pipeline or supports it, so once you have the shape of the pipeline in mind, the rest of the platform is much easier to place.
Why the work is staged: Upload → Review → Index → Export
A matter moves through four stages, each with a clear job:
Upload — you bring your documents in and BriefTech prepares them for use.
Review — you check and correct the details it has extracted — dates and descriptions.
Index — you build the Document Index: the ordered, structured spine of the matter.
Export — you turn that index into a deliverable — a paginated court bundle, or the Document Index as a Word or Excel file.
Separating the work this way means each stage has a single focus. You are never asked to order documents before they are ready, or to export before the index reflects what you want.
Organising your documents — into folders, with labels, or as collections — is not a stage of its own. You can do it from the Files or the Review tab at any point. Folders and collections also shape what your index and exports contain: you can group the index by folder and mirror that structure in a ZIP export, and a collection scopes both the index and the bundle built from it.
If you have come from the BriefTech website, it presents this same journey as six stages — Files, Orientation, Review, Structuring, Index, and Production. That is the full arc from evidence to bundle, including the parts BriefTech handles for you automatically. They map onto the four tabs you work in: Files (Orientation — the automatic reading and mapping of your documents — happens here), Review, Index (Structuring, ordering the evidence into the bundle, is part of building the index), and Export (Production — pagination, bookmarks and volumes). Same pipeline, described at two levels: six stages of what happens to your evidence, four tabs you drive.
The two workstreams that run alongside: AI analysis and collaboration
Not everything fits neatly into a stage. Two capabilities run alongside the whole pipeline, available at any point. AI analysis reads your documents and extracts structured information — document types, dates, and summaries. Collaboration lets you share the matter with colleagues and control who has access to it.
These are workstreams rather than steps: you might run AI analysis right after upload, or return to it once you have reviewed your documents, and you can invite a colleague at any time.
Why each stage builds on the one before
The order of the pipeline reflects real dependencies. A document must finish processing before there's anything to review: only once it's ready does the AI extract its dates and descriptions, and reviewing is where you check and correct those. Review feeds the index, because the dates and descriptions you confirm become the content of your Document Index. And the index drives export, because the bundle and the exported index are produced directly from the order and structure you set.
Working with the pipeline rather than against it keeps each stage's output trustworthy for the next.
For what happens to each document between upload and the moment it can be used, see The document lifecycle: from upload to ready.
What a matter holds
A matter is the container for everything that belongs to a single case: the documents and their metadata, the folders, labels and collections you organise them into, the facts you capture from them, the Document Index you build, the bundles you export, and the colleagues you have shared it with. Sharing a matter shares everything in it. Your credits and storage limits are set at the account level and apply across all your matters, not just this one.
Related
Last updated
Was this helpful?