> For the complete documentation index, see [llms.txt](https://docs.itconductor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itconductor.com/user-guide/reporting/creating-reports.md). # Creating Reports ### Create Ad hoc Reports Follow the instructions to create or test new reports that you need on a one-time basis. You may refer to the [Report Elements](/user-guide/reporting/report-elements.md) section for further guidance on creating reports. 1. Navigate to **My Objects → My Reports**.

Figure 1: My Objects Menu Options in IT-Conductor

2. Click on the **“+”** icon.

Figure 2: Created Reports in IT-Conductor

3. You will be prompted with this screen where you need to fill in the following details: * **Name** and **Description** * **Time Windows Begin/End** - Date for when the Report is ON (active) * **Owner** - Override instance owner; the schedule's owner is used by default. * **Removal Age** - Override the removal age of the instance. If not specified, use the definition's removal age. If the definition removal age is not specified, use the number of days since the last scheduled run. * **Output Type**, **Page Size**, and **Page Margin** for the report’s format * **Delivery Recipients**, **Sender**, and **Subject**

Figure 3: Create Report Wizard in IT-Conductor

To create a Report based on a previously existing template, select a file from the Git Repository list. Then select a report from the Report File list. The list of reports depends on the file you selected from the Git repository.

Figure 4: Selecting a Template from Git Repository

Figure 5: Selecting a Report from Report Files

4. Click on the **"+"** or **Save** icon to save and finish. --- # 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://docs.itconductor.com/user-guide/reporting/creating-reports.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.