How to Report Workforce Program Outcomes the Public Can Understand

A workforce board’s annual report states that its adult program achieved an employment rate in the second quarter after exit that exceeded its negotiated performance level. To the state agency that negotiated that level, the sentence carries real information. To a county commissioner deciding whether to support the board’s budget, it is a string of qualifiers. To a resident wondering whether the career center could help her find a better job, it is almost meaningless. She does not know what exit means in this context, why the second quarter matters, what a negotiated level is, or whether the number is good, bad, or ordinary. The board has reported its outcomes accurately and in full compliance with federal requirements. It has also communicated almost nothing to most of the people who might care.

The public workforce system collects a remarkable amount of outcome data. Under the Workforce Innovation and Opportunity Act, programs report standardized performance indicators, including employment rates after participants leave services, median earnings, credential attainment, measurable skill gains, and effectiveness in serving employers. States negotiate performance levels with the federal government and with local boards. Data are validated, adjusted for participant characteristics through a statistical model, and reported quarterly and annually. Much of this information is publicly available. Yet very little of it reaches the public in a form that people can understand and use. Outcome reporting in the workforce system is largely designed for compliance, written by and for people who already understand the system’s technical vocabulary.

This matters for several reasons. Residents deciding whether to use the career center or enroll in training deserve to know what results people like them have achieved. Employers deciding whether to hire through the system want evidence that it produces capable workers. Elected officials and funders deciding whether to invest need outcome information they can interpret and explain to their own constituents. Journalists covering the workforce system need data they can report accurately. And the system’s own credibility depends on the public’s ability to see that it produces results, or to see clearly where it falls short.

This article examines how workforce agencies can report program outcomes in ways the public can understand. Its central argument is that outcome reporting for the public is a translation task, not a reformatting task: agencies must decide which outcomes matter to which audiences, explain what each measure actually means in plain language, provide the context needed to interpret numbers, present data visually without distortion, acknowledge limitations honestly, and report equitably while protecting privacy. Doing so does not require abandoning technical accuracy. It requires carrying that accuracy across the gap between the system’s vocabulary and the public’s.

Compliance Reporting Versus Public Understanding

Workforce agencies report outcomes for two very different purposes, and confusing them is the root of most public reporting problems. Compliance reporting serves accountability within the system: states report to the federal government, local boards report to states, and providers report to boards. Its audience is technical, its definitions are precise, and its format is standardized so that results can be compared and aggregated. Public reporting serves understanding outside the system: it helps residents, employers, officials, and journalists grasp what the system does and how well it does it. Its audiences are diverse, mostly non-technical, and interested in meaning rather than specifications.

Compliance reporting is necessary and valuable. Standardized definitions allow fair comparisons across areas. Statistical adjustment accounts for differences in the people served. Data validation protects accuracy. Negotiated performance levels create accountability. None of this should be abandoned. The problem arises when compliance reports are treated as public reports, posted online or distributed to officials without translation, on the assumption that publishing the data is the same as communicating it.

Publishing compliance data without translation has predictable effects. Most readers cannot interpret it and ignore it. Some readers interpret it incorrectly, drawing conclusions the data do not support, such as assuming that a lower employment rate means a worse program, when it may reflect a program that serves people with greater barriers. A few readers, including journalists and critics, may seize on numbers out of context. And the agency loses the opportunity to explain its results, its challenges, and its value.

The distinction between compliance and public reporting also affects tone and framing. Compliance reports are often organized around whether the agency met its targets, with results framed as pass or fail against negotiated levels. This framing matters for accountability but is less meaningful to the public, who want to know what happened to people, not whether the agency met a number negotiated with another government agency. Public reports can include performance against targets, but they should lead with what outcomes mean for residents and employers.

Recognizing the two purposes allows agencies to design each type of reporting for its audience. Compliance reporting continues as required. Public reporting draws on the same data but selects, explains, contextualizes, and presents it differently. The two should be consistent, since public reports must accurately reflect compliance data, but they need not look alike. A public report might present three or four key outcomes in plain language with clear visuals, while the full compliance report remains available for those who want detail.

This approach requires investment. Translating outcome data for the public takes time, analytical skill, and communication expertise. Many workforce agencies have strong data staff but limited communication capacity, or communication staff who are not comfortable with data. Public reporting works best when data and communication staff collaborate, each contributing expertise.

The investment is worthwhile because outcome reporting shapes how the public perceives the workforce system. A system that reports outcomes clearly, honestly, and accessibly builds credibility and support. One that reports only in technical terms, or not at all, leaves the public to form impressions from anecdotes, assumptions, and occasional critical news stories.

What the Federal Performance Indicators Actually Measure

Before agencies can explain outcomes to the public, staff responsible for communication need a clear understanding of what the federal performance indicators measure, and what they do not. The summaries below describe the primary indicators of performance under WIOA in general terms. Precise definitions are set in federal law, regulations, and guidance, and agencies should consult those sources for technical details.

Employment Rate After Exit

Two indicators measure the share of participants who are in unsubsidized employment during the second quarter after they exit the program and during the fourth quarter after exit. For youth programs, the corresponding indicators include participants in education or training activities as well as employment. Exit generally occurs when a participant has not received services for a period and has no future services planned, so the measures look at outcomes roughly six months and one year after services end. Employment is typically verified through state unemployment insurance wage records, which capture most but not all employment.

What these indicators show is whether participants were working at those points after leaving services. What they do not show is whether the job was related to training, full-time, or good quality, or whether the program caused the employment, since participants might have found work without services.

Median Earnings

This indicator measures the median earnings of participants who are in unsubsidized employment during the second quarter after exit. The median is the middle value, so half of employed participants earned more and half earned less. Earnings are quarterly, not hourly or annual, which can make interpretation difficult for the public.

What this indicator shows is the typical earnings of employed participants shortly after leaving services. It does not show earnings for participants who were not employed, earnings growth over time, or hourly wages.

Credential Attainment

This indicator measures the share of participants enrolled in education or training who obtain a recognized postsecondary credential, or a secondary school diploma or equivalent combined with employment or further education, during participation or within a year after exit. Credentials include industry-recognized certificates, licenses, degrees, and others meeting federal definitions.

What it shows is whether participants in training earned recognized credentials. It does not show the value of particular credentials in the labor market.

Measurable Skill Gains

