Analytics for workforce development boards
Six primary indicators, defined in federal regulation, most measured two and four quarters after a participant exits. A record layout with hundreds of data elements behind it. A state system that rejects a file for a logic error without naming the case that caused it. And a board that meets next week and wants to know whether the numbers are moving the right way.
Blue Peak Data Consulting builds the reporting layer between your case management system and all of that: indicator dashboards, PIRL data quality checks that run before the file goes up, provider and one stop operator reporting, and the board packet on a schedule. Built in your own environment and handed over so your staff can change it.
What gets built
A first project is usually one or two of these, not all five.
Performance indicator dashboards
The six primary indicators at 20 CFR 677.155, each a rate with its numerator and denominator visible: employment in the second and fourth quarters after exit, median earnings in the second quarter, credential attainment, measurable skill gains, and effectiveness in serving employers. Broken out by program, provider and office, against your negotiated levels.
The lag problem, made visible
These indicators land two to four quarters after exit, so what your dashboard shows this month describes people who left a year ago. We build the exit cohort view beside the outcome view, so you see what is coming, not only what landed.
PIRL data quality checks
The checks that catch a record before the state system does: missing required elements, dates out of sequence, exits without a reason, credential dates outside the one year window, participants with services but no enrollment.
Provider and one stop operator reporting
Outcomes by training provider and program of study with cost and completion beside them, so eligible training provider decisions run on evidence. Traffic, service mix and outcomes by center, with the partner referral picture across the one stop.
Board packets, automated
The recurring packet that eats a week of somebody’s month becomes a scheduled refresh and an export. Same layout, same definitions, ready before the meeting.
What the state files, and what you owe it
For WIOA core programs under titles I and III, the U.S. Department of Labor requires each state grantee to file the WIOA Annual Report on the ETA-9169 template by October 1 in the Workforce Integrated Performance System, with the Eligible Training Provider report on ETA-9171. The Annual Statewide Performance Report Narrative follows on December 1. The quarterly performance report on ETA-9173 and the quarterly narrative report on ETA-9179 are due through the same system on the 15th day of the second month of the following quarter.
Those submissions are the state’s, not yours. What is yours is the data underneath them and the local area rows inside them. Since the March 2024 final rules adopted retention with the same employer as the effectiveness in serving employers criterion, title I formula grantees file that indicator twice, once statewide and once combining title I results for each local area. Local performance reaches a federal report either way.
Why PIRL checks belong on your side of the wall
The state system checks format, not meaning
Your state’s submission system validates format, value types and logical relationships between elements, and rejects non compliant files until the errors are fixed. What it cannot tell you is that a field is filled in correctly but wrong, the error that quietly moves a rate.
A PIRL file is not a snapshot
Each file carries at least two and a half years, ten quarters, of reportable individual, participant and exiter data, and DOL is moving programs from the 2021 layout to the 2025 one at different times. A mapping that worked last quarter can stop working next, so the check reads the layout.
The fix is upstream
Every error the checks surface points at a field somebody enters in the case management system. The useful output is not a list of bad records. It is a short list of the entry habits producing them, sent to the people who can change them.
Discovery
We read your case management export, your PIRL file and your provider and cost records, then agree what the first dashboard has to answer and which indicators it must reproduce. You get a written scope and a written quote before anything is signed. We will not claim familiarity with a case management system we have not worked in.
Solution design
The measures get defined once, following the federal specifications: who is in each numerator, who is in each denominator, which exclusions apply, and how a cohort period is bounded. Definitions live in the model, not in each report page, which is why numbers stop disagreeing.
Implementation
Report pages and the checks get built against your real data and reviewed with you as they go. Where a figure has to tie to a submitted report, we tie it and show the tie.
Optimization and handoff
Two to four weeks of tuning after the first release, usually across one reporting cycle, then you get the .pbix file, the documentation and a session with whoever maintains it. The model is yours, and if you never call us again everything keeps running.
What it costs and how you buy it
A quote from a written scope, each phase its own scope, acceptance and invoice. You buy the first dashboard, see it work through a reporting cycle, then decide whether there is a second. No annual license from us, no hosting fee, no seat count. If your office needs a quote with a statement of work attached, say so. Blue Peak is a SAM.gov active small business, UEI PRPBEM9HEND3, CAGE 15CS5, and will complete whatever vendor registration your board requires before an award.
Who does the work
Blue Peak’s senior consultants lead every build, and whoever scopes your dashboard builds it. Our lead consultant brings twelve years in production analytics, most of it in Power BI, SQL Server and the Microsoft stack.
That consultant led reporting on a $30M multi jurisdictional federal initiative from 2019 to 2022, integrating grantee data across jurisdictions and producing grant compliance reporting that passed federal funder review, and built an analytics product line used by more than 100 people at a national telecom, unifying a sales pipeline spanning six source systems into one Power BI environment.
That record was earned before Blue Peak, so we describe it as our people’s experience rather than the firm’s past performance, on purpose. What you get is people who have built performance reporting on grant funded programs where the numbers were checked.
Questions boards ask
What are the WIOA primary indicators of performance?
Six, set out at 20 CFR 677.155: the percentage of participants 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, credential attainment, measurable skill gains, and effectiveness in serving employers. For the youth program the first two indicators count education or training activities as well as employment. Credential attainment and measurable skill gains do not apply to the title III Employment Service program.
What is the PIRL and who files it?
The Participant Individual Record Layout is the standard record level file behind WIOA performance reporting. ETA-9170 is the joint layout used across the core programs; ETA-9172 is the Department of Labor only version. States submit PIRL files through the Workforce Integrated Performance System, which runs edit checks and aggregates the records into the quarterly and annual reports. Local areas do not file to that system, but the records in it are the ones your staff entered.
When are the WIOA performance reports due?
The Annual Report on the ETA-9169 template and the Eligible Training Provider report on ETA-9171 are due in the Workforce Integrated Performance System by October 1. The Annual Statewide Performance Report Narrative is due December 1. The quarterly performance report on ETA-9173 and the quarterly narrative report on ETA-9179 are due on the 15th day of the second month of the following quarter. Those are the state’s deadlines, and your data has to be clean well before each one.
Can you fix our WIOA data quality problems?
We can make them visible, which is the part that is actually missing. The checks run against your own file and point at the field and the record. The fix itself happens in your case management system, by the staff who enter the data, and it holds only if the checks keep running afterward. Any vendor who offers to clean your data once and leave is selling you a snapshot.
Do you work with the state agency or just the local workforce board?
Either. Most local boards start on their own data because they control it and can move quickly. Where the state agency is the grantee and the submission holder, we work to whatever data sharing arrangement the two of you already have and do not attempt to create a new one. We never ask for data your agreements do not cover.
Where does workforce participant data live and who can see it?
In your environment. Reports are built and published in your board’s or your agency’s own Microsoft tenant, never copied to a Blue Peak server and never sent to an outside service for processing. Participant records are personally identifiable, so row level security is configured from the start: a center manager sees their center, a board member sees aggregates, and the access rules are documented so your IT staff can audit them. Where a view can be built on aggregates rather than records, that is the version we would rather build.
Send one line: the report you hate producing
Email sergei@bluepeakdataconsulting.com and name the recurring report that costs you the most time, plus a rough figure for how long it takes today. You get an honest read back within one business day: what it would take, roughly how long, and whether it is worth doing at all.