> 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/why-teams-use-emory-pro.md).

# Why Teams Use Emory Pro

Teams use Emory Pro to reduce manual work, improve inspection quality, and create reliable operational evidence during inspections, handovers, and asset movements.

Key benefits include:

* Reduced paperwork and manual reporting
* Fewer missing photos, incomplete forms, and lost records
* Faster and more consistent inspections
* Clearer damage documentation
* Stronger handover proof with timestamps and signatures
* Better protection in case of disputes or claims
* Complete asset history in one central system
* Easier collaboration between internal teams, external partners, and customers
* Reliable offline work in low-connectivity environments
* Central visibility across locations, teams, and workflows

#### What Makes Emory Pro Different -:

Emory Pro is not a generic form or checklist tool. It is built for operational teams that need fast, visual, and reliable evidence for assets, inspections, and handovers.

#### Photo Annotation -:

Users can draw, circle, and annotate directly on damage photos. This makes visual evidence easier to understand and reduces ambiguity compared to text-only descriptions.

#### Offline Inspections at Scale -:

The mobile app supports large active inventories offline, allowing field teams to continue working even without internet access. Once connectivity returns, inspection data syncs automatically.

#### Damage Markings on Asset Blueprints -:

Teams can place damage markings on predefined asset blueprints, creating structured and precise visual documentation for vehicles, equipment, containers, units, or other asset types.

#### Handover Accountability -:

Digital signatures, timestamps, media evidence, user details, and inspection history help create a clear chain of custody across every handover.

#### Configurable Workflows -:

Organizations can configure asset types, inspection types, fields, lifecycle stages, and report outputs without developer support. This allows Emory Pro to adapt to different operational processes.

#### Web and Mobile Platform -:

Field teams complete inspections from the mobile app, while office teams, supervisors, and administrators manage workflows, users, reports, and dashboards from the web platform.


---

# 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/why-teams-use-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.