Job Description Template for Existing Employees

Standard Operating Procedure: Authoring and Updating Job Descriptions for Existing Employees

1. Document Control Block

• Document ID: SOP-TR-HR-042
• Effective Date: October 24, 2023
• Version: 3.1
• Review Cadence: Annual / Post-Organizational Restructuring

---

2. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the institutional protocol for designing, auditing, and updating job descriptions for existing employees at Template Registry. The objective is to ensure structural alignment between operational demands, compensation bands, legal compliance (FLSA, EEOC), and internal leveling matrices. Adherence to this SOP mitigates misclassification risk, ensures equitable performance management criteria, and maintains organizational transparency.

---

3. Scope & Prerequisites

Scope

This procedure applies to all People Operations Partners, Department Heads, and People Managers initiating or revising job descriptions for active internal personnel (promotions, lateral shifts, or substantial role evolution).

Prerequisites & Required Tools

• Access to the Template Registry HR Information System (HRIS) – Workday module.
• Access to the Enterprise Compensation Management Tool – Pave.
• Current Job Architecture Matrix and Leveling Framework (Internal Wiki: /engineering/leveling).
• Historical Job Description archives (PDF/Markdown format).

---

4. Roles & Responsibilities

---

5. Step-by-Step Procedure

Phase 1: Audit and Gap Analysis

• Retrieve the legacy job description from the HRIS archive.
• Conduct a 30-minute structured intake interview with the incumbent employee and the People Manager to capture actual day-to-day responsibilities.
• Document delta metrics: identify tasks added, deprecated, or shifted in priority over the past 12 months.
• Verify that current core competencies align with the strategic OKRs (Objectives and Key Results) of the department.

Phase 2: Drafting and Structural Standardization

• Initialize a new document using the official Template Registry Job Description Markdown schema.
• Formulate a precise, functional job title compliant with internal naming conventions (e.g., [Level] [Domain] [Discipline], such as Senior Systems Infrastructure Engineer).
• Write a 3-4 sentence organizational summary clearly defining why the role exists and its impact on company mission.
• Populate the Essential Duties and Responsibilities section, allocating approximate time percentages (must total 100%) to each primary domain.
• Define quantifiable performance metrics or Key Performance Indicators (KPIs) associated with the position.

Phase 3: Leveling, Benchmarking, and Compliance Review

• Cross-reference draft competencies against the Enterprise Leveling Framework to verify scope, autonomy, and complexity criteria.
• Submit draft to the Total Rewards team via the HRIS ticketing queue for market data benchmarking and salary band assignment.
• Route the documentation through Legal/Compliance if the role transition involves a change in FLSA exemption status (e.g., Non-Exempt to Exempt).
• Secure sign-off from the People Operations Partner confirming internal equity across peer positions.

Phase 4: Finalization, Communication, and Archival

• Update the position profile within the HRIS (Workday) with the finalized Markdown/PDF output.
• Schedule a formal 1:1 meeting between the People Manager and the employee to review the updated job description, expectations, and compensation adjustments (if applicable).
• Secure electronic signatures from the employee, People Manager, and POP via the electronic signing module.
• Archive the prior version with a timestamp and deprecation tag in the central document repository.

---

6. Quality Assurance & Pro-Tips

Best Practices

• Focus on Outcomes, Not Tasks: Frame responsibilities around what is achieved rather than the mechanical steps taken. Avoid vague statements like "other duties as assigned" without baseline context.
• Maintain Gender-Neutral Language: Run drafts through inclusive language scanners (e.g., Textio) to eliminate gender-coded jargon and ensure maximum applicant/incumbent objectivity.

Common Pitfalls

• Scope Creep Inflation: Avoid unintentionally inflating a mid-level role into a senior role simply to justify a merit increase without a structural change in organizational impact.
• Out-of-Date Competencies: Ensure technical stacks (e.g., specific cloud providers, frameworks, compliance standards) are current and deprecated technologies are purged.

Metric Thresholds

• SLA for Completion: The entire update cycle (Phase 1 to Phase 4) must not exceed 14 business days.
• Market Band Alignment: The proposed salary band must fall within 90% to 110% of the median market benchmark unless an explicit executive exception is documented.

---

7. Frequently Asked Questions (FAQ)

Q: What triggers a mandatory job description review for an existing employee? A: A formal review is mandatory during annual performance cycles if the role has evolved by $\ge$ 30%, prior to any vertical promotion, or during department-wide reorganizations. Minor task adjustments do not require a full SOP execution.

Q: How do we handle an employee who refuses to sign their updated job description? A: Job descriptions define operational expectations set by the organization. If an employee declines to sign, the People Manager and POP must conduct an alignment session to address concerns. Refusal to acknowledge receipt and understanding of job duties will be documented in the HRIS as an administrative note and does not exempt the employee from the stated duties.