> 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/what-is-emory-pro.md).

# What is Emory Pro -

With Emory Pro, teams can:

* Perform digital inspections on mobile or tablet
* Capture Photos, Videos, Comments, and Documents
* Annotate damage directly on photos (Photo Doodle)
* Add Damage Markings on Asset Blueprints
* Capture digital signatures during handovers
* Generate PDF inspection reports instantly
* Track the full history of every asset
* Scan QR codes, Barcodes, VINs, or Asset IDs
* Work fully offline and sync automatically when connectivity is restored
* Monitor assets, reports, and inspection status from the web dashboard

Emory Pro is designed for real operational environments where teams work in yards, warehouses, depots, ports, workshops, customer sites, and field locations.


---

# 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/what-is-emory-pro.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.
