Control it with a baseline and a documented change path, not with willpower. Get scope written down and signed off, then route every new request through a change request that states cost, schedule impact, and what gets displaced. Most creep is not malice, it is small additions nobody prices. Making the cost visible each time turns an argument about saying no into a decision the sponsor owns.
Why interviewers ask this
Scope creep is the most common way projects quietly fail, so the interviewer wants a mechanism rather than an attitude. They listen for a baseline you can point back to, a change process light enough that people actually use it, and the discipline to price every request rather than absorbing the small ones. They also want the sponsor making the call, since a project manager who unilaterally refuses work gets routed around within a month.
How to structure your answer
- Start with a written, signed baseline including an out of scope list.
- Route every request through a priced change log.
- Present cost, schedule impact, and what gets displaced.
- Give the decision to the sponsor rather than refusing it yourself.
Example answer
I control it with a baseline and a change path, because you cannot control it by being strict in meetings. At the start I get the scope written down in a form the sponsor actually signs, including a short out of scope list, which is the part people skip and the part that does all the work later. Then every new request goes on a change log, and I price it with the team: how many days, what it does to the critical path, and what comes out to make room. I take that to the sponsor as a decision rather than a refusal. What changed things for me on one program was making the change log a standing item in the weekly steering meeting. Once people saw a running total of days added by their own requests, the requests slowed right down without me having to say no to anyone.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksFollow-up questions to expect
- What do you do when the request comes from the person paying for the project?
- How do you handle small changes that individually look free?
- How formal should change control be on a six week project?
Related project manager questions
Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions