> 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/how-to-guides/organise.md).

# Organise Documents

Shape your document set before review: sort documents into folders, label them, group them into collections, and remove duplicates.

* [Organise documents into folders](/how-to-guides/organise/organise-documents-into-folders.md) — Create folders and move documents into them to mirror your case structure.
* [Apply labels to documents](/how-to-guides/organise/apply-labels-to-documents.md) — Create colour-coded labels and apply them to documents to mark relevance, privilege, or any category you need.
* [Group documents into a collection](/how-to-guides/organise/group-documents-into-collection.md) — Create a named collection to scope analysis or exports to a sub-set of the matter.
* [Find and remove duplicate documents](/how-to-guides/organise/find-remove-duplicates.md) — Detect near-identical documents and remove redundant copies before review.

***

**Next step:** once your document set is organised, [review the AI's work](/how-to-guides/review.md) — check and correct the extracted dates and descriptions.


---

# 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/how-to-guides/organise.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.