Support a commuter student facing a lab transportation barrier

A single weekly lab turns a minor transportation problem into an academic emergency. Miss one session and a student falls behind on skills the rest of the course depends on. Miss two and the whole term is at risk. A retention advisor sits in the middle of this problem without holding the levers that actually fix it. You cannot excuse a lab. You cannot promise a ride. What you can do is connect the student to the two people who decide those things, and do it before the next lab meets.

Why this conversation goes wrong

Retention advisors want to help right away, and that instinct works against them here. A student tells you the bus keeps letting them down, and the easy response is to offer a fix on the spot. Maybe you mention a shuttle program you heard about once, or tell the student the instructor will surely understand. Both answers feel kind in the moment, and both are wrong. You do not decide whether a lab requirement bends, and you do not decide who qualifies for transportation help. If you sound like you have already solved the problem, the student stops chasing the people who actually hold those decisions, and the days keep passing.

There is also a time pressure that makes this worse. A lab that meets once a week means every day you spend gathering information instead of connecting the student to someone with authority is a day closer to another missed session. That pressure pushes advisors toward shortcuts, like sending an email and assuming that counts as done, instead of making sure the student actually calls or walks over the same day. The urgency is real, but it argues for speed toward the right people, not speed toward a promise you cannot keep.

The other common failure is treating the conversation as finished once the student feels heard. Empathy matters, and a student should leave your office knowing someone took the problem seriously. But a student who feels comforted and still has no plan for the next lab has lost ground, not gained it. This conversation only works if it ends with two names, two contacts, and a written record of what has already happened.

How to prepare

Know your institution's structure before the student sits down. Know which office owns lab attendance policy, usually the program coordinator or the instructor teaching the course. Know which office reviews transportation support, usually a basic needs office or a dean of students. Write down how a student reaches each one the same day, not next week. If you have to search for this while the student waits, you have already lost time that cannot be recovered.

Pull up a calendar before you start, or ask the student to open their course schedule on their phone. You need the exact date of the next required lab, not a general sense of how often it meets. A lab that meets every Thursday and has already been missed twice is a different problem than a lab that meets again in ten days. The date tells you whether you are handling a same day emergency or something you can work through over the next few days.

The basic needs office likely has its own rules for transportation help, things like a cap on how many requests a student can make in a term, or a deadline for applying before the semester is half over. You do not need to memorize every rule, but you should know that rules exist, so you never speak as though the office will simply say yes.

Decide in advance what belongs to you and what does not. You gather facts and you make referrals. You do not judge whether the transportation problem is real, and you do not guess what an instructor will decide about a missed lab. Hold that line in your head and it stays out of your mouth.

What to say

Noah opens with the request most students lead with. "My bus keeps missing my stop and I am stuck. Can the lab get excused, or can the school pay for rides so I stop missing it?"

Advisor Celia does not answer either question yet. "I hear how much this is putting your course at risk. When does the lab meet next, and have you told the program coordinator what has been happening?"

Noah explains that the lab meets every Thursday, only once a week, and he has not told anyone yet because he thought the bus problem would sort itself out.

Celia lays out the two paths without promising either one. "The program sets the lab requirement, so the coordinator and your instructor are the ones who can explain your options for this term. The basic needs office also reviews transportation support, and they know their own eligibility rules better than I do. I can help you reach both today, and I will write down every date you have missed so you walk in with a clear record instead of a vague story."

Mistakes to avoid

A few habits sink this conversation more than any other.

1. Promising a lab exception or a funded ride before anyone with actual authority has looked at the case. You are not the decision maker, and sounding like one sets the student up for a letdown.

2. Skipping the exact date of the next lab. Without it, you cannot tell the student, or yourself, how urgent this really is.

3. Letting the student leave without a written list of missed dates. Instructors and coordinators respond to specifics, not a general sense that things have been hard.

4. Stopping the conversation after one referral. Send the student to the coordinator and to the basic needs office in the same conversation, not one now and one later. Waiting costs another lab session.

How to practice and score it

Run this scenario before you meet a real student like Noah. Build a calendar with one lab meeting a week and give yourself a case where the student has already missed one session. Practice asking for the next required date before you name a single resource. That order matters. Naming a resource first signals that you already have a solution, and it pulls the conversation away from the facts you still need.

Score your own performance, or a colleague's, against three things. Did you get the exact date of the next lab before offering help. Did you avoid promising an excused absence or funded transportation. Did the conversation end with two named contacts and a written list of missed dates, not just a sympathetic exchange.

DealSpeak's Education practice conversations hub gives retention teams more scenarios built the same way, including how to Design a tuition benefit partnership around real eligibility and how to Guide a veteran through credit and benefit questions. Running through a few of these before the real conversation happens builds the habit of separating what you can offer from what only another office can decide.

What good looks like

A strong version of this conversation does not solve Noah's transportation problem in the room. It gets him talking to the coordinator and the basic needs office before Thursday, carrying a written record that makes both of those conversations faster and more specific. That is the whole job for a retention advisor here. Get the facts, name the right people, put the record in the student's hands, and stay out of decisions that were never yours to make in the first place.