Job Description Example Business

Standard Operating Procedure: Business-Critical Job Description Development

---

1. Executive Summary & Purpose

The purpose of this SOP is to standardize the creation of high-fidelity job descriptions (JDs) at Template Registry. A robust JD serves as the foundational artifact for talent acquisition, performance management, and organizational scaling. This document ensures all JDs are bias-mitigated, competency-driven, and aligned with departmental output requirements.

2. Scope & Prerequisites

• Scope: Applies to all full-time, part-time, and contract roles within Template Registry.
• Prerequisites:
  • Approved Headcount Authorization (HCA-01).
  • Access to the Internal Competency Framework (ICF) database.
  • Standardized JD Template (TPL-HR-001).
• Tools/Software: Greenhouse (ATS), Notion (Drafting), Gender Decoder (Bias Mitigation).

3. Roles & Responsibilities (RACI)

---

4. Step-by-Step Procedure

Phase I: Discovery & Competency Mapping

• Define the "Definition of Done" for the role (key KPIs for the first 6 months).
• Identify the top 3 core competencies required (Technical vs. Behavioral).
• Align current role requirements with the internal career progression ladder.

Phase II: Drafting the Artifact

• Execute the "Hook": Write a 3-sentence summary of the company mission and team impact.
• List "Essential Functions": Use outcome-based language (e.g., "Build X to achieve Y" vs. "Responsible for X").
• Define "Must-Haves" vs. "Nice-to-Haves": Limit "Must-Haves" to 5 items to avoid talent funnel restriction.
• Apply Bias Mitigation: Run text through a gender decoder; adjust language to be gender-neutral and inclusive.

Phase III: Review & Institutional Alignment

• Validate compensation band against current market data via Radford or equivalent.
• Submit to Legal/HR for compliance check (ADA/EEOC requirements).
• Secure final signatory approval from Department Lead.

---

5. Quality Assurance & Pro-Tips

Best Practices

• Outcome Focus: Always describe the problem the hire will solve, rather than just a list of daily tasks.
• Accessibility: Ensure all formatting is screen-reader friendly (bullet points, clear headers).
• The 80/20 Rule: If a candidate meets 80% of the "Must-Haves," they are qualified. Do not inflate requirements.

Common Pitfalls

• "Kitchen Sink" Syndrome: Including every possible duty; focus only on the mission-critical deliverables.
• Internal Jargon: Avoid company-specific acronyms that alienate external candidates.

Metric Thresholds

• Quality Metric: Time-to-fill should decrease by 15% when JDs strictly adhere to the competency mapping phase.

---

6. Frequently Asked Questions (FAQ)

Q: Should I include salary ranges in the description?

• A: Yes. Transparency is mandatory per company policy and legal compliance. It drastically improves the quality-to-applicant ratio.

Q: Can I recycle an old JD for a new role?

• A: Only if the role function has remained static for <6 months. Otherwise, perform a "Gap Analysis" to ensure technical requirements match the current state of the stack/market.

Q: How do I handle a role that doesn't fit a standard level?

• A: Contact the Chief Architect’s office. All custom roles must be mapped to an existing band before the JD is posted.

---

Authorized by: Julian Vance, Chief Architect, Template Registry