This indicator measures the share of participants in education or training programs that lead to a credential or employment who achieve documented progress toward that goal during a program year, such as passing exams, completing training milestones, or advancing educational levels. It is a measure of progress during participation rather than an outcome after exit.

Effectiveness in Serving Employers

This indicator assesses how well the system serves employers. States have used approaches such as retention with the same employer, repeat business customers, and the share of employers in an area served by the system, and federal guidance on this indicator has evolved.

Statistical Adjustment and Negotiated Levels

Performance levels are negotiated between states and the federal government, and between states and local boards, using a statistical adjustment model that accounts for economic conditions and participant characteristics. This means that targets differ across areas and that a lower outcome may be appropriate for an area serving participants with greater barriers or facing weaker labor markets.

Understanding these indicators, including their limitations, is essential before translating them for the public. Communication staff should work closely with data staff to ensure accurate interpretation.

Why Standard Reports Confuse the Public

Standard workforce outcome reports confuse the public for reasons that go beyond jargon. The structure of the data itself creates interpretation challenges that must be addressed explicitly if public reporting is to succeed.

The first source of confusion is time lag. Because employment and earnings indicators are measured in the second and fourth quarters after exit, and because unemployment insurance wage records take time to become available, outcome data typically describe people who left services a year or more before the report is published. A report released this year may describe participants who received services two years ago, under different labor market conditions and possibly different program designs. The public naturally assumes a report describes current performance, and the lag is rarely explained.

The second source is the concept of exit. Outcomes are measured after participants exit, but exit is a technical event defined by the absence of services for a period, not a graduation or completion. The public may assume that outcomes describe people who completed programs, when they actually describe all exiters, including those who left early.

The third source is denominators. Each indicator applies to a specific group of participants, and the groups differ. Credential attainment applies only to participants in education or training, not to all participants. Median earnings applies only to employed participants. When a report presents several percentages side by side, readers may assume they all describe the same group, which leads to misinterpretation.

The fourth source is quarterly earnings. Median earnings are reported as quarterly amounts, which most people do not use to think about wages. A figure that represents a modest hourly wage may look either impressive or meager to readers who do not convert it.

The fifth source is negotiated levels. Reports that compare actual outcomes to negotiated targets, without explaining how targets are set, invite misunderstanding. A reader seeing that a local area exceeded its target may assume strong performance, while a reader seeing that another area fell short may assume weak performance, even though targets differ by area based on economic conditions and participant characteristics.

The sixth source is attribution. Outcome indicators show what happened to participants, not what the program caused. Many factors influence whether a participant finds employment, including the labor market, personal circumstances, and other services. The public often interprets outcome data as evidence of program impact, which overstates what the data can show.

The seventh source is aggregation. Outcomes reported for a whole program or area may mask large differences among participants, services, and locations. An overall employment rate may combine very different results for participants in training and those receiving only basic services, or for participants in different occupations.

The eighth source is comparison without context. Readers naturally compare numbers across areas, programs, or years, but differences may reflect who was served, economic conditions, or data changes rather than program quality.

Each of these sources of confusion can be addressed through explanation, context, and careful presentation. But none will be addressed automatically. Agencies that publish standard reports without attending to these issues should expect the public to misunderstand them. The sections that follow describe how to report in ways that anticipate and prevent misunderstanding.

Deciding What the Public Needs to Know

Public outcome reporting begins with selection. Workforce agencies have far more data than any public audience can absorb, and presenting everything overwhelms readers. Effective public reports select a small number of outcomes that matter most to their audiences and present them well, with fuller data available for those who want it. Deciding what the public needs to know requires thinking about audiences, their questions, and the decisions they face.

The first question to ask is who the report is for. A report for residents considering services will emphasize different outcomes than a report for county commissioners considering funding or a report for employers considering partnership. Many agencies try to produce a single report for all audiences, which often serves none well. A core public report with tailored versions or summaries for specific audiences is usually more effective.

The second question is what each audience wants to know. Residents typically want to know whether people like them found jobs after using services, how much they earned, and whether training led to credentials and better jobs. Employers want to know whether the system produces workers with relevant skills, how many hires it supports, and whether workers stay. Elected officials want to know how many people were served, what results were achieved, how public funds were used, and how results compare with expectations. Journalists want clear, accurate facts and context.

The third question is which outcomes answer those questions. For residents, employment rates after services, typical earnings expressed in familiar terms, and credential attainment for those in training may be most relevant. For employers, the number of employers served, hires, and retention may matter most. For officials, numbers served, key outcomes, cost information where available, and performance relative to targets may matter. Selecting outcomes that answer each audience’s questions keeps reports focused.

The fourth question is what level of detail is appropriate. Overall outcomes for the whole system provide a summary, but they may be too general to be useful. Outcomes for particular programs, such as training versus career services, or for particular occupations or populations, provide more useful information to residents considering specific services. Public reports can present a few headline outcomes and then offer more detailed breakdowns for those who want them.

The fifth question is what beyond federal indicators the public needs. Federal indicators are standardized but limited. Residents may want to know about job quality, such as whether jobs offered benefits or were full-time. Officials may want to know about local priorities, such as outcomes in target industries or for particular communities. Where agencies have reliable data on these matters, including them can make reports more meaningful, provided the data’s limitations are explained.

The sixth question is what should not be emphasized. Some data, while required for compliance, may confuse the public without adding value, such as complex adjustment factors or technical details of measurement. These can remain in compliance reports and technical appendices.

Selection should be deliberate and transparent. Agencies should avoid selecting only favorable outcomes while omitting unfavorable ones, which would mislead. The selection should be based on what matters to audiences, with the full data available for anyone who wants to examine it. A brief note explaining what the report covers and where to find complete data supports transparency.

Deciding what the public needs to know is a communication decision informed by data expertise. Communication staff understand audiences; data staff understand what the data can support. Making these decisions together produces reports that are both meaningful and accurate.

Translating Indicators Into Plain Language

Once agencies have selected the outcomes to report, they must explain each in language the public can understand. Translation involves more than replacing jargon with simpler words. It involves describing what each measure means, who it covers, and when, in terms that connect to readers’ experience, while remaining accurate.

The first principle is to describe outcomes in terms of people. Instead of reporting that the employment rate in the second quarter after exit was a certain percentage, a public report can say that about seven out of ten adults who received services were working about six months after they finished. The number is the same, but the description connects to people’s lives. Using approximate fractions or simple percentages, rather than decimals, makes numbers easier to grasp.

