Explain a program format change after an application

An applicant who asks to switch from an online cohort to a campus section is not testing you. Their work schedule changed, or a childcare arrangement fell through, and now the program they applied for does not match their life anymore. You are the first person they reach, and what you say in the next few minutes decides whether they trust the process or start calling other schools. Handle this well and you turn a scheduling problem into a clear form and a clear timeline. Handle it badly and you either promise a seat you cannot deliver or leave the applicant feeling like their request disappeared.

Why this conversation goes wrong

Two mistakes show up again and again. The first is overpromising. An advisor hears that an evening section has open seats and tells the applicant they are basically in. Capacity changes by the day, and the program office, not the advisor, decides who fills a seat. When that seat closes before the applicant's file gets there, the advisor looks like they lied.

The second mistake is the opposite problem, an answer so vague and procedural that the applicant learns nothing. Saying only that the request will be reviewed tells the applicant nothing about who reviews it, what they look at, or when they will hear back. Applicants in this situation are usually anxious about a real deadline, a start date they promised their employer or their family. Vague answers read as avoidance even when they are not meant that way.

There is a third trap that is easy to miss. Format changes often get tangled up with admission decisions in the applicant's mind. Maya does not just want a different schedule, she wants to know if switching sections will delay her acceptance. Those are two different processes handled by two different offices, and if you answer the admission question as though it were the same as the format question, you set an expectation the admission office may not meet.

How to prepare

Before you pick up the phone or open the chat, know three things cold. Know which office owns format change decisions for the program in question, since it is rarely the enrollment team alone. Know what information that office needs to evaluate a request, typically the applicant's identifier, current section, requested section, and the reason for the change. Know the current published timeline for a decision, not a guess, the actual number of business days the office has committed to.

If you do not know current seat counts for a specific section, say so plainly instead of estimating. An empty seat today can be gone tomorrow, and applicants remember the number you gave them, not the caveat you meant to attach to it. The same discipline applies whenever you touch recommendation letters or any other piece of the file you do not personally control, name the owner, do not guess the outcome.

What to say

Maya opens with the real problem. She says, "I applied for the online cohort, but my employer just changed my shift. Is there any way to move me into the campus section starting in January?"

Leon does not answer the capacity question yet. He gathers what the program office will need first. He says, "I can get the right request moving for you. Which campus and which meeting times would actually work with your new shift?" Maya names an evening section that meets twice a week.

Leon separates what he knows from what he does not. He says, "The program office reviews format change requests against section capacity and the requirements tied to your specific cohort. I do not have the current decision on seats in front of me, so I am not going to guess. I will confirm the exact request form and check with the program office on what else they need from you." Maya asks the question underneath her question, whether this will push back her admission decision.

Leon keeps the two processes apart instead of blending them. He says, "Admission review and section placement go through separate steps, and I do not want to give you an answer on one that actually belongs to the other. I will send you the current contacts for both, and I am keeping this request attached to your application file so nothing gets lost."

Notice what Leon does not do. He does not name a seat count. He does not promise a specific outcome. He does not brush past Maya's real question about timing. He answers the part he owns, names the part he does not, and commits to a specific next step.

Mistakes to avoid

Do not treat an open seat as a private promise to one applicant. Seats fill on a schedule you do not control, and the applicant will hold you to whatever number you say out loud.

Do not answer an admission question with a format answer, or the reverse. They are different reviews, often run by different staff, and applicants deserve to know that rather than getting one tidy answer that quietly covers both.

Do not send the applicant away without a specific next step. "Someone will be in touch" is not a commitment. Name the office, name the form, name the date the applicant should expect to hear something.

Do not let the file go quiet after you submit the request. If the program office needs something further from the applicant and days pass with no response, you are the one who has to close that loop, and the approach in reengaging a student who has stopped responding applies just as much here as it does earlier in the funnel.

How to practice and score it

Run this as a role play before it happens for real. Have a partner play an applicant whose work schedule just changed and who wants a section switch before a hard deadline. Your job is to ask three concrete questions, the format they want, the timing they need, and the constraint driving the request. Then explain who reviews the request in one clear sentence, no hedging, no jargon.

Score the attempt on one thing above all else, whether the response keeps the applicant's request separate from the institution's decision. A strong answer names the review owner, names the information that office needs, and gives a real date. A weak answer either promises an outcome the advisor cannot control or drowns the applicant in procedure without ever saying who decides or when.

Before you send a written follow up, read it back once. Check that it names an office, a form, and a date, and check that nothing in it reads like a guarantee. A manager reviewing your calls can use the same three checks, own the request, do not guess, name the next step.

DealSpeak's education practice conversations let you rehearse exactly this kind of exchange with an AI applicant before you face a real one, and get scored against these same standards. Practicing the separation between what you control and what the program office controls is the fastest way to sound calm and specific the first time it actually matters.

What good looks like

A format change is a logistics problem for the applicant and a policy question for your institution. Keep those two things separate, name the office that owns the decision, and give a real date instead of a hopeful one. Do that consistently and applicants stop worrying about whether you heard them, because you already showed them you did.