> 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/key-concepts.md).

# Key Concepts

#### Assets

Assets are the primary objects that are inspected, tracked, managed, or handed over in Emory Pro.\
An asset can represent a vehicle, trailer, machine, forklift, pallet, equipment, unit, room, or any other operational object your team needs to manage.\
Each asset can store its own details, inspection history, reports, media evidence, lifecycle stage, and linked containers.

#### Containers

Containers help organize assets into physical or logical groups.\
A container can represent a shipment, project, warehouse zone, tower, floor, batch, rack, or operational folder.\
One container can include multiple assets, and one asset can also be linked to multiple containers. This allows teams to create flexible hierarchies, visualize relationships, and navigate easily between connected assets.

#### Asset Types

Asset Types define the structure and configuration of different asset categories.\
Examples include:

* Vehicle
* Forklift
* Trailer
* Machine
* Equipment

Each Asset Type can have its own fields, inspection requirements, asset blueprints, layouts, and configuration rules.

#### Inspection Types

Inspection Types define the purpose or scenario of an inspection.\
Examples include:

* Check-In
* Check-Out
* Handover
* Damage Inspection
* Delivery Inspection
* Return Inspection
* Daily Check
* Quality Check

The combination of **Asset Type + Inspection Type** determines the inspection fields, required inputs, workflow logic, validation rules, and report output.

#### Reports

Reports are automatically generated once an inspection is completed.\
A report may include:

* Asset details
* Inspection results
* Photos and videos
* Damage markings
* Comments
* Timestamps
* User information
* Digital signatures
* Handover proof

Reports can be accessed through a digital link or downloaded as PDF files for internal records, customer communication, claims, audits, or handover documentation.

#### Tasks

Tasks help teams assign, manage, and track follow-up actions.\
A task can be created when damage is identified, equipment is missing, additional verification is required, or another team member needs to take action.\
Assigned users receive notifications and can complete the task by adding comments, photos, videos, documents, or other supporting evidence.

{% embed url="<https://emory.pro/platform/reporting-outputs/>" %}


---

# 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/key-concepts.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.