“Are we still on track?” “What is blocking the handover?” “Does that change fall within scope?” Project conversations become easier when you can explain the work, its timing and the decisions it needs. This guide teaches project management vocabulary through definitions, practical phrases and a worked status update.
Scope describes what a project includes, a deliverable is an output to provide, and a milestone marks a significant point in the work. Use dependency to explain how activities rely on one another, and change request to propose a change for review. A clear update states the current status, the reason for any delay and the next action.
What's your English level?
Take the test and get your certificate!
Scope, Deliverables and Milestones
These terms answer different questions. Scope tells people what is included, deliverables identify outputs, and milestones show significant points in progress. The Association for Project Management glossary provides specialist definitions; the examples below show how to use the vocabulary in everyday project discussions.
| Term | Meaning and example |
|---|---|
| Scope | The boundaries of the work. “Training is included in the scope, but ongoing support is not.” |
| Requirement | A condition or capability the work must satisfy. “One requirement is that users can download their reports.” |
| Deliverable | An output to be provided. “The training guide is our next deliverable.” |
| Milestone | A significant point or event in the project. “Approval of the design is a milestone.” |
| Acceptance criteria | Conditions used to decide whether an output is acceptable. “Let’s agree on the acceptance criteria before testing.” |
| Stakeholder | A person or group involved in, interested in or affected by the project. “We need feedback from the customer support stakeholders.” |
Imagine a team creating a staff training course. The videos and workbook are deliverables; approval of the completed course is a milestone. “Record the introduction” is a task, meaning a piece of work needed to produce an output.
Use in scope and out of scope to discuss boundaries: “Translation is out of scope for this phase.” This means it is not included in the current agreed work, not that it is unimportant. The APM’s scope management overview explains why both included and excluded work need clear definitions.
Schedules and Dependencies
A schedule sets out planned timing, while a deadline is the latest time something is due. An estimate is an informed approximation, not automatically a commitment. Compare “We estimate three days of work” with “We have committed to delivery by Friday.”
A dependency links work that relies on other work or conditions. For example, editing a video may depend on receiving the recorded footage. Say, “Editing depends on the recording being complete,” or “We cannot start editing until we receive the footage.”
Useful schedule phrases
| Phrase | Example |
|---|---|
| On track | “We are on track to finish the draft by Friday.” |
| Ahead of schedule | “The first module is two days ahead of schedule.” |
| Behind schedule | “Editing is one day behind schedule.” |
| Meet a deadline | “Can we meet the revised deadline?” |
| Miss a deadline | “We missed the deadline for the first review.” |
| Bring forward | “Can we bring the review forward from Thursday to Tuesday?” |
| Push back | “We propose pushing the review back from Tuesday to Thursday.” |
Include both dates when changing a meeting or delivery date. “Move it forward” can be interpreted differently, so “Move it from 12 May to 10 May” is clearer. Use by Friday for a completion deadline and on Friday for an event scheduled that day.
A resource is something needed to do the work, such as people, equipment or funding. Capacity describes how much work a person or team can take on. “We have limited editing capacity this week” identifies a constraint more precisely than “We are busy.”
Risks, Issues and Change Requests
Risk, issue and blocker
A risk involves uncertainty that could affect the project. In everyday updates, teams often use the word for a possible future problem, although project risk can also include opportunities. An issue is a current matter that needs attention or resolution.
Compare “The recording may arrive late” with “The recording has not arrived.” The first describes a risk; the second reports an existing issue. A blocker is a problem that prevents work from moving forward: “The missing recording is blocking the edit.”
To mitigate a risk is to reduce its likelihood or negative impact. To escalate an issue is to bring it to someone with the appropriate authority or ability to help. Neither verb means the problem has already been solved: “I escalated the access issue, and we are waiting for a decision.”
Requesting a change
A change request proposes a change to the agreed work or plan. Change control is the process for recording, assessing and deciding on such requests. APM’s change control guide distinguishes approval, rejection and deferral, so submitting a request is not the same as receiving permission to proceed.
Useful language includes “assess the impact,” “approve the request,” “reject the proposal” and “defer the decision.” A baseline is an agreed reference plan used for comparison. For example: “The extra module would change the scope and delivery date. We need approval before updating the baseline.”
Scope creep describes the gradual expansion of project scope, often without corresponding agreement about time or resources. Instead of using the term as an accusation, identify the added work: “The new request adds two videos that were not in the agreed scope.” Then ask how it should be assessed.
Giving a Clear Project Update
A useful update separates facts from forecasts and requests. State what is complete, what remains, what is affecting progress and who will do what next. You can then specify any decision you need.
Status: The workbook draft is complete. Video editing is one day behind schedule because the final recording arrived late.
Next action: Maya will complete the first edit by Wednesday. Leo will review it on Thursday.
Decision needed: Please confirm by Tuesday whether subtitles are required for this release. If they are, we will submit a change request with an updated estimate.
Notice that the update does not call a completed draft an approved deliverable. Review means examine and comment; approve means give the required agreement. Sign-off commonly means formal approval, while handover is the transfer of work, information or responsibility to another person or team.
A short project meeting
Manager: Is the course still on track for release?
Coordinator: The workbook is ready for review, but the video edit is delayed.
Manager: What does that affect?
Coordinator: The final review depends on the edit. We can keep the release date if approval comes by Thursday.
Manager: Please confirm the reviewer’s availability and flag any further delay today.
To flag something is to draw attention to it. To follow up on something is to check progress or take further action. An action owner is the person responsible for an agreed action: “Who is the owner of the reviewer-availability check?”
For broader meeting and email language, see our business English vocabulary guide. In a project update, add the specific dependency, effect and next step so the reader can act on the information.
Common Mistakes and Practice
Say “The task depends on approval,” not “depends of approval.” Use “We are making progress,” rather than “making a progress”: progress is normally uncountable. Say “discuss the delay,” without adding “about” after discuss.
Keep delay and postpone distinct. “The delivery was delayed” reports that it happened later than planned; “We postponed the review” says that someone moved it to a later time. When you propose a change, use “Could we postpone the review?” rather than implying the new date is already agreed.
Choose the best word or phrase
- The completed training guide is a ___. (deliverable / deadline)
- Testing cannot start until the build is ready. This is a ___. (dependency / quotation)
- The supplier might deliver late. This is a ___. (risk / completed task)
- We need to move the meeting from Monday to Wednesday. We want to ___. (bring it forward / push it back)
- The task depends ___ approval. (on / of)
- The request has been submitted but not approved. Can the team say it has sign-off? (yes / no)
Answers: 1. Deliverable, because it is an output. 2. Dependency, because one activity relies on another. 3. Risk, because the delay is still uncertain. 4. Push it back, because Wednesday is later. 5. On is the correct preposition. 6. No: submission does not establish approval.
Now rewrite “The project is late. We are working on it” with a concrete status, cause and next step. One possible answer is: “The draft is two days behind schedule because the source data arrived late. Nina will send the revised draft by Thursday.”
Frequently Asked Questions
Is a milestone the same as a deliverable?
No. A deliverable is an output, such as a report. A milestone marks a significant point, such as approval of that report. The two can be connected without meaning the same thing.
Does on track mean the work is finished?
No. It means progress is consistent with the intended plan or target. Say what the team is on track to do: “We are on track to finish testing by Friday.”
What should I say when I do not know the revised date?
State what is known and when you will provide the missing information. For example: “The review is delayed. I will confirm a revised date after speaking to the reviewer this afternoon.” Avoid presenting an estimate as a confirmed commitment.
Do all teams use these terms in exactly the same way?
No. Labels such as issue, blocker and sign-off can have specific meanings in an organisation. Ask a clear question when necessary: “Does ready mean ready for review or approved for release?” Shared understanding matters more than using the most technical word.
