> 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/how-emory-pro-works.md).

# How Emory Pro Works -

A typical Emory Pro workflow starts with an asset. The user identifies the asset by scanning a QR code, Barcode, VIN, asset ID, or by selecting it from the asset list. The inspection flow is based on the asset type and inspection type configured by the organisation. This means each workflow can be adapted to the way your business operates, without developer involvement.

During the inspection, the user can fill in structured fields, capture photos and videos, add comments, add Damage Markings on photos or Asset Blueprints, and collect signatures if required. Once the inspection is completed, Emory Pro generates an Inspection Report, available as a PDF and a secure digital link.

Every completed inspection becomes part of the asset’s history.

**Mobile App and Web App** Emory Pro is used across two main interfaces.\
\
**Mobile app** The mobile app is used by field teams, inspectors, drivers, warehouse workers, logistics teams, subcontractors, and external partners. It is used to:

* Start and complete inspections
* Scan assets
* Capture photos, videos, and documents
* Add damage markings
* Work offline
* Complete assigned tasks
* Sync inspection data once connectivity returns

The mobile app is available for [IOS](https://apps.apple.com/de/app/emory-pro/id6443503759) and [Android](https://play.google.com/store/apps/details?id=pro.emory.inspections\&gl=DE\&pli=1). The mobile app supports full offline functionality, including access to the complete asset inventory, inspection completion, and media capture. Data syncs automatically when connectivity is restored.

[**Web App**](https://www.webapp.emory.pro/login) The web platform is used by administrators, office teams, supervisors, and managers. It is used to:

* Manage assets and containers
* Configure inspection workflows and checklists
* Create users and roles
* Review inspection reports
* Monitor asset status
* Track inspection activity
* Manage operational settings
* View dashboards and statistics

Together, the mobile app and web platform help field and office teams work from the same operational data.


---

# 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/how-emory-pro-works.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.
