Setting Up Your Operational Structure
Before your team begins using uAuditor for inspections and operational monitoring, it is important to configure your organization’s structure inside the platform.
Setting up your operational structure ensures inspections, tasks, actions, and reports are assigned correctly across locations, users, and assets.
This setup is typically completed during onboarding, but administrators can review or update it at any time.
Why Operational Structure Matters
A properly configured structure allows you to:
- assign inspections to the correct locations
- control user access and permissions
- link equipment to inspection workflows
- generate accurate location-based reports
- automate task scheduling
- improve accountability across teams
Without this setup, inspections may not reflect your real operational environment.
Core Components of the Operational Structure
Your workspace structure is built using five main elements.
Zones
Zones group multiple locations into logical operational regions.
Examples include:
- Cities
- Regions
- Operational sectors
- Brand divisions
- Departments
Zones simplify reporting and access control across large organizations.
Example:
Western Region → Riyadh Branches
Eastern Region → Dammam Branches
Locations
Locations represent physical branches or operational sites where inspections take place.
Examples:
- Stores
- Warehouses
- Restaurants
- Production facilities
- Service centers
Each inspection is linked to a specific location for accurate tracking and reporting.
Users
Users are the people who access the platform and perform inspections or manage operations.
Examples:
- Inspectors
- Supervisors
- Quality managers
- Administrators
- Branch managers
Each user can be assigned to one or more locations depending on responsibilities.
Roles and Permissions
Roles define what each user can see or manage inside the platform.
Permissions control access to:
- Inspections
- Templates
- Reports
- Actions
- Broadcasts
- Settings
This ensures secure and structured access across teams.
Equipment and Assets
Equipment represents the physical assets inspected or monitored within your organization.
Examples include:
- Refrigerators
- Vehicles
- Machines
- HVAC systems
- Kitchen equipment
- Safety devices
Assets can be linked to inspections, monitoring devices, and reports.
Recommended Setup Order
For best results, configure your structure in this sequence:
- Create zones
- Add locations
- Register equipment
- Add users
- Assign roles and permissions
This ensures dependencies are configured correctly.
When Operational Structure Is Already Prepared During Onboarding
If your organization submitted onboarding documents earlier, your implementation team may already configure:
- Locations
- Users
- Roles
- Assets
- Templates
In this case, administrators only need to review and confirm accuracy before starting inspections.
Best Practices for Large Organizations
For multi-location environments:
- Group locations by region or business unit
- Assign location-specific administrators
- Separate inspection templates by operational type
- Define role-based access carefully
- Review structure before scheduling inspections
This improves automation accuracy and reporting clarity.
