How Collection Cases Are Assigned to Revenue Officers

I hear this more than you'd think: why me? Why did a Revenue Officer show up on my case when my neighbor owes more and has never seen one?

The answer is in the IRM, and it is less personal than people fear. Field Collection cases are assigned by group managers working from a prioritized electronic list, under rules designed so that no single employee controls who gets pursued. Here is how that works.

The fairness rule behind every assignment

IRM 1.4.50.10 (rev. 2025-04-01) opens with Policy Statement 1-236, Fairness and Integrity in Enforcement Selection. Assignment of work must align with it. The IRM says the purpose is to provide a framework for assigning work so that case assignments are free from personal bias.

IRM 5.1.20.1 (rev. 2024-10-07) makes the same point from the systems side. Collection inventory is systemically routed using scoring and routing systems so that no one individual can control the enforcement selection decision-making process.

So the Revenue Officer did not pick your file because they drove past your business. The system ranked it, and a manager assigned it according to written criteria.

Where the cases come from

Group managers assign from two places. The first is the group manager's hold file in the Integrated Collection System, known as ICS. IRM 1.4.50.10 says the hold file receives cases that bypass the queue and are directly assigned to Field Collection, plus transfers from other groups and functions such as ACS.

The second is the Queue, accessed through the GM Case Assignment function in the ENTITY case management system. IRM 5.1.20.4.1 calls GM Case Assignment the primary method Field Collection group managers use to assign inventory from the Queue to Revenue Officers in their group.

Which cases a group even sees depends on geography. IRM 1.4.50.10 says the cases available to a specific group are based on the zip code assignments of the group. Your address puts you in a particular group's queue.

Priority levels

Every case presented in ENTITY carries a priority level. IRM 1.4.50.8.4 lists them: 99 through 108 are high priority, 201 through 208 are medium priority, 301 and 302 are low priority, and 399 is a default for non-IDRS assignments that says nothing about actual priority. Cases are reprioritized weekly.

The IRM says the priority scoring was developed with an emphasis on recent business trust fund taxpayers and other selected criteria. Elements include balance due, return types, tax period, model score and selection code.

Priority level 99 is special. IRM 1.4.50.10 calls these Mandatory Accelerated Cases and says they should be assigned expeditiously to any grade-appropriate Revenue Officer before other queue cases.

The order managers must follow

IRM 1.4.50.10 divides inventory into three categories: mandatory, high priority and medium to low priority. Managers first assign mandatory cases in the hold file and priority 99 cases from the queue. Then they evaluate high priority cases in both places.

Mandatory assignments include certain federal tax deposit alerts, which must be assigned within seven calendar days of arriving in the group hold file, mandatory Other Investigations, IRS employee accounts and cases that cannot be moved to the queue.

The IRM also tells managers not to sit on hold file cases. To decrease cycle time, do not keep cases in the ICS hold file more than 45 days after receipt, and document the reason in the case history if a case stays longer.

Then comes a rule that answers the neighbor question. The IRM says it is generally inappropriate to assign medium or low priority accounts when high priority accounts are available for the same type of case. Your neighbor's account may simply score lower and never get pulled.

Predictive values

Within each priority level, ENTITY assigns one of five predictive values, a through e. IRM 1.4.50.10 says these help managers identify the most predicted productive work within each priority level.

The rule is specific. If two cases share a priority level, the one with the higher predictive value is assigned first. But managers are told it is not appropriate to assign a lower priority level case with a high predictive value over a higher priority level case with a low predictive value of the same type, unless the lower priority case is a mandatory assignment or a related taxpayer.

The IRM gives its own example: do not assign a 201 case with predictive value a ahead of a 101 case with predictive value d.

Case grade: matching difficulty to the officer

IRM 1.4.50.10.1 says balance due and delinquent return investigations are issued with a case grade of GS-11, 12 or 13, reflecting the anticipated difficulty. The Inventory Delivery System is the primary system that sets the grade, with an older workload system grading cases IDS does not.

Managers can regrade a case up or down when new information changes the picture, but the IRM says they will not normally change the grade unless the case meets at least three of the four factors at the new level. The ICS pick list factors are nature of the entity, range of case issues, personal contacts and impact of enforcement action. The reason goes into the case history.

This is why a complex business with multiple entities and payroll issues tends to land with a more senior officer than a single wage earner with one year owed.

Workload and inventory limits

Managers are not supposed to bury officers. IRM 1.4.50.10.2 suggests, absent indications to the contrary, limiting new assignments to five per work week, and warns that excessive simultaneous assignments could hurt an officer's ability to make timely initial contact and follow-up.

The same subsection sets standard inventory ranges. For GS-12 and GS-13 officers the range is 34 to 50 taxpayer cases. For GS-11 it is 53 to 79. When an officer's inventory exceeds the maximum, the manager should bring it back within the range within 10 work days or relieve the officer, in writing, of the IRM's prompt contact and follow-up requirements until it is.

That last rule is worth knowing. If an officer is slow to follow up, it may be workload, and the manager may have formally relaxed the timing rules for that officer.

Professional judgment plays a limited role

That phrase comes straight from IRM 1.4.50.10. Managers can consider geography, an officer's development needs and current workload, but even then the cases assigned should represent the highest priority available.

There is one judgment call that can work in a taxpayer's favor. The IRM says modules with less than six months remaining on the collection statute expiration date normally will not be assigned, with exceptions for high priority cases, high income non-filers and potentially egregious repeat trust fund taxpayers.

Managers also rotate officers. IRM 1.4.50.10.4 says, where feasible, geographic areas or caseloads should be rotated every three years to avoid over-familiarity with taxpayers in a particular area.

What this means for you

If a Revenue Officer has your case, a scoring system ranked it high enough to be pulled and a manager matched it to that officer's grade and territory. That officer has a manager who reviews the work and a set of written timelines to follow.

That is useful information. It tells you the case is not going back to the shelf on its own. It tells you there is a supervisor in the picture. And it tells you the officer's next moves are written down. For how to work with that officer once assigned, read Negotiating With a Revenue Officer.

Stop asking why you. Start asking what the officer is required to do next.