Discuss a program change after an application

An applicant who asks to switch programs after submitting materials is not trying to trick you. Their curiosity changed after they hit submit, and now they want speed. Your job is to treat the request seriously while keeping the actual decision with the people who own it, admissions staff, program advisors, and academic departments that set their own requirements.

Why this conversation goes wrong

Advisors want to help, and that instinct can push them past their authority. When an applicant sounds excited about a new major, it is tempting to say yes on the spot, or to imply the switch will happen automatically once you note it in the file. Neither is true. Programs differ in prerequisites, cohort size, and review timing. A computer science program might require a portfolio or a placement test that business never asked for, and it might already be close to capacity for the term the applicant wants. If you promise an easy switch and the review later comes back with conditions or a denial, the applicant feels misled, and the institution looks like it does not know its own rules. The opposite failure happens just as often. Some advisors get defensive, treat the request as a hassle, and shut it down without asking why the applicant changed direction. That reaction misses a real chance to learn something about the applicant's fit, and it makes the advisor sound like a gatekeeper instead of a guide.

How to prepare before you respond

Before you say anything, know the shape of the two programs the applicant is comparing. Pull up the prerequisites, deadlines, and any supplemental materials the new program requires that the original one did not. Know who owns the switch, whether that is admissions, the registrar, or a specific program coordinator, and know the exact form or process that starts a formal review. Have contact information for a program advisor ready, because a short conversation with someone who actually teaches in that department will do more for the applicant than anything you can offer from the enrollment side. Decide in advance what you can confirm today, such as that the request has been logged and sent for review, and what only the review committee can confirm, such as whether a seat is open or whether the applicant's current coursework satisfies the new prerequisites. Keeping those two categories separate in your head keeps you from mixing them out loud when the applicant is pressing you for a fast answer.

What to say

Start with the request itself, then ask about the reason behind it before you talk process. Maria tells her advisor, Priya, "I applied to the business program, but now I want computer science instead. Can you make that change today so I still get considered for fall." Priya answers, "I can pull up the change request process right now and walk you through it. What got you interested in computer science after you applied." Maria explains that she sat in on a friend's coding class and liked it more than she expected. Priya says, "That is worth exploring further. Computer science has different prerequisites and a separate capacity review, so I cannot confirm a switch today. Let us compare what the program requires against what is already in your file, then I will send the formal request to admissions this afternoon. A program advisor in computer science can also walk you through the coursework before you commit to anything." Maria asks how to reach that advisor, and Priya sends her the booking link before the call ends.

Notice what Priya did not do. She did not say the switch was easy, and she did not say it was impossible either. She separated the two actions buried inside the request, filing the change and learning about the program, and she named the specific people who own each one. That gives Maria a real next step instead of a vague promise she will have to chase down later.

Mistakes that undermine trust

The most common mistake is speaking for a committee you do not sit on. Saying something like "you should be fine" about acceptance or seat availability sets an expectation you cannot back up, and it puts the institution in a bad spot when the actual answer differs. A second mistake is treating the applicant's shifting interest as suspicious rather than normal. People learn more about a field after they apply to it, and that curiosity is a sign of engagement, not flakiness, so do not make the applicant feel like they did something wrong by asking. Third, do not let the conversation stay abstract. If you do not name a specific form, a specific contact, and a rough timeline, the applicant leaves with nothing to act on and calls back in a week asking what happened to their request. Fourth, avoid comparing the two programs in a way that sounds like your personal opinion. Your job is to relay the published requirements, not to tell the applicant which major is smarter or pays better.

How to practice and score this conversation

Run this scenario with a fictional applicant whose second choice program has a requirement the first one does not, a portfolio, an interview, or a placement exam. Ask one question about what changed their mind and one question about whether they meet the new requirement. Watch your own answer for two things. Did you name the actual form or process that starts the review, and did you name a real contact for program specific questions. If your practice response ends without either of those, it was too vague to help anyone. Then check the opposite failure, whether you predicted an outcome you do not control, such as acceptance, available space, or how existing credits will transfer. If you said any of those would definitely happen, mark it as a miss and run the exchange again until you can stay inside your authority without sounding cold.

DealSpeak is built for this kind of rehearsal. You run the scenario above against an AI counterpart, get scored on whether you stayed inside your authority, and repeat it until naming the form and the contact becomes automatic instead of something you have to think through live under pressure. The Education practice conversations hub has more scenarios built around the same kind of boundary, including how to explain a program format change after an application and how to guide an applicant who asks about recommendation letters.

A program change request is not a crisis. It is a normal part of how people apply to school, and most applicants just want to know what happens next. Handle it by naming the real process and the real people who run it, and let the applicant make an informed choice instead of a rushed one.