No Quotas: How Section 1204 Bars IRS Enforcement Goals

One of the most common fears I hear is that the Revenue Officer has a quota. That they need one more seizure this month, or a certain number of levies, and you are the unlucky account that fills it.

Federal law says otherwise. Since 1998, the IRS has been barred from using enforcement statistics to evaluate the employees who make enforcement decisions. The rule is detailed, and it is enforced through the IRS's own management manuals.

The statute

Section 1204(a) of the IRS Restructuring and Reform Act of 1998, set out as a note under 26 U.S.C. 7804, says the IRS shall not use records of tax enforcement results to evaluate employees, or to impose or suggest production quotas or goals with respect to such employees.

Section 1204(b) adds an affirmative requirement: the IRS shall use the fair and equitable treatment of taxpayers by employees as one of the standards for evaluating employee performance.

Section 1204(c) requires each appropriate supervisor to certify quarterly by letter to the Commissioner whether or not tax enforcement results are being used in a prohibited manner.

The regulation

Treasury implemented the statute in 26 C.F.R. Part 801, often called Regulation 801. Section 801.3(e)(1) says no IRS employee may use records of tax enforcement results to evaluate any other employee or to impose or suggest production quotas or goals for any employee.

The regulation defines evaluate broadly. It includes any process used to appraise performance for a performance rating, an award recommendation, an assessment of qualifications for promotion or reassignment, eligibility for incentives or bonuses, and ranking for reductions in force.

Section 801.3(b) requires that all IRS employees be evaluated on whether they provided fair and equitable treatment to taxpayers. Section 801.3(e)(3) says performance measures based in whole or in part on quantity measures will not be used to evaluate a non-supervisory employee who exercises judgment with respect to tax enforcement results.

What counts as an enforcement result

IRM 1.5.2 (rev. 2022-10-26) is the IRS's working manual on the rule. It defines a tax enforcement result, or TER, as the outcome produced by an employee's exercise of judgment in recommending or determining whether or how the IRS should pursue enforcement. Its examples include a lien filed, a levy served, a seizure executed, amounts assessed or collected, a fraud referral and the type of case closure.

A record of tax enforcement results, or ROTER, is the statistic: the number of liens filed, number of levies served, number of seizures executed, dollars collected, dollars per hour, number of full paid cases and similar compilations, according to IRM 1.5.2.11.

IRM 1.4.50.5.3 (rev. 2025-04-01), written for Collection group managers, lists prohibited examples in collection terms: number of delinquent returns secured, full payment rate, number of seizures made, number of levies issued, number of offers recommended for acceptance and number of accounts reported currently not collectible.

Who is covered

IRM 1.5.2.9 defines a Section 1204 employee as an employee or manager, at all levels, who exercises judgment in recommending or determining whether or how the IRS should pursue enforcement of the tax laws, plus employees who provide direction or guidance for field programs involving that work. The IRM's own example: an analyst who writes a compliance IRM is a Section 1204 employee.

The work determines coverage, not the title. IRM 1.5.2.9.1 gives examples of covered judgments, including the determination to conduct a seizure, the determination to file a lien and a decision to disallow an unsupported deduction. It says the rules generally do not cover purely mechanical tasks like correcting return errors or computing interest.

Revenue Officers and their managers are squarely inside the rule. So are the offer examiners who recommend whether to accept an offer, the employees who decide whether a lien should be filed and the managers who supervise all of them. The rule follows the judgment wherever it is exercised, which is exactly where a taxpayer would worry about a quota.

Imposing versus suggesting a quota

The IRM separates two violations. Imposing a quota, under IRM 1.5.2.9.2, is any managerial communication, oral or written, that requires a covered employee to achieve an enforcement result. The examples include requiring a certain average dollar amount collected per return or a certain number of seizures during a rating period.

Suggesting a quota, under IRM 1.5.2.9.3, is subtler. It is any managerial communication from which a reasonable person would infer the manager will evaluate the employee more favorably if a specific enforcement result is achieved, regardless of the merits of the case. One of the IRM's examples is a manager suggesting that an employee should achieve the same result in Case B as in Case A.

That is a strong rule. It is not just a ban on written quotas. It reaches the hallway conversation.

The fair treatment standard is mandatory

The quota ban has a flip side, and it is just as important. Section 1204(b) requires the IRS to use the fair and equitable treatment of taxpayers by employees as one of the standards for evaluating employee performance, and 26 C.F.R. 801.3(b) applies that requirement to all IRS employees.

Regulation 801 also requires the IRS's performance system for the general workforce to set one or more retention standards for each employee, make periodic determinations of whether the employee meets them and take action under applicable law when an employee does not. IRM 1.4.50 points Collection group managers to the retention standard for the fair and equitable treatment of taxpayers when they observe their officers.

In plain terms: a Revenue Officer cannot be rated on how many levies they issue, but they can be rated, and must be rated, on whether they treated you fairly. That is a performance standard written into federal regulation.

IRM 1.5.2.10 also draws a useful line. It says a tax enforcement result does not include quality review data or a review of an employee's work on a case, such as whether lien determinations were appropriate. Managers can and do evaluate whether the officer's decisions were correct. They just cannot count the outcomes.

What managers can measure

The IRS still measures things. IRM 1.5.2.12 describes quantity measures as outcome-neutral production and resource data, such as cases started, cases closed, time per case, inventory information and cycle time. IRM 1.5.2.13 describes quality measures, such as procedural accuracy and timeliness, determined by dedicated review staff.

And individual case review is allowed. IRM 1.4.50.5.3 notes that the prohibition does not cover enforcement results of individual cases when used to determine whether an employee exercised appropriate judgment based on a review of the employee's work on that case. A manager can review whether your Revenue Officer's decision to levy in your case was appropriate. The manager cannot count levies.

What this means for your case

Do not assume your Revenue Officer is chasing a number. The law forbids the IRS from rating them that way, and their manager certifies compliance every quarter. Assume instead that they are being evaluated on timeliness, procedural accuracy and fair and equitable treatment, because that is what the regulation and the manuals say.

That changes how you should approach them. An officer who is measured on following procedure and moving cases to resolution responds well to a complete, documented proposal. Give them a case they can close correctly, and you are aligned with how they are actually judged. I explain the review process in The Collection Group Manager.

If you ever hear an IRS employee say they need a certain number of enforcement actions, write it down. That statement describes exactly what Section 1204 forbids.