The project asks for a user representative, and the same enthusiastic colleague attends every session. User acceptance testing needs participants who cover the intended operational tasks and exceptions, with an appropriate owner authorised to accept the result. One available person may not represent every role that must use it.

The project reaches the end of discovery and begins implementation because that is what the timeline shows. A stage gate should be an explicit decision about the next commitment, with an authorised person checking the evidence and conditions. Reaching a date does not itself authorise more work or expenditure.

The sponsor receives a long update ending with “please advise”. The team knows there is a problem but has not presented a decision. A sponsor decision paper should state the choice required, who can make it, viable options, their consequences and the last useful decision date.

The sponsor wants reassurance. The project team wants fewer reporting requests. A useful project health review needs a defined question, access to relevant evidence and a clear route from findings to an authorised decision. Commission it to learn something actionable rather than obtain a reassuring colour.

The project is now expected to finish later, but nobody wants to change the approved date in the report. Update the forecast when the evidence changes. Replacing the baseline is a separate authorised decision about the reference plan, not the automatic consequence of an uncomfortable prediction.

The report says eighty per cent complete because most of the allocated hours have been used. That tells you about effort consumed, not necessarily accepted work. To report percentage complete, define what the total represents and what evidence earns progress against it.

The team is estimating tasks six months away while next week's supplier decision remains unresolved. Rolling-wave planning details near-term work and keeps later work at a higher level until enough information exists to plan it responsibly. The project still needs an overall direction, constraints and decision points.

The task needs two days of work, so it is booked for Tuesday and Wednesday. The person doing it is available for half-days, an input arrives Thursday and the reviewer works next Monday. Effort and elapsed duration answer different questions, and a delivery promise needs both.

Both teams have promised Friday, but they mean different working hours and one has a local holiday before the review. Plan a cross-party project handoff using an explicit date, local time, time zone, working calendar and acceptance window. A shared weekday name is not a complete agreement.

The deadline has moved forward. Someone suggests adding another person; someone else suggests doing everything in parallel. Assess a shorter project schedule by checking which activities control delivery and whether overlap or additional resources can genuinely reduce their duration.

Every task has a little extra time, yet the project still has no clear protection against uncertainty. Project time contingency is an explicit allowance in the schedule for identified uncertainty. Decide what it protects, where it sits and who may consume it rather than quietly padding every estimate.

The launch date is in the sales presentation. Nobody has checked whether the approval, supplier input and preparation can fit before it. To assess a fixed project deadline, work backwards from the result that must be accepted, confirm the essential sequence and compare its latest feasible start with actual availability.

The sponsor asks how long the work will take. You have a reasonable idea, but the answer depends on inputs nobody has confirmed. Give a project estimate as a range by describing the work, stating the conditions behind the lower and upper ends and explaining what evidence will narrow it.

Everyone has been asked to work faster, including the colleague whose task is not holding up the launch. A critical path is the sequence of linked activities that determines the earliest finish under the schedule's assumptions. Find that sequence before choosing which work to accelerate.

The project has consumed time and money, so everyone feels it must continue. That is understandable, but past expenditure does not answer whether the next commitment is worthwhile. A pause or stop decision should compare the remaining options, the project's continuing business purpose and the consequences of winding down or restarting.

The new workflow is live, the project is closed and the promised improvement has no named owner. A benefits owner is responsible for pursuing and reviewing an intended business improvement after the project output is delivered. The role needs operational influence and a clear route for decisions when the expected benefit does not appear.

A project lead waits for certainty before escalating a possible delay. By the time the date is definitely missed, the sponsor has few useful options left. An escalation threshold defines the condition that requires a higher-authority review, including who must respond and how soon.

The same operations lead is needed for a project workshop and a major client delivery. Both plans show the person as available because neither owner has seen the other commitment. A resource conflict needs a business priority decision, supported by the consequences of the available options.

A significant change has been approved, but the team is still reporting against a plan that no longer represents the authorised work. Rebaselining establishes a newly approved reference plan after an appropriate decision. It should preserve the history of what changed rather than erase missed commitments.

The main deliverable is accepted, but the project stays open because a few actions remain. Or it closes immediately and those actions disappear. Project closure should establish what has been accepted, what remains and who is authorised to carry the remaining responsibilities after the project team disbands.