The second principle is to define the group. Each outcome should state clearly whom it describes. A credential attainment figure should be described as the share of people who enrolled in training and earned a certificate, license, or degree, not as a figure for all participants. Clarity about the group prevents readers from comparing numbers that describe different people.

The third principle is to explain timing. Reports should state when outcomes were measured and which period of services they describe. A sentence such as these results describe people who finished services between a stated period, measured about six months and one year later, helps readers understand that the report reflects past services. Explaining the lag, and why it exists, prevents readers from assuming the report describes current performance.

The fourth principle is to convert earnings into familiar terms. Quarterly median earnings can be presented alongside an approximate hourly or annual equivalent, with a note about the assumptions used, such as full-time work. Explaining that the median means half earned more and half earned less helps readers interpret it. Agencies should be careful that conversions are reasonable and clearly labeled as approximations.

The fifth principle is to explain what exit means. A brief note that people are counted as having finished services when they stopped receiving services, whether or not they completed a program, prevents the assumption that outcomes describe only completers.

The sixth principle is to describe measures of progress differently from outcomes. Measurable skill gains describe progress during participation, such as passing an exam or completing a training milestone, not results after services. Describing them as progress during training distinguishes them from employment outcomes.

The seventh principle is to explain targets plainly. If reports include performance against negotiated levels, they should explain that targets are agreed with the state and adjusted for local economic conditions and the characteristics of people served. A sentence such as targets are higher in areas with strong job markets and lower in areas where more participants face barriers to employment helps readers understand why targets differ.

The eighth principle is to avoid implying causation. Plain-language descriptions should describe what happened to participants, not claim that services caused those results, unless evidence from rigorous evaluation supports such claims. Phrasing such as people who received services were working at these rates is accurate; phrasing such as services helped this many people get jobs implies causation the data cannot establish.

Plain-language translations should be reviewed by data staff for accuracy and tested with members of the intended audience for clarity. A glossary of key terms, written in plain language, can accompany reports for readers who want more detail. Consistent use of the same plain-language descriptions across reports and years helps readers become familiar with them.

Giving Numbers Context

A number without context invites misinterpretation. An employment rate of sixty-five percent might be strong for a program serving people with significant barriers in a weak labor market, or modest for a program serving recently laid-off skilled workers in a strong one. Median earnings that seem low may represent substantial gains for participants who had no income before services. Public reports that present numbers without context leave readers to supply their own, usually based on assumptions that may not fit. Providing context is essential to honest, useful outcome reporting.

The first form of context is who was served. Outcomes depend heavily on the characteristics of participants. A report that describes the people served, such as the share who were unemployed at entry, had low incomes, lacked a high school credential, had disabilities, had been involved with the justice system, or faced other barriers, helps readers understand outcomes. A program that serves many people facing barriers may have lower outcomes than one serving people with fewer barriers, while adding more value. Describing participants, in aggregate and without identifying individuals, is essential context.

The second form is economic conditions. Labor market conditions during and after services strongly affect employment outcomes. A report can briefly describe the local labor market during the period covered, such as unemployment rates and job growth, and note how conditions may have affected outcomes.

The third form is trends over time. Presenting outcomes for several years shows whether results are improving, stable, or declining, which is often more informative than a single year. Trends should be presented with attention to changes in definitions, data systems, or programs that might affect comparability.

The fourth form is comparison with relevant benchmarks. Comparisons with state averages, similar local areas, or prior years can help readers interpret results, provided the comparisons are fair. Comparisons should account for differences in who is served and in economic conditions. Comparisons with negotiated targets, explained as described earlier, provide another benchmark.

The fifth form is the starting point. Where data allow, describing participants’ situations before services, such as employment status or earnings before enrollment, helps readers understand change. A median earnings figure is more meaningful when readers know that many participants were unemployed or earning very little before services. Pre-service and post-service comparisons should be presented carefully, since they do not prove that services caused the change.

The sixth form is distinguishing services. Outcomes often differ substantially between participants who received training and those who received only career services, or among participants trained in different occupations. Breaking outcomes down by type of service or occupation, where sample sizes allow, gives readers more useful information.

The seventh form is cost and scale. For officials and funders, context about the number of people served and the resources used helps them understand outcomes in relation to investment. Cost information should be presented carefully, since costs per participant vary with services provided and populations served, and simple cost comparisons can mislead.

The eighth form is qualitative context. Brief descriptions of program changes, challenges, or notable developments during the period, such as a major layoff that increased dislocated worker enrollments, help readers understand outcomes.

Context should be provided concisely. Reports that bury outcomes under extensive caveats lose readers. The goal is to provide enough context for accurate interpretation, presented clearly alongside the outcomes, with additional detail available for those who want it.

Visualizing Outcomes Honestly

Charts, graphs, and infographics can make outcome data far more accessible than tables of numbers. A simple bar chart comparing employment rates over time, or an icon array showing seven out of ten people working, communicates quickly and memorably. But visualizations can also mislead, sometimes unintentionally, by exaggerating differences, hiding uncertainty, or implying comparisons that are not valid. Honest visualization combines accessibility with accuracy.

The first principle is choosing the right chart for the message. Bar charts work well for comparing values across categories, such as outcomes for different programs. Line charts work well for showing trends over time. Simple icon arrays, in which a set of figures represents a group of people with some highlighted, make percentages concrete for general audiences. Pie charts work for showing parts of a whole but become hard to read with many categories. Choosing the simplest chart that conveys the message clearly is usually best.

The second principle is honest scales. Bar charts should generally start at zero, since truncated axes exaggerate differences. A chart showing employment rates of seventy and seventy-four percent with an axis starting at sixty-five makes a small difference look large. Line charts showing trends may use scales that do not start at zero, but they should be labeled clearly and should not exaggerate fluctuations.

The third principle is clear labeling. Every chart should have a clear title stating what it shows, labeled axes, units, and the time period covered. Labels should use plain language consistent with the report’s text. Readers should be able to understand a chart without reading the surrounding text, though text can provide additional context.

The fourth principle is showing the right comparisons. Charts that place outcomes for different programs or areas side by side invite comparison. If those programs serve different populations or operate in different conditions, the chart should note this, or the comparison should be omitted. Charts should not imply that differences reflect program quality when they may reflect other factors.

