How State Workforce Agencies Can Communicate Monitoring Findings, Performance Expectations, and Corrective Actions to Local Boards Without Damaging the Relationship

A local workforce director opens an email from the state agency containing the final report from the annual monitoring review. It runs to thirty pages and lists fourteen findings, each with a citation, a description of the deficiency, and a required corrective action with a deadline. Several findings concern issues the director believes were explained during the on-site visit. Two concern practices her staff adopted on the advice of a state program specialist. One concerns a policy the state changed only months earlier. The report contains no mention of the area’s strong outcomes, its new youth partnership, or the improvements it made since last year’s review. By the end of the day, the director has forwarded the report to her board chair with a note expressing frustration, the board chair has called the county commissioner who serves as chief elected official, and the commissioner has asked why the state seems to be targeting their area. The state monitor who wrote the report believes she was simply doing her job.

Monitoring is a necessary function of the public workforce system. States are responsible under the Workforce Innovation and Opportunity Act and federal grant requirements for overseeing the use of funds by local areas, ensuring compliance with federal and state requirements, and assessing performance. Federal regulations require states to conduct monitoring of local areas, and states negotiate performance levels with local boards and may impose consequences when performance falls short over time. These responsibilities protect public funds and the people the system serves. They cannot be set aside to preserve good feelings.

Yet monitoring communication that damages the relationship between the state and local areas undermines the very purposes monitoring serves. Local areas that feel attacked become defensive, concealing problems rather than raising them. They may comply minimally with corrective actions rather than addressing root causes. They may escalate disputes to elected officials, consuming time and political capital on both sides. And they may disengage from the collaboration that state-local partnership requires. The goal of monitoring is better compliance and better results; communication that damages trust works against both.

This article examines how state workforce agencies can communicate monitoring findings, performance expectations, and corrective actions to local boards without damaging the relationship. Its central argument is that monitoring can be both rigorous and respectful when expectations are clear in advance, communication during reviews eliminates surprises, reports distinguish severity and recognize strengths, corrective action is designed collaboratively, consequences are explained fairly and consistently, chief elected officials and board chairs are engaged appropriately, and disagreements are handled through clear, respectful processes.

Partner and Overseer: The State’s Dual Role

State workforce agencies occupy two roles in relation to local areas. They are partners, providing funding, guidance, technical assistance, systems, and support so that local areas can serve jobseekers and employers effectively. They are also overseers, monitoring compliance, assessing performance, and holding local areas accountable for the use of public funds. These roles can coexist, but they create tension that shapes every interaction around monitoring.

The partner role depends on trust and openness. Local areas must feel comfortable asking questions, admitting uncertainty, and reporting problems. They must believe the state wants them to succeed. The overseer role depends on objectivity and accountability. The state must identify noncompliance, document it, require correction, and, when necessary, impose consequences. If the overseer role dominates communication, local areas may stop treating the state as a partner. If the partner role dominates, oversight may become lax, and problems may go uncorrected until they become serious.

The tension is often heightened by organizational structure. In many states, program staff who provide technical assistance and monitoring staff who conduct reviews are in different units, with different cultures and priorities. Local areas may experience the state as two different organizations, one helpful and one critical, sometimes giving inconsistent messages. A local area that followed a program specialist’s advice and then received a finding from a monitor experiences the dual role at its most frustrating.

Managing the dual role well requires communication that makes both roles explicit and consistent. Local areas should understand that the state monitors because it is required to and because accountability protects the system, not because it distrusts local areas. Monitoring should be framed as part of a shared commitment to compliance and quality, not as a contest. And the state’s partner and overseer functions should be coordinated, so that technical assistance and monitoring are aligned.

Several principles help. The first is that monitoring is not punishment. Its primary purpose is to identify and correct problems, protect funds, and improve performance. Communication should reflect this purpose. The second is that findings describe conditions, not character. A finding documents that a requirement was not met; it does not mean that local staff are incompetent or acting in bad faith. Communication should avoid language that implies otherwise. The third is that the state shares responsibility for outcomes. When local problems stem from unclear guidance, inconsistent advice, or system issues, the state should acknowledge its role. The fourth is that accountability is real. Respectful communication does not mean avoiding difficult findings or consequences. It means delivering them in ways that are clear, fair, and constructive.

When local areas experience monitoring as a fair, constructive process conducted by a partner who also holds them accountable, they are more likely to engage openly, correct problems effectively, and maintain a productive relationship with the state. The sections that follow describe how communication can achieve this balance at each stage of monitoring and performance management.

Why Monitoring Communication Strains Relationships

Understanding the specific ways monitoring communication damages relationships helps state agencies avoid them.

The first source of strain is surprise. Local areas that learn of findings for the first time in a written report, after an on-site visit in which no concerns were raised, feel ambushed. Surprise prevents local areas from providing context or correcting misunderstandings before findings are finalized, and it suggests that the state was not being transparent.

The second source is tone. Monitoring reports written in accusatory, absolute, or condescending language, such as describing practices as failures or using emphatic phrasing about deficiencies, provoke defensiveness. Even accurate findings can feel like attacks when phrased harshly.

The third source is lack of proportion. Reports that list minor documentation errors alongside serious compliance problems, with no distinction in severity, make every issue feel equally serious and can make a well-run area appear deeply troubled. Local areas may feel that the state is nitpicking or failing to see the bigger picture.

The fourth source is inconsistency. Local areas compare notes. When one area receives a finding for a practice that another area was not cited for, or when monitors interpret requirements differently from program staff, local areas perceive unfairness. Inconsistency undermines the legitimacy of monitoring.

The fifth source is ignoring context. Local areas operate under constraints, such as funding reductions, staff turnover, system problems, or unclear guidance. Findings that ignore these constraints, or that hold local areas responsible for problems caused partly by state actions, feel unjust.

The sixth source is omission of strengths. Reports that list only deficiencies, with no acknowledgment of what the area does well, give a distorted picture and demoralize staff who work hard. Local areas may conclude that the state sees only problems.

The seventh source is unrealistic corrective actions. Corrective actions with short deadlines, vague requirements, or demands disproportionate to the problem create burdens that local areas may struggle to meet, leading to further findings and escalating tension.

