The activity log

The activity log is the audit trail for the growth plan. Every change to the plan is recorded — who made it, what changed, when. The log is read-only; even HR administrators cannot edit or remove entries.

Where to find it

The log is part of the growth plan view. From /{slug}/app/grow/plans/{personId} (HR view) or /{slug}/me/plan (employee view), scroll to the Activity section. It is also accessible as a full-page view from the plan header by clicking View full activity.

What is logged

Every edit produces an entry. The catalogue of logged actions:

• Plan created — the growth plan was created (typically at hire time, by the handoff transaction).
• Target role set — targetRoleId was changed from null to a role.
• Target role changed — targetRoleId was changed from one role to another.
• Target role cleared — targetRoleId was changed from a role to null.
• Milestone added — a new milestone was created.
• Milestone updated — a milestone's title, description, linked competencies, or due date changed.
• Milestone status changed — a milestone moved between Not started, In progress, Done, Cancelled.
• Milestone removed — a milestone was deleted.
• Learning item added — a recommended item was added as a milestone.

For each entry, the log shows:

• Actor — who did it (HR admin name, line manager name, or employee name).
• Action — the catalogue label.
• Diff — for content changes, the before-and-after text. For status changes, the old and new status.
• Timestamp — to the minute.

Why the log is read-only

Two reasons:

• Trust. A development plan that anyone can rewrite history on is not trustworthy. The log is the artifact that makes the plan reliable as a record.
• Conflict resolution. When HR, the line manager, and the employee disagree on what was committed to, the log is the answer. It is single-source-of-truth precisely because no party can edit it.

If a logged action was made in error (e.g., a milestone deleted by accident), the recovery is to re-add the milestone — the log will then show both the deletion and the re-addition. Nothing is hidden.

Notifications driven by the log

When an action is taken on a plan by one of the three parties, the other two receive a PLAN_EDITED notification. The notification text reflects the action — Your line manager added a milestone to your plan — and links to the plan.

Notifications are not sent for every micro-edit. A burst of edits within ten minutes from the same actor is rolled up into one notification.

Exporting the log

The log can be exported as CSV from the View full activity page. Useful for HR audit trails or for inclusion in performance review documentation.

What is not in v0.5

• Comments on plan entries. A growth plan in v0.5 cannot be discussed in-product; conversations happen externally and the outcomes are recorded as edits to the plan. In-product comment threads are on the v0.6 watch list.
• Threaded review of historical states. The log shows what changed; it does not let you reconstruct the plan as it stood at a previous date. Plan version history is also on the v0.6 list.

Next

Section VI — The employee experience walks through the entire individual portal from the employee's perspective.