Job Description Template for Employee

Standard Operating Procedure: Creation, Validation, and Lifecycle Management of Employee Job Description Templates

---

1. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the institutional requirements, technical specifications, and procedural workflow for authoring, validating, and maintaining employee job description templates within the Template Registry ecosystem. The objective is to ensure 100% compliance with labor regulations, internal leveling frameworks, compensation benchmarks, and objective performance management standards across all enterprise divisions.

---

2. Scope & Prerequisites

2.1 Scope

This SOP applies to all People Operations, Human Resources Business Partners (HRBPs), Compensation Analysts, and Department Heads responsible for creating or modifying role-based templates within the organization.

2.2 Prerequisites & Tooling Access

• Authoring Software: Template Registry Authoring Suite (TRAS) v4.2+
• Version Control: Git-based Internal Repository (registry-core/jobs)
• Compliance Database: E-Verify, EEOC Compliance Portal, and internal Legal Framework API
• Compensation Tooling: Radford Global Database / Mercer Benchmark System

---

3. Roles & Responsibilities (RACI Matrix)

---

4. Step-by-Step Procedure

Phase 1: Requirements Gathering & Scoping

• 1.1 Initiate a Job Description Change Request (JDCR) ticket in the internal ticketing system.
• 1.2 Gather baseline organizational requirements, including department, band level, reporting structure, and FLSA (Fair Labor Standards Act) classification status.
• 1.3 Conduct a market compensation analysis via the Radford Database to align salary bands with current macroeconomic benchmarks.

Phase 2: Template Drafting & Structural Configuration

• 2.1 Open the Template Registry Authoring Suite (TRAS) and instantiate the baseline schema TR-JD-SCHEMA-V2.
• 2.2 Populate the Position Overview section, ensuring a concise summary of the role's primary objective and business impact.
• 2.3 Define Core Responsibilities & Essential Functions, ordering them by frequency of execution and strategic weight (minimum 5, maximum 8 items).
• 2.4 Establish Minimum Qualifications (Education, Years of Experience, Technical Certifications) and Preferred Qualifications using objective, verifiable metrics.
• 2.5 Specify Key Performance Indicators (KPIs) and OKR frameworks linked to the role to ensure operational alignment post-hire.

Phase 3: Compliance & Engineering Review

• 3.1 Execute the automated compliance checker script (./scripts/lint-jd-schema.py) against the drafted document to verify inclusive language and ADA/EEOC compliance.
• 3.2 Submit the template payload to the Compensation Department for internal equity verification.
• 3.3 Submit the verified draft to the Legal and Compliance division for regulatory sign-off.

Phase 4: Publishing & Lifecycle Integration

• 4.1 Commit the validated markdown/JSON payload to the registry-core/jobs Git repository following semantic versioning rules (v[Major].[Minor].[Patch]).
• 4.2 Merge the pull request upon receiving approval stamps from the Chief Architect and respective HRBP.
• 4.3 Trigger the webhook to propagate the live template to the Applicant Tracking System (ATS) and internal intranet portal.

---

5. Quality Assurance & Pro-Tips

5.1 Best Practices

• Objective Language: Focus on verifiable outputs rather than subjective traits (e.g., use "Analyzes quarterly financial statements using SQL" instead of "Detail-oriented financial wizard").
• Exhaustive Scope: Ensure physical and environmental requirements (e.g., remote, hybrid, travel percentage, lifting constraints) are explicitly documented to satisfy OSHA and ADA mandates.

5.2 Common Pitfalls

• Band Creep: Do not alter compensation bands within the template without a formal re-leveling audit by the Compensation Committee.
• Outdated Compliance Footers: Always utilize the automated schema linter to prevent legacy non-compliant legal boilerplate from appearing in new templates.

5.3 Metric Thresholds

• Review Cycle SLA: All template updates must pass through Phases 1–4 within a strict 10-business-day window.
• Linter Pass Rate: 100% syntax and regulatory check passing score required prior to merge execution.

---

6. Frequently Asked Questions (FAQ)

Q1: What should I do if a required technical stack updates faster than our annual review cadence?
A: Submit an emergency minor-version patch (e.g., v2.1.0 to v2.1.1) via the Git repository. Minor tool stack updates do not require a full Compensation or Legal review cycle, provided the core responsibilities and leveling bands remain unaltered.

Q2: How are remote vs. on-site location discrepancies handled within the template schema?
A: The template must utilize the dynamic location tag array (location_types: [remote, hybrid, on-site]). Selecting "hybrid" or "on-site" automatically injects the standardized geographic and physical workspace requirements module mandated by corporate facilities and legal.

---

End of Standard Operating Procedure.