The fifth principle is representing uncertainty and small numbers. Outcomes based on small numbers of participants can fluctuate widely and may not be reliable. Charts can indicate where numbers are small, for example by noting the number of participants, using lighter shading, or suppressing results below a threshold. Presenting small-sample results as definitive misleads readers.

The sixth principle is avoiding decorative distortion. Three-dimensional effects, exaggerated icons, and decorative elements can distort perception and distract from the data. Simple, clean visuals communicate more reliably.

The seventh principle is accessibility. Visualizations must be accessible to people with disabilities. This includes alternative text describing the chart’s content, sufficient color contrast, not relying on color alone to convey meaning, and providing the underlying data in an accessible table. Digital reports should meet recognized accessibility standards, consistent with the Department of Justice’s 2024 rule establishing technical standards for state and local government web content and mobile applications.

The eighth principle is consistency. Using consistent chart types, colors, and labels across reports and years helps readers learn to interpret them and compare results over time.

The ninth principle is testing. Showing draft visualizations to members of the intended audience and asking what they understand reveals whether charts communicate as intended. A chart that seems clear to data staff may confuse residents.

Honest visualization respects readers by giving them an accurate picture they can grasp quickly. It also protects the agency’s credibility, since misleading charts, once noticed, undermine trust in everything else the agency reports.

Reporting Limitations and Uncertainty

Workforce outcome data have real limitations, and honest reporting acknowledges them. Agencies are sometimes reluctant to discuss limitations, fearing that doing so will undermine confidence in their results. In practice, acknowledging limitations appropriately builds credibility, because it shows that the agency understands its data and is not overstating its case. Readers who later discover limitations the agency did not mention may conclude that the agency was hiding something.

The first limitation to acknowledge is that outcomes do not prove impact. Outcome indicators show what happened to participants after services, not what services caused. Some participants would have found jobs without services; others might have done better with different services. Determining program impact requires rigorous evaluation methods, such as comparison groups, which outcome reporting does not provide. Reports should describe outcomes as results experienced by participants, not as effects of the program, unless evaluation evidence supports causal claims. Where rigorous evaluations of similar programs exist, reports can cite them carefully, noting that findings from other evaluations may not apply directly.

The second limitation is coverage of employment data. Employment outcomes are typically measured through state unemployment insurance wage records, which capture most employment covered by unemployment insurance in the state. They may miss self-employment, some federal employment, informal work, and employment in other states unless interstate data exchange is used. Reports can note that employment figures may undercount some forms of work.

The third limitation is time lag, discussed earlier. Reports should explain that outcomes describe people who received services in an earlier period and may not reflect current programs or labor market conditions.

The fourth limitation is small numbers. Outcomes for small programs, small local areas, or small subgroups may be based on few participants and may fluctuate substantially from year to year. Reports should note when numbers are small and avoid drawing strong conclusions from them. Some results may need to be suppressed to protect privacy, as discussed in the next section.

The fifth limitation is changes over time. Changes in program design, data systems, definitions, or reporting rules can affect comparability across years. Reports presenting trends should note significant changes that might affect interpretation.

The sixth limitation is what the indicators omit. Federal indicators do not measure many things the public may care about, such as job quality, benefits, career advancement, or long-term earnings. Reports can acknowledge that the indicators capture important but limited aspects of outcomes, and can supplement them with other information where available and reliable.

Limitations should be presented proportionately. A brief, plain-language note on key limitations, placed near the outcomes it concerns, is usually sufficient for public reports. More detailed technical notes can appear in appendices. Burying outcomes under extensive caveats discourages readers, while omitting limitations misleads them. The goal is enough acknowledgment for accurate interpretation.

Uncertainty should also be communicated when reporting projections or preliminary data. If a report includes preliminary outcomes that may change as more data become available, it should say so. If it includes projections, such as expected outcomes for current participants, it should explain the basis and uncertainty.

Acknowledging limitations is not a sign of weakness. It reflects a mature, honest approach to data that sophisticated readers, including officials, funders, journalists, and researchers, recognize and respect. It also protects the agency when results are challenged, because the agency has already explained what its data can and cannot show.

Equity, Disaggregation, and Privacy

Overall outcomes can hide important differences among groups of participants. An employment rate that looks strong for the program as a whole may mask much lower rates for participants with disabilities, older workers, people with limited English proficiency, or residents of particular neighborhoods. Reporting outcomes by group, known as disaggregation, reveals whether the workforce system serves everyone well and where gaps exist. At the same time, disaggregated data can threaten individual privacy when groups are small. Balancing equity and privacy is a core challenge in public outcome reporting.

Disaggregation serves several purposes. It shows whether outcomes differ across groups defined by characteristics such as sex, age, race and ethnicity, disability status, veteran status, and barriers to employment. WIOA performance reporting includes disaggregation by various characteristics, and the law’s nondiscrimination provisions call for attention to equitable service. Disaggregated public reporting helps residents, officials, and advocates see whether the system serves their communities, and helps agencies identify where to improve.

Disaggregated results must be interpreted carefully. Differences in outcomes among groups may reflect differences in services received, barriers faced, labor market discrimination, occupations pursued, or other factors, not only differences in program quality. Reports should present disaggregated outcomes with context, avoiding implications that groups with lower outcomes are less capable or that differences are caused by the program alone. Where agencies have identified causes of disparities and are taking steps to address them, reports can describe those steps.

Privacy protection is essential. When groups are small, reporting outcomes may allow individuals to be identified, especially in small local areas. A report stating that one participant with a particular combination of characteristics in a small county was not employed could identify that person. Agencies should apply suppression rules, such as not reporting results for groups below a minimum size, and should consider complementary suppression to prevent small numbers from being calculated by subtraction. Many states have established suppression thresholds, and agencies should follow applicable state and federal guidance.

Privacy considerations extend to how data are combined. Combining several characteristics, such as age, disability status, and location, can create very small groups even when each characteristic alone covers many people. Reports should limit the number of characteristics combined in public tables.

When results are suppressed, reports should explain why, so readers understand that missing figures reflect privacy protection rather than missing data or concealment. A brief note stating that results for groups with fewer than a stated number of participants are not shown to protect privacy is sufficient.