The eighth source is going around local leaders. Communication that reaches board chairs, chief elected officials, or the media before local directors have had a chance to respond, or that bypasses local leadership entirely, damages trust with the people who must implement corrections.

The ninth source is unclear consequences. Local areas that do not understand what will happen if findings are not resolved, or if performance falls short, experience uncertainty and anxiety. Consequences that appear arbitrary or that arrive without warning are especially damaging.

The tenth source is no avenue for disagreement. When local areas believe a finding is wrong but have no clear process to dispute it, frustration builds and may be expressed through political channels instead.

Each of these sources of strain can be addressed through communication practices that maintain rigor while preserving respect. The following sections describe those practices.

Setting Expectations Before Monitoring Begins

Much of the tension around monitoring can be prevented by communication before reviews begin. Local areas that understand what will be reviewed, how, against what standards, and what happens afterward approach monitoring with less anxiety and more cooperation.

The first element is a published monitoring framework. States can publish a description of their monitoring approach, including the purpose of monitoring, the areas reviewed, the frequency of reviews, how areas are selected for more intensive review, the standards used, the categories of results, the corrective action process, and the dispute resolution process. A published framework makes monitoring predictable and demonstrates that it follows consistent rules.

The second element is sharing monitoring tools. Many states use monitoring guides or checklists that list the requirements reviewed. Sharing these tools with local areas in advance allows them to understand what monitors will look for and to conduct self-assessments. Some states encourage or require local self-monitoring using the same tools, which helps local areas identify and correct problems before state reviews.

The third element is advance notice of reviews. Local areas should receive notice of upcoming reviews with enough time to prepare, including the dates, scope, documents requested, staff to be interviewed, and logistics. Advance notice respects local workloads and allows local areas to gather materials efficiently. Unannounced reviews may be appropriate in limited circumstances, such as suspected fraud, but routine monitoring benefits from notice.

The fourth element is a pre-review conversation. A brief call or meeting before the review allows monitors and local leaders to discuss the scope, clarify expectations, identify any known issues the local area wants to raise, and establish a constructive tone. Local areas that disclose known problems in advance, and are already working on them, can be credited for doing so.

The fifth element is clarity about standards. Local areas should know which version of guidance applies to the period being reviewed. If guidance changed during the review period, monitors should apply the guidance in effect at the time of the activity reviewed, and local areas should know this.

The sixth element is explaining the categories of results. Local areas should understand how the state distinguishes between findings, which typically involve noncompliance with requirements and require corrective action; concerns or areas of improvement, which may involve practices that risk noncompliance or could be strengthened; observations; and promising practices. Understanding these categories in advance helps local areas interpret reports accurately.

The seventh element is aligning technical assistance and monitoring in advance. States can ensure that program staff and monitors share the same understanding of requirements before reviews begin, and that guidance and answers to questions are reflected in monitoring tools. This alignment prevents the situation in which local areas follow technical assistance advice and are later cited for it.

The eighth element is performance expectations communicated early. Negotiated performance levels and any state-specific performance expectations should be clear at the start of the program year, with explanation of how they were set and how performance will be assessed. Local areas should not learn about expectations only when results fall short.

Setting expectations in advance transforms monitoring from an unpredictable event into a known process. Local areas that understand the process can prepare, self-correct, and engage constructively.

Communicating During the Monitoring Review

The monitoring review itself, whether on site, remote, or a combination, is an opportunity to build understanding and prevent surprises. Communication during the review allows monitors to gather accurate information, gives local staff a chance to explain context, and ensures that the final report contains nothing the local area has not already heard.

The first element is an entrance conference. At the start of the review, monitors and local leaders can meet to confirm scope, schedule, and logistics, introduce participants, and set a collaborative tone. Monitors can explain the process and invite local leaders to raise any context they want considered.

The second element is real-time clarification. When monitors identify potential issues during the review, they can raise them with local staff promptly, asking for explanation or additional documentation. Many apparent problems are resolved when local staff provide context or locate missing documents. Raising issues in real time is fairer and more efficient than leaving them for the report.

The third element is respectful interaction with staff. Monitors interviewing frontline staff and reviewing case files should communicate respectfully, explaining the purpose of questions and avoiding interrogation. Frontline staff may feel anxious during reviews, and respectful interaction reduces anxiety and produces better information.

The fourth element is an exit conference. At the end of the review, monitors should meet with local leaders to share preliminary results, including potential findings, concerns, and strengths. The exit conference should give local leaders a clear picture of what the report is likely to contain, allowing them to ask questions, provide additional information, and begin planning responses. The principle of no surprises means that nothing significant should appear in the final report that was not discussed at the exit conference, unless additional analysis after the review reveals new issues, in which case the state should contact the local area before finalizing the report.

The fifth element is an opportunity to provide additional information. After the exit conference, local areas should have a defined period to submit additional documentation or explanation that might affect preliminary results. Monitors should consider this information before finalizing the report.

The sixth element is distinguishing preliminary from final. Monitors should be clear that results shared during the review are preliminary and subject to review, so that local areas understand that additional information can make a difference.

The seventh element is noting promising practices during the review. When monitors observe strong practices, acknowledging them during the review, not only in the report, builds goodwill and reinforces good work.

The eighth element is clarity on timelines. Local areas should know when to expect the draft or final report and what will happen next. Long, unexplained delays between the review and the report create anxiety and reduce the usefulness of findings.

Communication during the review shapes how local areas experience the entire monitoring process. A review conducted collaboratively, with issues raised openly and context considered, leads to a report that local areas recognize as fair even when it contains significant findings.

Writing Monitoring Reports That Inform Rather Than Indict

The monitoring report is the formal record of the review and often the document local boards, chief elected officials, and sometimes the public will read. How it is written shapes how the review is perceived and whether it leads to improvement. Reports can be rigorous and complete while also being clear, proportionate, balanced, and respectful.

The first principle is a clear executive summary. Reports should begin with a brief summary of the review’s scope, overall results, number and nature of findings and concerns, notable strengths, and next steps. Board members and officials who read only the summary should come away with an accurate picture.

The second principle is distinguishing severity. Reports should clearly separate findings that require corrective action from concerns or recommendations that are advisory, and from observations or promising practices. Within findings, the report can indicate severity, such as whether a finding involves questioned costs, systemic issues, or isolated documentation errors. A report that treats a missing signature on one file the same as a systemic failure to verify eligibility misrepresents the area’s situation.

