Creating Score Priorities
Creating score priorities in uAuditor allows administrators to define importance levels for inspection questions so that critical checkpoints have greater influence on inspection results than lower-impact observations. This helps organizations build structured and meaningful scoring models aligned with operational risk and compliance requirements 📊
Score priorities are configured once and can then be reused across all inspection templates.
What Are Score Priorities Used For?
Score priorities determine how strongly each question affects the final inspection score.
They help:
- emphasize critical compliance checkpoints
- reduce the impact of minor observations
- standardize scoring across templates
- improve performance benchmarking between locations
- strengthen analytics accuracy in dashboards and reports
This ensures inspection scores reflect real operational priorities.
When to Create Score Priorities
Organizations typically create score priorities when:
- launching a new inspection framework
- standardizing scoring across multiple templates
- introducing compliance-weighted scoring models
- separating safety-critical checks from routine observations
- improving branch comparison accuracy
Creating structured priorities early improves long-term reporting consistency.
How to Create a Score Priority
To create a new score priority:
- Open the Resources module
- Select Score Priorities
- Click Create Priority
- Enter the priority name (English)
- Enter the priority name (Arabic)
- Assign a weight value
- Select a display color
- Optionally set it as the default priority
- Click Save
The priority becomes available immediately for use inside inspection templates.
Choosing Weight Values
Weight values determine how much influence a priority level has on inspection scoring.
Example structure:
- High Priority → 50
- Medium Priority → 30
- Low Priority → 20
Higher values increase scoring impact when assigned to questions.
It is recommended to keep weights simple and balanced across templates.
Setting a Default Priority
You can define one priority as the default priority.
When set:
- new questions automatically inherit this priority
- template creation becomes faster
- scoring consistency improves across templates
This is especially useful for large inspection environments.
Selecting Priority Colors
Each score priority can include a display color to improve visibility during template design and reporting.
Common examples:
- Red → High priority
- Orange → Medium priority
- Green → Low priority
Color coding helps users quickly identify question importance levels.
Where Score Priorities Are Used
After creation, score priorities can be assigned to:
- dropdown questions
- number questions
- multiple choice questions
They influence:
- inspection score calculations
- performance dashboards
- analytics reports
- branch comparison metrics
This ensures scoring reflects operational importance across inspections.
Best Practices for Creating Score Priorities
To configure score priorities effectively:
- limit priorities to 3–4 levels maximum
- assign higher weights to compliance-critical checkpoints
- standardize priorities across templates
- avoid overlapping importance definitions
- review priorities periodically as inspection workflows evolve
Well-structured score priorities help organizations produce accurate inspection scores that reflect operational risk, compliance exposure, and execution quality across all locations.