Aggregation across years or areas can make disaggregated results more reliable and less identifying. Reporting outcomes for a subgroup over several years combined, or across a region rather than a single local area, may provide meaningful information where single-year or single-area results would be too small.

Disaggregated reporting should be paired with action. Reporting disparities without explaining what the agency is doing about them may frustrate readers and communities. Reports can describe strategies to address gaps, such as targeted outreach, accommodations, language access, or partnerships with community organizations, and can report on progress over time.

Communities affected by disparities should be engaged in interpreting and responding to data. Sharing disaggregated results with community organizations and advocates, and inviting their perspectives, can deepen understanding and build trust.

Equitable outcome reporting reflects the public workforce system’s commitment to serving everyone. Done with care for privacy and context, it strengthens accountability and guides improvement.

Reporting for Different Audiences

Different audiences approach workforce outcomes with different questions, levels of expertise, and time. A single report rarely serves all of them well. Agencies can maintain a common foundation of data and plain-language explanation while tailoring presentation to each audience’s needs.

Residents and Jobseekers

Residents considering services want to know whether the workforce system can help people like them. They benefit from brief, accessible summaries that answer practical questions: how many people found jobs, what typical earnings looked like, whether training led to credentials, and what outcomes looked like for particular training programs or occupations. Information should be available in the languages residents speak and in formats accessible on mobile devices. Outcome information for specific training programs, such as that published for eligible training providers, can help residents choose training, provided it is presented clearly.

Employers

Employers want evidence that the system produces capable workers and supports hiring. They benefit from information about the number of employers served, hires supported, retention of workers hired through the system, credentials earned in relevant fields, and employer satisfaction where measured. Brief, business-oriented summaries, perhaps shared through business services staff and employer networks, are more useful to employers than full reports.

Elected Officials and Funders

Officials and funders want to understand results in relation to public investment and community priorities. They benefit from concise summaries of key outcomes, numbers served, context about populations and economic conditions, performance relative to targets explained plainly, and descriptions of how funds were used. They often need information they can share with constituents, so summaries should be quotable and accurate. Briefings that allow questions are often more effective than written reports alone.

Board Members

Workforce board members, many of whom are business leaders, need outcome information to govern effectively. They benefit from regular, concise dashboards showing key outcomes, trends, and comparisons, with explanation sufficient for informed oversight. Board members also serve as ambassadors to the community, so they benefit from plain-language talking points.

Journalists

Journalists covering the workforce system need accurate, clear facts and context, often on tight deadlines. Fact sheets with key outcomes, definitions, context, and contact information for staff who can explain the data help journalists report accurately. Proactive outreach when reports are released, with staff available to answer questions, reduces the risk of misinterpretation.

Partners and Advocates

Community organizations, training providers, and advocates may want more detailed data, including disaggregated outcomes, to understand how the system serves their communities. Providing access to more detailed data, with appropriate privacy protections, supports their engagement.

Researchers and Technical Audiences

Some readers want full technical detail. Making complete compliance data, definitions, and methodology available, perhaps through a data portal or technical appendix, serves these readers and supports transparency.

Tailoring reports to audiences does not mean presenting different facts to different groups. All versions should be consistent with one another and with the underlying data. What changes is the selection, level of detail, framing, and format. Consistency across versions protects credibility, since audiences may compare them.

Producing multiple versions requires efficient processes. Agencies can develop a core set of plain-language outcome descriptions, charts, and context statements that are reused across versions, adapting presentation for each audience. Templates reduce the effort of producing tailored reports each year.

Reporting Training Provider Outcomes to Help People Choose

One form of outcome reporting has unusually direct consequences for individual decisions: performance information about training programs on the state’s eligible training provider list. Under WIOA, training providers seeking to serve participants with individual training accounts report performance information, and states make information about providers and programs available to help jobseekers choose training. For a resident deciding where to spend months of effort and a limited training voucher, this information can be among the most important outcome data the system produces. It is also among the most difficult to present well.

The first challenge is that program-level numbers are often small. A particular certificate program at a particular provider may enroll only a handful of WIOA participants in a year, making outcome rates unstable and potentially identifying. States commonly suppress or combine results below a minimum size, which leaves many programs without displayed outcomes. Public displays should explain plainly why some programs show no data, so residents do not assume that missing data means poor results, or good ones.

The second challenge is comparability. Programs serve different populations and lead to different occupations. A program with lower employment rates may be serving participants with more barriers, or training for an occupation with a slower hiring cycle. Displays that rank programs by a single number without context invite residents to make choices on misleading grounds. Showing outcomes alongside information about the occupation, typical wages in the region, and program length gives residents a fuller basis for comparison.

The third challenge is relevance. Residents choosing training want to know whether people who completed a program found jobs in the field and what they earned. The available data may describe all WIOA participants who exited, rather than completers or all students, and may not show whether jobs were related to training. Displays should state clearly whom the numbers describe and what they leave out.

The fourth challenge is presentation. Provider lists are often presented as long searchable tables with technical labels. Residents benefit from plain-language program pages that describe the program, its length and cost, the credential it leads to, outcomes in plain terms, and how to talk with a career advisor about whether it fits. Mobile-friendly, accessible design matters, since many residents search on phones.

The fifth challenge is guidance. Outcome data are one input into a training decision, not the whole answer. Career advisors play an essential role in helping residents interpret provider information alongside their own interests, skills, circumstances, and labor market information. Public displays can point residents to that conversation rather than implying that the numbers alone should decide.

Agencies that present training provider outcomes honestly and clearly help residents make better decisions and encourage providers to focus on results that matter. Those that present them as raw, unexplained tables leave residents to navigate high-stakes choices with numbers they cannot interpret.

Formats and Channels for Outcome Reporting

The format and channel of outcome reporting determine whether it reaches its audiences. A comprehensive annual report posted as a long document on a website may satisfy transparency requirements, but few people will read it. Agencies that want the public to understand their outcomes use a range of formats and channels, matched to how each audience seeks and consumes information.

A layered approach works well for many agencies, with each layer serving a different depth of interest:

• A one-page summary or infographic presenting a few key outcomes in plain language with simple visuals, for broad audiences and quick reference.

• A short public report of several pages, explaining key outcomes, context, trends, and limitations in plain language, for readers who want more understanding.

• An interactive dashboard or web page allowing users to explore outcomes by program, year, population, or area, with plain-language explanations and privacy protections built in.

