Get AI summaries of any video or article — Sign up free
Plan Your PhD With Notion (+ Free Template) thumbnail

Plan Your PhD With Notion (+ Free Template)

Mariana Vieira·
6 min read

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

TL;DR

Build a three-part system: a literature database for research retrieval, a project database for dissertation structure and deadlines, and a master to-do database for daily execution.

Briefing

A PhD dissertation is a long-running information project—full of papers, notes, deadlines, revisions, and shifting priorities—and the most practical way to manage it is to centralize everything into a small set of linked databases plus a master task list. The core setup is three pillars: a research/literature database to store documents and notes, a project database to track dissertation work (including chapters as sub-projects), and a consolidated to-do database that drives day-to-day execution through reminders, filtering, and status.

The research database is built for retrieval. Each entry should include a status field (e.g., not started, reading, finished) so work can be filtered by progress. Core properties include document name and author, with the document name acting as the gateway to a dedicated page for notes—whether those notes are free-form or follow a template. Keywords add another search layer for topics that may not appear in the title. To keep sources and context together, the database can store the original file (PDF upload or an internet link) and an added date for time-based searching. A key workflow improvement is linking this literature database to the project database, so thesis work can reference other academic projects and be broken down by chapter.

The project database organizes the dissertation as an ecosystem of deadlines and deliverables. It includes due dates with reminders, a status field (work in progress, completed, on hold), and a project type to distinguish different kinds of academic work such as articles, lectures, presentations, calls for papers, and dissertations. Projects can also be decomposed: dissertation chapters can be treated as sub-projects, each with its own linked pages. A linked dashboard then pulls together tasks, deadlines, relevant files (like proposal and outline), and a more formal references list that can be exported in bibliography format at the end.

Finally, the to-do list functions as the operational engine. Instead of scattering actionable items across multiple tools, tasks live in one master database with a checkbox for completion, so finished items disappear automatically via filtering. Each task entry uses a main name/description field for detail, plus scheduling fields for date and reminders. Categories help keep search usable—too narrow makes retrieval harder, too broad dilutes it. Tasks are linked back to the projects they belong to, enabling quick views of everything required for a specific chapter or dissertation phase.

Beyond the core databases, several templates are recommended to accelerate common PhD workflows: a synthetic notes template for skimming articles into context, contributions, and problems; an adapted CRM for tracking academic contacts and outreach; an external resources organizer for books, videos, courses, websites, and code snippets; a flashcards system built around spaced repetition and active recall; a reusable problem statement template to avoid restarting from scratch; and a retrospective exercise template for periodic reflection—capturing what’s working, what’s not, and turning lessons learned into follow-up action items. The overall message is straightforward: build a searchable system where research, project structure, and tasks reinforce each other, so the dissertation becomes manageable rather than overwhelming.

Cornell Notes

The dissertation planning system centers on three linked Notion databases: one for research and literature, one for projects (including dissertation chapters as sub-projects), and one master to-do list. The research database uses status, document name/author, keywords, stored files, and added dates to make papers and notes easy to retrieve, while linking literature items to thesis projects. The project database tracks due dates with reminders, project status, and project types, then uses a dashboard to aggregate tasks, deadlines, relevant files, and a references list for bibliography export. The to-do database drives execution with completion checkboxes, task details, reminders, and categories, and it links tasks back to the projects they support. This structure reduces duplicated copies and makes searching and planning faster.

Why split dissertation management into research, projects, and a master to-do list instead of using one database for everything?

The system separates concerns so each database can be optimized for a different job. The research/literature database is built for document retrieval and note storage, using fields like status (not started/reading/finished), document name and author, optional keywords, stored PDFs or links, and added dates. The project database is built for deadlines and structure, with due dates and reminders, status (work in progress/completed/on hold), and project type (article, lecture, presentation, call for papers, dissertation). The to-do database is built for execution, using a completion checkbox, a task name/description, scheduling fields (date and reminder), and categories—then linking each task to the project it supports. This avoids scattering actionable items across multiple places and keeps searching efficient.

What specific properties make the literature database fast to navigate?

