> For the complete documentation index, see [llms.txt](https://kitehouse.co.uk/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kitehouse.co.uk/docs/staff/reports/creating-a-report.md). # Creating a Report {% embed url="" %} A report or an incident holds key information on the context of an incident. To create a report, follow the steps below: {% stepper %} {% step %} ### Click the 'Create Report' button in the Reports tab In the header, click the **'Create Report'** button beside the site name and your profile. {% endstep %} {% step %} ### Creating a Report In the pop out, select an incident category, which students are involved, and the source of the incident. {% hint style="success" icon="lightbulb" %} **Tips** * You can select all of the students shown in the search bar by clicking the ' **Add All Matches'** button. * For multiple students, you can tick the checkbox ' **Raise one job per person'** to create individual reports for all students assigned. {% endhint %} Once done, click **'Create'** to save your report. {% endstep %} {% step %} ### Fill out the Incident Details Once the report is created, Kitehouse will assign an **incident ID** (ex: `I-0001`) to your report and directs you to the incident details. In the incident details, you can add more context to the report by assigning a staff member, adding a description, adding more students/staff that isn't added on the list, attachments and comments in the incident. {% hint style="warning" %} Features may be restricted based on your permissions configured by your site administrator. {% endhint %}

{% endstep %} {% endstepper %} ## Updating the Incident Pipeline To move an incident from one status to another, simply click the status you want the incident to move to. {% hint style="info" %} For incident categories with 2 or more terminal statuses, a dropdown will be shown with all of the options. {% endhint %}

--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://kitehouse.co.uk/docs/staff/reports/creating-a-report.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.