Overview
Rubrics in Pando are built from two types of competencies: core and domain-specific. Understanding the difference helps you decide what goes on every rubric vs. what's scoped to a specific role.
Core Competencies
Core competencies are org-wide behaviors that apply to everyone, regardless of role. They represent the shared expectations your organization holds for all employees β things like Communication, Collaboration, or Ownership.
Key characteristics: - Appear on multiple rubrics across different roles - Consistent description across the org (same name = same description β see Rubric competency naming rules) - Often tied to company values or cultural expectations
Examples: Communication, Collaboration, Problem Solving, Ownership, Adaptability
Domain-Specific Competencies
Domain-specific competencies are role-required skills that are only relevant to a particular role or rubric. They reflect the technical or functional expertise someone needs to perform in that role.
Key characteristics: - Scoped to a specific rubric β not expected to appear on all rubrics - Can have role-specific descriptions without the shared-name constraint - Change more frequently as roles evolve
Examples: SQL Proficiency (Engineering), Pipeline Management (Sales), Curriculum Design (L&D), Financial Modeling (Finance)
Why the Distinction Matters When Building a Rubric
Separating core from domain-specific helps you: - Avoid redundancy: Core competencies only need to be defined once and can be reused across rubrics. - Maintain consistency: Everyone is measured on the same core behaviors, even if their role-specific competencies differ. - Keep rubrics focused: Domain-specific competencies keep role rubrics targeted and meaningful rather than bloated.
Recommended starting point: Define your core competencies first. They're your foundation. Then layer in domain-specific competencies per role.
For questions, contact support@pando.com or use the in-app chat.