The third principle is precise, neutral language. Findings should describe what was found, what requirement applies, and why the condition does not meet the requirement, in factual, neutral language. Phrases such as the local area did not maintain documentation of selective service registration for two of twenty files reviewed are clearer and fairer than characterizations such as the local area failed to comply with eligibility requirements. Language should describe conditions, not judge character.

The fourth principle is citing requirements. Each finding should cite the specific requirement, whether federal regulation, state policy, or local policy, so that local areas can understand and verify the basis. Findings based on interpretations not clearly stated in guidance deserve particular care; if guidance was ambiguous, the report should acknowledge it and the state should clarify guidance.

The fifth principle is describing scope and sample. Local areas and readers need to know how many files or transactions were reviewed and how many had issues. Reporting that a problem occurred in two of twenty files provides context that a bare statement of the problem does not.

The sixth principle is acknowledging context. Where relevant, reports can note factors that contributed to issues, such as system problems, guidance changes during the review period, or staff turnover, without excusing noncompliance. Acknowledging context demonstrates fairness and helps identify root causes.

The seventh principle is recognizing corrections already made. If a local area corrected an issue during or after the review, the report should say so. Some states resolve minor issues during the review without formal findings.

The eighth principle is including strengths. Reports should acknowledge areas where the local area performs well and practices worth sharing. Balanced reports are more accurate and more motivating.

The ninth principle is clear, realistic corrective actions. Each finding should specify what the local area must do to resolve it, in clear terms, with a reasonable timeline. Corrective actions should address root causes, not only individual instances.

The tenth principle is review before finalization. Many states issue draft reports, allowing local areas to review for factual accuracy and submit responses before reports are finalized. Including local responses in the final report gives a complete record.

Reports written this way are no less rigorous than harsh ones. They are more credible, more useful, and far less damaging to the relationship that corrective action depends on.

Communicating Performance Expectations and Results

Performance accountability is distinct from compliance monitoring but closely related. Under WIOA, states negotiate performance levels for the primary indicators of performance with the federal government, and negotiate local performance levels with local boards, using a statistical adjustment model that accounts for economic conditions and participant characteristics. States assess local performance against these levels and may impose consequences for sustained failure to meet them. Communicating performance expectations and results clearly and fairly is essential to maintaining productive relationships.

The first element is transparent negotiation. Local performance levels should be negotiated, not simply assigned, with local boards understanding the basis for proposed levels, including the statistical adjustment model, prior performance, and expected conditions. Local boards should have an opportunity to provide information about local factors that may affect performance. Communicating the results of negotiation clearly, with documentation of agreed levels, establishes shared expectations.

The second element is plain explanation of indicators and adjustment. Local board members, many of whom are business leaders rather than workforce specialists, need to understand what the indicators measure and how performance is assessed. Plain-language explanations of each indicator, the time lags involved, and how statistical adjustment works help board members interpret results and govern effectively.

The third element is regular performance reporting. Local areas should receive performance data regularly during the year, not only at year end, so they can identify problems early and take action. Dashboards or reports showing performance relative to negotiated levels, with trends and comparisons, support ongoing management. Given time lags in outcome data, states can also share leading indicators that predict future performance.

The fourth element is early warning. When data suggest a local area is at risk of failing to meet performance levels, the state should communicate this early, offering technical assistance before the year ends. Early warning allows local areas to respond and demonstrates that the state’s goal is improvement, not sanction.

The fifth element is context in assessing results. Performance results are influenced by many factors, including economic conditions, changes in who is served, and data issues. When communicating results, states should consider and acknowledge context, consistent with the statistical adjustment framework. Areas serving more participants with barriers may have lower unadjusted outcomes while performing well relative to adjusted expectations.

The sixth element is clarity about consequences. Local areas should understand what happens if performance levels are not met, including the federal and state framework for consequences, such as technical assistance and, after sustained failure, more significant actions that may include reorganization in serious cases under WIOA. Clarity about consequences, communicated in advance and applied consistently, reduces anxiety and perceptions of arbitrariness.

The seventh element is recognizing strong performance. Local areas that meet or exceed expectations deserve acknowledgment. States can recognize strong performance publicly and share practices that contribute to it.

The eighth element is connecting performance to improvement. Performance communication is most constructive when it leads to conversations about what is working, what is not, and how to improve, supported by state technical assistance and peer learning.

Performance communication that is transparent, regular, contextualized, and improvement-oriented builds shared commitment to results. Communication that consists only of year-end pass or fail determinations, with consequences arriving unexpectedly, strains relationships and does little to improve performance.

Corrective Action as Collaboration

Corrective action is where monitoring either leads to real improvement or becomes a paperwork exercise. When corrective action is imposed rigidly, with prescribed steps and short deadlines, local areas may comply minimally, addressing the specific instances cited without fixing underlying causes. When corrective action is developed collaboratively, with the state and local area working together to understand root causes and design effective solutions, it is more likely to produce lasting change.

The first element is focusing on root causes. A finding often reflects an underlying cause, such as unclear procedures, inadequate training, insufficient staff, system limitations, or unclear state guidance. Corrective action plans should identify the root cause and address it, not only correct the cited instances. Conversations between monitors and local leaders about why a problem occurred help identify root causes.

The second element is local ownership. Local areas understand their operations best. Allowing them to propose corrective actions, within parameters set by the state, produces plans that fit local circumstances and builds ownership. The state’s role is to review plans, ensure they address findings adequately, and approve or request changes.

The third element is realistic timelines. Deadlines should allow enough time to implement meaningful changes, such as revising procedures, training staff, or updating systems. Timelines that are too short encourage superficial fixes. Timelines should be negotiated where appropriate, with deadlines for different actions staggered according to complexity.

The fourth element is clear acceptance criteria. Local areas need to know what evidence the state will require to close a finding, such as revised policies, training records, or a sample of corrected files. Clear criteria prevent repeated rounds of submissions and disagreements about whether findings are resolved.

The fifth element is technical assistance. Corrective action is an opportunity for the state to provide support. Offering technical assistance, such as model procedures, training, or peer connections with areas that handle similar issues well, helps local areas succeed. Communicating that assistance is available reinforces the partnership.

