Plan your thesis timeline: a method-aware roadmap
Build a thesis timeline that fits your method (literature-based, theoretical, or empirical) and paces every milestone against your real deadline, with progress read from actual verified work, not a checklist you tick by hand.

The advice to 'make a timeline' is easy to give and hard to use. A generic Gantt chart from a template doesn't know whether you're writing a literature-based thesis or running experiments, and a plan you build once and never touch drifts out of date the first week. Roadmap takes a different approach: it builds a milestone plan from your method, paces it against your real deadline, and reads your progress from the work you've actually done rather than a box you remembered to tick.
A milestone ladder that matches your method
When you create a project you pick your method: literature-based, theoretical, or empirical. Roadmap builds the standard milestone ladder for that method immediately, ready on day one. The difference is not cosmetic: an empirical thesis has design, data collection, and analysis milestones that a literature-based one simply doesn't, so a method-specific plan spares you steps that don't apply and includes the ones that do.
Deadline-aware pacing, in days
Set your deadline and every milestone gets a target date. The dashboard then tells you plainly where you stand: a headline says whether you're on track, ahead, or behind and by how many days, and the active milestone flags when it's running past its target. This is the number that actually changes behaviour: 'twelve days behind on the literature review' is something you can act on in a way that a static chart never prompts.
Change the deadline and the whole plan re-paces. The timeline is meant to move with your project, not sit frozen from the day you made it.
You mark milestones done, not the AI
Milestones are only ever completed by you. When your activity in a tool looks like a step is finished, Roadmap can suggest that it's done, but it never silently ticks your progress on your behalf. That keeps the plan honest in both directions: nothing shows complete that you didn't decide was complete, and the suggestion is there when you want the nudge.
Progress comes from real work, not vibes
The progress and grounding numbers on the dashboard are computed from your project's real verification ledger, not estimated. When it says a chapter's claims are verified, that reflects actual Fact-Checker verdicts against full text. A status like this is only useful if it can't flatter you, and this one is wired to the same records that gate drafting and compile everywhere else in the app.
The project brief keeps every tool aligned
Alongside the timeline, Roadmap holds your project brief: your pinned research question, conceptual framework, study design, and target venue in one place that every other tool reads. Change any of them and the change propagates, so your drafting and analysis are always framed on the current plan rather than a stale copy. The brief is what makes the roadmap a living center for the project instead of a separate to-do list.
Share progress with your supervisor
When your supervisor asks where things stand, you can share a read-only snapshot link instead of writing a status report at midnight. They see real progress and real verification stats, and you can revoke or rotate the link whenever you like. From here, the natural first move is to pin your research question and start building: the getting-started walkthrough takes you from a pinned question to your first grounded, defensible section.