• A full technical report or data download with complete compliance data, definitions, and methodology, for researchers and technical audiences.

• Audience-specific briefs for employers, officials, and partners, drawing on the same data.

• Fact sheets for journalists, with key figures, definitions, and staff contacts.

Each layer links to the others, so readers can move from summary to detail as their interest grows.

Channels should match audiences. Residents may encounter outcome information through the career center’s website, social media, printed materials at career centers and partner locations, and conversations with staff. Employers may receive it through business services staff, employer newsletters, and industry associations. Officials may receive it through briefings, presentations at public meetings, and written summaries. Journalists may receive it through press releases and direct outreach. Partners may receive it through partner meetings and newsletters.

Timing matters. Releasing outcome information at predictable times, such as an annual report released each year at the same time, helps audiences anticipate it. Coordinating release with board meetings, budget cycles, or legislative sessions can increase relevance for officials. Brief updates between annual reports, such as quarterly dashboard updates, keep information current.

Staff are a channel. Career advisors, business services representatives, and leaders who understand and can explain outcomes in plain language extend the reach of reports. Providing staff with brief talking points about key outcomes helps them share accurate information in their conversations with residents, employers, and partners.

Accessibility applies to all formats. Digital reports, dashboards, and documents should meet accessibility standards, including compatibility with screen readers, sufficient color contrast, and alternative text for visuals. Key summaries should be available in the languages most common in the community. Printed versions should be available for people without internet access.

Interactive dashboards require particular care. They offer flexibility but can overwhelm users or allow them to generate misleading comparisons. Dashboards should include plain-language explanations, default views showing the most important information, privacy protections that suppress small groups, and guidance on interpreting results.

Finally, formats should be evaluated. Website analytics, feedback from users, and observations from staff reveal which formats are used and understood. Agencies can refine their approach based on what works for their audiences.

Ethical Commitments in Outcome Reporting

Outcome reporting shapes public understanding of whether a publicly funded system works. Agencies face pressures to present results favorably, particularly when funding, reputation, or political support is at stake. Ethical commitments in outcome reporting ensure that the public receives an honest picture, protect the privacy of participants, and maintain the credibility that makes outcome data useful.

The first commitment is completeness. Agencies should not selectively report favorable outcomes while omitting unfavorable ones. Selection for public reports, as discussed earlier, should be based on what matters to audiences, not on which numbers look best. If a key outcome declined, it should be reported, with context and explanation. Readers who discover that unfavorable results were omitted lose trust in everything the agency reports.

The second commitment is accuracy. Every figure in a public report should match the underlying data, and every description should accurately reflect what the measure captures. Rounding, conversions, and plain-language descriptions should be checked by data staff. Errors, when discovered, should be corrected promptly and transparently.

The third commitment is avoiding overstated claims. Agencies should not claim that programs caused outcomes unless rigorous evidence supports such claims. They should not present outcomes for a subset of participants, such as training completers, as if they represented all participants, without clearly saying so. They should not use visualizations that exaggerate differences or improvements.

The fourth commitment is fair comparison. Comparisons across areas, programs, providers, or years should account for differences in populations served and conditions faced. Presenting raw comparisons that disadvantage programs serving people with greater barriers can create incentives to avoid serving those people, which undermines the system’s mission.

The fifth commitment is privacy. Participants’ personal information must be protected. Public reports should use aggregated data, apply suppression rules for small groups, and avoid any presentation that could identify individuals. Stories and examples accompanying outcome data should be used only with informed consent.

The sixth commitment is honesty about limitations, as discussed earlier. Acknowledging what the data cannot show is part of honest reporting.

The seventh commitment is independence from political pressure. Outcome reports should reflect the data, not the preferences of officials or leaders. Agencies should maintain processes that protect the integrity of data analysis and reporting, such as having data staff review all public figures and documenting methods. When political pressure arises to present results in misleading ways, agency leaders should resist it.

The eighth commitment is equity. Reporting should reveal, not hide, disparities in outcomes among groups, with appropriate context and privacy protection. Agencies committed to equitable service should be willing to show where they fall short.

The ninth commitment is accessibility. Public reports should be accessible to people with disabilities and available in the languages residents speak, so that outcome information is truly public.

These commitments may occasionally produce reports that are less flattering than agencies would prefer. But they build lasting credibility. Officials, funders, journalists, and residents who come to trust that an agency reports honestly are more likely to believe its good news, support its requests, and accept its explanations when results disappoint.

A Plain-Language Outcome Report in Practice

The following hypothetical example illustrates how a local workforce board might transform its outcome reporting. It does not describe an actual board.

A local workforce board has historically published its outcomes as a table in its annual report, listing each federal indicator for adult, dislocated worker, and youth programs alongside negotiated performance levels. The table uses technical labels and percentages to one decimal place. County commissioners rarely ask about it, and when a local news outlet reported on the board, the reporter compared employment rates across programs without understanding that they served different populations, producing a misleading story.

The board’s executive director asks data and communication staff to develop a public outcome report. They begin by identifying audiences and their questions. Residents want to know whether people like them found jobs and earned decent wages. Commissioners want to know how many people were served, what results were achieved, and how the board performed against expectations. Employers want to know about hires and credentials in relevant fields.

The team selects a small set of headline outcomes: the share of people working about six months and one year after finishing services, typical earnings expressed both as quarterly figures and approximate hourly equivalents, the share of people in training who earned credentials, and the number of employers served. They write plain-language descriptions for each, reviewed by data staff for accuracy, stating whom each figure describes and when it was measured.

They add context: a brief profile of who was served, including the share unemployed at entry and the share facing particular barriers; a note on labor market conditions during the period; three years of trends; and a plain explanation of how performance targets are set. They break outcomes down by whether participants received training or only career services, and by the most common training occupations, suppressing results for groups below a minimum size.

They design simple charts with honest scales and clear labels, along with icon arrays showing outcomes as shares of people. They include a short section on what the numbers can and cannot show, noting that outcomes describe what happened to participants rather than proving what services caused, and that employment data may miss some forms of work.

They produce a layered set of materials: a one-page summary, a short public report, an employer brief, a commissioner briefing, and a fact sheet for journalists, all drawing on the same figures. The summary is translated into the two languages most common locally. All digital materials are checked for accessibility. The full compliance data remains available online.