The sixth element is regular check-ins. During corrective action, periodic check-ins between state and local staff allow progress to be tracked, obstacles to be identified, and plans to be adjusted. Check-ins should be supportive rather than adversarial.

The seventh element is prompt closure. When local areas complete corrective actions, the state should review submissions promptly and formally close findings. Delays in closing findings leave local areas uncertain and may cause findings to appear unresolved in later reviews. Formal closure communicated clearly, perhaps with acknowledgment of the local area’s effort, completes the cycle.

The eighth element is addressing state-caused issues. When findings stem partly from unclear state guidance or system problems, the state should acknowledge its role and take its own corrective steps, such as clarifying guidance or fixing systems. Local areas that see the state accepting responsibility for its part are more willing to accept responsibility for theirs.

The ninth element is questioned and disallowed costs. Findings involving questioned costs carry financial consequences and require particular care. Local areas need clear explanation of the basis for questioning costs, the process for providing documentation that may resolve the question, and the potential financial consequences. These matters often involve chief elected officials, given their responsibility for funds, and should be communicated to them appropriately.

Collaborative corrective action produces better results and preserves relationships. It treats findings as shared problems to solve rather than offenses to punish.

Communicating Financial Findings and Questioned Costs

Of all monitoring results, financial findings carry the highest stakes for the state-local relationship. When monitors question whether costs were allowable, allocable, reasonable, or adequately documented, the possible outcome is that the local area must repay funds from non-federal sources. Because chief elected officials typically bear financial liability for misused funds, questioned costs reach the desks of county commissioners and mayors, who may have little familiarity with federal cost principles and strong concern about unexpected budget obligations. Communicating financial findings clearly, carefully, and fairly is essential to resolving them without lasting damage.

The first principle is precision about the issue. Financial findings should state exactly which costs are questioned, the amount, the period, the requirement involved, and why the documentation or circumstances do not meet it. Vague findings, such as a general statement that cost allocation was inadequate, leave local areas unable to respond and officials unable to gauge the risk. Precise findings allow local areas to locate documentation, correct allocations, or explain their reasoning.

The second principle is distinguishing questioned from disallowed. A questioned cost is one the state has concerns about; a disallowed cost is one the state has determined must be repaid after the resolution process. Communicating clearly where a finding stands in this process, and what steps remain, prevents officials from assuming that every questioned cost is an immediate liability.

The third principle is explaining the resolution process. Local areas need to know how they can resolve questioned costs: providing additional documentation, demonstrating that costs were allowable, reallocating costs to appropriate funding sources where permitted, or, if necessary, repaying from non-federal funds. They need to know the timelines, what evidence the state will accept, and who makes the final determination. Clear process communication reduces anxiety and supports resolution.

The fourth principle is early notice to governance leaders. Because questioned costs may become liabilities, chief elected officials and board chairs should be informed early, through the director and the state’s formal report, with plain-language explanation. Officials who learn about potential liabilities late in the process, or from auditors rather than from the state and their own staff, may react with alarm and frustration.

The fifth principle is distinguishing documentation gaps from improper spending. Many questioned costs arise from inadequate documentation of spending that was otherwise appropriate, rather than from misuse of funds. Communication should make this distinction clear where it applies, so that officials and the public do not infer wrongdoing where none occurred. At the same time, where findings suggest serious mismanagement or potential fraud, communication should be candid and should follow applicable referral and reporting requirements.

The sixth principle is technical assistance on financial systems. Financial findings often reflect weaknesses in cost allocation plans, procurement procedures, or documentation practices. Offering technical assistance, model procedures, or training on federal cost principles helps local areas strengthen systems and prevent recurrence.

The seventh principle is consistency with audits. Local areas may also be subject to single audits and state audits. Coordinating monitoring findings with audit findings, and communicating how they relate, prevents duplicate or conflicting demands.

Financial findings will always be uncomfortable. Communicated with precision, a clear process, early engagement of governance leaders, and fair distinction between documentation problems and misconduct, they can be resolved in ways that protect public funds while preserving trust between the state and the local officials who share responsibility for those funds.

Communicating Escalation and Sanctions Fairly

Most monitoring findings are resolved through corrective action. Sometimes, however, problems persist: corrective actions are not completed, findings recur, performance remains below expectations over multiple years, or serious problems such as misuse of funds emerge. In these cases, states may need to escalate, through more intensive oversight, special conditions on funding, disallowance of costs, or, in serious cases, actions provided for under WIOA such as reorganization. How escalation is communicated affects both its effectiveness and its consequences for the state-local relationship.

The first principle is predictability. Local areas should know in advance, through the published monitoring framework and performance policies, what circumstances lead to escalation and what steps are involved. Escalation should never come as a surprise. A graduated approach, in which consequences increase in steps with notice at each stage, allows local areas to respond before more serious action is taken.

The second principle is clear notice. When the state is considering escalation, it should notify the local area in writing, explaining the basis, the specific concerns, the potential consequences, the timeline, and what the local area can do to prevent escalation. Notice should be addressed to the appropriate officials, including the local board chair and chief elected official, given their governance and financial responsibilities.

The third principle is opportunity to respond. Before escalation takes effect, local areas should have an opportunity to respond, provide information, and propose solutions. Many situations can be resolved at this stage if local leaders understand the seriousness of the concern and commit to action.

The fourth principle is proportionality. Consequences should be proportionate to the seriousness and persistence of the problem. Communication should explain how the chosen response relates to the problem, which helps local areas see escalation as fair rather than punitive.

The fifth principle is consistency. Escalation should follow consistent criteria across local areas. Local areas that perceive inconsistent treatment, such as similar problems in other areas being treated more leniently, will view escalation as unfair or politically motivated.

The sixth principle is support alongside consequences. Even as the state escalates, it can continue to offer technical assistance and support for improvement. Communicating that the goal remains improvement, and that the state will help, keeps the partnership alive.

The seventh principle is careful public communication. Escalation may become public through board meetings, public records, or media inquiries. The state should communicate factually and professionally, avoiding inflammatory characterizations. Local and state leaders should coordinate where possible so that public statements are accurate and do not escalate conflict unnecessarily.

The eighth principle is respecting due process. Where formal processes for appeals, hearings, or dispute resolution apply, the state should explain them clearly and follow them carefully.

