For GSC preparation, study Canadian construction management concepts as decision rules rather than definitions: learn which contract form shifts which risk, how a delay fact pattern converts into an extension-of-time position, and which change pathway fits the facts. Then test yourself with case readings scored against a structured rubric.
Distinguishing Canadian Contract Forms: Stipulated Price, Cost Plus, Unit Price, and Construction Management
Construction management assessment rewards knowing which contract form moves which risk. Stipulated price, cost plus, unit price, construction management, and design-build each allocate price certainty, scope authority, and payment mechanics differently, and scenario questions hinge on those differences.
Start with price risk. In a stipulated price arrangement, the contractor agrees to a fixed sum for a defined scope, so the contractor generally carries the risk of cost growth unless a change or relief event intervenes. In a cost plus arrangement, the owner reimburses actual costs plus a fee, so the owner absorbs most cost-estimate risk but gains transparency into spending. Unit price contracts sit between them: quantities are measured as work proceeds, so quantity uncertainty is shared while unit rates stay fixed.
Then add delivery authority. Under a construction management model, the construction manager advises the owner and administers trade contracts rather than carrying the whole build at a lump sum; under design-build, one entity contracts for both design and construction, shifting design coordination risk inward. When a scenario describes who signs trade contracts or who employs the designers, use those cues to identify the delivery model before answering anything about liability or payment. Compare each new fact pattern against this table rather than against a memorized list.
- Cue words for stipulated price: fixed contract price, tendered sum, defined drawings and specifications.
- Cue words for cost plus: reimbursable costs, fee, auditable expenditures.
- Cue words for unit price: schedule of rates, measured quantities, progress payment by actual quantities.
- Cue words for construction management: trade contracts, advisory role, agency or non-agency relationship.
- Cue words for design-build: single-source responsibility, performance specifications, design liability.
| Form or delivery model | Price basis | Typical cost-growth risk holder | Facts that point to it |
|---|---|---|---|
| Stipulated price (e.g., CCDC 2 style) | Single fixed contract price | Contractor, within defined scope | Tendered lump sum, complete design at award |
| Cost plus (e.g., CCDC 3 style) | Actual cost plus fee | Owner | Incomplete design, transparency and audit rights |
| Unit price (e.g., CCDC 4 style) | Fixed unit rates on measured quantities | Shared: owner on quantities, contractor on rates | Roadworks, earthworks, uncertain volumes |
| Construction management (e.g., CCDC 5 style) | CM fee plus trade contracts | Depends on agency or non-agency terms | Owner engaged early, phased procurement |
| Design-build (e.g., CCDC 14 style) | Single design-build contract, typically stipulated price | Design-builder, coordinated internally | Performance specs, one responsible entity for design and construction |
Delay Analysis: Separating Compensable Time from Recoverable Cost
A delay fact pattern becomes an extension-of-time decision only after you classify each delay event: who caused it, whether it sat on the critical path, and whether concurrent events overlap. Treat compensable time and recoverable cost as separate questions.
Trace the mechanics in three steps. First, build the timeline: what happened, in what sequence, over which calendar days. Second, test criticality: an event only extends the completion date if it delayed a critical-path activity, so a two-week slowdown on a parallel non-critical activity changes no milestone. Third, test concurrency: when an owner-caused event and a contractor-caused event delay the same critical window, standard practice is that time and money entitlements can diverge. In this simplified framing, the contractor may still receive time for the owner-caused event while being barred from recovering time-related costs for the overlapping contractor-caused period; the governing contract terms always control the outcome.
Worked scenario: an owner delivers geotechnical information ten days late, and during that same window the contractor's only excavator breaks down for six days. The mistaken move is claiming ten days of extension and ten days of extended general conditions costs. The better decision is to separate the questions: request an extension reflecting the owner-caused critical delay, acknowledge the concurrent equipment failure, and limit the cost claim to the days where the owner-caused delay ran without concurrency. It matters because the notice and quantum positions change: a blended claim invites a reduction for the contractor-responsible portion, while a cleanly separated claim is easier to defend and to document.
Change Management: Choosing Between Change Order, Change Directive, and Claim
Scope shifts follow three different procedural routes. A change order records an agreed change with agreed cost and time. A change directive directs the work when parties cannot agree on terms. A claim preserves entitlement when no agreement is reached.
Under Canadian standard forms such as CCDC 2, a change order is the ordinary instrument: both parties sign, the contract price or completion date adjusts, and the work proceeds cleanly. A change directive exists precisely for disagreement: the owner can direct additional work while pricing remains unresolved, and the contractor is generally expected to proceed and resolve the cost afterwards through the contract's mechanisms. A claim is the contractor's own position asserted within notice timelines when it believes entitlement exists but no instrument has been issued. The differences are procedural doors, and walking through the wrong one weakens recovery even when the underlying entitlement is real.
Worked scenario: midway through a school project, the owner verbally asks the contractor to upgrade a curtain wall system, and the contractor proceeds immediately to hold the schedule. The mistaken move is completing the work and invoicing it as extras without paper. The better decision is to price the change, confirm scope and cost in writing, and obtain a change order before proceeding; if agreement stalls, request the owner's change directive and record the directed work, dates, and resources. It matters because unsigned verbal extras leave the contractor arguing valuation after the fact, while a directed change keeps the schedule moving and preserves a documented entitlement trail.
Reading Case Facts: A Five-Step Extraction Method
Case questions bury decisions under narrative detail. Extract in a fixed order: parties, contractual basis, event timeline, notice compliance, and remedy sought. This stops you from answering a scheduling question that was actually a payment question.
Apply the five steps in order. Identify the parties and their contractual relationships, because obligations run along contract lines and a party without a contract usually has no direct claim. Name the contract form and delivery model, because that tells you which risk allocation applies. Build the event timeline with dates, since sequence and overlap drive delay and notice conclusions. Check notice compliance against the stated timeline, because most standard forms condition entitlement on timely written notice. Finally, state the remedy the question actually asks about: time, money, both, or a procedural step.
Practical exercise: take any construction news brief or past project dispute and write a ten-line case note. Expected observations for a strong note: parties and relationships named in the first line, contract form identified with one sentence of justification, timeline reduced to dated events, each notice characterized as given or missed with its date, and a closing position on the remedy. Self-check rubric, scoring one point each: (1) contract form correctly inferred; (2) critical path effect stated, not assumed; (3) concurrency addressed if two events overlap; (4) notice dates cited; (5) remedy separated from liability. Five points means ready to move on; three or fewer means repeat the extraction on a fresh scenario before adding new content.
Documentation That Supports Decisions: Daily Reports, RFIs, and Notices
Documentation questions test whether records support entitlement, not whether paperwork exists. Daily reports prove site conditions, requests for information resolve design gaps before work proceeds, and written notices preserve rights within the timelines a standard form imposes.
Connect each document type to the decision it supports. Daily site reports carry weight when they record weather, workforce, equipment, visitors, and delivered work by date, because delay and disruption arguments are built from dated observations rather than reconstructed memory. Requests for information matter when a scenario shows an ambiguous drawing: the better practice is to issue the RFI, hold affected work where the contract allows, and document the direction received, rather than guessing and absorbing rework. Progress claims and payment records matter when the question is quantum, because values must reconcile against measured work, materials on site, and retainer or holdback terms.
Practice the linkage by reverse-engineering: pick a scenario outcome, such as an extension of time for a late delivery, and list which records would have supported each element of the claim. A strong self-check is whether your list distinguishes corroboration from entitlement: a purchase order proves the delivery date, the daily reports prove standby impact, and the notice letter preserves the right to claim. If all three live in the same document in your answer, you are conflating evidence with procedure, and case answers will read as assertions rather than supported positions.
Safety and Ethics Scenarios: Decision Rules for Field Pressure
Ethics and safety scenarios in construction management ask you to choose a professional response under schedule or cost pressure. Anchor on three rules: refuse unsafe direction, disclose conflicts of interest early, and separate your employer's interests from your certification obligations.
Paper-scenario method: read the fact pattern and identify the pressure, the hazard or duty, and the decision point. Canadian occupational health and safety is provincially regulated, and across jurisdictions workers and supervisors hold duties to protect against known hazards, with the right to refuse unsafe work; a scenario in which a schedule argument is used to push past a missing guardrail resolves through the refusal and reporting pathway, not a productivity trade-off. For ethics, the decision points are gift and favour thresholds, bid confidentiality, and situations where your advice to the owner would serve your own firm's interests, which call for disclosure or withdrawal from the decision.
Study technique: write each ethics rule as an if-then sentence and test it against three pressure types: authority pressure (a superior directs it), peer pressure (the team has always done it), and self-interest pressure (it benefits you). If your rule collapses under any pressure type, rewrite it until it holds. This converts vague principles into reusable triggers, which is what scenario questions measure: not whether you can state that safety matters, but whether you can pick the compliant action when the scenario makes the non-compliant action look cheap and fast.
An Adaptive Four-Week Sequence and Readiness Checklist
Sequence study by decision difficulty: contract forms and risk first, then delay and change application, then documentation and ethics, finishing with timed case readings. Adapt week three onward based on your rubric scores rather than a fixed calendar.
Suggested sequence. Week one: build the contract-form comparison table yourself from scratch, then classify ten one-paragraph scenarios by form and delivery model. Week two: delay analysis only; write one extension-of-time position per day using the three-step method, alternating scenarios with and without concurrency. Week three: change management and documentation together, since change directives and claims live or die on records; score each written position against the five-point rubric. Week four: mixed timed cases plus ethics if-then drills; spend the final days only on whichever topic scored below four out of five, not on re-reading strengths. Adjust the weighting to your own background: a contracts-heavy reader may compress week one and expand week two.
Readiness checks before you stop. One: given any paragraph naming parties, dates, and a scope shift, you can name the correct procedural pathway and justify it in under five sentences. Two: you can state, from memory, who holds cost-growth risk under each of the five contract forms in the table. Three: your delay positions consistently separate time from money and address concurrency when events overlap. Four: your case notes cite notice dates and distinguish evidence from procedure. Five: your ethics if-then rules survive all three pressure types. These are learning milestones for your own tracking, not predictions of any exam result. One short administrative note: current credential requirements, application processes, and any assessment logistics are set and maintained by the Canadian Construction Association, so verify them directly on its Gold Seal Certification page rather than relying on third-party summaries.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.