In Pando, competency names are global — they're shared across all rubrics. If two rubrics use the same competency name, they must use the same overall description (not to be confused with level-specific definitions, example behaviors, and example tasks, which can be rubric-specific). If you want different descriptions for different roles or rubrics, use different names.

When you create a competency, the name and description are stored as a single shared record. If you add that competency to a second rubric, it carries the same description — you can't have "Metrics" mean one thing on the Engineering rubric and something different on the Sales rubric.

Key rule: Same name = same description, always.

If the same skill applies to multiple roles but should be described differently, give them distinct names.

Examples: - "Metrics — Sales" and "Metrics — Engineering" instead of "Metrics" on both. - "Communication" (org-wide core competency) vs. "Executive Communication" (senior roles only).

This keeps each competency's description accurate without creating unintended cross-rubric conflicts.

If you update a competency description on one rubric, that change applies everywhere that competency is used. Employees across all rubrics using that competency will see the updated description.

Before renaming or updating a shared competency: Check which rubrics use it. Unintended changes to other rubrics can confuse employees mid-cycle.

Before building a new rubric, audit your existing competency library. Reuse competencies where the name and description are genuinely the same across roles. Create new competencies when the role-specific meaning diverges — even slightly.

For questions, contact support@pando.com or use the in-app chat.