# Creating cross-references {% embed url="" %} Clause9 distinguishes between three different kinds of cross-references: * To a clause within **the same clause file** * To another clause **within the same document** * To a document **within the same binder** {% hint style="info" %} Cross-references to a document within the same binder are also the topic of [another article](/binders/cross-references-between-documents.md). {% endhint %} ## Cross-references within the same clause file {% code overflow="wrap" %} ``` 1. Alpha 2. Beta * element 1 * element 2 * element 3 ``` {% endcode %} ### **Numbered sub-clause** `§number` is used to refer to a numbered sub-clause within the same clause file. For example, use `§2` to refer to `2. Beta`. In the document, it will say *Clause 2*. Under the *reference styling settings*, you can change the word used for “Clause” in the document (e.g. “Article” or “Section”). ### **Clause as a whole** `§this` is used to refer to the current numbered subclause. `§this-title` refers to the title of the entire clause. In the above example, if you were to insert `§this` into 2. Beta, the reference in the document would show as *this Clause 2.* By inserting `§this-title` into `* element 1`, Clause9 will convert the code to *this Clause 2* since *Clause 2* is the associated clause title. If the title is currently not visible, an error will appear. ### **Bullets** If you created a regular bullet list (using asterisks), referring to the previous bullet is done with the command `§*-`, the next bullet with `§*+` and the current bullet with `§*`. More information on how to create enumerations can be found [here](/clauses/enumerations.md). ## Cross-references within the same document or binder There are two different methods of cross-referencing: * One-time reference to another clause using cross-tags * Content-based reference to another clause using concepts This type of cross-reference will work both when the target clause is located in the same document and when it is located in another document of the same binder. ### **Cross-tags** This allows you to insert a reference to another clause using its cross-tag. In order to insert a cross-tag, first, navigate to the clause the reference should be directed to. The cross-tag-name is assigned under cross-tags and entered by hitting the enter key.
Now, the cross-tag can be inserted in the clause content body by typing `§cross-tag-name` (e.g. `§this-is-the-cross-tag-name`). ### **Concepts** This command allows you to insert a reference to the first clause in the document that implements a specific concept. Concepts are implemented under the links tab of a clause.
In order to insert the reference, type `§#concept` (e.g. `§#client`). It is highly prefereable to use cross-tags to insert cross-references. Unless there is a good reason to use a concept (e.g. the target clause already implements a certain existing concept), cross-tags should be used. Cross-tags are much faster (in terms of document loading time) and do not require a separate file to be created in the clause library. ### Cross-references to another document in the binder Inserting a cross-reference to another **document** in the binder is very similar to inserting a cross-reference to a clause. A document can contain cross-tags or implementing links to concepts much like a clause can. In the *Binder* panel, click the *Properties* button at the button and then click the target document (the document you would like to refer to) in the pop-up menu.
Now you will be able to edit that document’s properties. Insert a cross-tag (or an implementing link to a concept), similar to [creating a cross-reference to another clause](#clause), and save the document by clicking *save in library* or *update adhoc doc* (as relevant). ### When to use concepts and when to use cross-tags? Which of the two approaches you should use, mainly depends on the question whether you are already using that concept as a defined legal term in the document. If that is not the case, then it’s much faster to use a cross-tag reference, as this avoids that you have to create a new concept. It also avoids that you litter your database with single-use concepts. Furthermore, cross-tags are a lot easier to process for Clause9 so especially when you are working in long, complex documents, performance will be significantly increased if you primarily rely on cross-tags as opposed to concepts. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.clause9.com/clauses/how-to-clauses/creating-cross-references.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.