Office Clerk_General Job Description Template

In plain language: States the official job title, the department the role sits within, the FLSA classification (exempt or non-exempt), and the employment type (full-time, part-time, or temporary).

Common mistake: Classifying a general office clerk as exempt to avoid overtime obligations. Most clerical roles do not meet the FLSA duties or salary-level tests for exemption, and misclassification triggers back-pay liability plus penalties.

In plain language: A 3–5 sentence overview of the role's primary purpose, day-to-day work environment, and general contribution to the department or organization.

Common mistake: Writing a vague summary that could apply to any administrative role. A generic summary weakens the document's usefulness as a performance-management tool and attracts unqualified applicants.

In plain language: A detailed, prioritized list of the core tasks the clerk is expected to perform regularly — formatted to distinguish essential functions from marginal duties for ADA compliance purposes.

Common mistake: Listing duties without flagging which are essential functions. Under the ADA and equivalent statutes, employers must be able to demonstrate which duties are essential when evaluating accommodation requests — unlabeled lists create legal ambiguity.

In plain language: Specifies the minimum education, experience, and skills a candidate must possess to be considered — these criteria must be directly job-related and applied consistently to avoid discrimination claims.

Common mistake: Including education or experience requirements that exceed what the job actually demands — for example, requiring a bachelor's degree for a role that only needs a diploma. Inflated requirements can constitute disparate-impact discrimination under equal employment opportunity law.

In plain language: Lists additional credentials, software knowledge, or experience that would make a candidate more competitive but are not mandatory for the role.

Common mistake: Treating preferred qualifications as screening criteria during hiring. Once a candidate meets all required qualifications, preferred items should serve only as tiebreakers — using them as mandatory filters invalidates the distinction and can create discrimination exposure.

In plain language: Identifies the direct supervisor, any dotted-line reporting relationships, and whether the clerk exercises supervisory authority over other staff or volunteers.

Common mistake: Leaving the reporting structure vague or listing 'various supervisors.' Unclear authority chains cause task-prioritization conflicts, complicate performance reviews, and create liability when instructions from competing supervisors lead to errors.

In plain language: States the hourly wage or salary band, standard working hours, overtime eligibility, and whether the role is on-site, hybrid, or remote.

Common mistake: Omitting the compensation band from the job description in jurisdictions that legally require pay transparency (Colorado, New York, California, and others). Non-compliance attracts regulatory complaints and fines.

In plain language: Describes the physical demands of the role — lifting limits, extended sitting, screen time — and any environmental conditions relevant to the position.

Common mistake: Omitting physical requirements entirely for desk-based roles. Even sedentary jobs involve physical demands — prolonged sitting, repetitive keyboard use — that must be documented to properly evaluate accommodation requests under disability law.

In plain language: A signature block confirming the employee has received, read, and understood the job description — and acknowledges it is not a contract of employment unless incorporated into one.

Common mistake: Including language suggesting the job description constitutes a binding contract of employment. Courts have used broadly worded job-description acknowledgments as evidence of implied contracts, limiting an employer's ability to terminate at will.

An office clerk general job description is a formal document that defines the title, duties, qualifications, reporting structure, compensation range, and working conditions for a general clerical support role. It serves multiple purposes: attracting qualified candidates, setting performance expectations, supporting ADA accommodation evaluations, and anchoring disciplinary or termination decisions to documented role requirements.

A job description is generally not a contract of employment on its own, but it can become one if it contains promissory language or is incorporated by reference into an employment agreement. To prevent unintended contract formation, include a clear disclaimer in the acknowledgment section stating that the document does not constitute a contract and that employment remains at-will or subject to a separate employment agreement.

Required qualifications are the minimum criteria a candidate must meet to be considered for the role — they must be directly tied to essential job functions. Preferred qualifications are additional credentials or skills that would enhance performance but are not mandatory. The distinction matters legally: applying preferred qualifications as screening criteria during hiring blurs the line and can create discrimination exposure if those criteria have a disparate impact on protected groups.

It depends on jurisdiction. Colorado, New York, California, Washington, and several municipalities now legally require salary or hourly rate disclosure in job postings. Even where not mandated, including a compensation band improves candidate quality, reduces negotiation time, and supports internal pay-equity practices. Check the specific requirements of every location where the posting will be published.

Under the Americans with Disabilities Act — and equivalent statutes in Canada, the UK, and the EU — employers must determine whether a qualified individual with a disability can perform a role's essential functions, with or without reasonable accommodation. A well-drafted job description that explicitly labels essential versus marginal functions provides the evidentiary foundation for this analysis and strengthens the employer's position in any accommodation dispute.

Yes. An employee acknowledgment signature confirms the individual received and understood their role expectations — a record that is valuable during performance management, disciplinary proceedings, or litigation. The signature should be obtained before or on the first day of employment. The acknowledgment should also state that the document is not a contract of employment.

Yes, a single description can apply to all incumbents in the same role title, provided their duties and qualifications are substantively identical. If two employees with the same title perform meaningfully different duties — different departments, different supervisors, or materially different responsibilities — they should have separate descriptions to accurately reflect their roles and support fair performance evaluation.

Review the description any time the role's duties change materially — when new software is adopted, responsibilities are reassigned, or the organizational structure changes. At minimum, conduct an annual review aligned with the performance-appraisal cycle. An outdated description can undermine discipline or termination decisions if the employee's actual duties no longer match what is documented.

A legally defensible job description clearly labels essential functions, ties required qualifications directly to those functions, uses objective language for physical requirements, includes a pay transparency disclosure where required, and carries an acknowledgment signed by the employee before or on day one. It avoids inflated requirements, promissory language, and vague duty statements that cannot be used as performance-management benchmarks.