Growth plan and milestone

A growth plan is the artifact where one person's development is committed to and tracked. Each Person has at most one growth plan; the plan is co-edited by HR, the line manager, and the employee.

Anatomy of a plan

• Target role (optional) — the role the employee is working toward.
• Milestones — discrete development goals.
• Linked learning items — courses or programmes added from the recommendations surface.
• Activity log — chronological record of every edit, with actor and diff.
• Status — DRAFT (created at hire, before any party has touched it) or ACTIVE (any party has edited it at least once).

Plans do not have a status that indicates complete or closed. They are alive while the person is an employee; they wind down when the person leaves.

Milestones

A milestone has:

• A title.
• A description — what good looks like.
• Linked competencies — the competencies the milestone is meant to develop.
• Status — not started, in progress, done, or cancelled.
• An optional due date (with a reminder fired two weeks before).

Milestones can be added, edited, or removed by any of the three editing parties. The most useful plans have three to five active milestones at a time.

How a plan is created

Automatically, by the hire handoff. The plan is created in DRAFT with no milestones and no target role — you add milestones once you and the employee agree on a development direction.

The first edit by any party flips status to ACTIVE.

Co-editing

Three parties have full editing access:

• HR Administrator.
• Line Manager — for plans of their team members.
• Employee — for their own plan.

There is no approval workflow. Anyone can change anything at any time. The activity log captures every change, so accountability is via record rather than via gate.

This is intentional. Approval workflows tend to make plans into documents nobody touches; the freely-editable model keeps plans alive.

Activity log

The log is the audit trail. It records:

• Every milestone added, updated, status-changed, or removed.
• Every target role set, changed, or cleared.
• Every learning item added.

Each entry has actor, action, diff, and timestamp. The log is read-only — no party can edit or delete entries.

When one party edits the plan, the other two receive a PLAN_EDITED notification. Bursts of edits from the same actor within ten minutes are batched into one notification.

What a plan does not contain

• Performance reviews. Performance is a separate signal that the platform does not record in v0.5.
• Compensation goals. Compensation lives in your HRIS.
• Confidential HR notes. The plan is co-visible to all three editing parties; there is no private side-channel for HR-only notes within the plan in v0.5.
• Organisation-wide goals. Plans are per-person.

Plan lifecycle when someone leaves

When a Person's status changes from EMPLOYEE to FORMER_EMPLOYEE, their plan is preserved (for audit) but no longer surfaces in the active-plans list. The activity log remains intact.

If the Person is re-hired later, the platform creates a new plan rather than reactivating the old one — the rationale is that an old plan rarely reflects current circumstances.