Building a consistent, University-wide structure for staff positions, career growth, and workforce planning
The University of Oklahoma is rebuilding the way staff jobs are defined, organized, and connected to the labor market. The work produces two things: a job architecture that groups every staff job by discipline and by the complexity and scope of the work, and a job profile for each job in that structure, written consistently so that similar work is described the same way across campuses.
In partnership with Huron Consulting Group, Human Resources is building this structure with subject matter experts from colleges and administrative units across the University, who are reviewing the job families, subfamilies, and profiles in their area of expertise. The result will give employees a clearer view of how their work is defined, how it relates to similar work elsewhere at OU, and what progression within their field can look like.
What this work is not:
Current Phase: Foundation — Communication and roll out
This Month's Focus: Communication to Supervisors and Employees
Next Milestone: Leader & Partner Readiness — Leadership and Staff Announcements
Target Implementation: December 2026
Last Updated: November 6, 2026
What changes is how your job is described and organized in our records. What stays the same is your pay, your reporting relationship, and the work you actually perform.
| What Changes | What Stays the Same |
|---|---|
| The job profile behind your position, describing the work it performs. | Your base pay. No employee receives an increase or a reduction as a result of this work, and no positions are being eliminated. |
| Establishing a job family, subfamily, career stream, and career level for each job code. | Your reporting relationship and the person you report to. |
The structure makes several things clearer than they are today:
Key milestones are below. Outcomes are not set in stone, and there are multiple points along the way that can lead to refinement.
Human Resources is leading this work in partnership with Huron Consulting Group, together with senior leaders, managers, and subject matter experts from across the University who review the structure and validate job profiles for their areas.
The goal is to not disrupt open job searches during the transition period. To accomplish this, it is allowed to keep job listings using the old job codes open thru January, if needed to complete the job recruitment. During this same time, new job listings must begin using the new job codes on their PA1 ePAFs.
11/02/2026: Start using new job codes on PA1 ePAFsfor filling staff vacancies
2/01/2027: Open PA1s and job listings with old job codes will be closed. New PA1s and new job listings must be entered.
February 2027: All old job codes will be inactivated.
Old job codes have 4 numeric digits, while new job codes have 5 numeric digits. Job codes may also include 1 letter.
12/18/2026: All pending staff ePAFs using the old job codes must be executed or withdrawn
12/19-12/26: No ePAFs can be entered for staff whose titles use the old job codes
12/19/2026: Update job codes of all staff, inactivate job codes not used on open PA1s used for filling vacancies
12/26/2026 (NRM) 12/27/2026 (HC): Effective date of new job code on staff job data
12/26/2026 (NRM) 12/27/2026 (HC): Begin any new ePAFs for staff
When |
Rule |
|---|---|
Before conversion |
Do not future-date ePAFs beyond 12/26 (NRM) or 12/27 (HC) for employees whose tites use the old job codes. |
After conversion |
Do not backdate staff ePAFs earlier than 12/26 (NRM) or 12/27 (HC). |
The University is rebuilding the way staff jobs are defined and organized. The work produces a job architecture that groups staff jobs into families and subfamilies by discipline and into career streams and levels by the complexity of the work, and a job profile for each job, written consistently so that similar work is described the same way across campus.
Full-time and part-time staff positions across the Norman, Oklahoma City, and Tulsa campuses, including executives and administrative deans serving in staff roles. Faculty, student employees, graduate students, contract, temporary, and occasional employees, athletics coaching staff, USPS positions, and clinical positions associated with the OU Health integration are not included.
Job families and subfamilies are intentionally not built around a unit's organizational structure. They group positions by the nature of the work — the discipline, roles, and responsibilities — so that similar jobs are described and leveled consistently no matter where they sit on the org chart. A position in finance-related work, for example, maps to the Finance family whether it lives in a college, an academic unit, or central administration. A family or subfamily that appears to fall outside a unit's identity is simply describing the type of work the role performs; it does not move the position out of its department, change its reporting line, or redefine the unit. The job architecture is a classification framework, not an organizational-design decision; it standardizes how jobs are described and compared and does not determine how units organize or report.
We understand that in smaller colleges and units, a single position often spans several functions. When a role includes duties that cross more than one job profile, the position is assigned to the job code that reflects its primary function — the core responsibility that defines the role and occupies the majority of the employee’s time.
Secondary duties don’t change the mapping. Instead, they are captured as position-specific responsibilities in the individual’s position description, so the full scope of the work is documented even though the job code reflects the predominant function.
For example, a position whose core role is specimen collection but who also assists with research tasks is mapped as the primary role (e.g., Phlebotomist), with the additional duties noted in the position description. If, over time, a secondary function grows to become the employee’s predominant work, the position can be reviewed again to confirm the mapping still fits.
No. Your base pay is not changing as a result of this project. No employee receives an increase or a reduction because of it. The work is about how jobs are described and organized, not about changing pay.
Every staff job is being redefined and remapped this year, so the standing reclassification cycle is paused during the transition to avoid classifying positions against a structure that is being replaced. Reconsideration is the route for classification questions in the meantime, and the standing cycle restarts on September 1, 2027.
A progression that describes the nature of work being performed. Career streams include: Operational Contributor, Professional Contributor, Managerial, and Executive.
The knowledge, skills, behaviors, and abilities required to successfully perform the responsibilities of a job. Competencies help define expectations for performance, development, and career growth.
A federal law that establishes requirements related to minimum wage, overtime eligibility, recordkeeping, and employee classification as exempt or non-exempt. FLSA status is determined based on applicable regulations and job responsibilities.
A framework to organize and structure the various positions. It provides a systematic way of categorizing and classifying different work based on factors such as responsibilities, qualifications, skills, and other job-related characteristics.
A group of jobs involving similar types of work and requiring similar training, skills, knowledge, and expertise. The job family concept helps organize related jobs for purposes of pay, career progression, and performance management. Examples include Human Resources; Information Technology; Research.
A structured system for organizing and defining jobs across the University based on the work performed, responsibilities, scope, skills, competencies, and qualifications required. The job architecture provides a consistent approach for how jobs are classified, evaluated, and managed across the organization.
The strategic process of reviewing, evaluating, and aligning existing positions within the job architecture based on each position's primary responsibilities, competencies, required qualifications, skills, and scope of work. Job mapping ensures positions are placed within the appropriate job family, subfamily, career stream, and career level.
A high-level definition of a job's purpose, responsibilities, and qualifications. Used to ensure consistency in the way jobs are defined across the University.
The overall breadth and impact of a position, including the complexity of work, decision-making authority, level of responsibility, and influence within the organization.
A subset of a job family, usually more specialized in nature. Examples include: Compensation, Benefits (subfamilies within Human Resources); Computer Operations, Systems Administration (subfamilies within Information Technology).
A title assigned within the job architecture to consistently identify similar roles across the organization. Standardized job titles may appear in HR systems, while departments may continue using working titles that reflect specific operational needs. This is the job title you will see in PeopleSoft that is linked to the job code.
An individual with specialized knowledge or expertise in a specific area who provides input, guidance, and validation during the position review process.
A department-specific title used to describe an employee's role or area of responsibility. A working title may differ from the standardized job title used in HR systems. This title is typically used in job postings, employee signature lines, business cards, and similar contexts.