Eligible Training Provider List ETPL Performance Reporting: Building the Data Pipeline

Featured image with a lavender pastel background and a confetti pattern, showing the post title "ETPL Performance Reporting: Building the Data Pipeline"

Eligible Training Provider List ETPL Performance Reporting: Building the Data Pipeline

The eligible training provider list ETPL is each US state’s list of training programs approved under section 122 of the Workforce Innovation and Opportunity Act (WIOA). Staying on it means reporting outcome data, and since 2021 that means data on all your students, not only the WIOA-funded ones. A workable pipeline captures records once, keeps one identity per student, attaches the state’s employment match, and exports in each state’s format.

This guide is for training providers that run instructor-led programs and are asked for performance data they do not yet hold in one place. Your state workforce agency’s policy has the final say on formats and deadlines.

Key takeaways

  • Federal rules set the outcome measures; each state sets the file format, portal and schedule. Build one canonical student record and one adapter per state.
  • The “all students” waiver expired on June 30, 2021, so states report on every student in a program of study, not only WIOA-funded ones.
  • Employment and earnings usually come from a wage record match that needs a reliable identifier. Plan how you will collect, protect and record refusals of it.
  • Check counts against simple arithmetic rules before every submission, and keep a frozen copy of what you sent.

What does the eligible training provider list ETPL require from a training provider?

WIOA section 122 requires the Governor’s rules to make providers submit “appropriate, accurate, and timely information” on performance, credentials, cost of attendance and completion rate. A provider that intentionally supplies inaccurate information loses eligibility for “not less than 2 years”.

The regulation that applies this, 20 CFR 680.460, requires the state’s information requirements to include seven items for WIOA participants:

  • The percentage in unsubsidized employment in the second quarter after exit.
  • The percentage in unsubsidized employment in the fourth quarter after exit.
  • Median earnings in the second quarter after exit.
  • The percentage who obtain a recognized postsecondary credential or secondary diploma during participation or within one year after exit.
  • The recognized credentials received.
  • Cost of attendance, including tuition and fees.
  • The program completion rate.

The statute is on the US Code page for 29 U.S.C. 3152. The regulation adds that the state sets the timeframe and manner of collection, at least every two years, and that collection must not be unduly burdensome or costly to providers.

The scope is wider than WIOA-funded students. Department of Labor notice TEN 7-21, dated September 23, 2021, states that the “ETP All Students Waiver expired on June 30 2021”. From program year 2021, states report for WIOA participants and for all students in a program of study.

Which ETPL performance data elements must a provider be able to produce?

A provider needs enrolment counts, exit counts, completions, credentials, and the identifiers that let outcomes be found, for each program of study. The Department of Labor’s ETA-9171 specification numbers these elements. The table maps the “all individuals” elements to the records your pipeline must hold.

ETA-9171 element What it counts (per the specification) Where it comes from in your pipeline
120 Individuals served Students enrolled in the program of study in the reporting period, WIOA and non-WIOA Enrolment and session records
121 Exited Students who completed, withdrew or transferred in the period Exit status and exit date
122 Program of study completed Exiters who completed rather than withdrew or transferred Completion rule applied to attendance and assessments
123, 124 Employed in quarter 2 and quarter 4 after exit Exiters in unsubsidized employment, found “through a wage record match or other supplemental means” State wage match results, or your own supplemental evidence
125 Median earnings Earnings in the second quarter after exit, for those employed State wage match results
126 Credential attainment Credential earned during the program or within one year after exit Credential records with award dates
129, 130 Denominators Exiters who were in quarter 2 or quarter 4 after exit during the period Exit dates and calendar logic
110, 175, 176 Program and provider identity CIP code, provider EIN, unique provider ID Your program catalog, kept stable over time

The wording comes from the ETA-9171 specification, approved under OMB control number 1205-0526 through April 30, 2028. It defines a program of study as a program of training services under 20 CFR 680.420.

The state report adds parallel WIOA-participant elements and counts by age, sex, race and barriers to employment. TEGL 3-18 says states can generate much of that themselves, so check before building it.

Pro tip: Store the exit reason, not a completed flag. The specification splits exits into completed, withdrew and transferred. A boolean “completed” field cannot separate the last two. If your TMS derives completion from attendance by rule, as the TMS data model post suggests, save the derived status, exit date and rule version together.

What is the status of the federal ETPL rules as of November 2026?

As of November 2026, the 2014 WIOA statute, its regulations and DOL’s 2018 reporting guidance still apply. TEGL 3-18 lists its expiration as “continuing”, and the sources reviewed for this guide showed no later notice rescinding it. A House reauthorization bill, H.R. 8210, had not become law in any of them.

