When an interviewer asks “How do you respond when plans change at the last minute?”, the short answer they hope to hear is: you find out what has actually changed, re-plan around what is now fixed, tell the people affected, and deliver the version that is still possible. This article answers the questions candidates most often have about this question, from what it tests to what to say when the change was a mess.
What is the interviewer really testing?
Adaptability, but a specific kind of it. The Canada Revenue Agency publishes the competencies it assesses candidates against. It defines adaptability as “showing openness to change and altering behaviours in order to work effectively” when faced with new information or a changing situation. Its lowest-level indicators include obtaining “necessary information or clarification in order to understand the change”. At higher levels, they include adapting plans and processes and shifting priorities in response to new risks.
The UK Civil Service behaviours contain related indicators. Under “Changing and Improving”, junior staff are expected to “respond in an effective and appropriate manner when emergencies arise”. Under “Delivering at Pace”, staff at HEO and SEO grades are expected to “act promptly to reassess workloads and priorities when there are conflicting demands”.
Put simply, they are checking three things: do you get clear on the change before acting, can you rebuild a plan quickly, and do you keep quality and communication going while you do it?
Is this a “tell me about a time” question or a “what would you do” question?
It can be either, and the way you answer differs. The US Office of Personnel Management describes the two types: situational questions ask what you would do in a job-like scenario, and behavioural questions ask you to describe what you did, on the basis that past behaviour predicts future behaviour.
- If it is phrased “How do you respond…”: give your approach in three or four sentences, then offer a short example. A general answer with no example is hard to score.
- If it is phrased “Tell me about a time…”: lead with the story and let your approach show through what you did.
What should the answer include?
Four moves, in this order:
- Clarify. What exactly has changed? What is now fixed (the deadline, the budget, the client’s must-haves) and what can be adjusted? This takes minutes, and it stops you re-planning around a rumour.
- Re-plan. Decide what to drop, delay or do differently. Say the trade-off out loud: “We kept the core report and moved the appendix to the following day.”
- Communicate. Tell everyone affected what is changing for them, including people who aren’t in the room, before they find out some other way.
- Deliver and debrief. Finish the new version, then note one thing that would make the next late change easier.
The STAR pattern (situation, task, action, result) carries these moves well. Most of the time should go on the action, because that is where the four moves happen.
What does a good answer sound like?
The three answers below are illustrative. They show the moves in different settings, and none is a real candidate’s answer.
Event coordinator
“Two hours before a client workshop, the venue told us the main room was flooded. First I confirmed with the venue manager what was still available: a smaller room with fewer seats. Then I asked the client contact which sessions were essential. We kept the morning plenary in the smaller room and moved two breakout sessions to video calls. I messaged every attendee with the new room and links within half an hour, and told the caterer to change the setup. The workshop started fifteen minutes late. Afterwards I added a backup-room clause to our venue checklist.”
Junior software developer
“On the day before a release, product asked us to drop a feature for legal reasons. Before touching the code, I asked whether they needed it removed or just hidden, because that changed the risk a lot. Hidden was enough. I put it behind a feature flag, the tester re-ran the affected tests, and I updated the release notes so support wouldn’t promise the feature to customers. We released on time. Since then I’ve suggested building risky features behind flags from the start.”
Retail team member
“Our store manager called in the morning to say a regional visit had been moved forward to that afternoon. Two colleagues were off sick. I checked with the supervisor which areas the visitor would focus on, which turned out to be the promotion displays and the stockroom. We left a lower-priority shelf reset for the next day, and I took the stockroom while a colleague finished the displays. I told the person on the tills that we’d be short on the shop floor for an hour, so she could call for help if a queue built up.”
Each answer clarifies before acting, names what was dropped or delayed, and tells the people affected. None of them claims that nothing was lost.
What should I avoid saying?
- “I love change, it never bothers me.” This is hard to believe, and it doesn’t show a method.
- “I just work longer hours until it’s done.” Effort is fine, but on its own it suggests you can’t re-plan. Long hours also aren’t always possible.
- Blaming whoever made the change. Even if the change was poorly handled, keep the focus on your response.
- Re-planning alone and in silence. If your story has no step where you tell anyone, the panel will notice.
- Quietly lowering quality. If something had to give, say so openly and explain who agreed to it.
How is this different from related questions?
Several common questions sound similar, and if you are asked more than one of them, you should use different examples.
| Question | Focus |
|---|---|
| Last-minute changes | Speed of re-planning and communication when a fixed plan breaks |
| Change you disagree with | Raising concerns properly, then committing to a decision |
| Handling stress and pressure | How you stay effective personally under a heavy load |
| How you prioritise | How you rank work in a normal week |
| Handling interruptions | Protecting focus from frequent small disruptions |
If you disagreed with the late change, you can mention it in a single sentence (“I raised the risk with my manager, then got on with it”). Then return to the four moves.
What if my example didn’t go perfectly?
That is often better than a story where everything went perfectly. Late changes usually cost something, such as a delay, a smaller scope or an unhappy stakeholder. Say what was lost, why that was the right thing to give up, and what you changed afterwards. The CRA’s higher-level adaptability indicators include preparing for change and adapting processes, so a debrief that leads to a checklist, a backup plan or a new habit fits what assessors are looking for.
Which roles ask this most, and how should I adjust?
- Project and operations roles: stress the re-planning and the stakeholder updates. Showing how a schedule or scope was rearranged is strong evidence. If this is your field, the project manager resume builder shows how to word this kind of achievement on a CV.
- Hospitality, events and retail: stress speed, keeping customers informed, and dividing work among the team.
- Healthcare and other safety-critical roles: make it clear that the re-plan stayed within protocols, and that you escalated anything outside your authority.
- Technical roles: stress understanding the real requirement before changing anything, and controlling risk through testing, release notes or rollback plans.
How do I find a good example?
Look back over the past year for any time a date moved, a client changed a brief, a colleague was absent at short notice, a supplier failed, or a system went down. Write each one as a single line, then pick the one where you can name a specific trade-off and a specific person you informed. If you are early in your career, a group project where a team member dropped out the week before submission is a fair example. The resume questions hub has more prompts for turning past experience into application material.
Frequently asked questions
Can I say I find last-minute changes frustrating?
Yes, briefly, if you move straight on to what you did. One honest sentence (“it was frustrating because we’d already printed the packs”) makes the answer more believable. A whole paragraph of complaint does the opposite.
What if the change was caused by my own mistake?
That is a different question: how you handle being wrong. Choose an example where the change came from outside, such as a client, a manager, a supplier or a regulator, so that the answer shows adaptability rather than damage control.
Is it acceptable to use a personal example?
Use a work, study or volunteering example if you have one. A personal example, such as a travel plan that fell apart, can work for a first job, but keep it short and connect it to how you would act at work.
How long should my answer be?
About a minute and a half to two minutes for a past example. A hypothetical answer can be shorter, around a minute, followed by a brief example if you have one.
Sources
- Adaptability (CRA candidate assessment), Canada Revenue Agency (Canada.ca)
- Success Profiles: Civil Service behaviours, UK Cabinet Office (GOV.UK)
- Structured Interviews, US Office of Personnel Management
- The STAR method, National Careers Service (UK)