The following is generated by AI with key points supplied by me.
Weekly one-on-one meetings with your PhD advisor are a cornerstone of steady research progress. In computer science (and other fields), these regular check-ins serve as crucial “checkpoints” to ensure you and your advisor stay aligned on goals and issues. In fact, a PhD thesis can be seen as “a culmination of hundreds of weekly meeting updates stitched together,” with each week’s progress contributing a small piece to the final dissertation. Below, we summarize expert advice and proven strategies to help you prepare effectively for your weekly progress meetings.
Start preparing early. Don’t wait until the last minute to think about what to discuss. A common recommendation is to decide on the key points – results, questions, and topics – at least two days before your meeting. Spend time reviewing your recent work: gather data, code, figures, ideas, and any questions that arose during the week. This reflection not only helps you identify progress and problems, but also ensures you won’t forget important details.
Create a concise meeting agenda or slide deck. Writing down an agenda focuses your thoughts. Include the main updates and issues you want to cover. For example, one professor advises his students to prepare an agenda document “with figures, updates, [and] questions” the evening before and add it to a shared space (e.g. a Notion page). This gives you “ample time to collect [your] thoughts” and prevents the meeting from devolving into “oh, I forgot to mention that” moments. Some students use a single evolving slide or a short 3–5 slide presentation highlighting the week’s work – primarily visuals like graphs or diagrams to quickly recap progress. Keep it simple and avoid text-dense slides; the goal is to remind your advisor of what you’ve been doing and set the stage for discussion.
Send the agenda or materials ahead of time. Whenever possible, share your agenda, slides, or any write-up with your advisor before the meeting. This might mean emailing it a day in advance for a weekly meeting (or ~3 days ahead if the meetings are less frequent). Providing a brief written update or document beforehand gives your advisor a chance to read and digest your progress. As a result, they can come to the meeting prepared with feedback or ideas, making the face-to-face time more productive. Even a short bullet-point email can help ensure “everyone is aligned” on the agenda. Sharing materials in advance also demonstrates professionalism and respect for your advisor’s time.
Tip: If you’re working on code or experiments, consider sharing links instead of raw outputs. For example, upload code to a repository (e.g. GitHub) and include the link, or put large data sets and preliminary results into a Google Sheet with graphs. Likewise, if you’ve started writing any part of a paper or thesis, share that draft (many advisors encourage writing during research, not just after). Ensuring your advisor has access to these materials (with proper permissions) ahead of the meeting can save time and facilitate detailed feedback.
Having a clear structure for the meeting discussion is key. A well-organized agenda keeps the conversation focused and ensures you cover all the important points. Many sources recommend a basic template for one-on-one meetings with advisors:
Recap of Last Meeting & Action Items: Begin by refreshing what happened last time. Don’t assume your advisor remembers all the details – they likely supervise multiple projects. Take 2–3 minutes to summarize the previous meeting’s key points and the tasks or goals you agreed on. One experienced student suggests doing this in “3-4 sentences” at the start: remind everyone what you were supposed to accomplish since the last meeting. This closes the loop on past items and shows accountability. If you had specific to-dos or experiments to run, report on their status first.
Progress Since Last Meeting: Next, detail what you have done in the past week. Focus on tangible outcomes. Rather than just saying “I worked on X,” show evidence or give concrete summaries. For example, instead of saying “I read 5 papers,” present a short summary of each with key takeaways and how they relate to your work. In a few sentences or bullet points, cover what you did, what results or insights you obtained, and what didn’t work as expected. Aim to convey the impact of your work (e.g. “Implemented a new sorting algorithm; it improved runtime by 20% in initial tests”) rather than just the activity (“wrote some code”). This part can be 4–6 sentences long as a verbal update or a section of your agenda. If possible, bring something visual or tangible to supplement your update – for instance, a graph of results, a brief demo of a feature, or a snippet of output. This helps ground the discussion in concrete progress.
Questions & Challenges: After sharing your progress, discuss any problems, blockers, or decisions you’re facing. Be honest about challenges. If you hit a bug in your code, got confusing experimental results, or are unsure how to proceed on some aspect, flag it for discussion. This is where you tap into your advisor’s expertise. However, don’t come empty-handed on problems – try to propose a few possible solutions or approaches for each challenge. For example: “I’m stuck on achieving convergence in the model; I’ve tried A and B which didn’t work. One idea I have is to try C next – what do you think?” This proactive approach shows initiative and gives your advisor something specific to react to. Avoid simply saying “I have no progress” or “I’m completely lost” without context. Even if you feel stuck, you can always “show up with something” – outline what you’ve attempted and where you suspect the issue lies. Remember, being stuck is actually one of the best reasons to meet – it’s an opportunity to brainstorm with your advisor’s help. (As one professor put it, a student “unable to make progress is often the best reason to have a meeting”.) Use the meeting to get “unblocked” by asking specific questions.
Plans and Next Steps: Before concluding the meeting, define what comes next. Based on your recent results and the discussion, outline your plan for the next week (or until the next meeting). This might include new experiments to run, analyses to perform, sections to write, or papers to read. It’s wise to get explicit agreement on these action items with your advisor. Many advisors like to set concrete goals for the next meeting during the wrap-up. For example, you might say: “So for next week, I will implement the improved algorithm and test on dataset Y, and also draft the related work section.” Your advisor can confirm or adjust these targets. Don’t forget to consider long-term objectives too: some mentors suggest spending a few minutes connecting weekly tasks to the bigger picture (upcoming conference deadlines, thesis timeline, etc.). Regularly revisiting the high-level goals ensures you’re not losing sight of overarching milestones. Even a short discussion of how this week’s work moves you toward a publication or your thesis can be valuable. This forward-looking step helps both you and your advisor leave the meeting with a clear mutual understanding of expectations until the next check-in.
By following a consistent structure (past progress → current updates → issues → next steps), you make it easy for your advisor to follow along and provide input on each aspect. In fact, Dr. Joe Bathelt provides a sample meeting agenda with exactly these sections – “progress since the last meeting, questions/challenges, and plans”. Such a template ensures you don’t forget anything important.
Use templates or tools to stay organized. Consider keeping a dedicated document (or slide deck) for your weekly meetings. Some students maintain a running Google Doc or Notion page for meeting agendas and minutes, shared with their advisor. In this document, you can fill in your agenda before each meeting and later record key discussion points and decisions. Having a template with sections like Agenda, Discussion Notes, and Action Items can be very effective. Make space to jot down what your advisor says during the meeting (or right after) – for example, answers to your questions, new ideas or paper references they mention, and any agreed tasks or deadlines. This way, you build a written record of your progress and your advisor’s guidance over time.
Track your progress with a research journal. Many veteran students recommend keeping a daily or weekly research log. This is simply a habit of writing a few bullet points each day about what you worked on. It might seem trivial, but it serves multiple purposes: it helps you resume work quickly each day, keeps you motivated by showing that you are in fact making progress, and catalogs what worked and what didn’t. Critically, “at the end of the week, [you] can summarize the daily bullet points to update [your] advisor”. In other words, your daily notes become a cheat-sheet for preparing your weekly meeting report. It’s surprisingly easy to forget what you did just a few days ago – a brief log prevents that. Before your meeting, review your week’s notes to compile your accomplishments and select issues to discuss. Some students even bold or highlight major results in their notes to ensure those make it into the meeting agenda. Using apps or tools (like Notion, Evernote, or even a simple paper notebook) for this purpose can instill consistency.
During the meeting, take notes. Don’t rely on memory to recall your advisor’s advice or new tasks. Jot down key points either in your meeting doc or a notebook as you talk. Note down any feedback, suggestions, or references your advisor gives. Also write out the agreed next steps in clear terms. After the meeting, you can tidy these notes into a short summary.
Send a post-meeting summary. It’s a great practice to follow up after your meeting (within a few hours or by next day) with a brief email to your advisor summarizing what was discussed and listing your action items. This doesn’t have to be long – a few bullet points summarizing the decisions or advice and the plan going forward is enough. For example: “Summary of today’s meeting: 1) We decided I will do X and Y next; 2) You suggested checking paper Z for related work; 3) We identified issue Q with the experiment, which I will troubleshoot. By next meeting: I aim to complete X and prepare preliminary results from Y.” Such a recap helps ensure nothing was misunderstood, and it gives your advisor a written record to refer to. It also signals that you value the meeting and are acting on the guidance. As one guide notes, sharing an agenda beforehand and a summary afterward keeps meetings focused and everyone on the same page. It only takes a few minutes but greatly enhances clarity and accountability.
Leverage technology for efficiency. Besides shared documents, consider calendar tools and reminders. If your advisor is very busy or forgetful, a polite calendar invite for the meeting and/or a reminder email with the agenda can be helpful. Some students use project management or note-taking apps to organize topics over the week (for instance, adding questions to a list as soon as they arise so they’re ready by meeting time). The specific tools can vary – whether it’s a lab wiki, a Markdown notes file in a Git repository, or an online workspace – the goal is to make preparation and record-keeping as seamless as possible. The exact format matters less than consistency. Choose a system that you and your advisor are comfortable with (some advisors might even provide a template or prefer a certain format for updates).
Finally, if a week passes without an actual meeting (due to travel, etc.), you should still send a short written update. Many advisors appreciate a quick weekly email update in lieu of a meeting. This ensures continuous communication and can flag any concerns early. It’s essentially an asynchronous mini-meeting on paper.
Treat the meeting as a two-way conversation. Remember that your advisor is not there to micromanage a checklist of your tasks, but to mentor and collaborate with you. Approach the meeting with a mindset of getting feedback and guidance, rather than feeling you must just “prove you were productive.” In the words of one PhD student-turned-professor, “these meetings are for getting feedback… You put in your update and you get back feedback. The meeting is for your benefit.” In other words, use the time to ask questions, get advice, and brainstorm – things that will help move your research forward. Adopting this attitude can ease the pressure; you’re not going into a performance review, but a discussion to help you progress.
Be honest and proactive about problems. A common challenge is the fear of admitting lack of progress or confusion. However, hiding issues will only hurt you later. If an experiment failed or you had a unproductive week, don’t cancel the meeting or try to sweep it under the rug. It’s actually vital to still meet regularly even when progress is slow. Be frank about what didn’t work, and use the meeting to diagnose and overcome the issues. Advisors expect that research can hit dead-ends; what they want to see is your problem-solving process and willingness to discuss solutions. In fact, coming to a meeting with zero updates but a willingness to talk about a paper you read or a new idea you had is far better than not meeting at all. It keeps momentum and re-syncs your plan for the next week. Many advisors would prefer you say “I’m stuck on X – can we figure it out together?” than to go radio-silent. One faculty guide explicitly notes that students often mistakenly avoid meetings when stuck, whereas that’s precisely when a meeting can save you days by identifying an oversight or new approach.
Avoid last-minute cramming. Another pitfall is rushing to get “results” the night before your meeting. This can lead to sloppy work or data you don’t fully understand, and your advisor will notice if you seem unprepared to discuss what you present. It’s far better to plan your work such that you have something sensible to show, even if small, than to generate “random data… a few hours before the meeting that you have no clue about.” If you consistently prepare your thoughts and agenda ahead of time, you’ll break the cycle of scrambling to look productive. Remember, quality and clarity of discussion in the meeting matter more than sheer quantity of slides or experiments. As Prof. Biswabandan Panda puts it, “it is not important to showcase that you have done a lot… It is important to have a detailed, comprehensive discussion on the small things that you have done.” Your advisor is a collaborator, not just a supervisor – they are interested in understanding your work and thought process, not just checking off tasks. So help them help you by preparing thoughtful updates, even if they cover modest progress.
Stay solution-oriented and independent. Over time, aim to take more ownership of meeting content. Instead of waiting for your advisor to tell you what to do next, come with your own ideas. For instance, propose: “I was thinking we could try approach X next – does that sound reasonable?” or “I’d like to submit this work to Conference Y in a few months.” Advisors appreciate students who show initiative in suggesting experiments, publications, or skill development. This proactiveness demonstrates your growth toward becoming an independent researcher. Similarly, if you need something from your advisor (like a letter, or feedback on a draft), ask clearly rather than assuming they will anticipate it. Good communication means being unafraid to seek specific guidance or clarification. Also, be open about any roadblocks in your life or work that might affect progress (e.g. “I have been struggling with debugging and it’s slowing me down” or “I have an upcoming family event, so I might have less time this week”). Clear communication builds trust and lets your advisor adjust expectations or offer support as needed.
Conclude with mutual understanding. By the end of the meeting, you and your advisor should both be clear on what was decided and what the next steps are. If anything feels unresolved or you’re unsure about a suggestion made, don’t hesitate to ask for clarification before you leave. It can help to literally recap: “So, to summarize, I will do A and B next, and we’ll meet next Wednesday to review, correct?” This ensures no misunderstandings. As noted, writing this summary in an email afterward is a good reinforcement.
To pull it all together, here’s a quick checklist you can follow when preparing for your weekly PhD meeting:
Mid-week: Review your research log or notes. Start listing what you’ve done, any results, and any problems or questions that arose.
Two days before meeting: Finalize what items you want to discuss. Identify the data, figures, or code you will show. Formulate specific questions you need to ask your advisor (technical, logistical, or otherwise).
One day before: Write a brief agenda or slide summary. Include: 1) a recap of last week’s goals, 2) this week’s progress (bulleted), 3) any challenges or decisions to discuss, 4) proposed next steps. Keep it to a digestible length (e.g. one page or a few slides). Email this to your advisor (and any co-advisors) ahead of the meeting. If relevant, share links to code, datasets, or draft documents with appropriate access permissions.
Day of meeting (beforehand): Refresh yourself on the agenda and materials you sent. Bring printouts or have your slides/doc open for reference. Also bring a notebook or device for taking notes.
During the meeting: Start by summarizing last meeting and progress (refer to your agenda). Then dive into discussing results and asking for input on challenges. Listen actively to your advisor’s feedback; ask follow-up questions if something is unclear. Take notes on important points (especially any suggestions, paper references, or action items). Manage the time to ensure you get to all your questions – the agenda will help keep on track. Before closing, confirm the tasks and goals for next week and the expected date of the next meeting.
After the meeting: Soon after, write down any additional details from the discussion while it’s fresh. Send a short summary email thanking your advisor for their input, and list the agreed-upon next steps and any pending items (e.g. “Will send you draft by Friday for feedback”). Update your to-do list or calendar with the new tasks and deadlines. Continue your daily research log, which will feed into the next agenda.
By following these practices, your weekly meetings will become more structured, efficient, and rewarding. You’ll find that good preparation not only impresses your advisor but, more importantly, helps you clarify your own thinking and identify what you need. Consistently well-prepared meetings lead to faster problem-solving, clearer guidance, and a strong advisor–student rapport. In short, invest in the preparation so that each meeting propels your research forward – week by week, all the way to your thesis success.
- University of Cambridge, Postdocs of Cambridge Society UCU Researcher Survival Guide
- University College London The Good Supervision Guide for New and Experienced Research Supervisors of PhDs.
- Smart Researcher Blog How to Get the Best Supervision from your PhD Supervisor
- Eva Lantsoght / AcademicTransfer How to Have Efficient Meetings with Your Supervisor
- Joe Bathelt: How to Prepare for a Meeting With Your PhD Supervisor Like a Pro
- Biswabandan Panda Weekly Research Progress Meetings: How To Do It Right If You Want To Do It Right?.
- Austin Z. Henley Lessons from My PhD