The ninth principle is a path back. Local areas subject to escalated oversight should know what they must do to return to normal status, and the state should communicate clearly when they have done so. A clear path back encourages improvement and acknowledges progress.

Escalation is sometimes necessary to protect public funds and participants. When communicated predictably, clearly, proportionately, consistently, and with continued support, it can achieve its purpose while preserving the possibility of a productive relationship afterward.

Communicating With Local Board Chairs and Chief Elected Officials

Monitoring communication typically flows between state monitors and local workforce directors or administrative staff. But local boards and chief elected officials have formal governance responsibilities under WIOA, and chief elected officials generally bear liability for misused funds unless otherwise agreed with the governor. These leaders need appropriate information about monitoring results, and the way they receive it significantly affects the state-local relationship.

The first principle is appropriate routing. Final monitoring reports and significant findings should be shared with the local board chair and chief elected official, not only with staff. These leaders are responsible for oversight of the local system and need to know about compliance and performance issues. Many states address final reports to the chief elected official and board chair with copies to the director.

The second principle is sequencing that respects local leadership. While board chairs and chief elected officials should receive reports, local directors should not be bypassed. Directors should see draft or preliminary results first, have an opportunity to respond, and be able to brief their board chair and chief elected official before the final report arrives. Leaders who receive a critical report without warning from their own staff may react more strongly than they would if briefed in advance.

The third principle is summaries for governance audiences. Board chairs and elected officials may not read lengthy technical reports. A clear executive summary, describing overall results, significant findings, strengths, and required actions in plain language, helps them understand the situation and their role.

The fourth principle is explaining governance implications. Leaders need to understand what findings mean for them, such as whether questioned costs could become liabilities, whether board action is required, or whether performance shortfalls could lead to consequences. Clear explanation allows leaders to fulfill their oversight responsibilities.

The fifth principle is offering briefings. For significant findings or escalation, the state can offer to brief the board chair and chief elected official directly, in person or by video, alongside the local director. A conversation allows leaders to ask questions, understand context, and hear directly from the state that its goal is improvement. Briefings can defuse tension that a written report alone might create.

The sixth principle is presenting at board meetings when invited. Local boards sometimes invite state staff to present monitoring results. State staff who present clearly and respectfully, acknowledging strengths as well as findings, model the partnership the state hopes to sustain.

The seventh principle is consistent messages to staff and leaders. What the state tells board chairs and elected officials should be consistent with what it told local staff. Inconsistent messages create confusion and suspicion.

The eighth principle is respecting multi-jurisdictional arrangements. In local areas with multiple chief elected officials, communication should reach all appropriate officials according to their agreement, not only the lead official.

When board chairs and chief elected officials receive monitoring information appropriately, they can support corrective action, hold local staff accountable constructively, and serve as partners with the state in improving the local system. When they receive it poorly, they may become adversaries, escalating disputes politically and complicating resolution.

Consistency and Fairness Across Local Areas

Local workforce directors talk to one another, through state associations, regional meetings, and informal networks. They compare monitoring experiences. When they discover that similar practices received different treatment in different areas, or that monitors interpret requirements differently, the legitimacy of monitoring suffers. Consistency and fairness across local areas are essential to maintaining trust in the monitoring process.

The first practice is standardized monitoring tools. Using the same monitoring guides, checklists, and sampling methods for all local areas ensures that reviews cover the same requirements in the same way. Tools should be updated when guidance changes and shared with local areas.

The second practice is monitor training and calibration. Monitors should be trained on requirements, tools, and the distinction between findings, concerns, and observations. Periodic calibration sessions, in which monitors review sample cases together and discuss how they would classify issues, promote consistent judgments.

The third practice is internal review of reports. Before reports are finalized, supervisory or peer review can check for consistency with other reports, accuracy of citations, appropriate classification of severity, and tone. Internal review catches inconsistencies before they reach local areas.

The fourth practice is a record of interpretations. When monitors encounter ambiguous situations, the state’s resolution should be documented and applied consistently in future reviews. Where interpretations clarify policy, they should be shared with all local areas through guidance or frequently asked questions.

The fifth practice is alignment with technical assistance. As discussed earlier, monitoring and program staff should share interpretations, so that local areas do not receive conflicting messages. Joint meetings, shared documentation of answers, and involvement of monitors in guidance development support alignment.

The sixth practice is statewide trend reporting. Periodically sharing statewide summaries of common findings, without identifying individual areas, helps all local areas learn from common issues and demonstrates that findings reflect consistent standards. Trend reports can also reveal where state guidance needs clarification.

The seventh practice is fairness in risk-based monitoring. Many states use risk assessments to determine the intensity of monitoring for each area. Local areas should understand the criteria used, so that more intensive monitoring is seen as based on objective factors rather than targeting.

The eighth practice is avoiding retrospective application of new interpretations. When the state clarifies or changes an interpretation, it should apply the new interpretation prospectively, not cite local areas for practices that were consistent with earlier understanding. Communicating this principle reassures local areas that they will not be penalized for following prior guidance.

The ninth practice is responsiveness to concerns about consistency. When local areas raise concerns that they were treated differently from others, the state should investigate and respond honestly. If inconsistency occurred, acknowledging it and correcting it builds credibility.

Consistency does not mean ignoring differences in local circumstances. It means applying the same standards and processes to all areas, while considering context in assessing severity and designing corrective actions. Local areas that trust the consistency of monitoring are more likely to accept its results.

Recognizing Strengths and Promising Practices

Monitoring tends to focus on what is wrong, because identifying noncompliance is its primary function. But monitors also observe what local areas do well: effective processes, innovative services, strong partnerships, and practices other areas could learn from. Recognizing these strengths makes monitoring more balanced, more accurate, and more motivating, and it turns monitoring into a source of learning across the system.

The first reason to recognize strengths is accuracy. A report that lists only deficiencies gives an incomplete picture of a local area’s operations. Board members and elected officials reading such a report may conclude that the area is poorly managed when in fact it performs well overall with a few compliance issues. Including strengths provides a fuller and fairer account.

The second reason is motivation. Local staff who work hard and see only criticism may become discouraged. Acknowledgment of good work reinforces effective practices and sustains morale, which supports corrective action on the issues that need attention.

