> For the complete documentation index, see [llms.txt](https://manual.harpe.io/start/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.harpe.io/start/manual/incidents/viewing-an-incident.md).
# Viewing an Incident
The specific details for an incident can be viewed by clicking into the incident from the table. From here, the report for the incident can be viewed.
Incident view
## **Incident Report**
The incident report can be viewed by clicking the Incident Report button from a specific incident's page. Each incident should undergo an appropriate investigation which should be recorded on this page.
Incident report view
**Incident Description**
An overview of the incident and its events.
**Business Impact**
The overall impact the incident had on your organisation.
**Root Cause Analysis**
Analysis of the incident to derive its root cause.
**Resolution**
What steps have been taken by the organisation to rectify this incident, ensuring it will not occur again.
**Authorities Notified**
The authorities notified of the incident - For example, the police, or ICO.
**Conclusion**
A brief summarisation regarding the incident and its resolution.
---
# 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://manual.harpe.io/start/manual/incidents/viewing-an-incident.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.