Job Description Examples for Administrative Assistant

Standard Operating Procedure: Authoring Institutional-Grade Administrative Assistant Job Descriptions

Document ID: SOP-TR-HR-408
Effective Date: October 24, 2023
Version: 3.2
Review Cadence: Annual
Owner: Julian Vance, Chief Architect, Template Registry

---

1. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the mandatory engineering protocol for authoring, reviewing, and publishing administrative assistant job descriptions within the Template Registry ecosystem. The objective is to eliminate role ambiguity, ensure strict alignment with organizational competency frameworks, optimize applicant tracking system (ATS) parsing performance, and establish measurable performance metrics prior to requisition approval.

---

2. Scope & Prerequisites

Scope

This procedure applies to all hiring managers, human resources business partners (HRBPs), and technical recruiters drafting job descriptions for Administrative Assistant roles across all operational tiers (Associate, Senior, and Executive).

Prerequisites & Required Tools

• Access to the Template Registry HR Information System (HRIS) and ATS module.
• Approved departmental budget requisition ID.
• Standardized Template Registry Competency Matrix (TR-CM-v4).
• Markdown editor or internal rich-text requisition builder.

---

3. Roles & Responsibilities (RACI Matrix)

• Responsible (R): Drafts the initial job description utilizing approved templates.
• Accountable (A): Validates compliance, compensation bands, and final sign-off.
• Consulted (C): Provides technical accuracy reviews and structural governance checks.
• Informed (I): Receives the final published requisition for sourcing execution.

---

4. Step-by-Step Procedure

Phase 1: Structural Setup & Role Tiering

• 1.1 Access the HRIS and instantiate a new requisition using the baseline "Administrative Assistant" template.
• 1.2 Determine the operational tier based on scope of support:
  • Tier I: General department support, scheduling, and data entry.
  • Tier II: Cross-functional project coordination, advanced document management, and budget tracking.
  • Tier III (Executive): C-suite calendar management, confidential stakeholder communications, and travel logistics.
• 1.3 Verify that the compensation band matches the regional labor market benchmark stored in TR-COMP-DB.

Phase 2: Core Competency & Task Definition

• 2.1 Author the Primary Objective Summary in exactly two sentences, defining the role's immediate impact on operational velocity.
• 2.2 Populate the Essential Duties and Responsibilities using active-voice verbs (e.g., orchestrate, reconcile, compile).
• 2.3 Define quantifiable daily metrics (e.g., "Manage dynamic calendars for up to 12 executives with zero scheduling conflicts").
• 2.4 Explicitly list software proficiencies required, categorizing them into Mandatory (e.g., Microsoft 365, Google Workspace, Concur) and Preferred (e.g., Jira, Salesforce, Tableau).

Phase 3: Qualification Matrix & ATS Optimization

• 3.1 Delineate Minimum Qualifications (e.g., High School Diploma + 3 years administrative experience, or equivalent associate degree).
• 3.2 Establish Preferred Qualifications to narrow high-volume candidate funnels.
• 3.3 Ensure the inclusion of high-density keyword clusters to maximize ATS parsing efficiency without engaging in keyword stuffing.
• 3.4 Append the mandatory Template Registry Equal Opportunity Employer (EOE) and accommodation clauses.

Phase 4: Quality Gate & Sign-Off

• 4.1 Run the drafted text through the internal bias-detection linguistic scanner.
• 4.2 Submit the requisition packet to the HRBP for compliance verification.
• 4.3 Obtain final authorization from the department head before routing to Talent Acquisition for active sourcing.

---

5. Quality Assurance & Pro-Tips

Best Practices

• Precision over Generality: Avoid vague catch-alls like "other duties as assigned." Every responsibility listed should account for at least 5% of the role's actual weekly bandwidth.
• Outcome-Oriented Framing: Frame tasks by their business outcome (e.g., "Prepare monthly expense reports to ensure compliance with internal audit standards" rather than just "Do expense reports").

Common Pitfalls to Avoid

• Over-credentialing: Do not require a Bachelor's degree for Tier I or Tier II operational roles unless specific regulatory compliance dictates it, as this artificially depresses qualified applicant flow.
• Outdated Tool Stacks: Ensure software requirements reflect current enterprise standards rather than legacy systems.

Metric Thresholds

• Time-to-Fill Target: Requisitions utilizing this standardized SOP must achieve an initial candidate slate presentation within 10 business days.
• Conversion Rate: Qualified-to-interview pass rate must meet or exceed 15% to validate job description clarity.

---

6. Frequently Asked Questions (FAQ)

Q1: What should I do if an administrative role requires support across multiple distinct departments?
A: Utilize the Tier II or Tier III matrix framework, explicitly defining the percentage allocation of time dedicated to each department in the operational scope section to prevent expectation drift.

Q2: How do I handle sudden changes to required software competencies mid-recruitment?
A: Do not edit an active requisition in flight if candidates are already in late-stage pipelines. If the change is business-critical, close the requisition, update the SOP template via change control, and re-issue a revised requisition ID.