The third reason is learning. Practices that work well in one area can benefit others. When monitors identify promising practices, the state can share them, with the originating area’s permission, through technical assistance, peer learning events, or statewide communications. Monitoring then contributes to improvement across the system, not only in the area reviewed.

The fourth reason is relationship. Recognition signals that the state sees local areas as partners with strengths, not only as entities to be corrected. This perception makes local areas more receptive to findings.

Recognizing strengths effectively involves several practices. Monitors can be trained and encouraged to look for strengths as well as deficiencies, with monitoring tools that include prompts for noting effective practices. Reports can include a dedicated section on strengths and promising practices, described specifically rather than with generic praise. Exit conferences can begin or end with acknowledgment of strengths. The state can maintain a collection of promising practices identified through monitoring, available to all local areas. Areas whose practices are shared can be credited publicly.

Recognition should be genuine and specific. Generic statements, such as staff were professional and cooperative, add little. Specific descriptions, such as the area’s process for verifying training provider outcomes before approving individual training accounts is thorough and well documented, provide meaningful acknowledgment and useful information for others.

Recognition should not soften or obscure findings. A report can recognize strengths while still clearly stating findings that require correction. The two are complementary: balanced reports make findings more credible, because they demonstrate that monitors evaluated the area fairly.

Performance recognition also matters. Local areas that meet or exceed performance levels, or that show significant improvement, can be acknowledged through state communications, events, or letters to board chairs and chief elected officials. Recognition from the state carries weight with local leaders and reinforces the partnership.

A monitoring process that recognizes strengths as well as deficiencies is more accurate, more motivating, and more useful to the whole system.

Handling Disagreements and Appeals

Local areas will sometimes disagree with monitoring findings, performance determinations, or proposed consequences. They may believe that a finding misinterprets a requirement, that monitors misread documentation, that context was ignored, or that a consequence is disproportionate. How the state handles disagreement significantly affects the relationship. A clear, respectful process for resolving disagreements channels them productively; the absence of one pushes them toward political escalation.

The first element is informal resolution. Many disagreements can be resolved through conversation. Local areas should feel free to raise concerns with monitors and supervisors during and after the review, and the state should be open to reconsidering findings when local areas provide new information or persuasive interpretation. Informal resolution is faster and less adversarial than formal processes.

The second element is a defined response process. Draft reports should allow local areas to submit written responses, including disagreements with findings, within a defined period. The state should consider responses seriously and, in the final report, either revise findings or explain why they stand. Including the local area’s response in the final report ensures that its perspective is recorded.

The third element is escalation within the state. When local areas remain in disagreement after the response process, they should be able to request review by state managers above the monitoring unit. A higher-level review, by staff not involved in the original determination, provides a check on errors and demonstrates fairness.

The fourth element is formal processes. WIOA and its regulations, as well as state law, provide for grievance and appeal processes in certain circumstances, such as appeals of sanctions or certain determinations. States should explain these processes clearly, including timelines and procedures, and follow them carefully. Local areas should understand their rights.

The fifth element is professional tone. Disagreements should be handled professionally on both sides. State staff should avoid defensiveness and should not treat disagreement as insubordination. Responses to local concerns should be respectful and substantive, engaging with the local area’s arguments.

The sixth element is learning from disagreements. When disagreements reveal ambiguities in guidance or inconsistencies in monitoring, the state should address them, clarifying guidance or adjusting monitoring practices. Disagreements are valuable sources of feedback.

The seventh element is federal consultation. Some disagreements involve interpretation of federal requirements. In these cases, the state can consult its federal regional office, communicating the question and the answer to the local area.

The eighth element is preserving the relationship during disputes. Even during formal disputes, the state and local area must continue working together on other matters. Keeping disputes focused on the specific issue, and continuing cooperation elsewhere, prevents a single disagreement from damaging the entire relationship.

The ninth element is honoring outcomes. When the state concludes that a finding was in error, it should withdraw or revise it promptly and acknowledge the error. When the state upholds a finding, it should explain its reasoning clearly. Either outcome, communicated respectfully, maintains credibility.

A fair, accessible process for disagreement signals that the state is confident in its findings but open to being wrong. Local areas that trust the process are less likely to seek political intervention and more likely to accept outcomes.

Relationship-Preserving Monitoring in Practice

The following hypothetical example illustrates how a state workforce agency might improve its monitoring communication. It does not describe an actual state.

A state workforce agency notices growing tension with local boards. Several local directors have complained to the state workforce association that monitoring reports are harsh and inconsistent, and two chief elected officials have contacted the governor’s office about findings they considered unfair. A review of recent reports shows that they list findings without distinguishing severity, rarely mention strengths, use accusatory language, and sometimes cite practices that state program staff had approved. Exit conferences are brief, and some findings appear in reports without having been discussed.

The agency’s leadership decides to redesign its monitoring communication. It convenes a working group including monitors, program staff, and several local directors, coordinated with the state workforce association. The group develops a published monitoring framework describing the purpose of monitoring, areas reviewed, risk-based selection criteria, result categories, corrective action processes, and dispute resolution. The agency shares its monitoring guides with all local areas and encourages local self-monitoring using the same tools.

Monitors receive training on the new framework, neutral report writing, and the no-surprises principle. Calibration sessions help monitors classify issues consistently. Program and monitoring staff begin meeting monthly to align interpretations, and answers to policy questions are shared with monitors.

The redesigned process begins with advance notice and a pre-review call. During reviews, monitors raise potential issues in real time and hold substantive exit conferences covering all preliminary findings, concerns, and strengths. Draft reports follow a new template with an executive summary, separate sections for findings, concerns, observations, and promising practices, neutral language, citations, sample sizes, and context. Local areas have thirty days to respond, and responses are included in final reports.

Final reports are addressed to the chief elected official and board chair, with the director copied, after the director has had time to brief them. The state offers briefings for areas with significant findings. Corrective action plans are developed by local areas with state technical assistance, with clear acceptance criteria and realistic timelines. Findings are closed promptly when corrective actions are complete.

The agency also publishes an annual statewide summary of common findings and promising practices, and holds a peer learning session where local areas share practices identified through monitoring.

Over two years, complaints to the association and the governor’s office decline. Local directors report that monitoring feels fairer and more useful. Repeat findings decline, suggesting that collaborative corrective action is addressing root causes. Monitors report that local areas are more forthcoming about problems.

