> 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="<https://player.mediadelivery.net/embed/619136/65bda506-a564-4897-9f00-c253092b24bf?autoplay=false&loop=false&muted=false&preload=true&responsive=true>" %}

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 '<i class="fa-layer-plus">:layer-plus:</i> **Add All Matches'** button.
* For multiple students, you can tick the checkbox ' <i class="fa-square-check">:square-check:</i> **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 %}

<figure><img src="https://3602476689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpWzphhnllUlrdiqcsZC%2Fuploads%2FEDK7gOUPiORPQk2GFTtY%2FKitehouse%20Docs%20(12).png?alt=media&amp;token=8bb0f086-ba43-40c9-80a5-914cd56f1e7c" alt=""><figcaption></figcaption></figure>
{% 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 %}

<figure><img src="https://3602476689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpWzphhnllUlrdiqcsZC%2Fuploads%2FugQS8YOmKNoZ6wsu2ySm%2FKitehouse%20Docs%20(11).png?alt=media&amp;token=b6021455-246b-442a-b03b-5ddaa1074591" alt=""><figcaption></figcaption></figure>


---

# 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/creating-a-report.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.
