# Marking up Schedules / Annexes A schedule comes at the end of a piece of legislation. It is a separate from the main content and has a separate heading, subheading and table of contents. A schedule has a heading, such as 'Schedule 1', 'First Schedule', or sometimes just 'Schedule'. Some schedules also have a subheading, such as 'Laws Amended'. The pattern for Schedules / Annexes is as follows: * On a new line, the keyword: `ANNEXURE`, `APPENDIX`, `ATTACHMENT`, or `SCHEDULE` * On the same line, after a space, the name of the element, e.g. `Annex` or `Schedule 1` * On the next line, optionally, an indent and `SUBHEADING`, followed by a space and the subheading, e.g. `Laws repealed` * Below the main heading, indented, the content of the Schedule / Annex. {% hint style="info" %} Don't use italics or bold markup on any headings, including in Schedules / Annexes. {% endhint %} ### Examples ``` ANNEXURE Annex SUBHEADING Conclusions of the subsidiary body on scientific, technical … PARA 1. First paragraph in the Annex. ``` ``` ANNEXURE Annex SUBHEADING List of elements of methodological guidance Methodological approaches for identifying, monitoring, and assessing … SUBPARA (a) Recognize and fully include traditional knowledge, … ``` --- # 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://docs.laws.africa/markup-guide/marking-up-schedules-annexes.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.