> 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.md).

# Reports

<figure><img src="https://3602476689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpWzphhnllUlrdiqcsZC%2Fuploads%2FMkhYLSSKtLflWn2ZU92m%2FKitehouse%20Docs%20(16).png?alt=media&amp;token=553b01f3-3fe2-41ee-a9e9-92d64e83d789" alt=""><figcaption></figcaption></figure>

The reports tab holds all of the incidents recorded in your site. From a simple lockout to a full investigation, all of these are recorded to Kitehouse.

For more articles regarding reports, click here:

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><p><i class="fa-file-plus">:file-plus:</i></p><p><strong>Creating a Report</strong><br>A report or an incident holds key information on the context of an incident.</p></td><td></td><td><a href="https://kitehouse.co.uk/docs/staff/reports/creating-a-report.md">Creating a Report</a></td></tr></tbody></table>

## Filtering Incidents

You can search for a specific incident by either:

* Inputting the **incident ID** (ex: `I-0001`) in the search bar
* Filter incidents to a specific student based on their **Student ID** and/or between **two dates**.
* Filter incidents that are assigned to you and/ocurrently open.

## Recommended Incidents

In the top of the incidents list, Kitehouse will recommend incidents that requires immediate attention. These are highlighted in yellow.

For incidents that haven't got an activity recorded, Kitehouse will show a callout stating that it hasn't got any activity within a certain amount of days.


---

# 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://kitehouse.co.uk/docs/staff/reports.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.
