From Survey to Action: Engagement Action Planning for Agencies

FEVS results drop in October. HR teams distribute reports. Executives see slides. And then the year moves on. In agency after agency, that is the whole cycle — and it is the wrong cycle. OPM's framework is explicit: a survey is not the deliverable; it is the starting point of a collect → study → act loop. Break the loop at the action step and you do not just fail to improve — you actively make things worse.

The mechanism is straightforward. Employees who complete a survey and observe nothing change learn — correctly — that completing the survey changes nothing. Response rates fall, scores on the belief-the-survey-will-be-used items fall further, and the next cycle produces less useful data than the one before it. Donald Kettl, one of the foremost federal management scholars, put it plainly: running a survey without visibly acting on it "undercuts the entire value of the process."

Federal agencies are required by regulation (5 CFR Part 250, Subpart C) to conduct an annual employee survey, and agencies must post survey dates and results no later than 120 days after administration closes (PLAY-007). Posting results is the statutory floor — it is not action planning. It is the precondition for action planning. What happens in the weeks after posting is what determines whether next year's score moves.

OPM's official action-planning guide is titled, deliberately, "A Simple Approach to Action." The agencies that fail at action planning almost always fail by making it complicated — agency-level task forces, enterprise improvement roadmaps, multi-year priorities attributed to the Secretary's initiative. OPM's instruction runs in the opposite direction: keep it simple, keep it at the work-unit level, keep it owned by the manager of that unit (PLAY-004).

The model has four elements. First, pick one focus area — the specific domain you will change this cycle, not a theme or a category. Second, take two or three concrete action steps, at least one of which employees can observe quickly. Third, assign a named individual owner to each action step with a due date. Fourth, talk about the plan four times throughout the year — not in executive briefings, but to the work unit that gave you the data.

OPM's action-plan template includes fields for Focus Area, Issue, Action, Action Step, Due Date, Owner, and Status. The operative field is Status. When named owners are updating that field and communicating changes to the team, the plan is alive. When Status reads "in progress" for months without a word to the team, the plan is dead — and the team knows it before the next survey cycle opens.

OPM defines the threshold precisely: an "area that needs improvement" is any item where 35% or more of employees responded unfavorably (PLAY-004). In most agencies, that definition generates a list — sometimes a long one. The action-planning discipline is to select one item from that list and commit to moving it, rather than distributing effort thinly across all of them.

For the majority of federal work units right now, recognition is the obvious candidate. The item "In my work unit, differences in performance are recognized in a meaningful way" scored 47% positive on the 2024 FEVS — the lowest-scoring item on the entire governmentwide survey (OPM FEVS, 2024). Nearly every agency clears the 35% unfavorable threshold on recognition. More importantly, recognition is also one of the cheapest items to act on: frequent, non-monetary peer recognition under Title 5 §4503 requires no budget line and no procurement cycle. The gap between score and action is almost entirely a behavior change, not a resource constraint.

Choosing recognition is not the only defensible choice — your work unit's specific data may point elsewhere, and it should. But there is always a defensible choice, and OPM's model demands committing to one. An action plan that lists recognition, communication, leadership visibility, and career development as four co-equal focus areas is not a plan. It is a list of aspirations with no owner.

Every action step in the OPM model must have a named owner — not "HR," not "the management team," not "leadership." One person. With a due date. Ownership diffusion is the most common way action plans fail without ever being acknowledged as failures: everyone is accountable, so no one is, and the plan drifts through the year with Status perpetually at "in progress" (PLAY-004).

The quick win is the companion mechanism. A quick win is an action the work unit can observe soon after the plan is shared — before any reasonable person has given up hope that something will change. It does not have to be large. A supervisor's handwritten note to each team member naming one specific thing that will be different, posted in a shared space, is a quick win. A manager sending a personal email acknowledging specific contributors by name is a quick win. What it cannot be is a promise to convene a committee that will report back in Q3.

Named owners and quick wins are also the mechanism by which managers prove to their teams that survey participation produces real outcomes. OPM's research shows that employees' belief that survey results will be used to improve their agency is itself among the lowest-scoring engagement items — meaning employees are skeptical by default (PLAY-005). A quick win from a named owner, delivered early in the action cycle, is the fastest way to change that belief in a specific work unit.

The close-the-loop mantra is the Partnership for Public Service's distillation of what top agencies do differently. HHS's version: "you spoke, we listened, this happened." The exact wording is flexible; the discipline is not. Every action taken in response to survey feedback must be explicitly connected — in a communication, not just an internal report — back to the feedback that triggered it. Connected to the employees who gave that feedback, not just to the SES layer that received the data (PLAY-005).

The 2024 FEVS showed a governmentwide response rate of 41%, up from a pandemic low of 34% in 2021 (OPM FEVS, 2024). That recovery reflects years of agencies improving their close-the-loop practices across cycles. Response rates rise when employees have directly observed that completing the survey produces visible change. They fall when they have observed the opposite. The close-the-loop communication is the most direct lever any manager holds over the agency's next response rate.

