A team changes its discovery process. The competency rubric gets updated to match. Six months later, somebody compares this quarter's scores with last quarter's and assumes the number measures the same thing.

It may not.

If the definition of acceptable performance changed, the history needs to preserve that change. Otherwise, a tidy trend line can hide a moving standard.

This is a governance proposal for an enablement system. It does not establish employment policy or promise that a rubric removes every source of judgment.

For each competency, keep a stable name or identifier, a version, an owner, an effective date, and the reason for the latest change. Preserve the earlier definition alongside the current one.

The change note should explain the behavior that changed. “Updated language” is too vague when the edit changes what a person must demonstrate. “Added confirmation of business impact before proposing a next step” is something a manager can understand and teach.

That record also helps distinguish a correction from a new expectation. Fixing a typo and adding a performance requirement should not look identical in the history.

A definition may appear in onboarding, practice exercises, manager coaching, and annual evaluation materials. Updating the master document does not guarantee all of those uses change with it.

Keep a short list of those dependencies. When the standard changes, the owner can identify the training that needs revision and the managers who need the explanation. This does not need to become a new software project. A linked list is enough for a small pilot.

Where the rubric informs formal employee evaluation, work with the appropriate people leaders on how and when the revised expectation takes effect. The learning team should not quietly rewrite those conditions through a training document.

Attach the rubric version to the evidence you collect. When you review a result later, you can see which expectation was in force and avoid treating different definitions as directly comparable.

Start with one competency that has recently changed. Reconstruct the earlier definition, explain the new one, and identify which materials use it. If you cannot find that information, you have found a useful maintenance task.

A competency function becomes easier to trust when people can tell what the standard is, who owns it, and how it became the current standard. The change log makes that history available without requiring everyone to remember the conversation.