Priority should calculate automatically when agents set impact and urgency on incidents — not be a manual dropdown they can forget or get wrong. This guide shows you how to configure the lookup rules that drive ServiceNow's automated priority calculation.
Why manual priority assignment breaks down
Before priority lookup rules, agents had to manually select High, Medium, or Low priority on every incident, often guessing or applying it inconsistently. Different agents would prioritize the same type of issue differently, and urgent issues would sit unnoticed because someone forgot to set priority correctly. Service desk managers and incident coordinators inherit this mess — they can't trust priority values for reporting or escalation rules because the data quality is unreliable.
How priority calculation works
ServiceNow calculates priority automatically using a lookup table that maps impact and urgency combinations to specific priority values. When an agent sets Impact to High and Urgency to High, the system looks up that combination in the Priority Lookup Rules table (pa_priority_lookup) and sets Priority to 1 - Critical. This happens on record save, not real-time. The priority field becomes read-only in most cases — agents control it indirectly by setting impact and urgency. Start with ServiceNow's default mappings and adjust based on your organization's actual escalation needs.
Tuning priority rules for production
Once basic priority calculation works, refine the mappings based on real incident data. Most organizations discover their default rules create too many Critical priorities or not enough, skewing dashboards and SLA targets. Add custom priority values beyond 1-5 if your escalation process needs finer granularity. Consider creating separate lookup rules for different record types if your organization handles incidents, problems, and changes differently. Document your priority definitions clearly — agents need to understand what High impact means for your business, not guess.
Before you start
- •itil role or higher
- •Incident table write access
Sourdough: ServiceNow Monitoring and Analytics
A Chrome extension for ServiceNow Admins and Developers with essential tools, analytics, graphs and monitoring features.
Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.
Step by step
Access the Priority Lookup Rules table
Navigate to System Definition > Tables and search for 'pa_priority_lookup'. Click on the table name, then click 'Open table' from the related links. This opens the current lookup rules that map impact/urgency combinations to priority values.
Review existing lookup combinations
Examine the current mappings to understand what's already configured. Each record shows an Impact, Urgency, and resulting Priority value. Note that ServiceNow ships with a standard 3x3 matrix (High/Medium/Low impact vs High/Medium/Low urgency). Look for gaps or mappings that don't match your organization's escalation needs.
Modify an existing lookup rule
Click on a lookup rule that needs adjustment. Change the Priority field to the value that should result from that impact/urgency combination. For example, if High impact + Low urgency currently maps to Priority 2, but your business treats any high-impact issue as Priority 1, change it. Save the record.
Add new lookup combinations
Click New to create additional mappings if needed. Set the Impact and Urgency values, then select the appropriate Priority. This is useful if you've added custom impact or urgency values beyond the standard High/Medium/Low options, or if you need more granular priority distinctions.
Test priority calculation on incidents
Open an existing incident or create a test incident. Change the Impact and Urgency values to combinations you've modified, then save the record. Verify that Priority updates to match your lookup rules. Test several combinations to confirm the mapping works correctly.
Validate historical incident priorities
Run a report on recent incidents to check if existing priority distributions make sense with your new rules. Look for incidents where the current priority doesn't match what your new lookup rules would generate. Consider whether you need to bulk-update existing incidents or just apply the new rules going forward.
Most organizations apply new priority rules only to future incidents to avoid disrupting historical reporting.
Best practices
Document your impact and urgency definitions clearly before changing lookup rules — agents need to understand what 'High impact' means for your business.
Avoid creating too many Critical (Priority 1) combinations — if everything is critical, nothing is.
Test lookup rule changes in a development instance first — priority drives SLA calculations and escalation workflows that break when misconfigured.
Consider the downstream effects on dashboards and reports that rely on priority distribution when modifying existing rules.
Create a backup of your current pa_priority_lookup table before making changes — you'll want to revert quickly if the new mappings cause problems.
Test Your Knowledge
Quick 3-question quiz — see how your ServiceNow skills stack up.
A list view on a table with millions of records is slow. Best fix?
Select an answer to continue