> For the complete documentation index, see [llms.txt](https://docs.emory.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emory.pro/emory-pro-overview/the-problem-emory-pro-solves.md).

# The problem Emory Pro solves -

In many operations, inspection evidence is fragmented.\
Photos are stored in WhatsApp.\
Forms are completed on paper.\
Reports are created manually in Excel. \
Damage is noted in text without photos, timestamps, or location data.\
Handover records are incomplete, unsigned, or difficult to trace.

When something goes wrong, teams often struggle to answer simple questions: \
  **Who inspected this asset?**\
  **What was its condition before handover?**\
  **When was the damage recorded?**\
  **Where is the photo evidence?**\
  **Who accepted the asset?**\
  **Which report should we trust?**

Emory Pro brings all Inspection Data, Media, Signatures, Reports, and Asset history into one structured system. This helps teams reduce disputes, improve accountability, and create a single source of truth for every asset.

{% embed url="<https://emory.pro/features/>" %}


---

# 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://docs.emory.pro/emory-pro-overview/the-problem-emory-pro-solves.md?ask=<question>&goal=<endgoal>
```

`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.