How the IRS Grades Its Own Collection Work: Embedded Quality and National Quality Review

The IRS cannot rate its collectors on how many levies they issue. So how does it judge whether the work was good? It grades the cases.

The system is called Embedded Quality. Managers use it to review their own employees, and a separate national staff uses it to sample closed cases and measure the organization. The attributes they score are the closest thing the IRS has to a written definition of a well-worked collection case.

Where the requirement comes from

IRM 5.13.1.1.2 (rev. 2022-10-06) traces it to Treasury's Regulation 801, adopted under the IRS Restructuring and Reform Act of 1998. The IRM quotes the regulation's focus: quality measures look at whether IRS personnel devoted an appropriate amount of time to a matter, properly analyzed the facts, complied with statutory, regulatory and IRS procedures, took timely actions, and provided adequate notification and made required contacts with taxpayers.

The same subsection says the use of Embedded Quality in Collection's field programs was established by a 2007 Letter of Understanding with the National Treasury Employees Union and later incorporated into the national agreement.

IRM 5.13.1.1 says Embedded Quality covers Field Collection, Advisory, Property Appraisal and Liquidation Specialists, Field Offer in Compromise and Field Insolvency.

The five measurement categories

IRM 5.13.1.2 says the system calculates quality as the percentage of applicable attributes coded correct within five measurement categories. Here they are in the IRM's words, lightly condensed.

• Customer Accuracy: whether the customer was given a complete and correct tax resolution without negative impact.
• Regulatory Accuracy: adherence to statutory and regulatory process requirements.
• Procedural Accuracy: adherence to non-statutory internal process requirements.
• Professionalism: communication that promotes a positive image of the IRS.
• Timeliness: resolving issues in the most efficient manner.

Notice what is not on the list. Dollars collected. Number of levies. Number of seizures. The categories measure whether the job was done correctly and on time, not how hard the employee squeezed.

Why it exists

IRM 5.13.1.1.1 explains that Embedded Quality was developed to support the IRS's balanced measures. Organizational performance is evaluated using attributes that identify actions that move cases toward closure through appropriate and timely case activity, and the same attributes link individual performance to organizational goals.

IRM 5.13.1.2 describes three components: improving how quality is measured and reported, creating accountability by connecting employee reviews to quality measurement, and improving the design and use of quality review resources. The reviews are divided into three functions, Collection, Advisory and Insolvency, and further into 16 Specialized Product Review Groups, each with its own job aid defining the attributes for that program area.

Two kinds of review

There are two separate tracks. IRM 5.13.1.3 describes the managerial review process, where managers use the Embedded Quality Review System, EQRS, to assess employee performance. Review data maps to the employee's critical job elements and is used to track performance, identify training needs and plan workload.

IRM 5.13.1.4 describes Field Quality reviews, done by dedicated reviewers on the National Quality Review System, NQRS, to measure organizational performance. Closed case files are reviewed and the results roll up into the business results portion of the IRS's balanced measures.

The IRM keeps them apart. IRM 5.13.1.3 says managerial reviews are performed independently from Field Quality reviews, and Field Quality review results are never used for evaluation of individual employees.

How cases get picked for national review

IRM 5.13.1.9.1 says Collection Quality staff pull closed Field Collection cases from ICS weekly and place randomly selected cases on a sample template. The closed cases can come from many dispositions, including full pay, adjustments, installment agreements, currently not collectible closures, federal tax deposit alerts, delinquent return cases and cases closed to Insolvency or the offer program.

The same subsection identifies the IRS status codes behind those closures: full pay is status 12, an installment agreement is status 60 and adjustments can be status 12 or 53.

IRM 5.13.1.5 says the national reviews also cover offer cases, bankruptcy cases worked in Insolvency and lien discharge, subordination and withdrawal requests worked in Advisory. After review, IRM 5.13.1.8 says paper files are stamped QR, for Quality Reviewed, and electronic closed cases carry a notation that Field Quality accessed them.

Cases the national reviewers skip

Not every closed case is reviewable. IRM 5.13.1.9.1 tells Field Quality reviewers not to review cases with no case history or no case actions recorded, balance due cases still in status 26 or assigned to Field Collection, cases where the officer took no action to resolve the case, such as a not collectible closure based on a prior not collectible closure, cases where the approval or last history entry is six months or more before the review, and related cases without enough information to complete the review.

Read the list backwards and it tells you what the IRS wants to measure: real case work, recently completed, with a history that shows the decisions. A file with no history is not a quality file. It is an unreviewable one.

Managers grade too, on a schedule

On the managerial side, IRM 1.4.50.5.2.2 (rev. 2025-04-01) requires group managers to review at least eight cases a year for officers at GS-11 and above rated fully successful, and at least twelve for lower grades or officers rated below fully successful. IRM 1.4.50.5.2.1 says a deficiency found in 25 percent or more of the cases reviewed should generally be noted as an area of special concern, and that some single deficiencies, like an expired statute, can be critical.

When a manager directs specific case actions during a review, IRM 1.4.50.5.2.1 says a follow-up review should be scheduled 60 to 90 days later to confirm the instructions were followed. Written feedback must reach the employee within 15 work days, and IRM 1.4.50.5.2.2 says a review not shared within that window must not be used for any evaluative purpose.

Taxpayer rights are part of the score. IRM 1.4.50.5.2.1 says taxpayer rights are evaluated in EQRS attribute 607, and a rating that the right to representation was not observed requires a narrative explaining why.

And quality review is how the IRM expects managers to police IRM compliance generally. IRM 1.11.6.1.5 (rev. 2025-09-02) says that during quality review, managers evaluate whether employees researched, interpreted and correctly applied IRM instructions.

The Section 1204 guardrail

Quality review sits inside the quota ban. IRM 5.13.1.5 says requests to add discretionary review items must go through the Collection Quality Program Manager and be considered consistent with IRM 1.5.2, the Section 1204 statistics rules. I explain those rules in No Quotas: How Section 1204 Bars IRS Enforcement Goals.

In other words, the IRS can measure whether an officer followed procedure in your case. It cannot turn that measurement into a count of enforcement outcomes.

Why this matters to you

The quality attributes tell you what the IRS itself considers a properly worked case: facts analyzed, procedures followed, required notices and contacts made, timely action and professional communication. When you think an employee got it wrong, frame your concern in those terms. A manager who grades their officers on regulatory accuracy and timeliness understands that language immediately.

It also explains some officer behavior that looks like caution or delay. An officer who insists on verifying an expense, documenting a contact or issuing a formal Form 9297 before moving on is doing what the quality attributes reward. Work with that instinct rather than against it, and your case usually moves faster.

It also tells you the file will be read again. Every case history entry, deadline and financial analysis could end up in front of a reviewer. Officers know that. It is one reason they document so carefully, and one reason you should too.