ServiceNow Assignment Rules

Assignment Rules automatically route tickets to the correct group or agent without any manual intervention. Instead of a dispatcher reading each new ticket and deciding who should handle it, ServiceNow evaluates the ticket's details against pre-defined rules and sets the assignment group — in real time, when the ticket is created.

What Assignment Rules Do

Imagine a company's IT service desk receives 300 tickets per day. Manually reading each one and deciding whether it goes to the Network team, the Desktop team, or the Applications team would consume hours of a human's time. Assignment rules handle this routing automatically within seconds of ticket creation.

New Incident Created
        │
        ▼
ServiceNow checks all active Assignment Rules
        │
        ├── Rule 1: Category = Network → Assign to "Network Support"
        ├── Rule 2: Category = Hardware → Assign to "Desktop Support"
        ├── Rule 3: Priority = 1-Critical → Assign to "Major Incident Team"
        └── Rule 4: Location = Building B → Assign to "Site B IT Team"
        │
        ▼
First matching rule wins → Assignment Group set automatically

Where to Find Assignment Rules

Navigate to System Policy > Rules > Assignment in the left navigation menu. The assignment rules list shows all active rules, the table they apply to, their filter conditions, and the order in which they run.

Components of an Assignment Rule

Name

A descriptive name that explains what the rule does. Clear names like "Route Network Incidents to Network Support" make maintenance easier when rules need to be updated months later.

Table

Assignment rules apply to one specific table. A rule on the incident table fires when incidents are created or updated. Separate rules handle change requests, service requests, and other tables.

Filter Conditions

The condition that must be true for the rule to apply. Conditions check field values on the record. Multiple conditions combine with AND logic — all conditions must match for the rule to fire.

Example Assignment Rule:
─────────────────────────────────────────────────────────
Name:             Route VPN Issues to Network Team
Table:            Incident [incident]
Active:           ✓
Filter:           Category = Network
                  AND Short Description contains "VPN"
Assign to Group:  Network Support
Assign to User:   (leave empty - group is enough)
─────────────────────────────────────────────────────────

Assignment Target

The assignment rule sets either an Assignment Group, a specific Assigned To user, or both. Setting only the group is the recommended approach. Individual agents then pick up tickets from the group queue. Assigning directly to one person risks tickets sitting unattended when that person is unavailable.

Order

Each rule has an order number. ServiceNow evaluates rules from lowest order number to highest. The first rule whose conditions match wins. Rules with lower order numbers run first and take priority over higher-numbered rules.

Rule Evaluation Order:
──────────────────────────────────────────────────
Order │ Rule Name                  │ Match Result
──────────────────────────────────────────────────
100   │ Critical → Major Incident  │ No match (Priority = 3)
200   │ VPN → Network Support      │ MATCH! → Assign here
300   │ Network → Network Support  │ (skipped — rule 200 already matched)
──────────────────────────────────────────────────

Priority-Based Assignment

Some organizations route high-priority incidents to specialized teams. A Priority 1 (Critical) incident might go directly to a Major Incident Management team, bypassing the standard first-line service desk. An assignment rule with filter Priority = 1-Critical and order 100 ensures critical tickets always get special handling before any other rules run.

Location-Based Assignment

Organizations with multiple offices use location-based assignment rules to route tickets to the on-site team. A user in the London office submits an incident. The assignment rule checks the caller's location field, finds "London," and assigns the ticket to the "London IT Support" group — ensuring a local technician handles it.

Combining Assignment Rules with Other Automation

Assignment rules work alongside other automation tools in ServiceNow. A business rule might update a field value, which then triggers an assignment rule. The result is a chain of automation that handles routing without any human dispatcher. This combination is the foundation of a lean, efficient IT service desk.

Testing an Assignment Rule

After creating an assignment rule, test it by creating a test incident that matches the rule's conditions. Check whether the Assignment Group field populates correctly upon saving. If the rule doesn't fire, verify that the rule is active, the conditions match the record exactly, and no higher-priority rule is catching the ticket first.

Assignment Rules vs. Business Rules

Assignment Rules are a simplified, no-code tool specifically for routing work. Business Rules are more powerful scripted automation that can do almost anything — but require JavaScript. For straightforward routing tasks, assignment rules are the right choice. For complex conditional logic that assignment rules cannot express, a business rule handles the same outcome with custom scripting.