Job Description Template Notion

SOP-HR-042: Standardized Job Description Lifecycle Management

1. Executive Summary & Purpose

This SOP defines the institutional protocol for the creation, versioning, and distribution of Job Descriptions (JDs) via the Notion framework. The objective is to eliminate linguistic variance, ensure compliance with labor regulations, and maintain a high-fidelity "Single Source of Truth" (SSOT) for organizational role architecture.

2. Scope & Prerequisites

• Scope: Applies to all departments within Template Registry.
• Required Tools:
  • Notion (Enterprise Workspace access required).
  • Standardized Template ID: TR-HR-MASTER-JD-001.
• Prerequisites: Hiring Manager must have a finalized Role Assessment Form (RAF) prior to template deployment.

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase I: Initiation & Scoping

• Verify the existence of an approved headcount requisition.
• Duplicate the master template TR-HR-MASTER-JD-001 into the "Drafts" workspace.
• Populate the "Header Data" block: Job Title, FLSA Status, Salary Band, and Department.

Phase II: Content Architecture

• Role Summary: Draft a 3-sentence elevator pitch emphasizing the strategic value of the role.
• Core Competencies: Map 5-7 core responsibilities to specific departmental KPIs.
• Qualifications: Differentiate between "Required" (Hard blockers) and "Preferred" (Optional/Bonus) criteria.
• EEO Statement: Ensure the automated Notion database property includes the current, legally vetted EEO boilerplate.

Phase III: Review & Version Control

• Set Notion page status to "In Review."
• Trigger an automated notification to HR and Legal using the @mention function.
• Finalize the version history via the Notion "Page History" export prior to promoting to "Approved."

5. Quality Assurance & Pro-Tips

• Metric Thresholds:
  • Diversity Index score must be > 0.8 (using integrated AI analysis tools).
  • Readability score must fall between Grade 10-12.
• Pro-Tip (Database Linking): Use Notion "Relation" properties to link the JD directly to the Candidate Pipeline database. This ensures candidates are auto-tagged based on the specific job ID.
• Common Pitfall: Avoiding the overuse of industry jargon. Stick to standard nomenclature to prevent parsing errors in ATS (Applicant Tracking Systems).

6. Frequently Asked Questions

Q: Can I modify the structure of the master template for specialized engineering roles? A: No. Structural modifications compromise reporting integrity. Use the "Expanded Technical Annex" block if additional hardware/stack requirements are needed, but do not alter the parent schema.

Q: How do I handle version updates once a job is live? A: Use the "Archive" property in Notion. Create a new page with the updated content, redirect the old page link to the new one, and mark the previous version as Status: Deprecated.

Authorized by: Julian Vance Chief Architect, Template Registry