Project Coordinator Job Description Template

In plain language: Establishes the exact job title, the department the role sits within, and the employment classification (full-time, part-time, contract).

Common mistake: Using a generic title like 'Coordinator' without specifying level or department — this creates ambiguity during performance reviews and compensation benchmarking.

In plain language: A 3–5 sentence overview of the role's purpose, how it supports the broader team or organization, and the scope of projects involved.

Common mistake: Writing a position summary that duplicates the duties list verbatim — the summary should explain why the role exists, not itemize every task.

In plain language: The primary functions the employee is hired to perform, listed with enough specificity to support performance management and ADA accommodation assessments.

Common mistake: Listing more than 10–12 duties without differentiating essential from marginal functions — courts and HR tribunals apply different standards to each when assessing accommodation or termination for cause.

In plain language: Identifies the direct supervisor, any dotted-line relationships, and the cross-functional teams or stakeholders the coordinator routinely works with.

Common mistake: Omitting dotted-line or matrix reporting relationships — coordinators often support multiple project managers, and undefined authority lines cause conflict and accountability gaps.

In plain language: The minimum education, experience, certifications, and skills necessary to perform the role — these are the threshold criteria used in hiring and, if needed, termination for cause.

Common mistake: Setting degree requirements that are not demonstrably linked to job performance — this creates disparate impact exposure under equal employment opportunity laws in the US, UK, and EU.

In plain language: The measurable outcomes and quality standards against which the coordinator's performance will be evaluated, typically reviewed at 30/60/90 days and annually.

Common mistake: Omitting performance standards entirely and relying on subjective manager assessment — without defined KPIs, disciplinary action or termination for performance reasons is harder to defend.

In plain language: States the pay band or salary range, FLSA classification (exempt or non-exempt), payment frequency, and a reference to the applicable benefits program.

Common mistake: Publishing a salary range that conflicts with the internal job grade — this creates pay equity exposure and undermines trust when the offer does not align with the posted range.

In plain language: Describes the work environment (office, remote, hybrid, field), hours, travel expectations, and any physical demands required to perform essential functions.

Common mistake: Omitting physical requirements for field or site-based coordinator roles — this creates ADA and duty-to-accommodate problems when a physical limitation arises post-hire.

In plain language: Establishes the coordinator's obligation to protect project data, client information, and proprietary business information encountered during the course of the role.

Common mistake: Referencing a confidentiality policy that employees have never been given access to — courts have found that obligations tied to unattached, unseen documents are unenforceable.

In plain language: A signed declaration by both the employer and employee confirming the employee has received, read, and accepted the job description as a record of their role.

Common mistake: Omitting the disclaimer that the job description is not a contract — without it, detailed duties and performance standards can be interpreted as contractual guarantees that limit the employer's ability to adjust the role.

A project coordinator job description is a formal document that defines the duties, qualifications, reporting structure, performance standards, and employment conditions of a project coordinator role. It serves as the authoritative record of what the position requires and is used in hiring, onboarding, performance management, and — when incorporated into an employment contract — as a legally referenced scope-of-work document.

A project coordinator supports the planning, execution, and monitoring of projects by maintaining schedules and documentation, coordinating meetings and communications, tracking action items and deliverables, and preparing status reports for project managers or leadership. The role differs from a project manager in that it typically operates under supervision rather than independently owning project outcomes.

Typical requirements include a bachelor's degree in business, communications, or a related field (or equivalent experience), one to three years of coordination or administrative experience, and proficiency in project management tools such as Asana, Jira, or MS Project. Certifications like CAPM or a PMP foundation credential are commonly listed as preferred. Only include qualifications demonstrably linked to essential functions to avoid disparate impact exposure.

A job description is generally not a binding employment contract on its own, but it can create legal obligations when incorporated by reference into an employment agreement or offer letter. Courts in the US, Canada, and the UK have occasionally treated detailed duty lists and performance standards as implied contractual terms. Including a clear disclaimer that the document is not a contract and that employment terms are governed by a separate agreement is the standard way to prevent this.

Several US states — including Colorado, New York, California, and Washington — and the EU Pay Transparency Directive require employers to disclose a salary range in job postings. Even where disclosure is not mandated, publishing a range reduces negotiation friction and improves candidate quality. The range stated in the job description must match the approved internal pay band for the role to avoid pay equity and transparency law violations.

A project manager job description defines a role that independently owns project outcomes — setting scope, budget, and stakeholder strategy. A project coordinator description defines a supporting role that maintains documentation, tracks tasks, and facilitates communication under a manager's direction. The coordinator description typically requires one to three years of experience versus five or more for a manager, and the compensation band is correspondingly lower.

Review the job description annually, whenever the role's scope changes materially, or before opening a new recruitment cycle. Outdated descriptions with obsolete tools, superseded reporting lines, or stale compensation ranges create legal exposure in pay transparency jurisdictions and erode trust with both candidates and incumbents. File every revised version with the date of update in the employee's personnel record.

When a job description is incorporated by reference into an employment contract, the duties, qualifications, and performance standards it contains become contractual obligations. Materially changing those duties without the employee's written consent can constitute a unilateral variation of contract — which in the UK and Canada may give rise to a constructive dismissal claim. Ensure the employment contract includes language permitting reasonable duty adjustments and have the employee acknowledge any significant updates in writing.

For most standard domestic hires, a well-structured template is sufficient. Consider legal review when the description will be incorporated by reference into an employment contract, when the role involves access to sensitive data subject to GDPR or CCPA, when the employer operates in multiple jurisdictions with different pay transparency or accommodation requirements, or when the position involves supervisory authority that creates additional liability exposure.