Respond to an inquiry about returning after suspension

A student reaches out days before a suspension ends and asks the one question you cannot answer, whether they will be allowed back in. The fear behind that question is real, and so is the pull to say something reassuring. As a retention advisor, your job is not to predict a conduct decision. Your job is to hand the student a clear path to the process that actually makes that call, and to help them walk it without confusion.

Why This Conversation Goes Wrong

Students in this spot are often scared, embarrassed, or angry, sometimes all three in the same sentence. They want certainty, and they want it now. That pressure pushes advisors toward two bad habits. The first is guessing at an outcome to calm the student down, saying something like "you'll probably be fine" when you have no authority over the decision. The second is promising to speed up a process you do not control, telling the student you will get the conduct office to move faster.

Both habits feel kind in the moment and cause real damage later. If the student is denied return after you hinted it would be fine, they remember exactly who told them otherwise, and the institution loses credibility it needs for the next hard conversation. If you promise to push the timeline and nothing changes, the student now distrusts your office along with the conduct office. Neither habit gets the student closer to what actually helps, which is knowing the steps in front of them and taking the first one.

How to Prepare

Before you take a call like this, get a few things straight in your own head.

1. Know exactly where the return process is documented, and know which office owns the final decision. You should be able to point to the page or the notice language without hunting for it live.
2. Know the boundary between what you can discuss and what belongs to the conduct file. You should never ask a student to share more case detail than they volunteer, and you should not repeat or speculate about details even if the student brings them up.
3. Know how to help with the mechanics, reading a notice for required steps, drafting a meeting request, finding the right contact for scheduling.
4. Know the policy on advisors or support persons attending meetings with the student, so you can answer that question directly instead of guessing.

This kind of preparation is the same discipline that makes other education conversations go well. If you have practiced how to stay inside your lane while still being useful, you already have the muscle for this one. The same logic shows up when you Run a roster sync discovery conversationwhere the advisor gathers facts and hands off to the right system instead of guessing at technical causes.

What to Say

Marcus writes in and says, "My suspension is supposed to end next month. Can you just tell me if I'm getting back in, and can you get the conduct office to move faster."

Dana replies, "I can walk you through the return process and help you get ready for your meeting with the conduct office. What does your notice say about the date, and has anyone given you instructions for requesting to return."

Marcus explains that the notice mentions a meeting, but he has not scheduled it yet.

Dana says, "The conduct office decides on returns, so I cannot tell you what they will decide, and I cannot change their timeline. Here is what we can do right now. We can go through your notice together and pull out the required steps. We can write down the questions you want to ask at that meeting. We can also find out exactly who handles scheduling so you are not guessing. If you want to bring an advisor or a support person, the office can explain how that works. Do you want to start by drafting the meeting request."

Marcus agrees, and they draft the email together, line by line, until it names a specific date range and asks a specific question about the process.

Notice what Dana did not do. She did not soften the seriousness of the process, and she did not offer false comfort. She turned a vague fear into one concrete action, sending a meeting request, and she pointed Marcus to the office that owns the answer he actually wants.

Mistakes to Avoid

A few patterns show up again and again in these conversations, and each one costs you trust.

1. Predicting the outcome, even in soft language like "I think you'll be okay." That sentence sounds supportive and reads as a promise.
2. Asking for case details the student has not offered. You do not need to know what happened to help someone find the return process.
3. Offering to intervene with the conduct office's timeline. That office runs on its own schedule for reasons you do not control and should not undermine.
4. Treating the student's fear as a problem to soothe rather than a signal to act on. Sympathy without a next step leaves the student exactly where they started.
5. Ending the conversation without a concrete task. A student who leaves with an email drafted or a meeting scheduled is in a different position than one who leaves with reassurance and nothing else.

How to Practice and Score It

This conversation rewards rehearsal because the wrong words come out fast under pressure. Set up a practice scenario with a fictional suspension notice that includes a return date and a required meeting. Play the student and push for a direct answer about the outcome, then play the advisor and notice how tempting it is to give one.

Score the practice run on four things. Did the advisor ask what instructions the student already has before describing next steps. Did the advisor avoid any language that predicts or implies an outcome. Did the advisor stay out of case details the student did not raise. Did the conversation end with one specific action, a drafted email, a named contact, a scheduled meeting.

A manager reviewing these calls should read the transcript back and flag any sentence that sounds like a guess dressed up as encouragement. That single habit, catching soft predictions before they leave your mouth, separates advisors students trust from advisors students later feel misled by. DealSpeak sessions built around this scenario let you run the exchange repeatedly until the boundary between support and prediction becomes automatic, which matters more than it might seem the first time you try it live.

If you want more scenarios built for this kind of boundary work, the library of Education practice conversations covers related situations, including how to Scope a safety credential request with clear boundaries.

Closing

Students in this situation are not asking for false hope, they are asking for a way forward. Give them the process, not a prediction, and the fear in the room turns into a task list they can actually complete. That shift, from uncertainty to action, is the entire job.