Project Manager Job Description Template

In plain language: States the exact job title, the department or business unit the PM belongs to, and the FLSA or employment classification (exempt salaried, in most cases).

Common mistake: Using a generic title like 'Manager' without specifying the project management function. Vague titles create classification ambiguity and complicate performance reviews and termination proceedings.

In plain language: Identifies who the PM reports to and lists the roles that report to the PM, establishing the chain of authority and accountability.

Common mistake: Omitting the PM's own direct reports. Courts and HR tribunals use the reporting structure to determine whether a role change constitutes a demotion — missing this field weakens the employer's position.

In plain language: The main list of project management functions the employee is expected to perform — scope definition, scheduling, budget tracking, stakeholder communication, and risk management.

Common mistake: Listing responsibilities so broadly that any task could be assigned without notice — or so narrowly that role evolution requires formal contract amendments. Strike a balance with a residual-duties clause ('and such other duties as may reasonably be assigned').

In plain language: Specifies the dollar threshold up to which the PM can approve spending without escalation, and defines what procurement or resource decisions require sign-off from a senior leader.

Common mistake: Not including this clause at all. Without documented authority limits, the company is exposed to unauthorized commitments and the PM is exposed to disciplinary action for decisions they believed were within their scope.

In plain language: Lists the minimum educational background and professional certifications needed to be considered for the role — typically a bachelor's degree and PMP or PRINCE2 for mid-to-senior positions.

Common mistake: Setting qualification thresholds that screen out protected classes without business justification. A requirement for 10+ years of experience for a mid-level role may be challenged under age or gender discrimination statutes in several jurisdictions.

In plain language: Identifies desirable (but not mandatory) skills — agile methodologies, stakeholder management, specific industry experience — that differentiate strong candidates.

Common mistake: Listing preferred skills in mandatory language ('must have') and required skills in optional language ('nice to have'). The distinction matters legally — courts use the written job description to evaluate whether a termination for failure to meet requirements was justified.

In plain language: States the measurable outcomes the PM is expected to achieve — on-time delivery rates, budget variance thresholds, stakeholder satisfaction scores — and the review cadence.

Common mistake: Leaving KPIs out of the job description entirely and managing them informally. When a PM is terminated for performance, the absence of written standards makes it difficult to defend the decision against a wrongful dismissal claim.

In plain language: Discloses whether the role is on-site, hybrid, or remote; expected travel percentage; and any physical demands relevant to the work environment.

Common mistake: Omitting location and travel expectations from the description and imposing them after hire. Unilaterally adding substantial travel requirements post-hire is a textbook constructive dismissal trigger in Canada and the UK.

In plain language: Notes that the PM is subject to the confidentiality and IP assignment provisions of the broader employment agreement — ensuring the job description cross-references binding obligations already in place.

Common mistake: Treating the job description as a standalone document with no reference to the employment contract. Without a cross-reference, courts may treat the job description as the complete agreement, undermining IP and confidentiality provisions in the main contract.

A project manager job description is a formal document that defines the responsibilities, authority, qualifications, reporting structure, and performance standards for a PM role. When signed and attached to an employment contract as a Schedule of Duties, it becomes a legally binding record of agreed-upon role expectations — useful for onboarding, performance management, and defending termination decisions.

At minimum: role title and classification, reporting hierarchy, core duties with specific deliverables, budget authority limits, required and preferred qualifications, measurable performance standards, work location and travel requirements, and a cross-reference to the governing employment agreement. Missing authority limits or KPIs are the two omissions most likely to create legal exposure.

A job description attached as Schedule A to a signed employment contract is generally enforceable when properly executed in most jurisdictions. As a standalone document without a signature, it has persuasive but limited legal weight. For the document to bind both parties — particularly on duties, authority, and performance standards — it should be signed by both the employer's authorized representative and the employee before the start date.

Material changes to duties, reporting structure, or authority without employee consent can constitute constructive dismissal in Canada, the UK, and the EU. In the US, at-will employment generally allows role adjustments, but even at-will employees may have contract-based claims if the job description was incorporated into the employment agreement. The safest approach is to obtain written consent — or provide additional consideration — any time a signed job description is substantially amended.

Standard minimum requirements for a mid-level PM include a bachelor's degree in a relevant field, 3–5 years of project management experience, and a PMP or equivalent certification. Senior roles typically require 7–10 years of experience and a track record managing budgets above $500K. All requirements should be genuinely job-related — requirements that disproportionately screen out protected classes without business justification may violate EEOC, Human Rights Code, or Equality Act standards depending on jurisdiction.

A job description defines what the employee will do — duties, qualifications, authority, and KPIs. An employment contract defines the terms of the employment relationship — compensation, benefits, IP assignment, non-compete, termination, and governing law. The job description is typically incorporated as Schedule A to the contract. Relying on a job description alone leaves the employer without enforceable confidentiality, IP, and termination provisions.

For mid-to-senior PM roles, PMP certification is widely recognized as a relevant and defensible mandatory requirement. For junior or coordinator-level roles, marking it as preferred rather than required keeps the candidate pool wider. A practical middle ground is 'PMP required within 12 months of hire' — this sets a clear expectation while allowing experienced PMs who are not yet certified to apply. Some jurisdictions and industries (construction, government) have sector-specific certifications that are more relevant than PMP.

A signed job description establishes the documented baseline for the role. If an employer later expands duties significantly, removes budget authority, demotes the PM in the reporting structure, or adds substantial travel, the deviation from the signed description is measurable — and the employer can document consent to any changes. Without this baseline, employees in Canada, the UK, and the EU can argue any material change constitutes constructive dismissal with no written record to contradict them.

A job description designed for an employee should not be used unchanged for an independent contractor engagement. Using it as-is risks misclassification — regulators in the US (IRS), Canada (CRA), and the UK (HMRC) look at behavioral control when determining worker status, and a detailed duties schedule is one indicator of an employment relationship. For contractors, use a Statement of Work or Independent Contractor Agreement with a deliverables-based scope instead of a duties-based job description.