{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":32856,"path":"it-service-management/incident-management/def-prio-lookup-rules.md","title":"Define priority lookup rules","bundle":null,"doc_type":null,"release":"australia","body":"\n# Define priority lookup rules\n\nDefine impact and urgency combinations that determine incident priority and the SLA for each priority for an organization. Only administrators and data lookup administrators can configure these rules.\n\n## Before you begin\n\nRole required: data\\_lookup\\_admin, or admin\n\n## About this task\n\nPriority lookup rules are organizational configurations set by administrators. These rules ascertain how impact and urgency values combine to determine the priority of each incident. Individual incident responders cannot change the priority lookup rules. If the calculated priority seems incorrect for your organization, contact your system administrator to review the configured rules.\n\n## Procedure\n\n1.  Navigate to **All** > **System Policy** > **Rules** > **Priority Lookup Rules**.\n\n2.  Select **New**.\n\n3.  On the form, fill in the fields.\n\n    |Field|Description|\n    |-----|-----------|\n    |Impact|Impact is a measure of the effect of an incident, problem, or change on business processes.|\n    |Urgency|Urgency is a measure of how long the resolution can be delayed until an incident, problem, or change has a significant business impact.|\n    |Priority|Priority is based on impact and urgency, and it identifies how quickly the service desk should address the task.|\n    |Application|Application scope of the rules. The scope defines whether the rules are available for all applications or for scoped applications.|\n    |Active|Option to define whether the rule is active or not.|\n    |Order|Sequence in which the rules appear in the priority lookup list. This field indicates the sequence of the rule that is executed first.|\n\n    **Note:**\n\n    Priority is calculated according to the following sample data lookup rules:\n\n    |Impact|Urgency|Priority|\n    |------|-------|--------|\n    |1 - High|1 - High|1 - Critical|\n    |1 - High|2 - Medium|2 - High|\n    |1 - High|3 - Low|3 - Moderate|\n    |2 - Medium|1 - High|2 - High|\n    |2 - Medium|2 - Medium|3 - Moderate|\n    |2 - Medium|3 - Low|4 - Low|\n    |3 - Low|1 - High|3 - Moderate|\n    |3 - Low|2 - Medium|4 - Low|\n    |3 - Low|3 - Low|4 - Low|\n\n    By default, the **Priority** field is read-only and must be set by selecting the **Impact** and **Urgency** values. To change how the priority is calculated, you can either alter the priority lookup rules or disable the **Priority is managed by Data Lookup - set as read-only** UI policy and create their own business logic.\n\n4.  Select **Submit**.\n\n\n**Parent Topic:**[Configuring Incident Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/incident-management/incident-configuration.md)\n\n"}}