OPM recommends four touchpoints throughout the year — roughly quarterly. Not one announcement at the beginning and silence for the rest of the cycle. Not a year-end summary buried in an all-hands presentation. Four active check-ins: here is what we said we would do, here is where we are, here is what we learned, here is what comes next. That cadence keeps the plan alive and signals that the survey is a management tool, not an annual compliance exercise.

Agencies that run the same FEVS cycle year after year without moving scores almost always fall into one or more of five documented failure modes (PLAY-006):

1. Fixing everything at once. The action plan lists seven improvement areas with no priority order. Nothing moves because everything is a priority — which in practice means nothing is. Commit to one.

2. The plan lives in HR, not in the work unit. HR owns the document, runs the reporting, and presents results to the Deputy Secretary. The work-unit manager never shared results with the team and never named a local owner. Employees experience FEVS as something that happens to them, not something that changes their reality.

3. No named owners or due dates. Action steps read: "leadership will explore options for improving recognition." That sentence names no one, sets no deadline, and defines no criterion for success. It is a commitment to consider, not a commitment to act.

4. A static document. The plan was written in November after results were released, and it was never revisited. When the next FEVS cycle opens, Status fields still read "in progress" from eleven months ago. Employees who remember what was promised also remember what was not delivered.

5. Labor relations skipped. A recognition program rolls out without satisfying bargaining obligations, triggers an unfair labor practice charge, and gets unwound. The failure mode is not the legal obligation itself — it is treating that obligation as a surprise rather than a gating requirement at the start of planning.

OPM's action-planning guide is explicit: for organizations with bargaining-unit employees, supervisors must ensure all labor-relations obligations are met in accordance with law and existing collective bargaining agreements before acting on the plan (PLAY-006). This is not boilerplate. It is a gating requirement that belongs at the beginning of the planning process, not at the end.

New recognition programs, scheduling changes, and team-activity initiatives typically touch "conditions of employment" — which, under the Federal Service Labor-Management Relations Statute (Title 5, Chapter 71) administered by the FLRA, agencies may be required to bargain over before implementing (PLAY-022). The practical question is not whether the obligation exists, but whether the specific proposed action triggers it. That determination belongs to your labor-relations office, not the action-planning team.

The correct sequence: before finalizing the action plan, route proposed actions through labor relations. If a proposed recognition program or scheduling pilot triggers a bargaining obligation, determine whether you must bargain over the decision itself, the impact, or both before rollout. Agencies that treat labor relations as a partner rather than a checkpoint rarely face the rollback problem — and their plans survive long enough to actually move scores. State and local settings operate under different statutes — PERBs, state labor codes, MOUs — but the principle is identical: identify the obligation early, engage the union where the law requires it, and document the consultation.

Pulse surveys — typically five to ten questions, run monthly or quarterly — work best as a targeted check on specific action areas between FEVS cycles (PLAY-009). The governing rule is simple: only survey as often as you can visibly act. A pulse acknowledged with a summary and a named next step strengthens the signal. A pulse that HR reads and files without a word to the team loses more goodwill than it generates. Keep pulse wording aligned with FEVS items so trends are interpretable across cycles, and keep the annual FEVS as the system of record rather than competing with it.

For HR leads managing action planning in 2025 and 2026, there is one critical data context: the 2025 FEVS was cancelled. OPM suspended it in August 2025 — the first cancellation since the survey became annual in 2010. OPM's director indicated FEVS will return in 2026 (PLAY-008). The 2024 FEVS remains the newest official federal engagement data and the correct baseline for any action plan.

In the gap, the Partnership for Public Service fielded its 2025 Public Service Viewpoint Survey (PSVS). The PSVS returned a government-wide Engagement and Satisfaction Index Score of 32 out of 100 (Partnership for Public Service, 2025 Public Service Viewpoint Survey — NOT FEVS; NOT comparable to prior years). The PSVS used different methodology, a far smaller sample (11,083 respondents), and 23 questions — 19 derived from FEVS items but not identical. The Partnership explicitly states the PSVS is not directly comparable to prior FEVS years (PLAY-008). Never read the 32/100 PSVS score as year-over-year FEVS movement. Your 2024 FEVS results are your baseline; build action plans on that data.

Where Actify fits: Actify is the post-survey action layer — the "we did" half of "you said / we did." Once FEVS or pulse data surfaces a focus area, Actify runs the activities and peer recognition that respond to identified gaps: activity-first engagement, gamification, non-monetary peer recognition aligned with Title 5 §4503, and an automatic monthly lightweight pulse check that keeps the action cycle visible. Actify is not a FEVS-grade survey engine; it does not administer the 16 statutory questions, generate FEVS-comparable data, or replace the annual census. For state and local HR leads, FedRAMP gating is lighter and the fit is strongest; at most federal agencies, FedRAMP/ATO requirements gate adoption of any cloud tool. Actify does not fix pay, staffing levels, or labor-relations obligations. It runs the recognition and activity layer after those structural pieces are in place.