The example illustrates the core principles: published expectations, shared tools, aligned technical assistance and monitoring, communication during reviews, no surprises, balanced and neutral reports, collaborative corrective action, appropriate communication with governance leaders, consistency, recognition of strengths, and fair processes for disagreement.

Measuring Monitoring Communication

Monitoring units typically track their activity: reviews conducted, findings issued, corrective actions closed. These measures say little about whether monitoring communication is effective or whether it preserves productive relationships. Measuring communication and its effects helps states improve monitoring as a tool for compliance and improvement.

The first area is local experience. Surveys of local directors after reviews can ask whether expectations were clear, whether issues were discussed before the report, whether the report was fair and accurate, whether strengths were recognized, and whether corrective action was workable. Periodic surveys of local areas about the state’s monitoring overall track trends over time.

The second area is surprises. Tracking how often final reports contain findings not discussed at the exit conference measures adherence to the no-surprises principle.

The third area is timeliness. Tracking the time from review to draft report, draft to final, and corrective action submission to closure shows whether the process moves efficiently. Long delays reduce usefulness and increase frustration.

The fourth area is consistency. Analysis of findings across areas, and internal reviews of reports for consistency, reveals whether monitoring applies standards evenly. Disputes about inconsistency are also an indicator.

The fifth area is corrective action effectiveness. The rate of repeat findings in later reviews indicates whether corrective actions address root causes. Declining repeat findings suggest effective collaborative corrective action.

The sixth area is disagreements. Tracking the number of disputes, their resolution, and how often findings are revised shows whether the dispute process works and may reveal problems in monitoring practices.

The seventh area is escalation to political channels. Contacts from elected officials about monitoring, complaints to associations, and similar signals indicate relationship strain. Declines suggest improved communication.

Several questions help states assess monitoring communication:

• Do local directors report that monitoring expectations were clear and that results contained no surprises?

• Are reports issued and findings closed within target timeframes?

• Are findings consistent across local areas for similar issues?

• Are repeat findings declining over time?

• Are disagreements resolved through the state’s process rather than through political escalation?

Results should be reviewed by monitoring and program leadership and shared with local areas, along with improvements the state will make. This transparency models the accountability the state asks of local areas.

Measurement should not compromise the integrity of monitoring. The goal is better communication, not fewer findings. A monitoring process that issues fewer findings because monitors avoid difficult issues would be a failure, not a success.

How Workforce Monitoring Communication Compares With Other Agency Types

Many oversight relationships in government involve one entity reviewing another’s compliance and performance, and their experiences offer lessons for workforce monitoring communication.

Government auditors, including state auditors and independent auditors conducting single audits of federal funds, follow professional standards that include communicating findings to management, obtaining management responses, and including those responses in reports. Auditing standards emphasize objectivity, evidence, and clear distinction between findings of different significance. Workforce monitoring can borrow these practices, including management responses and clear classification of findings.

State education agencies monitor school districts for compliance with federal programs, such as special education and Title I. Many have adopted differentiated monitoring approaches, in which the intensity of monitoring depends on risk and performance, and they combine monitoring with technical assistance. Their experience shows the value of tiered support and of framing monitoring as part of improvement.

Health care accreditation organizations review hospitals and other providers, communicating findings, requiring corrective action, and recognizing strengths. Accreditation processes often include exit conferences, opportunities for clarification, and structured corrective action plans with evidence requirements, practices similar to those recommended for workforce monitoring.

Federal agencies monitor states, including the Department of Labor’s monitoring of state workforce agencies. State agencies experience monitoring from the receiving end, and their own experiences with federal monitors, both positive and negative, can inform how they monitor local areas.

Regulatory agencies inspecting private businesses, such as workplace safety or environmental regulators, operate in an enforcement relationship that is more adversarial than the state-local workforce partnership. Their experience highlights the importance of due process and consistency, but workforce monitoring should not adopt an enforcement posture inappropriate to a partnership.

What distinguishes workforce monitoring communication is the combination of a partnership relationship in which the state depends on local areas to deliver results; shared governance with local boards and chief elected officials who have formal authority and liability; federal requirements for state oversight; negotiated performance levels with statistical adjustment; and local areas of widely varying capacity. These features make the balance between partnership and oversight, alignment of technical assistance and monitoring, no-surprises communication, collaborative corrective action, and careful engagement with governance leaders especially important. Workforce agencies can borrow from audit standards, education’s differentiated monitoring, and accreditation’s structured processes, adapting them to the workforce partnership.

Tying It All Together

Monitoring communication is not a side function of state oversight. It determines whether monitoring produces lasting improvement or defensive compliance, whether local areas raise problems or conceal them, and whether the state-local partnership survives the accountability that federal law requires. Rigor and respect are not opposites; the most effective monitoring combines both.

States serve as both partners and overseers, and the tension between these roles is sharpened when technical assistance and monitoring are disconnected. Communication that makes both roles explicit, frames monitoring as improvement rather than punishment, describes conditions rather than character, acknowledges shared responsibility, and maintains real accountability helps balance them.

Monitoring communication strains relationships through surprise, harsh tone, lack of proportion, inconsistency, ignored context, omitted strengths, unrealistic corrective actions, bypassed local leaders, unclear consequences, and no avenue for disagreement. Each can be addressed.

Before monitoring, published frameworks, shared tools, advance notice, pre-review conversations, clarity about applicable standards and result categories, alignment of technical assistance with monitoring, and early performance expectations set the stage. During reviews, entrance conferences, real-time clarification, respectful interaction, substantive exit conferences, opportunities for additional information, clarity about preliminary results, acknowledgment of strengths, and clear timelines prevent surprises. Reports with executive summaries, distinguished severity, neutral language, citations, scope, context, recognition of corrections, strengths, clear corrective actions, and draft review inform rather than indict.

Performance communication involves transparent negotiation, plain explanation of indicators and adjustment, regular reporting, early warning, context, clarity about consequences, recognition, and connection to improvement. Collaborative corrective action addresses root causes with local ownership, realistic timelines, clear acceptance criteria, technical assistance, check-ins, prompt closure, acknowledgment of state-caused issues, and care with questioned costs. Escalation, when necessary, is predictable, clearly noticed, open to response, proportionate, consistent, accompanied by support, carefully communicated publicly, respectful of due process, and offers a path back.

