Job Description Template for HR

Standard Operating Procedure: Creation, Validation, and Deployment of Enterprise Job Descriptions

1. Document Control Block

• Document ID: SOP-HR-TR-402
• Effective Date: October 24, 2023
• Version: 3.2.0
• Review Cadence: Annual / Post-Organizational Restructuring
• Owner: Chief Architect, Template Registry & Global Head of Total Rewards

---

2. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the institutional engineering lifecycle for authoring, validating, and deploying standardized job descriptions (JDs) across Template Registry. The purpose is to eliminate role ambiguity, ensure strict compliance with federal and international labor standards (e.g., FLSA, EEOC, GDPR), establish equitable compensation bands, and provide an authoritative data schema for downstream Applicant Tracking Systems (ATS) and Human Resources Information Systems (HRIS).

---

3. Scope & Prerequisites

• Scope: Applies to all full-time, part-time, and contractual positions across all operational tiers (IC1 through Executive Leadership) within Template Registry.
• Prerequisites & Access Requirements:
  • Active enterprise license for Workday (HRIS) and Greenhouse (ATS).
  • Authorized access to the Template Registry Master Repository (GitHub Enterprise: /hr-governance/job-templates).
  • Completed training in Job Architecture & OE (Organizational Effectiveness) Methodology*.
• Required Tools: Markdown editors, YAML parsers, HRIS compliance validator CLI tool (tr-hr-cli).

---

4. Roles & Responsibilities (RACI Matrix)

---

5. Step-by-Step Procedure

Phase 1: Intake and Requirement Analysis

• 1.1 Initiate a Job Requisition Request via the HRIS portal, supplying organizational unit codes and budget allocation IDs.
• 1.2 Audit existing job taxonomy within the Template Registry repository to determine if an inherited or parent template exists (/templates/base/).
• 1.3 Conduct a scoping session with the Hiring Manager to define primary business objectives, core competencies, and critical success metrics for the initial 90 days.

Phase 2: Structural Drafting & YAML Frontmatter Integration

• 2.1 Clone the latest schema-compliant job description markdown template from the master repository.
• 2.2 Populate the YAML frontmatter block with mandatory metadata: job_code, flsa_status, compensation_band, department_id, and reporting_tier.
• 2.3 Draft the Position Summary focusing strictly on business outcomes rather than task lists (maximum 3 sentences).
• 2.4 Formulate the Essential Duties and Responsibilities section using active verbs, weighted by percentage of time spent (Total must equal 100%).
• 2.5 Define Required Qualifications (differentiating strictly between Minimum and Preferred criteria to mitigate adverse impact under EEOC guidelines).

Phase 3: Compliance & Compensation Validation

• 3.1 Run the local syntax and compliance validation script: tr-hr-cli validate --file path/to/job_description.md
• 3.2 Submit the drafted YAML/Markdown payload to Total Rewards for market-rate benchmarking and exemption-status validation (FLSA/International equivalents).
• 3.3 Submit the payload to Legal Counsel if the role involves handling classified IP, PII, or international cross-border deployment.
• 3.4 Address and resolve all validation warnings flagged by the tr-hr-cli build pipeline.

Phase 4: Sign-off, Publishing, and Integration

• 4.1 Obtain formal cryptographic or system-logged approvals from the Hiring Manager, HRBP, and Total Rewards Lead.
• 4.2 Merge the pull request (PR) into the main Template Registry branch, triggering the automated webhook to sync the record to Greenhouse and Workday.
• 4.3 Verify the live posting in the ATS, confirming formatting integrity, compensation transparency disclosures, and equal opportunity disclaimers.

---

6. Quality Assurance & Pro-Tips

Best Practices

• Behavioral Anchors: Ensure all competency requirements map directly to Template Registry’s core values matrix to maintain interview consistency.
• Inclusive Language: Utilize automated auditing tools to scrub gender-coded terminology from technical requirements.
• Granular Metrics: Clearly state output metrics (e.g., "maintain 99.9% uptime SLA") rather than vague inputs (e.g., "manage systems").

Common Pitfalls to Avoid

• Over-credentialing: Do not mandate advanced degrees unless strictly required by operational or regulatory constraints; this artificially restricts candidate flow.
• Stale Templates: Never copy-paste legacy JDs without running them through Phase 3 compliance checks; labor laws and market bands update continuously.

Metric Thresholds

• Time-to-Publish: Maximum 48 hours from intake to ATS synchronization.
• Compliance Error Rate: 0% tolerance for missing FLSA/Equal Pay disclosures in jurisdictions where mandated.

---

7. Frequently Asked Questions (FAQ)

Q1: What should I do if a role crosses two compensation bands or departments? A1: The role must be assigned to a primary home department based on financial budget ownership (>= 51% cost allocation). Dual-reporting lines must be documented in the YAML frontmatter under matrix_reporting, but compensation is anchored strictly to the primary band.

Q2: How are updates handled for active, filled positions when a job description changes? A2: Minor updates (typos, tool stack updates) can be pushed via a standard PR. Structural changes (adding supervisory responsibilities, altering compensation bands) require a formal re-evaluation by Total Rewards and an internal equity review before the updated template is deployed.