Job Description Template Quality Control

SOP: Job Description Template Quality Control (JD-TQC)

---

1. Document Control Block

---

2. Executive Summary & Purpose

This document mandates the standardization, validation, and archival process for Job Description (JD) templates within the Template Registry. The purpose is to ensure all recruitment assets satisfy institutional equity standards, mitigate legal liability, and maintain internal alignment with organizational competency frameworks.

---

3. Scope & Prerequisites

• Scope: Applies to all master templates stored in the Central Repository.
• Prerequisites:
  • Access to the Template Registry Version Control System (VCS).
  • Approved Legal/HR compliance checklist.
  • Software: Jira (Tracking), GitHub (Template Repository), MS Word/G-Docs (Review Layer).
  • PPE: N/A (Digital environment).

---

4. Roles & Responsibilities (RACI Matrix)

---

5. Step-by-Step Procedure

Phase 1: Intake & Versioning

• Create a feature branch in the VCS specifically for the JD template update.
• Verify the current document ID matches the repository index.
• Pull the most recent approved master template.

Phase 2: Structural Audit

• Validate mandatory sections (Job Summary, Core Competencies, Legal Disclaimers).
• Ensure formatting consistency (font standards, header hierarchy, bullet-point indentation).
• Verify placeholder visibility (ensure all [BRACKETED_FIELDS] are actionable).

Phase 3: Compliance & Bias Mitigation

• Run the text through the Gender Decoder/Bias analysis tool.
• Confirm adherence to regional labor laws (ADA, EEOC, local mandates).
• Validate salary transparency requirements against current state/provincial statutes.

Phase 4: Final Approval & Commit

• Secure sign-off from the HR Compliance Officer via Jira ticket.
• Merge feature branch into the production master branch.
• Update the Document Control Block with the new Version/Date.

---

6. Quality Assurance & Pro-Tips

• Metric Thresholds:
  • Bias Score: Must remain within the "Neutral" range for all incoming edits.
  • Field Completeness: 100% of defined mandatory fields must be validated.
• Pro-Tips:
  • The "Rule of Three": Every change must be audited by at least three sets of eyes (Editor, Compliance, Architect) before push.
  • Automation: Utilize regex-based scripts to scan for illegal terminology (e.g., age-coded language like "digital native") before manual review.
• Common Pitfalls: Do not modify the underlying metadata schema without notifying the Lead Architect; this breaks automated downstream population.

---

7. Frequently Asked Questions

Q: Can I add non-standard sections to a template for specific senior roles? A: No. Modifications to the structural hierarchy require a formal change request submitted through the Architecture Review Board. Use the "Supplemental Info" field instead.

Q: What happens if a compliance breach is found in a live template? A: Immediate rollback to the previous v-minus-1 stable state. Initiate a formal Post-Mortem within 24 hours of the discovery to prevent recurrence.

---

End of Document. Authorized by Julian Vance, Chief Architect.