A growth plan is the artifact where development is actually planned. It belongs jointly to three parties — HR, the line manager, and the employee — and they all edit it. The platform's job is to keep the editing co-ordinated, log every change, and make the plan a useful reference rather than a forgotten document.
Where to find it
For HR / line manager: /{slug}/app/grow/plans/{personId}. For the employee: /{slug}/me/plan. Both edit the same plan; the views are tailored slightly to the role.
What a plan contains
Four parts:
- Target role — the role the employee is working toward, if any. Picked from any role in the workspace; defaults to null.
- Milestones — discrete development goals, each with a title, description, optional due date, and one or more linked competencies the milestone is meant to develop.
- Linked learning items — courses or programmes (from the recommendations surface) that have been added to the plan.
- Activity log — a chronological list of every edit, with actor and diff.
Who can edit what
- HR — everything.
- Line manager — everything for plans of their team members.
- Employee — everything on their own plan.
There is no approval workflow. Anyone authorised to edit can make a change at any time; the change is logged, all parties are notified.
Why no approval
Two reasons:
- Approvals slow down the conversation. A growth plan that requires sign-off on every milestone change becomes a document people stop touching. The point of the plan is to be alive.
- The activity log gives accountability without bureaucracy. Every change is attributable; bad changes can be reverted in a follow-up conversation rather than blocked at gate.
If a workspace strongly prefers an approval flow, the request is on the v0.6 watch list. The default is no approval.
Editing a milestone
From either view, click + Add milestone or click an existing milestone to expand it. The fields are:
- Title — a short name for the development goal.
- Description — what good looks like, in 1–3 sentences.
- Linked competencies — the competencies this milestone develops, picked from the taxonomy.
- Due date — optional; reminders fire two weeks before.
- Status — Not started, In progress, Done, Cancelled.
The save is immediate. There is no draft state; what you see is what others see.
Editing the target role
From the plan header, click the target-role pill. A picker opens with every role in the workspace. The choice is logged in the activity log and triggers a PLAN_EDITED notification to the other two parties.
Changing the target role has no other side-effects in v0.5 — career path computation continues to be driven by the profile rather than the plan's target. In v0.6, plans with explicit targets will likely receive prioritised learning recommendations.
AI draft plan
Once a target role is set, the milestones section shows an AI draft plan button (HR / line manager only). Clicking it — and confirming the AI-cost prompt — asks the model to turn the person's competency gaps toward the target role into a sequenced set of ~3–6 milestones: foundational gaps first, weighted 70:20:10 (mostly on-the-job stretch, some mentoring, few formal courses).
The result is a draft, never auto-saved. It fills a review panel below the button where you can edit each title, drop milestones you don't want, then click Add all to plan to persist them through the normal milestone flow — or Discard. Nothing touches the plan until you add it. The button never fires on its own; if no target role is set, it asks you to pick one first. If the person already meets every requirement of the target role, it reports that there are no gaps to plan.
Linked learning items
From the learning recommendations surface, an Add to plan action creates a milestone of type learning and links the recommended item. The same is available from the employee's own learning page.
Activity log
Every edit is logged with:
- Actor — who made the change (HR / line manager / employee).
- Action — milestone added, milestone status changed, target role changed, learning item added, etc.
- Diff — what changed.
- Timestamp.
The log is read-only. It cannot be edited or deleted by anyone, including HR. Audit trails for development conversations require this.
Next
The next page covers learning recommendations — the surface that proposes specific courses and programmes to address gaps.