The team tests drafts with a small group of residents, an employer, and a commissioner’s aide, revising wording that confused them. When the report is released, the executive director briefs commissioners, business services staff share the employer brief, and communication staff send the fact sheet to local media with an offer to explain the data.

Commissioners ask more informed questions at the next budget hearing. The local news outlet’s next story accurately describes outcomes for training participants and notes the populations served. Career advisors begin using the summary in conversations with residents considering training.

The example illustrates the core principles: identifying audiences and questions, selecting meaningful outcomes, translating indicators into plain language, providing context, visualizing honestly, acknowledging limitations, disaggregating with privacy protection, tailoring formats, ensuring accessibility, and testing with audiences.

Testing Whether Reports Are Understood

Publishing a plain-language report does not guarantee that people understand it. Agencies can assume their reports are clear because staff find them clear, but staff are not the audience. Testing whether reports are understood, before and after publication, reveals whether communication succeeds and guides improvement.

The first method is comprehension testing before publication. Agencies can show draft reports to a small number of people from each intended audience, such as residents, employers, and officials’ staff, and ask them to explain in their own words what key outcomes mean, whom they describe, and what conclusions they would draw. Misunderstandings reveal where wording, visuals, or context need revision. Even a handful of conversations can identify significant problems.

The second method is task-based testing. Readers can be asked to find specific information, such as the share of training participants who earned credentials or typical earnings for a particular occupation, and to describe how confident they are in their answer. Difficulty finding information indicates problems with organization or format.

The third method is monitoring use after publication. Website analytics show how many people view reports, which formats they use, how long they spend, and which pages they visit. Low engagement with a dashboard or high exit rates from a report may signal problems. Downloads of summaries versus full reports reveal which formats audiences prefer.

The fourth method is gathering feedback. Brief feedback forms on report pages, questions to staff who share reports, and conversations with officials and partners provide information about whether reports meet needs. Staff who use reports in conversations with residents and employers can report what questions arise and what confuses people.

The fifth method is reviewing how reports are used by others. When journalists, officials, or partners cite outcome data, agencies can review whether they interpret it accurately. Misinterpretations suggest that reports need clearer explanation or that additional outreach is needed.

Several questions guide evaluation of public outcome reports:

• Can readers from each audience correctly explain what the key outcomes mean and whom they describe?

• Can readers find the information most relevant to them quickly?

• Do readers understand that outcomes describe past services and do not prove impact?

• Are journalists and officials citing outcome data accurately?

• Which formats and channels are reaching which audiences?

Testing should be ongoing. Each year’s report can be improved based on testing and feedback from the previous year. Over time, agencies develop plain-language descriptions, visuals, and formats that their audiences understand reliably.

Testing should include people with disabilities and people with limited English proficiency, to ensure that accessible and translated versions communicate as intended.

Finally, testing should inform internal practice. Findings about what confuses audiences can guide staff training, talking points, and the design of future reports. A culture in which communication is tested, not assumed, strengthens all of an agency’s public reporting.

How Workforce Outcome Reporting Compares With Other Agency Types

Many public agencies report performance data to the public, and their experiences offer lessons for workforce outcome reporting.

Public schools and school districts report student outcomes, including test scores, graduation rates, and other measures, often through state report cards. Education reporting has grappled with many of the same challenges as workforce reporting: technical measures that the public misunderstands, comparisons across schools serving different populations, disaggregation by student group, privacy protection for small groups, and pressure to present results favorably. Many states have redesigned school report cards with plain-language explanations, contextual information, and layered formats, providing models workforce agencies can study.

Higher education institutions report outcomes such as graduation rates, earnings of graduates, and loan repayment, including through federal tools that allow comparison of institutions. Experience with these tools shows both the value of comparable outcome data for consumers and the risks of comparisons that ignore differences in students served. Workforce agencies reporting outcomes for eligible training providers face similar issues.

Health care systems and public health agencies report quality and outcome measures, often with risk adjustment to account for differences in patient populations. The health care experience shows the importance of explaining risk adjustment to the public and of avoiding incentives to avoid serving high-risk populations, parallel to concerns about workforce programs avoiding participants with barriers.

Police departments and justice agencies increasingly report data on activities and outcomes through public dashboards. Their experience highlights the importance of context, consistent definitions, and community engagement in interpreting data.

Transportation and utility agencies report performance measures such as on-time performance and service reliability. Their use of simple, consistent public indicators shows how technical performance can be communicated accessibly.

What distinguishes workforce outcome reporting is the combination of long time lags between services and measured outcomes; exit-based measurement that differs from intuitive notions of completion; quarterly earnings that require conversion; statistical adjustment and negotiated targets; multiple programs serving different populations under different rules; and a mission to serve people facing barriers, which makes fair comparison especially important. These features make translation, context, and honest acknowledgment of limitations particularly important. Workforce agencies can borrow from education report cards, health care risk adjustment communication, and performance dashboards, but must adapt these approaches to the specific structure of workforce data.

Tying It All Together

Outcome reporting is not a side function of the public workforce system. It is how residents, employers, officials, and journalists come to understand whether the system works. Compliance reporting, essential for accountability within the system, does not serve these audiences on its own. Public outcome reporting draws on the same data but selects, translates, contextualizes, and presents it so that people outside the system can understand it.

The work begins with a clear understanding of what federal performance indicators measure: employment rates in the second and fourth quarters after exit, median earnings in the second quarter after exit, credential attainment, measurable skill gains, and effectiveness in serving employers, all under negotiated, statistically adjusted performance levels. It continues with recognition of why standard reports confuse the public: time lags, the technical meaning of exit, differing denominators, quarterly earnings, unexplained targets, implied attribution, aggregation, and comparisons without context.

Effective public reporting decides what each audience needs to know and selects a small number of meaningful outcomes, without omitting unfavorable results. It translates indicators into plain language, describing outcomes in terms of people, defining groups, explaining timing, converting earnings, clarifying exit, distinguishing progress from outcomes, explaining targets, and avoiding causal claims. It provides context about who was served, economic conditions, trends, benchmarks, starting points, types of services, cost and scale, and notable developments.

Visualizations should be chosen for clarity, use honest scales, be clearly labeled, show only fair comparisons, represent small numbers appropriately, avoid decorative distortion, and be accessible. Limitations, including the difference between outcomes and impact, gaps in employment data, time lags, small numbers, changes over time, and what indicators omit, should be acknowledged proportionately. Disaggregation reveals equity gaps, and privacy protection through suppression and aggregation prevents identification of individuals.