The dated status of each layer, from the primary documents:

  • Statute: WIOA section 122, 29 U.S.C. 3152, enacted July 22, 2014.
  • Provider eligibility guidance: TEGL 8-19, dated January 2, 2020, replaces TEGL 41-14.
  • Reporting guidance: TEGL 3-18, issued August 31, 2018, effective from program year 2018. States submit the ETA-9171 through the Workforce Integrated Performance System (WIPS) as a .csv or .txt file.
  • All students: the waiver ended June 30, 2021, per TEN 7-21.
  • Pending bill: H.R. 8210, the A Stronger Workforce for America Act of 2026, was introduced on April 6, 2026 and approved by the House Education and Workforce Committee later that month. As introduced, it rewrites the provider performance report provision.

Treat the bill as a reason to keep your pipeline configurable. The introduced text directs the Secretary of Labor to develop or revise report templates within 24 months of enactment.

Why can’t one export serve every state’s ETPL portal?

Federal rules fix the measures, but each state decides how providers submit them: portal, file type, columns and schedule. The regulation lets the state set the “timeframe” and “manner” of collection. Two states’ published guidance shows how far the formats can drift apart.

State What its provider guidance says
Wisconsin One individual-level CSV per program year, uploaded to the ETPL Provider Portal from the state’s template; altered templates are rejected. Columns include names, sex, date of birth, start and end dates, completed, withdrew and transferred flags, and credential fields. SSN is optional on the template but needed for wage and employment verification.
Rhode Island A guide marked November 2021 describes a cumulative program-year Excel file uploaded each quarter through its provider portal. It asks for an SSN or ITIN, start date, status, exit date and credential flag. Quarters 1 to 3 are due 20 days after quarter end; quarter 4 within 45 days.

These come from Wisconsin’s ETPL performance page and Rhode Island’s reporting guide. Do not copy them as a specification: your state’s current notice governs. Rhode Island’s site also carries a second, undated process document describing a form-based collection of program-level counts, so confirm which one applies.

The lesson is architectural. Keep each state’s columns, cadence and due dates as dated, sourced configuration that an adapter reads, the approach described in the post on grant-funded training data exports. Then a rule change becomes a configuration edit, not a rebuild.

How should an eligible training provider list ETPL reporting pipeline be designed?

Use five stages: capture events once in a canonical record, resolve each student to one identity, attach employment outcomes when the state supplies them, validate the counts, and export through a state-specific adapter. Each stage has one owner and one failure mode, so errors surface before the state sees them.

What should the canonical student record contain?

It should hold every field any state adapter might need, whatever the state’s column names, captured when each event happens:

  • An internal student key that never changes and is never an SSN.
  • Program of study ID with CIP code, hours and weeks, linked to a stable provider ID.
  • Start date, status (enrolled, completed, withdrew, transferred), exit date and exit reason.
  • Credential name and award date, so “within one year after exit” can be calculated.
  • A funding flag (WIOA or not) and any demographics your state requires.
  • The date and wording of the privacy notice the student saw.

How do you keep one identity per student and protect it?

In both states above, wage matching depends on an SSN or ITIN, so isolate that identifier. Store it in a separate encrypted table keyed to the internal student key, read it only inside the export job, and dedupe on name, date of birth and identifier before issuing a new key. The adapter decides whether a state wants it at all.

Plan for refusals and invalid numbers. Rhode Island’s guide says a student who refuses must be given a generated nine-digit identifier beginning with 000, and warns that an invalid number blocks wage matching. That is one state’s rule, so store a “refused” status in your own database, not a fake number.

On privacy, TEGL 3-18 says public ETPL reports must not reveal personally identifiable information, and that disclosing such information from education records must follow the Family Educational Rights and Privacy Act (FERPA), including its prior written consent requirements. Whether FERPA covers a given private provider is a question for your state agency or counsel. Rhode Island’s guide recommends telling students about the collection before enrollment and offers a sample letter.

How do employment and wage outcomes get attached?

The specification says employment is found “through a wage record match or other supplemental means”, and TEGL 3-18 encourages states to run wage matches on providers’ behalf. So accept whatever outcome file your state returns, keyed by student and quarter, and do not build a private wage database.

Quarter arithmetic matters. DOL’s TEGL 10-16 Change 3 (June 11, 2024) counts from the exit quarter: for an exit between January 1 and March 31, “the first quarter after exit would be April 1st through June 30th”. The second quarter after exit is then July to September. That guidance covers the WIOA performance indicators, so confirm your state applies it to ETPL data.

What does the counting logic look like in code?

The core logic is small: count enrolments in the program year, count exits and completions by exit date, and find the calendar quarter where each exiter’s outcomes sit. This Python sketch does that for invented data. It is a design sketch, not the DOL calculation.

from datetime import date as D

def quarter_window(exit_date, n):
    q = exit_date.year * 4 + (exit_date.month - 1) // 3 + n
    year, qi = divmod(q, 4)
    start = D(year, qi * 3 + 1, 1)
    nxt = D(year + (qi == 3), (qi + 1) % 4 * 3 + 1, 1)
    return start, D.fromordinal(nxt.toordinal() - 1)

