01When to use the project manager job description, and who uses it
The projects director or general manager writes this description when work turns from scattered tasks into a project with a scope, a schedule and a budget: building a new branch, rolling out a system, staging an event or carrying out a customer contract. HR uses it in the contract and to set the job's level and financial authority, and the manager reviews the holder on keeping the project to schedule and budget and on the satisfaction of whoever asked for it.
It is reopened when the project grows into phases that each need a manager; when the job is given authority to approve contractor claims after only recommending them; or when the company moves from a single project to a portfolio competing for the same team.
02The project manager job description
The template groups the project manager's work under 5 headings, Scope and plan, Schedule and budget, Team, contractors and suppliers, Risks and quality and Stakeholders and reporting, followed by how the job is measured, who suits it and where it is done.
[Company name] Job Description Job title: Project Manager Department: Projects Reports directly to: [Projects Director / Operations Manager / General Manager] Supervises: [The project team of engineers and coordinators, and coordinates contractors and suppliers] Work location: [head office, with visits to the project site] Work pattern: [full-time] Issue date: [date] Version: [number] Job summary The project manager leads a project from request to handover: sets the scope and plan, follows schedule and budget, coordinates the team, contractors and suppliers, manages risks and change requests, and sends progress reports to stakeholders. Duties and responsibilities 1) Scope and plan - Turn the customer's or management's request into a written scope with clear deliverables. - Prepare the project plan with its phases, dates and owners. - Agree the acceptance criteria before execution starts. 2) Schedule and budget - Follow actual progress against the schedule and update the plan at any change. - Follow actual spending against the project budget. - Raise any variance with its causes and the options proposed to treat it. 3) Team, contractors and suppliers - Assign work to the team and follow it to completion. - Coordinate the work of contractors and suppliers and receive what they deliver. - Hold periodic follow-up meetings and record their decisions. 4) Risks and quality - Record expected risks, with a response plan for each, and follow them. - Control change requests by estimating their effect before they are approved. - Check that deliverables meet the acceptance criteria before handover. 5) Stakeholders and reporting - Keep the customer or management informed of progress and problems. - Hand over and close the project, recording the lessons learned. - Keep the project documents: contracts, minutes and changes. Suggested performance indicators - Keeping the project to the approved schedule. - Keeping it to the approved budget. - No change carried out without written approval. - Customer or management satisfaction at handover. - Completeness of the closing documents. Qualifications and experience - Bachelor's degree in engineering, business administration or a field that suits the type of project. - At least [__] years managing similar projects. - A project management certification is a plus. Skills required - Planning and scheduling. - Cost and budget control. - Negotiating with contractors and suppliers. - Leading a team that does not always report to the role. - Presenting and writing reports. Working conditions - Office hours, with visits to the project site [when needed]. - Pressure close to handover dates. Approval [Approver's name and job title] Signature: ________ Date: [date] Job holder acknowledgment I have read the job description of "Project Manager" above and confirm that I understand its duties. Name: [employee name] Signature: ________ Date: [date]
03The project manager description, clause by clause
Scope and plan: what is in and what is out
A project starts with a written scope that sets the deliverables, their acceptance criteria and what falls outside, because most disputes come from a scope understood two ways. The project manager writes the plan and divides its responsibilities, the project owner approves it, and its technical part is carried out by the site engineer.
Schedule and budget: a variance raised early
The manager compares actual with plan weekly on the schedule and monthly on the budget, and raises a variance as soon as it appears with two or three options to treat it. A project found late at handover has no room left for a remedy.
Team and contractors: coordinating without standing authority
The manager leads people from several departments who usually do not report to them, so relies on clear tasks, dates and meeting minutes rather than orders. What contractors and suppliers hand over is received against the acceptance criteria, and anything that does not match is objected to in writing.
Risks and quality: every change has its price
The manager logs the risks and who treats each one, and estimates the effect of every change request on schedule and cost before the project owner agrees. A change carried out without written approval is the root of the dispute at the close.
Stakeholders and reporting: a report that asks for a decision
A periodic progress report goes to whoever funds or requested the project, with what is done, what remains, the risks and the decision needed. The project closes with documents, a signed handover and written lessons, so the next project does not start from zero.
Approval and signature
The project manager description ends with the approver's name, title, signature and date, so when duties change a new version is issued with a new number instead of handwritten edits.
04Interview questions that test the project manager description
- 01A key supplier is late and sits on the project's critical path. What do you do? Work out the effect on the handover date, test the alternatives, whether another supplier, speeding up or reordering tasks, put the options with their cost to the project owner, and record the decision.
- 02The customer asks for an added feature close to handover. How do you respond? Neither refuse nor accept at once. Estimate its effect on time and cost and present it as a change request that is approved in writing or deferred to a later phase.
- 03A team member from another department keeps missing their dates. How do you handle it? Speak to them first to learn the reason, then take it to their direct manager with the effect of the delay on the project, not as a personal complaint.
- 04How do you know a project has started to drift? When small overdue items pile up in linked work, or output falls short of plan for several weeks running, before it shows in the budget.
05A filled-in example: a project manager for a contracting company in Riyadh
A contracting company in Riyadh hires a non-Saudi project manager for a residential compound, reporting to the projects director and leading a site engineer, a foreman and a procurement team. The company wrote that the progress report is weekly, that changes need written approval, and that the manager's financial ceiling is in the authority document. The single overtime hour in the example only shows the hourly rate.
| Field | In the example |
|---|---|
| Company | A contractor delivering commercial and residential projects |
| City | Riyadh |
| Work period | Morning, 8:00 am to 5:00 pm with an hour's break |
| Start date | 2026-12-20 |
| Nationality | Non-Saudi |
| Basic salary | SAR 17,000.00 |
| Housing allowance | SAR 4,250.00 |
| Transport allowance | SAR 1,700.00 |
| Total monthly salary | SAR 22,950.00 |
Entering these project manager numbers in the GOSI calculator, the end-of-service calculator, the overtime calculator and the leave calculator returns the same results:
| Calculation | Result | Basis |
|---|---|---|
| End of probation (90 days) | 2027-03-19 | the start date counts as day one |
| Actual hourly wage | SAR 95.63 | (basic + allowances) ÷ 30 ÷ 8 hours |
| Overtime hourly rate | SAR 131.04 | actual hourly wage + 50% of the basic hourly wage |
| Pay for 1 overtime hour | SAR 131.04 | overtime rate × hours |
| Employee GOSI share per month | SAR 0.00 | nothing is deducted from a non-Saudi employee |
| Employer GOSI share per month | SAR 425.00 | 2% of the contributory wage |
| End-of-service award if the contract ends at term after two years | SAR 22,950.00 | half a month's wage per year for the first five years, on the total of SAR 22,950.00 to 2028-12-19 |
| Annual leave earned by the end of probation | 5.18 days | 21 days per year of service, pro rata |
06Hard cases and common mistakes in a project manager description
The project owner asks to speed up while the team is short
The manager sets out the cost of speeding up and its effect on quality and risk, and offers options: add to the team, cut the scope or postpone a phase. The description gives the role the right to assess, not to decide.
A contractor hands over work that does not meet the acceptance criteria
The manager records the non-conformity with photos and the comparison to the drawing, asks for correction in writing by a date, and does not accept before it. The technical quality detail sits with the site engineer.
A project manager leads several projects at once
The description sets how many concurrent projects are acceptable and writes which project takes priority when they compete for the same team.
The project is stopped before completion
The manager records what was done, what was spent and what the parties committed to, and hands over a closing file, since a stopped project sometimes returns months later.
Common mistake: Writing "manages the project" with no scope
A description with no limits loads the job with everything nobody else owns. Put in the deliverables and the limits of authority.
Common mistake: Confusing the project manager with a coordinator
A coordinator follows dates; a project manager owns the plan, the budget and the decision when things drift.
07Steps to adapt the project manager description to your company
- 1
State the type of projects
Construction, technology, events or organizational change? The type changes the qualifications, the deliverables and the contractors named.
- 2
Set the authority over the budget
Does the role recommend spending or approve it, and up to what level? Refer the ceiling to the authority document rather than writing a figure in the description.
- 3
Separate it from the site engineer
A project manager owns the plan, the budget and the decision when things drift; a site engineer carries out the technical side. If one job holds both, say so plainly.
- 4
Write the scale of what it runs
One large project or several small ones at once? That sets the effort required more than the number of years does.
- 5
Name the stakeholders
The customer, management, the funder and the main contractor: who receives the reports and who approves changes.
08Project manager description checklist before approval
6 items
09Frequently asked questions
A project manager has a start, an end and a delivery; an operations manager runs ongoing work that does not end in a handover.
Make it a plus unless the customer asks for it in the project contract.
Often the manager leads a temporary team from different departments. Write whether anyone reports to the role administratively or is only led for the project.
Yes, adapt the examples of deliverables, contractors and suppliers to the kind of project.
In contracting it helps; elsewhere an understanding of the deliverables is enough. Write what is needed to suit your type of project.
The manager they report to, with input from team members and the project owner; write that in the description.
Write the indicator without its target figure, since the figure changes from one project to another.
Yes. Replace contractors with vendors and sites with work environments.
