Job Description Template for WORD

Standard Operating Procedure: Deployment and Standardization of Job Description Templates within Microsoft Word

1. Document Control Block

• Document ID: SOP-TR-ENG-042
• Effective Date: October 24, 2023
• Version: 2.4.0
• Review Cadence: Annual
• Classification: Institutional Standard

---

2. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the engineering-grade protocol for creating, formatting, and distributing standardized Job Description Templates in Microsoft Word (.dotx) format across Template Registry. The purpose is to eliminate layout drift, enforce structural compliance with organizational metadata schemas, and guarantee accessibility (WCAG 2.1 AA) across all human resources and engineering requisition workflows.

---

3. Scope & Prerequisites

• Scope: Applies to all People Operations, Talent Acquisition, and Engineering Management personnel authoring or maintaining employment requisitions.
• Required Tools & Software:
  • Microsoft Word for Microsoft 365 (Version 2308 or later)
  • Template Registry Typography Pack (Inter / Fira Code families installed locally)
  • Adobe Acrobat Pro (for final PDF compliance verification)
• Prerequisites:
  • Valid organizational credentials for the Template Registry SharePoint asset repository.
  • Familiarity with Microsoft Word Styles pane and XML property mapping.

---

4. Roles & Responsibilities (RACI Matrix)

---

5. Step-by-Step Procedure

Phase 1: Environment Setup and Master Template Initialization

• Launch Microsoft Word and select File > New > Personal (or create a blank document).
• Immediately save the document via Ctrl+S as a Word Template (.dotx) named TR_Master_Job_Description_v2.4.dotx in the designated secure directory: C:\Users\[User]\Documents\Custom Office Templates\.
• Access the Developer tab (enable via File > Options > Customize Ribbon if hidden) and open the Document Property XML mapping pane to bind future metadata fields (e.g., Requisition ID, Department, Hiring Manager).

Phase 2: Structural Typography and Style Architecture

• Open the Styles Pane (Alt + Ctrl + Shift + S) and modify the base Normal style to Inter, 10.5 pt, #222222 font color, with 1.15 line spacing and 4 pt space after.
• Define Heading 1 as Inter Bold, 16 pt, #0A2540 (Primary Institutional Navy), with 12 pt space before and 4 pt space after. Check "Add to gallery" and "Automatically update."
• Define Heading 2 as Inter SemiBold, 12 pt, #425466 (Secondary Slate), with 8 pt space before and 2 pt space after.
• Configure custom style TR_Body_List for bulleted constraints using a strict 0.25-inch left indent.

Phase 3: Layout Engineering & Component Assembly

• Configure Page Setup margins to precisely 1.0 inch (72 pt) on all four sides.
• Insert a structural header frame containing the organizational logo (right-aligned, exact height 0.4 inches) and a dynamic Document Property field for the Requisition ID (left-aligned).
• Build the core modular sections using single-cell borderless tables for precise alignment of metadata blocks:
  • Role Overview & Mission Statement
  • Essential Responsibilities & Key Deliverables
  • Minimum Qualifications & Technical Prerequisites
  • Preferred Competencies & Cultural Add
• Implement a read-only footer containing dynamic page numbering (Page X of Y) and the ISO-compliant document ID (SOP-TR-ENG-042).

Phase 4: Validation, Accessibility Audit, and Deployment

• Run the built-in Microsoft Word Accessibility Checker via Review > Check Accessibility. Resolve all errors related to missing alt text, unassociated header rows in tables, and low contrast ratios.
• Protect the document structure by navigating to Review > Restrict Editing, checking "Allow only this type of editing in the document," setting it to "Filling in forms," and applying an institutional password.
• Export a master reference PDF to verify visual parity, then upload the finalized .dotx payload to the Template Registry cloud repository with version tag v2.4.0.

---

6. Quality Assurance & Pro-Tips

Best Practices

• Never use the spacebar for indentation: Always rely on paragraph formatting rules and native Word tab stops to prevent structural collapse when viewed on alternative devices.
• Style-Driven Design: Restrict manual formatting (bolding individual words, changing font sizes ad-hoc). All visual changes must flow directly from the global Style definitions.

Common Pitfalls

• Floating Images: Inserting images "In Line with Text" rather than leveraging fixed anchoring rules, which causes layout displacement on high-DPI displays.
• Orphaned Headings: Failing to check "Keep with next" on Heading 1 and Heading 2 styles, resulting in headers stranded at the bottom of pages.

Metric Thresholds

• Accessibility Compliance: 100% pass rate on WCAG 2.1 AA automated checks.
• File Footprint: Master .dotx file size must not exceed 250 KB (excluding embedded vector graphic assets).

---

7. Frequently Asked Questions

• Q: Why must we save the file as a .dotx rather than a standard .docx?
  • A: Saving as a .dotx (Word Template) ensures that users generate a new document derived from the master template rather than accidentally overwriting the baseline engineering structure.
• Q: How do I fix broken table borders when pasting content from external web forms?
  • A: Highlight the affected table cells, navigate to Table Design > Borders, and reapply the institutional table grid profile (#E0E6ED, 0.5 pt solid line). Alternatively, use Ctrl + Shift + V to paste text-only values.