Get AI summaries of any video or article — Sign up free
How I Get Organised for a New Academic Semester as a PhD Student thumbnail

How I Get Organised for a New Academic Semester as a PhD Student

Ciara Feely·
5 min read

Based on Ciara Feely's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Start with a six-month “year at a glance” calendar and mark fixed semester dates first, then add optional deadlines like conference submissions.

Briefing

A PhD semester plan that actually works starts with a clear calendar of non-negotiable dates—then layers in deadlines, personal life, teaching duties, and research goals so nothing important gets pushed aside. The organizing system centers on a “year at a glance” view (six months at a time) where fixed semester milestones—class start dates, breaks, assessments, and meetings—sit alongside optional but time-sensitive commitments like conference submission deadlines.

From that overview, the planning shifts to publication strategy. Conference deadlines become the anchor points because they tend to cluster into a few predictable windows each year. Instead of trying to force a paper into any random month, the plan aligns thesis and paper work with the months when conferences are most likely to accept submissions. The approach also uses subject focus as a guide: if a recommender systems or case-based reasoning conference is coming up, the research work in the preceding weeks is geared toward those themes. Months without major conference targets are treated as better fits for journal submissions, general thesis writing, and literature review.

Personal logistics get treated as part of academic sustainability, not an afterthought. Birthdays are added to the calendar with linked gift ideas so reminders don’t vanish until it’s too late. Medical, dental, and personal-care appointments are booked early—while the semester is still calm—because later busyness makes both booking and attending appointments less likely. Holidays are planned with the same logic: the calendar looks for natural breaks, public holidays, and workable multi-day windows (often three to four days), including trips like visiting family or traveling abroad. The reasoning is practical—overwork can force “unplanned” time off through illness—so the goal is to schedule recovery deliberately, especially right after a publication cycle when taking a couple of days off is most realistic.

Once the semester-level picture is set, the system moves to weekly execution by mapping teaching and service responsibilities. Even when the PhD student no longer takes classes, teaching assistant or demonstrator roles still require fixed hours for marking, grading, invigilation, and prep meetings. For each teaching commitment, details are organized into a reference table: who to contact (other demonstrators), course description and learning outcomes, demonstrator hours and locations, and any prep requirements. The same planning area tracks committee work—such as monthly meetings for an equality, diversity and inclusion committee—and research-group updates tied to weekly meetings and monthly reporting.

Finally, the plan connects time management to skill-building. A time-blocked weekly schedule reserves several hours of deep, focused thesis work (programming or writing) and allocates daily time for other obligations. On lighter days, transferable skills take priority—specifically improving software engineering practices like packaging code for readability and reuse. With fixed commitments placed first, the remaining calendar space is shaped into large deep-work windows (ideally around four hours), with self-care and routines built around them.

Cornell Notes

The semester planning method starts with a “year at a glance” calendar covering about six months, marking fixed dates (class start, breaks, assessments) and adding optional deadlines like conference paper submissions. Conference timing drives research focus: work is geared toward relevant topics ahead of major submission windows, while non-conference months are used for journal work, thesis writing, and literature review. Personal appointments, birthdays (with gift ideas), and holidays are scheduled early to prevent overwork-driven burnout and last-minute cancellations. Teaching assistant/demonstrator duties, committee meetings, and research-group reporting are then broken down into weekly and monthly requirements. A time-blocked weekly schedule reserves deep-work blocks for thesis tasks and uses lighter days for transferable skill development, such as writing more reusable, readable code.

How does the plan decide what to work on during each part of the semester?

It begins with fixed semester dates, then overlays conference submission deadlines and conference dates. Because conference submissions often cluster into a few predictable periods, the plan treats those windows as the times to prioritize conference-ready work. When no major conference is coming up, the calendar shifts toward journal submissions, thesis writing, and literature review. The research topic focus also changes with the target venue—for example, recommender systems or case-based reasoning work is emphasized when those conferences are approaching.

Why are conference deadlines treated differently from journal deadlines?

Conference deadlines are usually concentrated into one submission date per year (and one main conference per year), so they create clear planning constraints. Journal submissions are described as more flexible and more evenly distributed across the year, so they fit better into months between conference cycles. The practical takeaway is to schedule conference-driven work around the submission window rather than trying to force it into months with no conference targets.

What personal-life items get integrated into the academic calendar, and what’s the purpose?

Birthdays are added alongside a linked list of gift ideas so reminders lead to actionable choices later. Medical, dental, and personal-care appointments are booked early in the semester, when the student is less busy, because later busyness reduces both the likelihood of booking and actually attending. Holidays are also planned by looking for natural breaks and public holidays, aiming for multi-day recovery windows—often right after a publication push—to avoid taking time off only when overwork leads to illness.

How are teaching assistant or demonstrator responsibilities translated into weekly planning?

Teaching commitments are broken into fixed hours and recurring tasks like marking, grading, and any exam or invigilation work. For each class, the plan keeps a structured reference: contact points (other demonstrators), course description and learning outcomes, demonstrator hours (times and locations), prep meeting requirements, and any additional grading or email-related tasks. This ensures weekly schedules include the necessary teaching prep and administrative follow-through.

What role do committees and research-group meetings play in the schedule?

Committee work is tracked with upcoming meetings—typically monthly—so it can be accounted for during monthly planning. Research-group responsibilities are also scheduled: weekly meetings require preparation and updates, while monthly reporting includes achievements such as publications or completed work. The system is designed to prevent these service and group obligations from slipping between research and teaching tasks.

How does the plan use lighter days to build transferable skills?

After reserving deep-work blocks for thesis programming or writing and filling the rest of the week with teaching, committee, and administrative tasks, the plan uses days with fewer fixed obligations for skill development. In this semester’s case, the focus is on better software engineering habits—making code more readable and reusable by packaging it properly—supported by courses and goals tied to that improvement.

Review Questions

  1. When planning a six-month window, what categories of dates are added first, and why does that order matter?
  2. How does the plan decide whether to prioritize a conference paper versus journal writing in a given month?
  3. What specific information gets recorded for each teaching assistant/demonstrator role, and how does that feed into weekly time-blocking?

Key Points

  1. 1

    Start with a six-month “year at a glance” calendar and mark fixed semester dates first, then add optional deadlines like conference submissions.

  2. 2

    Use conference submission windows to drive research focus and topic selection; align work with the months when submissions are most relevant.

  3. 3

    Plan personal appointments and book them early to reduce the chance of skipping them during busier weeks.

  4. 4

    Schedule holidays intentionally—especially around publication cycles—to avoid overwork-driven illness and forced time off.

  5. 5

    Break teaching assistant/demonstrator duties into fixed hours and recurring tasks, and keep a per-class reference table for contacts, learning outcomes, and prep requirements.

  6. 6

    Track committee meetings and research-group reporting on monthly and weekly rhythms so service work doesn’t get squeezed out.

  7. 7

    Time-block the week by placing fixed commitments first, then carving out large deep-work windows for thesis tasks and using lighter days for transferable skill building (e.g., reusable code practices).

Highlights

Conference submission deadlines act as the calendar’s main research engine, shaping both what gets written and when.
Personal-care planning is treated as part of academic performance: early booking and scheduled recovery reduce burnout risk.
Teaching assistant planning becomes actionable by storing per-class details like learning outcomes, demonstrator hours, prep needs, and contact points.
Transferable skill work isn’t left to chance; it’s assigned to lighter days using the same time-blocked structure as research and teaching.

Topics

Mentioned