def program_counts(students, py_start, py_end):
    out = {"served": 0, "exited": 0, "completed": 0, "credential": 0}
    for s in students:
        out["served"] += s["start"] <= py_end and (s["exit"] is None or s["exit"] >= py_start)
        if s["exit"] and py_start <= s["exit"] <= py_end:
            out["exited"] += 1
            out["completed"] += s["status"] == "completed"
            out["credential"] += s["credential"]
    return out

def employed_after_exit(students, wages, n, as_of):
    hits = denom = 0
    for s in students:
        if s["exit"] is None:
            continue
        start, end = quarter_window(s["exit"], n)
        if end >= as_of:          # window still open: leave out of the denominator
            continue
        denom += 1
        hits += wages.get((s["id"], start), False)
    return hits, denom

students = [  # invented, for illustration only
 dict(id="S1", start=D(2025,7,7),  exit=D(2025,9,26),  status="completed",   credential=1),
 dict(id="S2", start=D(2025,7,7),  exit=D(2025,8,15),  status="withdrew",    credential=0),
 dict(id="S3", start=D(2025,10,6), exit=D(2025,12,19), status="completed",   credential=1),
 dict(id="S4", start=D(2026,1,12), exit=D(2026,3,27),  status="completed",   credential=1),
 dict(id="S5", start=D(2026,4,6),  exit=None,          status="enrolled",    credential=0),
 dict(id="S6", start=D(2026,5,4),  exit=D(2026,6,12),  status="transferred", credential=0),
]
wages = {("S1", D(2026,1,1)): True, ("S1", D(2026,7,1)): True,
         ("S3", D(2026,4,1)): True, ("S4", D(2026,7,1)): False}

c = program_counts(students, D(2025,7,1), D(2026,6,30))
e2, d2 = employed_after_exit(students, wages, 2, D(2026,11,15))
e4, d4 = employed_after_exit(students, wages, 4, D(2026,11,15))
print(c)
print("Employed Q2:", e2, "of", d2, "| Q4:", e4, "of", d4)
assert c["exited"] >= c["completed"] and e2 <= d2 and e4 <= d4

Running it prints:

{'served': 6, 'exited': 5, 'completed': 3, 'credential': 3}
Employed Q2: 2 of 4 | Q4: 1 of 2

The student who exited in June 2026 is left out of both outcome counts because that window is still open. A real pipeline should also wait for the state’s data to be available, not merely for the quarter to end.

Before each export, run arithmetic checks like the final assert. Exits cannot be fewer than completions, employed counts cannot exceed their denominators, and no student may appear twice in a program year. A failed check should block the export. After a pass, store the exact file, a hash, the adapter version and the date, so a later state query can be answered with what you sent.

Pro tip: Test the calendar edges. Write unit tests for exits on December 31, January 1 and March 31, and the first day of a program year. Rollovers are where hand-rolled date logic fails, and a one-quarter error moves a student into the wrong outcome window.

What should you do next?

Start with your state’s ETPL page and provider policy: find the current file template, the identifier rule, the schedule and the contact for data questions. Then list which fields in the table above you can already produce from enrolment and exit records. The gaps are your build list.

If you run sessions and enrolment in a training management system, check that it can export the canonical fields before designing anything new. SimpliTrain, Mundrisoft’s training management platform, covers scheduling, assessments and certification tracking, according to its demo page. Its public pages do not mention ETPL or WIOA, so ask in a demo what it can export rather than assuming a fit.

Ask a workforce compliance specialist or your state ETPL coordinator to read your final mapping before the first live submission.

Frequently asked questions

Do ETPL reporting rules apply to students who are not WIOA-funded?

Yes. DOL’s TEN 7-21 says the waiver that limited reporting to WIOA-funded students expired on June 30, 2021. Since program year 2021, states report for WIOA participants and all students in a program of study, so providers need outcome-ready records for every student.

Do I have to collect Social Security numbers for ETPL reporting?

The federal provisions reviewed for this guide do not name SSNs, and states choose how to get outcomes. Wisconsin’s template makes the SSN optional but needed for wage verification, while Rhode Island’s guide asks for an SSN or ITIN. Ask your state which identifier it accepts, and how it wants refusals recorded.

How often do providers have to report ETPL data?

The regulation says providers submit performance and cost information for each program at least every two years, on a timeframe the state sets. States report annually to DOL. Providers see anything from annual uploads, as in Wisconsin, to quarterly ones, as in Rhode Island’s guide.

Who calculates employment and earnings outcomes?

Usually the state. The ETA-9171 specification says employment is determined through a wage record match or other supplemental means, and TEGL 3-18 encourages states to run wage matches for providers. The “other supplemental means” wording leaves room for provider-supplied evidence, so ask whether your state expects any.

What happens if the data we submit is wrong?

The statute ends eligibility for at least two years where a provider intentionally supplies inaccurate information. States also review eligibility information at least every two years and may set minimum performance levels for continued eligibility. Honest errors fall under your state’s procedure, so correct them quickly.

Alert: mundrisoftcareers.com is not affiliated with Mundrisoft Solutions. Beware of fake job offers and trust only our official recruitment channels.