What Your Advisor Expects You to Get Out of a Conference
A conference trip is an investment your advisor makes in you. Here is what they actually expect you to come back with.
Most advisors never spell this out, so here it is plainly. Sending you to a conference costs real money from a grant, and that money has an opportunity cost measured in equipment, other students, and your advisor’s time. When they approve the trip, they are making an investment in you and expecting a return. The return is almost never “you attended every session.” It is what you bring back.
If you are reading this before your first trip, the companion piece on what to expect as a first-time attendee covers the logistics. This post is about the part that actually matters to the person funding you.
“It was good” is not a trip report
The single most common failure is coming back with nothing specific to say. “It was good, I learned a lot” tells your advisor the investment did not pay off, or that you cannot articulate why it did. Either way it is a bad signal.
Your advisor wants concrete returns. Here are the five they care about most.
1. Specific work you didn’t know about
You should come home able to name three or four papers, talks, or posters that are directly relevant to your project or the lab’s direction, and say why they matter. Not “there was a lot of interesting work on diffusion models.” Instead: “Group X showed a result that makes our approach in chapter three weaker, and here is the citation.” That sentence is worth the airfare.
2. People, not just papers
Conferences exist because the hallway and the poster session are where research actually moves. Your advisor expects you to talk to people, and especially to the people whose work you cite. Walk up to a poster, say you have been building on their method, ask the question you could not answer from the paper. Most senior researchers are generous with five minutes. The students you meet at your first conference are the reviewers, collaborators, and hiring committees of the next decade.
If your advisor knows people at the venue, they will often offer introductions. Take every one of them. An introduction from your advisor is a door that will not be open later.
3. A sense of where the field is going
You have a vantage point your advisor does not have on this specific trip. They want your read on the room. What is everyone suddenly working on. What got abandoned. Which problems people argued about at dinner. What the senior people seemed worried about. This is the kind of signal that shapes what the lab works on next, and they are sending you partly to collect it.
4. The lab represented well
If you are presenting, your talk or poster is the lab’s reputation in that room, not just yours. Advisors expect you to have practiced, to handle questions without getting defensive, and to be the person who is pleasant to talk to at the poster. If you are not presenting, you still represent the group every time you ask a question in a session or introduce yourself. This is not about being impressive. It is about not being the reason someone remembers the lab poorly.
5. Follow-up that actually happens
This is the step almost everyone skips, and the one advisors quietly notice. The value of a conference is realized in the two weeks after it, not during it. The email you send to the person whose poster you liked. The paper you actually read because someone recommended it. The introduction you make good on. A conference where you followed up on three things is worth more than one where you attended thirty talks and emailed no one.
What your advisor does not expect
Worth saying clearly, because anxiety about this is common and counterproductive:
They do not expect you to understand every talk. Nobody does. Sitting in a session on a subfield you do not work in and grasping the high-level question is a perfectly good outcome.
They do not expect you to network the entire room. Three real conversations beat thirty business-card exchanges. Introverts do not need to become extroverts for four days.
They do not expect you to skip sleep, skip meals, or push through serious jet lag to attend a 9am session on day three. You are not useful exhausted, and they know it.
They do not expect you to have everything figured out. You are there to learn what the field looks like up close. That is the point.
The checklist
Save this. Send it to your students. It is built to be the thing you link instead of writing the email every year.
Before you go
- Read the program and mark the talks and posters that matter for your work, not just the famous names
- Make a short list of people whose work you cite who will be there, and where to find them
- Ask your advisor who they know at the venue and whether they will make introductions
- If you are presenting, practice the talk out loud at least twice, and have answers ready for the three hardest questions
- Have a one-sentence and a one-minute version of what you work on, ready before you land
- Book early so you are near the venue and not commuting an hour each way. WorkWander’s conference pages list curated hotels near each venue
During the conference
- Go to at least one poster session with the intent to talk, not browse
- Introduce yourself to two people whose work you actually know, every day
- Take notes you will understand in a month, organized by “relevant to my project” and “relevant to the lab”
- Write down names and what you said you would follow up on, immediately, not from memory later
- Eat with people you do not know when you can. Dinners are where the real conversations happen
- Protect enough sleep to be coherent. A tired day three is wasted money
After you are back
- Send the follow-up emails within two weeks, while they still remember you
- Write a short trip report for your advisor, even if they did not ask for one
- Actually read the two or three papers people recommended
- Tell the lab, in a meeting or a message, the three things that surprised you about where the field is going
The trip report
A short written report is the deliverable that signals you understood the assignment, even when no one asked for it. Half a page is enough. What was relevant to your project. Who you talked to and what came of it. What the field seemed to be moving toward. What you are going to do differently because of the trip.
It takes twenty minutes and it is the clearest possible evidence that the investment paid off. Advisors remember the students who write them.
The short version
A conference is not a reward and it is not a vacation with a badge. It is a research instrument your advisor is paying to point at the field on your behalf. Come back with specific work, real conversations, a read on where things are going, and follow-up that you actually do. That is the whole job, and it is very doable.
If you are choosing which conferences are worth this effort in the first place, the CORE rankings explainer is a good place to start, and the full conference calendar lets you plan the year around the venues where your community actually gathers.