GSC Project Manager common mistakes
GSC Project Manager · Understand the traps and how to avoid them.
Approving a business case on the strength of a headline benefit figure without tracing it to a stated baseline, measurement method, and owner, so the case cannot later be tested against outcomes.
Candidates treat the business case as a narrative justification rather than a decision instrument, and rush to the 'approve' answer because it sounds decisive.
What to do instead
Before choosing, check whether the case names a quantified baseline, a measurement approach, a benefit owner, and an explicit option comparison. If any is missing, the correct action is usually to return it for completion, not to approve.
Building a schedule by linking every activity to its predecessor with finish-to-start logic and no leads, lags, or resource levelling, then declaring the resulting end date achievable.
Candidates learn the network diagram mechanics in isolation and default to the simplest logic, forgetting that real schedules must reflect resource availability and realistic overlaps.
What to do instead
When a question shows a compressed or resource-constrained situation, look for the answer that applies resource levelling or critical chain buffering rather than one that simply shortens durations or adds lag without justification.
Confusing contingency reserves with management reserves and charging identified risk responses to the wrong one, which distorts both the cost baseline and the approval authority needed to release funds.
The two reserves are taught together and the distinction hinges on whether the risk is identified in the register, a detail candidates skim past under time pressure.
What to do instead
Anchor the rule: known risks go in the cost baseline as contingency; unknown risks sit outside the baseline as management reserve and require sponsor approval. Match the risk's register status first, then pick the reserve.
Treating a risk register as a static list produced at planning and answering later questions as if no risk response has been executed or reassessed.
Candidates memorise the register as a planning artefact and do not carry forward the idea that risk management is iterative across the life cycle.
What to do instead
When a scenario describes a change in conditions, expect the correct answer to involve reassessing probability and impact, updating the register, and re-evaluating response adequacy, not simply logging the risk and moving on.
Choosing 'increase inspection' or 'add more testing' as the response to every quality problem, including ones caused by an unstable process or unclear requirements.
Inspection feels like a safe, active answer, and candidates underweight prevention-based options such as process adjustment or root-cause analysis.
What to do instead
Diagnose the cause first: if defects trace to a process or requirement gap, the answer is prevention (process change, clearer acceptance criteria); inspection is correct only when the problem is detection of nonconforming output.
Selecting the lowest-priced bid as the award recommendation without checking whether the procurement approach, evaluation criteria, and contract type were suited to the requirement.
Candidates import a general 'save money' instinct and overlook that award must follow the stated evaluation criteria and the chosen contract type's risk allocation.
What to do instead
Read the solicitation's evaluation method before judging the bid. If the question asks what should happen next, the answer usually restores adherence to the published criteria or the contract's change and acceptance provisions.
Responding to a stakeholder objection by escalating it to the sponsor instead of first engaging the stakeholder through the agreed communication approach.
Escalation looks like decisive action, and candidates confuse authority with the obligation to manage the relationship at the working level.
What to do instead
Follow the escalation threshold: routine concerns are handled through the communication plan and stakeholder engagement activities; escalation is reserved for issues beyond the project manager's authority or outside agreed tolerances.
Reporting a schedule or cost variance as a status update without analysing the trend, forecast, and corrective options before recommending action.
Candidates answer the surface question ('what is the variance?') and stop, missing that earned value questions usually ask for the implication and the response.
What to do instead
On any variance question, compute the index and forecast first, then ask whether the cause is one-off or systemic. Choose answers that pair the finding with a proportionate corrective action and a re-baselining decision only where tolerances are breached.
Declaring the project closed once deliverables are accepted, skipping the benefits realisation plan, lessons capture, and handover of ongoing ownership.
Candidates equate closure with delivery, and benefits realisation is often taught as a separate topic rather than the final phase of the project.
What to do instead
Treat closure as complete only when outputs are transitioned, benefits measurement is assigned to an owner with a review schedule, lessons are recorded, and resources are released. Select answers that include these steps.
Accepting a gift, favour, or outside engagement without checking the organisation's policy and disclosing it, on the reasoning that it does not affect judgement.
Candidates answer the ethical question by their own personal standard rather than the professional and organisational standard, and underestimate the appearance-of-conflict test.
What to do instead
Apply the sequence: consult the governing policy or code, disclose to the appropriate authority, and decline or seek approval where required. The correct answer is almost always the transparent, documented route rather than a private judgement.