Skip to content

Work an action plan

An action plan is the follow-up to something the analysis found — a widening skill gap, an attrition projection, a bias flag. It records what you intend to do about it, as a list of items with owners and progress, so remediation is tracked rather than remembered.

Required role: Administrator.

  1. Go to Performance → Insights → Action Plans.
  2. Select Create Plan.
  3. Enter the Title and choose the Source type.
  4. Write the Expected outcome — what success looks like.
  5. Add each Action item, giving it a title and optionally a description.
  6. Set the Priority and the Due date.
  7. Select Create plan.
OptionDescription
Dashboard InsightSomething noticed on a dashboard.
Predictive AnalyticsA prediction — attrition, skill gaps, hiring need, promotion pipeline.
Skill Gap AnalysisA capability shortfall found in gap analysis.
Bias FlagA finding from AI bias monitoring.
Vera ConversationSomething that came out of a conversation with Vera.

The source is not decoration. It records why the work was started, which is what makes a plan defensible months later when somebody asks what you did about a finding.

Example: a bias flag on promotion readiness at HC Corp produces a plan whose source says so. Six months on, that plan is the evidence that the flag was investigated rather than noted.

Generate from Insight builds a plan from an existing finding rather than from a blank form. It reads the source — a prediction, a bias report, or a skill trend analysis — and seeds the action items from the recommendations already in it.

To seed items from a predictive analytics, skill gap, or bias flag source, you must identify which finding to read by supplying its Source ID. Left blank, you get a generic plan with no seeded items.

Generating a plan uses AI and consumes credits. The list shows how the plan was produced and what it cost, in the By and Credits columns.

Example: generating from HC Corp’s twelve-month skill-gap prediction seeds items straight from that prediction’s recommendations. Creating the same plan by hand costs nothing and gives you exactly the items you wrote.

OptionDescription
TitleThe plan’s name.
SourceWhere the finding came from.
StatusWhere the plan has reached.
ProgressCompleted items against the total.
ByWhether the plan was generated or written by hand.
CreditsCredits consumed if it was generated.
CreatedWhen it was created.

The status filter defaults to Active, which combines proposed and in-progress plans. Completed and dismissed plans are still there — change the filter to see them.

OptionDescription
Active (proposed + in progress)Everything still open.
Proposed onlyCreated but not started.
In progress onlyStarted.
CompletedFinished, with an outcome recorded.
DismissedClosed without being carried out.

Each action item carries its own state, and selecting it advances that state: Pending becomes In Progress, and In Progress becomes Completed. A completed item can be moved back to pending, and an item that is not completed can be cancelled.

Overall progress on the plan is the proportion of its items completed, so the plan’s percentage is only as honest as the item states.

Complete asks for an Outcome describing what actually happened, and records it against the plan. Dismiss closes the plan without carrying it out.

Write a real outcome. The expected outcome says what you hoped for; the actual outcome is the only record of what the work achieved, and it is the difference between a plan that proves something and a tick in a list.

Example: closing HC Corp’s cloud-skills plan with “four engineers certified, gap down from 9 to 5” is worth reading next year. Closing it with “done” is not.

A completed plan is a record that a finding was acted on, held next to the finding that produced it. Where the underlying analysis can be regenerated — a prediction, a gap analysis, a bias report — run it again after the plan closes, because the honest test of remediation is that the measurement moved.