Board chairs and chief elected officials receive appropriate information, sequenced to respect local leadership, summarized for governance audiences, with governance implications explained and briefings offered. Consistency is supported by standardized tools, calibration, internal review, recorded interpretations, alignment with technical assistance, trend reporting, transparent risk criteria, prospective application of new interpretations, and responsiveness to concerns. Recognizing strengths improves accuracy, motivation, learning, and relationships. Fair processes for disagreement, from informal resolution to formal appeal, channel disputes productively. And measuring local experience, surprises, timeliness, consistency, repeat findings, disagreements, and political escalation shows whether monitoring communication is working, without compromising monitoring’s integrity.

Strategic Communication Support

Improving monitoring communication requires examining how monitoring is planned, conducted, reported, and followed up; aligning monitoring with technical assistance; developing frameworks, templates, and training; and rebuilding trust where relationships have been strained. Monitoring units are often focused on completing required reviews and may lack capacity or perspective to redesign their communication. External support, including neutral facilitation between state and local partners, can help.

Stegmeier Consulting Group (SCG) helps public agencies communicate oversight and accountability in ways that maintain productive relationships. For state workforce agencies, that work can begin with an assessment of current monitoring communication: reviewing monitoring frameworks, tools, reports, and corrective action processes; interviewing monitors, program staff, and leadership; and gathering perspectives from local directors, board chairs, and chief elected officials. This assessment identifies where communication creates unnecessary strain and where it works well.

From that foundation, SCG can help develop a published monitoring framework, report templates with executive summaries and severity distinctions, plain-language explanations of performance indicators and adjustment, corrective action templates with clear acceptance criteria, and governance briefing materials for board chairs and chief elected officials. SCG can facilitate working groups bringing state and local staff together to design these elements, which builds shared ownership.

Implementation support can include training monitors in neutral report writing and constructive exit conferences, facilitating calibration sessions, designing processes for aligning technical assistance and monitoring, and developing approaches for sharing promising practices. Evaluation support helps agencies measure local experience, timeliness, consistency, and repeat findings. The aim is monitoring that holds local areas accountable while strengthening, rather than eroding, the partnership on which the workforce system depends.

Future Trends

Several established developments are shaping how state workforce agencies communicate monitoring and performance accountability. Risk-based and data-driven monitoring approaches continue to develop. Rather than reviewing every area with the same intensity, many states use data on performance, financial indicators, prior findings, and other factors to target monitoring where risk is greatest. These approaches can make monitoring more efficient, but they require transparent communication about risk criteria so that local areas understand why they are reviewed more or less intensively.

Remote and hybrid monitoring has become more common, with document review conducted electronically and interviews held by video. Remote monitoring can reduce burden but may lose some of the relationship-building benefits of on-site visits. States can preserve communication quality by holding substantive virtual entrance and exit conferences and maintaining personal contact with local leaders.

Continuous monitoring through data systems is emerging in some states, with dashboards that allow both state and local staff to see compliance and performance indicators in near real time. Continuous monitoring can shift the emphasis from periodic findings to ongoing improvement, if communicated as a shared tool rather than surveillance.

The federal performance accountability framework may evolve. Guidance on indicators such as effectiveness in serving employers has developed over time, and potential changes to federal workforce program structure, contemplated in budget proposals in recent cycles, could alter performance expectations and monitoring requirements if enacted. Whether and how such changes occur is uncertain. States will need to communicate any changes clearly to local areas.

Funding pressures may intensify monitoring scrutiny. When funding is reduced, the stakes of questioned costs and performance consequences rise, and relationships may be strained further. Clear, fair communication becomes even more important under financial pressure.

New requirements in partner programs may expand monitoring scope. Federal legislation enacted in 2025 broadened work requirements associated with SNAP and introduced community engagement requirements for certain Medicaid enrollees, with implementation phased in by states. Where workforce systems play roles in these programs, states may need to monitor new activities and communicate new expectations.

Finally, staff turnover in both state and local agencies means that monitors and local directors may change frequently. Documented frameworks, shared tools, and consistent processes help maintain consistency and relationships through turnover, so that the quality of monitoring communication does not depend on particular individuals.

Conclusion

The thirty-page report with fourteen findings, no mention of strengths, and two citations for practices a state specialist had recommended did not need to provoke a call to the county commissioner. Every finding in it might have been accurate. What made it damaging was that the director had not heard several of the findings before, could not tell which mattered most, saw her area’s progress ignored, and found herself cited for following the state’s own advice. The commissioner’s question about whether the state was targeting the area was a predictable reaction to communication that felt one-sided.

For state workforce agency leaders and monitoring managers, the implication is that the way monitoring is communicated deserves as much care as the review itself. That means publishing the rules of monitoring in advance, aligning monitors with program staff, raising issues during the review rather than first in the report, distinguishing serious findings from minor ones, writing in neutral language with citations and sample sizes, recognizing strengths, designing corrective action with local areas around root causes, routing reports to board chairs and chief elected officials after directors have had a chance to brief them, applying standards consistently, and giving local areas a fair way to disagree.

States that communicate monitoring this way will not avoid hard findings or difficult consequences, nor should they. But they will find that local areas raise problems earlier, correct them more completely, and continue to see the state as a partner even while it holds them accountable.

Stegmeier Consulting Group’s Strategic Approach to Communication Systems

SCG approaches monitoring communication as a system that must hold local areas accountable while keeping the state-local partnership intact. That approach examines how monitoring is announced, conducted, reported, and resolved, and where local areas experience it as surprise, inconsistency, or attack. It then helps state agencies publish clear monitoring frameworks, align technical assistance with monitoring, hold reviews that raise issues openly, write reports that distinguish severity and recognize strengths, and design corrective action collaboratively around root causes.

For state workforce agencies, this means local directors who know what to expect and hear nothing new in final reports, board chairs and chief elected officials who receive clear governance summaries at the right time, performance expectations explained in plain language with early warning when results lag, escalation that is predictable and proportionate, and a fair process for disagreement. It means monitoring that remains rigorous while building the trust that leads local areas to surface problems early and fix them for good.

Use the form below to connect with our team and explore how strategic communication support can help your state workforce agency communicate monitoring findings, performance expectations, and corrective actions without damaging relationships with local boards.