Setup Overview
Everything you need to know before configuring Emory Pro for your organisation.
This page explains the recommended setup order, the difference between administrator setup and field usage, and the key concepts you should understand before going live.
Recommended setup order
Complete the setup steps in the order below. Each step builds on the previous one, so following this sequence will help you save time and avoid unnecessary rework later.
1
Create your organisation
2
Complete company and contact details
3
Set up Asset Types
4
Set up Inspection Types
5
Define Lifecycle Stages
6
Add or import assets
7
Set up Roles & Permissions
8
Invite team members
9
Install and log in to the mobile app
10
Run your first test inspection
Admin setup vs field usage
Emory Pro is used across two main interfaces: the web platform and the mobile app.
The initial configuration is completed by an administrator in the web platform. Once the setup is ready and tested, field users can start using the mobile app to complete inspections.
Administrators use the web platform to:
Manage organisation settings and branding
Configure Asset Types and Inspection Types
Define Lifecycle Stages
Add or import assets
Create and manage Groups
Set up roles and permissions
Invite and manage users
Review Inspection Reports
Monitor activity through dashboards and operational views
Field users use the mobile app to:
Search for or scan assets
Complete assigned inspections
Capture photos, videos, comments, and signatures
Add Damage Markings on photos and Asset Blueprints
Complete handovers in the field
Work fully offline when there is no internet connection
Sync inspection data automatically once connectivity is restored
Field users do not need to be involved in the initial configuration. Invite them once the setup has been completed and tested.
Start with a simple workflow
For your first setup, keep the configuration focused and simple.
A smaller setup is easier to test, easier to explain to your team, and easier to expand once the first workflow is working correctly.
A good starting point is:
One organisation
One administrator
Two or three field users
One Asset Type
One Inspection Type
A small number of test assets
One report format
Example starting workflows
Vehicle Check-In
An inspector scans a vehicle QR code, completes a condition checklist, captures photos, adds Damage Markings if required, and generates a Check-In Report.
Equipment Handover
An inspector completes a handover checklist, both parties sign on the mobile device, and a signed Handover Report is generated instantly.
Once you have tested one workflow end to end, you can expand your setup with additional Asset Types, Inspection Types, users, Containers, report templates, and integrations.
How the key concepts connect
Understanding the main building blocks will make the setup process easier.
Asset Types define the structure of the physical objects your team manages, such as Vehicles, Forklifts, Containers, or Equipment.
Inspection Types define the purpose and structure of an inspection, such as Check-In, Check-Out, Handover, Daily Check, or Damage Inspection.
The combination of Asset Type + Inspection Type determines the checklist, fields, workflow logic, and report output for each inspection.
Assets are the individual objects your team inspects. Each asset belongs to an Asset Type.
Lifecycle Stages show where an asset is in your operation, such as Inbound, Active, In Repair, Outbound, or Delivered.
Containers help organise assets into logical groups, such as by location, shipment, project, customer, or batch.
Roles control what each user can see and do across the platform.
Inspection Reports are generated automatically after an inspection is completed. They include inspection fields, media, Damage Markings, signatures, timestamps, and user details.
Setup checklist
Use this checklist to confirm everything is ready before going live with your team.
Organisation created
☐
Company details completed
☐
Asset Types configured
☐
Inspection Types configured
☐
Lifecycle Stages created
☐
Assets added or imported
☐
Containers created, if required
☐
Roles and permissions configured
☐
Team members invited
☐
Mobile app installed by field users
☐
Test inspection completed
☐
Test report reviewed
☐
Report template confirmed
☐
Test report shared with a contact
☐
What to expect after setup
Once your setup is complete and your team starts using Emory Pro in the field, you will have:
A structured record of every inspection, damage finding, and handover
Full asset history accessible from one scan
Inspection Reports generated automatically without manual reporting
A single source of truth for your operational evidence
From this point, the administrator’s role shifts from initial configuration to ongoing management. This includes monitoring activity, reviewing reports, managing users, tracking asset status, and expanding Emory Pro as your operation grows.
Ready to begin?
Start with Create Your Organisation.
Last updated