Key properties include a status field to filter papers by reading progress, document name and author as core identifiers, and an optional keywords property to search by topic even when the title doesn’t reflect it. The database can store the original file (PDF upload or an internet link) so notes and source live together in one place. An added date supports searching based on when documents were collected. The literature database is also linked to the project database so thesis work can reference sources and other academic projects, including breaking work down by chapters.

How does the project database turn a PhD into manageable pieces?

It treats the dissertation as a set of projects and sub-projects. A project entry can represent the thesis overall or a specific chapter, with sub-pages for deeper organization. Properties include due date with reminders, a status field (work in progress/completed/on hold), and a project type to distinguish different academic activities like articles, lectures, presentations, calls for papers, and dissertations. A linked dashboard then aggregates tasks and deadlines, relevant files (such as proposal and outline), and a more formal references list that can be exported in bibliography format at the end.

What makes the to-do database effective day-to-day?

Tasks are centralized and made actionable through a completion checkbox and filtering. When a task is marked complete, it can be hidden automatically, so only remaining work stays visible. Each task has a main name/description for detail, plus date and reminder fields so Notion can alert when deadlines approach. Categories support search, but the guidance is to avoid overly narrow categories that make retrieval difficult and overly broad categories that undermine the purpose of filtering. Linking tasks to projects enables quick views of everything needed for a specific chapter or dissertation phase.

Which extra templates address common PhD pain points beyond tracking?

Several templates target recurring workflows: a synthetic notes template for skimming scientific articles into a brief summary capturing context, contributions, and problems; an adapted CRM template for networking and tracking contacts with fields like associations and contact status; an external resources template for organizing books, videos, courses, websites, and code snippets; a flashcards template using spaced repetition and active recall so cards resurface like Anki; a problem statement template to reuse when starting new projects; and a retrospective exercise template for periodic reflection—what’s going well, what’s going wrong, and what follow-up action items to create.

How does linking databases reduce duplication and improve retrieval?

Instead of copying the same information into multiple categories or tools, the system stores each research item once in the literature database with its notes and source file. Linking literature items to projects lets thesis chapters reference the right sources without re-filing. Linking tasks to projects lets the to-do database serve as a single execution layer while still providing project-specific views. The result is fewer duplicates, faster searching, and smoother navigation across the dissertation’s research-to-writing pipeline.

Review Questions

  1. If a paper’s title doesn’t reflect the topic you care about, which database property helps you still find it quickly, and why?
  2. How do completion checkboxes and filtering work together in the master to-do database to keep the workload view clean?
  3. What fields in the project database support both planning (structure/status) and execution (deadlines/reminders), and how does the linked dashboard use them?

Key Points

  1. 1

    Build a three-part system: a literature database for research retrieval, a project database for dissertation structure and deadlines, and a master to-do database for daily execution.

  2. 2

    Use a status property in the literature database to filter papers by reading progress (not started, reading, finished) and speed up workflow decisions.

  3. 3

    Store notes on a per-document page linked from the document name, and optionally add keywords so searching works even when titles don’t match your topic.

  4. 4

    Track dissertation work in the project database with due dates and reminders, status (work in progress/completed/on hold), and project types; treat chapters as sub-projects.

  5. 5

    Create a linked dashboard per project to aggregate tasks, deadlines, relevant files, and a references list that can be exported in bibliography format.

  6. 6

    Keep tasks in one to-do database with a completion checkbox, scheduling fields (date/reminder), and categories that are neither too narrow nor too broad.

  7. 7

    Use specialized templates—synthetic article notes, CRM networking, external resources, flashcards, problem statements, and retrospectives—to reduce repeated setup work and improve learning loops.

Highlights

The dissertation system hinges on three linked databases: research/literature, projects (including chapters as sub-projects), and one master to-do list.
A status field in the literature database turns reading into a filterable pipeline, so papers move from “need to start” to “finished” without manual sorting.
Project dashboards can aggregate tasks, deadlines, files, and references, enabling a structured path toward bibliography export at the end.
The to-do database uses completion checkboxes plus filtering so finished tasks disappear automatically, keeping attention on what remains.
Periodic retrospectives are treated as a core PhD tool: reflect, identify what went wrong or right, then generate follow-up action items.

Mentioned