Administrative Assistant Job Description Template

In plain language: States the official job title, the department the role sits within, and the direct supervisor or manager the employee reports to.

Common mistake: Using a generic title like 'Admin' without specifying the department or level. This creates HRIS mismatches and makes compensation benchmarking unreliable.

In plain language: A 3–5 sentence overview of the role's purpose, primary function, and how it supports the organization — the first thing a candidate reads.

Common mistake: Writing the summary as a vague tagline ('a dynamic, multi-tasking professional') rather than a specific description of organizational function. Vague summaries attract mismatched applicants and weaken the document's value as a performance baseline.

In plain language: A numbered or bulleted list of the core tasks the employee is expected to perform, written as active-voice statements beginning with action verbs.

Common mistake: Including responsibilities the role will 'occasionally assist with' alongside true essential functions without distinguishing them. Mixing essential and marginal duties complicates ADA accommodation analysis and can expose the employer to discrimination claims.

In plain language: The minimum education, experience, certifications, and technical skills a candidate must possess to be considered for the role.

Common mistake: Setting degree requirements that are not genuinely necessary for the role. Several US jurisdictions and the EEOC have flagged blanket degree requirements for admin roles as potentially discriminatory when not job-relevant.

In plain language: Additional skills, certifications, or experience that would make a candidate stronger but are not eliminatory screening criteria.

Common mistake: Treating preferred qualifications as hard filters during screening. Preferred criteria are not pass/fail — applying them as such undermines the stated distinction and may narrow the candidate pool unlawfully.

In plain language: States the salary range or hourly rate, pay frequency, and an overview of benefits the employee is eligible for — referenced by category rather than plan specifics.

Common mistake: Omitting the salary range entirely. Pay transparency laws in California, Colorado, New York, and Washington now require salary ranges in job postings, and omitting them in the job description creates compliance risk and reduces application volume.

In plain language: Specifies whether the position is full-time or part-time, the standard hours and days, whether overtime is expected, and the physical work location.

Common mistake: Not stating the FLSA exemption status (exempt vs. non-exempt). This omission leads to payroll errors and overtime disputes, particularly for administrative roles that often fall in the gray zone of the administrative exemption.

In plain language: Describes any physical demands (sitting, lifting, typing) and technology requirements (hardware, software, internet speed) necessary to perform the essential functions.

Common mistake: Skipping this section entirely. Without documented physical requirements, the employer has no baseline for evaluating accommodation requests under the ADA or equivalent statutes, and may be unprepared for a disability-related dispute.

In plain language: Affirms the employer's commitment to non-discriminatory hiring and invites candidates with disabilities to request reasonable accommodations.

Common mistake: Using a boilerplate EEO statement that omits recently protected categories in the applicable jurisdiction — such as sexual orientation and gender identity under the EEOC's post-Bostock interpretation. Outdated language creates legal exposure.

In plain language: A signed confirmation by the employee that they have read, understood, and agree to the duties and requirements described — creating a documented record of mutual understanding.

Common mistake: Treating the signature block as optional for existing employees during a job description update. An unsigned update has no evidentiary weight if a performance dispute or accommodation claim arises later.

An administrative assistant job description is a formal written document that defines the duties, qualifications, compensation, reporting structure, and employment conditions for an administrative support role. It serves as a hiring tool, a performance baseline, a legal record of agreed expectations, and — when signed — a foundational document in the employee's personnel file. A well-drafted job description also supports FLSA classification decisions and ADA accommodation analysis.

At minimum: job title and department, reporting line, a position summary, essential duties listed as active-voice statements, required and preferred qualifications, compensation range and FLSA status, employment type and schedule, physical and technical requirements, an EEO statement, and a signature block. Missing the FLSA classification or physical requirements sections are the two most common gaps that create downstream legal exposure.

Most administrative assistants are non-exempt and entitled to overtime pay at 1.5× their regular rate for hours over 40 per week. To qualify for the FLSA's administrative exemption, an employee must earn at least $684 per week on a salary basis and exercise genuine discretion and independent judgment on matters of significance — a threshold most general admin roles do not meet. Misclassifying an admin as exempt exposes the employer to retroactive overtime liability of up to three years.

While no federal statute specifically requires a signed job description, obtaining a signature is strongly recommended. A signed document creates a documented record that the employee received, read, and understood the role's expectations and physical requirements — which is the baseline evidence needed in a performance dispute, an ADA accommodation request, or a wrongful termination claim. Execute the signature block before or on the employee's first day of work.

Yes, but you must adjust the physical requirements, technical requirements, and location fields accordingly. For remote roles, document internet speed and equipment requirements, specify which software platforms the employee must use, and note whether on-site attendance is required for any regular activities. Some jurisdictions — including California and Canada — have specific remote work disclosure obligations that should be reflected in the job description or an accompanying remote work addendum.

A job description defines the role — its duties, qualifications, and general conditions. An employment contract is the binding legal agreement that governs the employment relationship, including compensation, IP assignment, confidentiality, termination, and severance. The job description is typically attached to or referenced in the employment contract. Neither document is a substitute for the other — both should be executed before the employee's start date.

Yes. California (SB 1162), Colorado (EPEWA), New York City (Int. 1208), Washington State, and British Columbia all require employers to disclose salary ranges in job postings, and some extend this obligation to written job descriptions provided to candidates or employees. The FTC and NLRB have also signaled broader pay transparency enforcement. Omitting a salary range in jurisdictions with active disclosure laws can result in fines and reputational damage.

Review every job description annually or whenever the role materially changes — new software tools, a shift from on-site to hybrid, a change in reporting structure, or a significant expansion of duties. Each material update should be re-executed with a fresh employee signature and dated in the personnel file. An outdated job description used in a performance-management process is a significant credibility risk in employment disputes.

Avoid age-coded phrases like 'recent graduate,' 'young and energetic,' or 'digital native' — these signal age bias under the ADEA. Do not use gender-coded language (e.g., 'manpower,' 'he/she') or phrases that imply a preference for a specific national origin or physical appearance. Avoid blanket physical requirements ('must be able to lift heavy objects') without specifying the actual threshold, and never include salary history inquiries in jurisdictions where they are banned.