3) Technical and professional questions (Canada-specific)
This is where interviews are won. A Canadian Quantity Surveyor interview often sounds like a working session: CCDC language, tender strategy, change management discipline, and tool fluency.
Q: Which CCDC contract forms have you worked with, and how do they affect change management?
Why they ask it: They’re testing Canadian contract literacy and whether you understand notice, valuation, and documentation.
Answer framework: Contract–Process–Proof — name the form(s), explain your CO workflow, list the proof you rely on.
Example answer: “I’ve worked mainly with CCDC 2 (stipulated price) and CCDC 5B (construction management at risk). In both, I’m strict on early notice and a clean paper trail—site instructions, RFIs, revised drawings, and a priced change proposal with backup. The contract form changes the commercial levers: stipulated price pushes harder on scope definition and exclusions, while CM models require tighter open-book tracking and trade buyout reconciliation.”
Common mistake: Name-dropping CCDC without explaining how it changes your day-to-day controls.
Q: How do you build a Class D vs Class C vs Class B estimate, and what changes between them?
Why they ask it: They want to see if you understand estimate maturity, not just takeoff.
Answer framework: Maturity ladder — inputs, method, contingency, and accuracy range by class.
Example answer: “For a Class D, I’m using high-level quantities, benchmarks, and parametric rates with a larger contingency and explicit assumptions. By Class C, I’m measuring key systems, validating with trade input where possible, and tightening risk allowances. Class B is where scope is far more defined—detailed takeoff, more firm quotes, and a clearer separation between contingency, escalation, and allowances. What changes most is the quality of scope definition and how transparent I am about uncertainty.”
Common mistake: Pretending early estimates are ‘accurate’ instead of managing uncertainty.
Q: Talk me through your bid leveling process. What do you look for beyond the bottom line?
Why they ask it: They’re testing whether you can prevent scope gaps and future claims.
Answer framework: Compare–Normalize–Clarify–Recommend.
Example answer: “I start by normalizing scope—same inclusions, same alternates, same schedule assumptions. Then I check exclusions, unit rates, crew assumptions, and whether the bidder carried the right general conditions. I flag risk items like missing permits, incomplete temp works, or unrealistic productivity. My recommendation isn’t just ‘lowest price’; it’s best value with the cleanest scope and least downstream exposure.”
Common mistake: Choosing the lowest number without interrogating scope and risk.
Tools matter in Canada because teams are often distributed and reporting-heavy.
Q: Which software tools do you use for takeoff, estimating, and cost reporting?
Why they ask it: They want to know how fast you can plug into their workflow.
Answer framework: Tool–Use case–Output — name tools, what you do in them, what you produce.
Example answer: “For takeoff I’ve used Bluebeam Revu and PlanSwift depending on the project. For estimating and reporting, Excel is still the backbone, but I’m comfortable building structured cost plans and cashflows and tying them to a WBS. On delivery-side cost control, I’ve worked with ERP-style cost codes and monthly cost reports—forecast at completion, committed cost, and variance notes that leadership can actually act on.”
Common mistake: Listing tools like a résumé keyword dump with no outputs (what reports, what decisions).
Canada-specific employers also like hearing you can work with drawings and models without pretending you’re a designer.
Q: How do you use BIM quantities (e.g., from Revit/Navisworks) without blindly trusting the model?
Why they ask it: They’re testing whether you understand model risk and measurement rules.
Answer framework: Trust-but-verify — validation checks + reconciliation to drawings/specs.
Example answer: “I’ll use model quantities to speed up measurement, but I validate them. I check model completeness, LOD, and whether elements are modeled consistently—especially openings, finishes, and MEP components. Then I reconcile model takeoff to key 2D drawing checks and the spec. If there’s a mismatch, I document the assumption and quantify the delta so the estimate remains defensible.”
Common mistake: Saying “the model gives the quantities” as if that ends the conversation.
Here’s one that only real QS candidates anticipate: escalation and procurement timing.
Q: How do you handle escalation in a Canadian market with long lead times?
Why they ask it: They’re testing whether you can separate pricing risk from scope and schedule.
Answer framework: Baseline–Index/quotes–Timing–Sensitivity.
Example answer: “I set a pricing date baseline, then apply escalation based on either current trade feedback or a documented index approach, depending on project stage. I tie escalation to procurement timing—steel, curtain wall, switchgear—because lead times drive exposure. I’ll present a sensitivity range so leadership can decide whether to accelerate procurement, lock pricing, or carry a defined allowance.”
Common mistake: Hiding escalation inside contingency so nobody can manage it.
They’ll also test whether you understand payment and cost-to-complete mechanics.
Q: What’s your approach to monthly cost reporting and forecasting (EAC)?
Why they ask it: They want to know if your forecasts are predictive or just historical.
Answer framework: Committed + forecast + risk — separate what’s locked, what’s expected, and what’s uncertain.
Example answer: “I break the forecast into committed costs (contracts, POs), expected costs for unbought scopes, and risk allowances tied to a live risk register. Each month I reconcile actuals, update commitments, and re-forecast remaining work based on progress and productivity signals. I also write variance commentary that explains ‘why’ and ‘what we’re doing next,’ not just ‘up/down.’”
Common mistake: Treating EAC as ‘actuals plus a guess’ without a method.
Now the failure scenario—because it happens.
Q: What do you do if your cost system or shared drive goes down right before a client cost report is due?
Why they ask it: They’re testing resilience, controls, and whether you can still produce defensible numbers.
Answer framework: Fallback–Validate–Communicate.
Example answer: “First I switch to my last exported dataset—previous month’s report, the latest commitment log, and any locally saved CO trackers—so I can produce a controlled ‘best available’ update. Then I validate the few high-impact codes manually with PMs and key subs to avoid reporting a false trend. Finally, I communicate early: what’s confirmed, what’s provisional, and when the final reconciled report will follow once systems are restored.”
Common mistake: Going silent and missing the reporting deadline without a controlled interim.
And yes—regulation and certification awareness matters, even if the role isn’t a regulated title everywhere.
Q: Are you pursuing (or do you have) PQS with CIQS, and how does that show up in your work?
Why they ask it: They’re checking commitment to Canadian professional standards and structured competency.
Answer framework: Status–Competencies–Application.
Example answer: “I’m working toward PQS through CIQS, and I’m using the competency framework to document experience across estimating, procurement, and contract administration. Practically, it’s pushed me to be more systematic: measurement rules, audit trails, and consistent reporting formats. Even when a project is chaotic, I keep the documentation clean so decisions are defensible.”
Common mistake: Treating certification as a badge instead of a practice standard.