Job Description Template Microsoft WORD

Standard Operating Procedure: Standardized Job Description Lifecycle

Document ID: TR-HR-JD-001
Effective Date: 2023-10-27
Version: 1.0.0
Review Cadence: Annual

1. Executive Summary & Purpose

This procedure defines the institutional requirements for authoring, formatting, and deploying Job Description (JD) templates within Microsoft Word. The purpose is to ensure brand consistency, legal compliance, and structural uniformity across all human capital procurement efforts at Template Registry.

2. Scope & Prerequisites

• Scope: Applies to all departments initiating a new hire requisition.
• Software Requirements: Microsoft Word (Version 2019/365 Desktop Client).
• Prerequisites:
  • Approved Job Requisition Form (JRF).
  • Access to the "TR_Global_Corporate_Style_Guide.dotx" template file.
  • Minimum technical competency in MS Word Styles and Table formatting.

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase I: Environment Setup

• Launch Microsoft Word.
• Navigate to File > New > Personal and select the TR_Global_Corporate_Style_Guide.dotx.
• Enable the Navigation Pane (View > Navigation Pane) to monitor document hierarchy.

Phase II: Structural Assembly

• Header Input: Populate the metadata block (Role Title, Department, Reports to).
• Role Summary: Draft 3–5 sentences defining the business necessity and core impact of the role.
• Primary Responsibilities: Use bulleted list formatting. Limit to 8–10 high-impact items.
• Qualification Matrix: Separate into "Required" (Must-haves) and "Preferred" (Nice-to-haves) to minimize applicant pool noise.
• Legal Disclosures: Append the mandatory EEO/Diversity statement as per the template’s footer.

Phase III: Formatting Validation

• Apply Heading 1 to section titles for accessibility tagging.
• Ensure all tables have a Table Header row with consistent shading (Hex: #F2F2F2).
• Perform a final check for "Track Changes" (Review > Tracking) to ensure no editorial comments remain.
• Export to PDF via File > Export > Create PDF for final distribution.

5. Quality Assurance & Pro-Tips

• Metric Threshold: Ensure the Reading Ease score (Word/Editor tool) is ≥ 60 for optimal clarity.
• Pro-Tip (Styles): Never use manual formatting (bolding/font sizing). Always modify the assigned Style (e.g., "Normal" or "List Paragraph") to maintain global document integrity.
• Common Pitfall: Over-reliance on gendered language. Use an automated gender-decoder tool before final submission to avoid unconscious bias in the candidate funnel.

6. Frequently Asked Questions (FAQ)

Q: Should I save the JD as a .doc or .docx?
A: Always use .docx. The legacy .doc format does not support modern accessibility tags required for screen readers.

Q: Can I embed graphics or company logos?
A: Only the official header/footer logo is permitted. Embedding additional images increases file size and often causes layout corruption during automated parsing by Applicant Tracking Systems (ATS).

Q: How do I handle document version control?
A: Use the v[Major].[Minor] naming convention in the file footer (e.g., JD_Senior_Architect_v1.2). Never include "Final" or "Draft" in the filename.

Authorized by: Julian Vance, Chief Architect