Reports should be tailored to residents, employers, officials, board members, journalists, partners, and technical audiences, using layered formats and appropriate channels, with staff equipped to share outcomes in plain language. Ethical commitments to completeness, accuracy, restraint in claims, fair comparison, privacy, honesty about limitations, independence from political pressure, equity, and accessibility protect credibility. And testing whether reports are understood, through comprehension testing, task-based testing, use monitoring, feedback, and review of how others cite data, ensures that reporting achieves its purpose.

Strategic Communication Support

Translating workforce outcome data for the public requires collaboration between data experts and communicators, careful decisions about selection and framing, plain-language writing that remains technically accurate, honest visualization, attention to equity and privacy, and testing with real audiences. Many workforce agencies have strong data capacity and limited communication capacity, or the reverse, and few have time to redesign their reporting while meeting compliance deadlines. External support can help agencies build public reporting practices that last.

Stegmeier Consulting Group (SCG) helps public agencies make complex information understandable to the people it affects. For workforce agencies, that work can begin with a review of current outcome reporting: examining compliance and public reports, dashboards, and materials; interviewing data staff, communication staff, leaders, and board members; and gathering perspectives from residents, employers, officials, and journalists about what they understand and what they need. This review identifies the gaps between what the agency reports and what its audiences can use.

From that foundation, SCG can work with data and communication staff to identify priority audiences and questions, select headline outcomes, and develop plain-language descriptions of each indicator that data staff confirm as accurate. SCG can help develop context statements, honest visualizations, limitation notes, and disaggregation approaches consistent with privacy requirements, and can help design layered formats including summaries, public reports, audience briefs, journalist fact sheets, and dashboard guidance.

Implementation support can include templates that make annual production efficient, talking points and training for staff and board members, accessibility review, and translation coordination. SCG can also help design and conduct comprehension testing with residents, employers, and officials.

Evaluation support helps agencies monitor how reports are used and understood, review how others cite their data, and refine reporting each year. The aim is outcome reporting that the public can understand, that decision-makers trust, and that honestly shows what the workforce system achieves and where it needs to improve.

Future Trends

Several established developments are shaping how workforce agencies report outcomes. Data integration across systems is expanding in some states. Linking workforce data with education, unemployment insurance, public assistance, and other records allows richer analysis of participant pathways and longer-term outcomes. These linked data systems can support more meaningful public reporting, such as earnings several years after training or outcomes for people who move between programs. They also raise privacy and governance questions that require careful attention.

Interest in measuring job quality is growing. Federal indicators focus on employment and earnings shortly after exit, but policymakers, funders, and advocates increasingly ask about benefits, schedule stability, advancement, and long-term earnings. Some agencies are exploring ways to measure and report these dimensions, though data sources are limited. Public reporting may increasingly include job quality information where reliable data exist, accompanied by clear explanation of limitations.

Public expectations for transparency and accessible data continue to rise. Interactive dashboards, open data portals, and mobile-friendly reports are becoming common across government. Workforce agencies will face expectations to provide accessible, current outcome data online. Meeting these expectations while maintaining accuracy, privacy, and interpretability requires investment in both technology and communication.

Accessibility requirements for digital government content are becoming more concrete. The Department of Justice’s 2024 rule under Title II of the Americans with Disabilities Act established technical standards for state and local government web content and mobile applications, with compliance deadlines phased by government size. Workforce agencies’ online reports and dashboards will need to meet these standards.

Emerging technologies, including artificial intelligence tools, are being explored for data analysis and for generating plain-language summaries of data. Such tools may help agencies produce accessible reports more efficiently, but they also carry risks of inaccuracy, oversimplification, or misinterpretation. Any use of these tools in public reporting should include human review for accuracy, and their role in workforce reporting is still developing.

The federal performance accountability framework itself may evolve. Guidance on indicators such as effectiveness in serving employers has developed over time, and future legislation or regulation could change indicators or reporting requirements. Budget proposals in recent cycles have also contemplated consolidating workforce funding streams, which could affect how outcomes are measured and reported. Whether and how such changes occur is uncertain. Agencies that have built strong public reporting practices, grounded in plain language, context, and honesty, will be able to adapt those practices to new indicators and structures.

Conclusion

The resident who reads that the adult program exceeded its negotiated employment rate in the second quarter after exit deserves better. She deserves to know, in words she can use, that most adults who received services were working about six months after they finished, what they typically earned, whether training led to credentials, what kinds of people the program served, and what the numbers can and cannot tell her. None of that requires abandoning the federal indicators or compromising accuracy. It requires carrying the same data across the gap between the system’s vocabulary and hers.

For workforce board directors, state agency leaders, and the data and communication staff who support them, the implication is that public outcome reporting deserves its own design, separate from compliance reporting though grounded in the same data. That means deciding which audiences matter and what they need to know, translating each indicator into plain language that data staff confirm as accurate, providing context about who was served and under what conditions, presenting charts that do not distort, acknowledging limitations without burying results, reporting disparities while protecting privacy, and testing whether people actually understand what is published.

Agencies that make this investment will find that their outcomes start to do the work outcomes should do: informing residents’ choices, earning employers’ confidence, supporting officials’ decisions, and helping journalists report accurately. They will also find that honest reporting, including honest reporting of results that disappoint, builds the kind of credibility that makes their good news believable.

Stegmeier Consulting Group’s Strategic Approach to Communication Systems

SCG approaches workforce outcome reporting as a communication system that connects compliance data to public understanding. That approach brings data and communication staff together to decide which audiences matter and what each needs to know, then translates federal performance indicators into plain language that remains technically accurate. It builds in the context that numbers need, including who was served, labor market conditions, and trends, and presents outcomes through honest visuals, proportionate notes on limitations, and disaggregated results that protect privacy.

For workforce boards and state agencies, this means layered reporting that serves residents, employers, officials, board members, journalists, and technical audiences from a single consistent foundation. It means staff and board members who can explain outcomes accurately in their own conversations, accessible and translated materials, and testing that confirms people actually understand what is published. It means reporting that holds to completeness and honesty, so that the public can trust both the system’s successes and its candor about where it falls short.

Use the form below to connect with our team and explore how strategic communication support can help your workforce agency report program outcomes the public can understand.