Job Description Template Ms WORD

Standard Operating Procedure: Creation, Formatting, and Governance of Institutional Job Description Templates (MS Word)

Document ID: SOP-TR-ENG-042
Effective Date: October 24, 2023
Version: 3.1.0
Review Cadence: Annual
Classification: Internal Operational Standard / Template Registry Architecture

---

1. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the engineering specifications, document architecture, and procedural workflows for authoring, maintaining, and deploying standardized Job Description (JD) templates in Microsoft Word (.docx format) across Template Registry and subsidiary entities.

The purpose is to eliminate typographic inconsistency, enforce institutional typography and metadata standards, ensure compliance with global employment regulations (ADA, EEOC, GDPR), and optimize document parsability for modern Applicant Tracking Systems (ATS).

---

2. Scope & Prerequisites

2.1 Scope

This standard applies to all Human Resources personnel, Hiring Managers, and Technical Writers tasked with creating or modifying employment requisitions and role charters utilizing the Microsoft Word template infrastructure.

2.2 Prerequisites & Tools

• Software: Microsoft Office 365 Word (Desktop Client, v2304 or later). Web-based Word is strictly prohibited for master template authoring due to layout engine disparities.
• Asset Library: Access to the Template Registry Design System asset repository (\\assets.templateregistry.internal\branding\typography).
• Fonts Required: Aptos and Aptos Display (Primary), Calibri (Legacy Fallback).
• Permissions: Level 3 write access to the central document repository.

---

3. Roles & Responsibilities

---

4. Step-by-Step Procedure

Phase 1: Document Initialization & Grid Setup

• Launch Microsoft Word and open a blank document (do not use third-party templates).
• Set page margins uniformly to 1.0 inch (Top, Bottom, Left, Right) via Layout > Margins > Normal.
• Configure document properties via File > Info > Properties: set Title to [Department]_[Role Title]_JD_v3, Author to Template Registry HR Ops, and Company to Template Registry.
• Unlink the Header and Footer from previous sections if building a multi-page operational document.

Phase 2: Typography & Style Hierarchy Configuration

• Open the Styles Pane (Alt + Ctrl + Shift + S). Modify or create styles strictly adhering to the following parameters:
  • Title Style: Aptos Display, 24pt, Bold, Color: Deep Navy (#002060), Spacing: 0pt before, 12pt after.
  • Heading 1: Aptos Display, 16pt, Bold, Color: Deep Navy (#002060), Spacing: 12pt before, 4pt after, "Keep with next" enabled.
  • Heading 2: Aptos, 13pt, Bold, Color: Slate Grey (#595959), Spacing: 6pt before, 2pt after, "Keep with next" enabled.
  • Body Text: Aptos, 11pt, Regular, Color: Charcoal (#262626), Line Spacing: 1.15x, Space After: 4pt.
• Save the customized styles to the local template profile (Normal.dotm or dedicated .dotx file).

Phase 3: Structural Content Assembly

Insert and populate the mandatory institutional sections utilizing explicit tables and bullet lists:

• Section 1: Header Block (Metadata Table)
  • Insert a 2-column, 4-row borderless table for Position Title, Department, Reports To, and FLSA Classification.
• Section 2: Organizational Overview & Purpose
  • Insert Heading 1. Draft a concise 3-4 sentence narrative defining the role's mission within Template Registry.
• Section 3: Essential Duties & Responsibilities
  • Insert Heading 1. Utilize bulleted lists. Ensure action verbs are used in the present tense (e.g., Architects, Deploys, Analyzes).
• Section 4: Qualifications & Competencies
  • Subdivide using Heading 2 into "Required Qualifications" and "Preferred Qualifications".
• Section 5: Working Conditions & Physical Demands
  • Detail environment parameters, travel requirements, and ergonomic thresholds to maintain ADA compliance.

Phase 4: Accessibility & ATS Optimization Auditing

• Run the built-in accessibility checker via File > Info > Check for Issues > Check Accessibility. Resolve all errors and warnings.
• Ensure all structural headers utilize native Word Heading styles rather than manual font sizing and bolding (critical for screen readers and ATS layout ingestion).
• Verify that no text boxes are utilized for primary body content, as non-floating frames can obstruct sequential parsing engines.
• Export a test copy to PDF (.pdf) to verify visual fidelity and font embedding integrity.

---

5. Quality Assurance & Pro-Tips

Best Practices

• Use Content Controls: For fields requiring repetitive input (e.g., Salary Grade, Location), deploy Developer tab Content Controls (Plain Text or Drop-Down List) to restrict unauthorized structural modifications.
• Explicit Table Widths: Always set table column widths explicitly via table properties rather than dragging visual boundaries, preventing layout collapse across different screen resolutions and Word versions.

Common Pitfalls

• Do not utilize hard returns (multiple Enter keystrokes) to manage vertical spacing; always configure Paragraph Spacing ("Space Before" / "Space After").
• Do not embed raster images of organizational charts; use native Word SmartArt objects for vector scalability.

Metric Thresholds

• ATS Parse Rate: $\ge 98%$ structural data extraction accuracy.
• Accessibility Score: 100% compliance pass rate on Microsoft Accessibility Checker.

---

6. Frequently Asked Questions (FAQ)

Q: Can I use custom fonts downloaded from external foundries to match a specific team's branding?
A: No. To ensure multi-system rendering fidelity and regulatory compliance, only institutional standard fonts (Aptos, Aptos Display, and Calibri) are authorized for production documents within Template Registry.

Q: Why does the ATS fail to parse my bulleted lists correctly?
A: This typically occurs when authors use manual symbols (e.g., hyphens, dashes, or custom wingdings) instead of native Word bullet lists. Always utilize the native Bullet Library within the Home tab to ensure proper Unicode tag generation.