From map to timeline: turning concepts into an implementation plan
A topic map answers 'what'. A timeline answers 'when'. This lesson walks through pulling elements from your map onto Marvex's Timeline Studio to turn conceptual understanding into a class-by-class teaching plan.
A topic-overview map gives you the conceptual structure; pulling its elements onto a Timeline transforms that structure into a sequenced delivery plan. Each lesson, week, or class period becomes a column on the timeline; each map-branch becomes an event scheduled on the right day. The result: a teaching plan that's provably derived from your map, easy to share with department heads, and that students can revisit during revision as a checklist of 'have I understood every element?'.
Why a map alone isn't a teaching plan
A finished topic map shows you what students need to understand. It does not, on its own, tell you when to teach each piece, how long each piece needs, or what depends on what. Those are timeline questions — sequenced, dated, dependency-aware.
Most teachers try to bridge this gap mentally. They look at the map, look at the calendar, and translate one into the other in their head. That works for the first map but breaks the moment plans change (a snow day, an interruption, a class that needs more time on lesson 3). The result is a map you stop referring to and a teaching plan that no longer matches what you actually taught.
The fix is to make the bridge explicit. Marvex Studio's Timeline Studio is the same tool, with a chronological axis instead of a hierarchical one. Drop map-branches onto the timeline, and you get a teaching plan that's literally derived from your map and stays in sync with it.
The map → timeline transform
Open the map from Lesson 2 in Studio. From the map's toolbar, choose Studio → New Timeline from this map. Marvex creates a fresh Timeline Studio canvas, with the map's first-level branches pre-loaded as draft events on a 'To be scheduled' column.
Drag each draft event onto the date or class-period when you intend to teach it. The default time axis spans your current half-term, but you can change it to a single week (for a workshop) or a full year (for a syllabus overview) from the Timeline settings panel.
Supporting elements from the map carry over as sub-events attached to their parent. A first-level branch like 'Causes of the French Revolution' might unfold into three sub-events on the timeline: 'Economic pressure (Week 3)', 'Political grievance (Week 4)', 'Social tension (Week 5)'. You decide which level of map-detail makes the cut onto the timeline — most teaching plans live at the first-and-second level, leaving deeper detail in the map itself.
What the timeline gives you that the map doesn't
1. Pace visibility. A topic with eight first-level branches scheduled across six classes shows up immediately as overloaded. The map alone hides this; the timeline forces the realisation.
2. Dependency tracking. Some elements have to come before others (you can't teach Krebs cycle before glycolysis). On the timeline, draw an arrow from prerequisite to dependent and Marvex flags any scheduling that violates it.
3. Catch-up sessions. Snow day on Tuesday? Drag the affected events three days forward. The dependency arrows re-route automatically; you see at a glance what else has to shift.
4. A shareable artefact for department heads. Timelines export as PDF or PNG. A two-page PDF showing how you'll deliver a topic, anchored to specific dates, is everything a head of department needs to see for sign-off.
5. Revision scaffolding for students. Share the timeline with students at the end of the topic. They use it as a checklist — 'have I understood the Week 3 cluster?' — and as a structural cue for exam recall.
Embed the timeline inside the map
Marvex supports inserting a Timeline directly inside a element on the parent mind-map (Studio → Insert → Timeline). This is the most powerful version of the workflow: students see the topic map with the teaching schedule embedded right where they expect it, so the 'what' and the 'when' live in one shareable artefact.
Practically: pick a element on your map called 'How this topic will be taught' (or similar). Insert a timeline into it. The same map → timeline transform fills it with the events you scheduled. Anyone viewing the map can expand the timeline element to see the full delivery plan.
The implementation discipline
Once the timeline is live, keep it as your source of truth for the topic delivery. After each class, mark the events you actually covered as Done. Marvex tracks completion at the event level and rolls it up at the topic level — a glance at the timeline tells you how far through the planned material you actually are, not how far you think you are.
When you finish the topic, the timeline becomes a historical record. Marvex keeps it linked to the map so next year, when you come to teach the same topic, you open both side-by-side: the map is still accurate, and the timeline shows you what you actually had to cut, repeat, or expand last year. This year's plan starts from last year's evidence, not your imagination.
Questions teachers ask
What if I'm teaching the same topic across multiple classes at different paces?
+
Create one timeline per class (Timeline Studio → New Timeline → Copy structure from existing). Each timeline shares the same source map but tracks its own dates and completion. When you update the map, every timeline picks up the change.
Does the timeline export work with school systems like Google Classroom or Moodle?
+
Timelines export as PDF, PNG, and an ICS calendar feed. ICS is the standard format both Google Classroom and Moodle ingest — paste the URL into either as a calendar feed and your scheduled events appear in the student-facing UI automatically.
Can I keep the map private but share only the timeline with students?
+
Yes. The map and timeline have independent share settings. A common pattern is: private map for your own planning + teaching prep, public timeline (read-only) shared with students for sequencing and revision.