> For the complete documentation index, see [llms.txt](https://docs.statuspal.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.statuspal.io/platform/incidents-and-maintenance/reporting-an-incident.md).

# Reporting an Incident

As mentioned earlier, there are [many ways to report an incident](/platform/incidents-and-maintenance.md#ways-an-incident-can-be-created). This is how to do it via the StatusPal Admin UI.

### Understanding the fields for reporting an incident

<div align="left"><figure><img src="/files/2Orndt3IGFiZVg7cxxK0" alt="" width="563"><figcaption></figcaption></figure></div>

* **Title**: Add a short, descriptive title summarizing the incident.
* **Incident Type**: Select the type of incident (e.g., Minor incident, Major incident) to indicate its severity and impact level.
* **Starts At / Ends At**: Specify when the incident began and, if applicable, when it is expected to or has already ended.
* **Affected Services**: Choose the impacted services from the list. You can select one or multiple services.
* **Private Notes**: Include internal notes or sensitive details, such as troubleshooting steps or resolution context. These notes are only visible to team members with Admin UI access.
* **Initial Update**: Provide an update for subscribers describing the nature of the incident.
* **Type**: Define the type of issue.
* **Description**: Add more context or detailed information about the incident. This field supports Markdown for formatting.
* **Tweet**: Check this box to send an update via Twitter.
* **Notify Subscribers**: Check this box to notify subscribers via email, SMS, or other configured channels.