Missed two weeks of classes? A catch-up triage plan
In this article (7 sections)
Related programme: the Data Science course (6 months; ₹1,30,000 (inclusive of GST) · EMI from ₹5,000/month).
If you have missed two weeks of a data science course, do not rewatch everything in order. Keep attending current classes, list what you missed, sort it by what the next sessions depend on, and cover only those foundations in the first week. Everything else — optional depth, extra practice sets — goes into a second pass once you are back in step.
First, the three things to do today
- 1Message your mentor or batch coordinator. Say what you missed and when you can resume. A short note works: "I missed sessions 9–12 due to a family emergency. I am attending from Saturday. Which topics from those sessions do the next two classes build on?" That last question saves you hours.
- 2Download or bookmark every missed recording, notebook and assignment brief in one folder, so you are not hunting for them later.
- 3Attend the very next live class, even underprepared. You will follow more than you expect, and it tells you which gaps actually hurt.
Sort the missed topics
Put every missed topic in one of three buckets:
| Bucket | Test | Examples in a DS course |
|---|---|---|
| Foundation | A coming session or the next assignment uses it directly | Train/test split, pandas groupby, a first model's fit/predict pattern |
| Assessed | It has a graded assignment or quiz with a deadline | The assignment brief from the missed week |
| Depth | Useful, but nothing upcoming requires it yet | An extra algorithm variant, an optional reading, a bonus dataset |
Foundations come first, then assessed work, then depth. If you are unsure which bucket something belongs in, that is exactly the question for your mentor.
Order the foundations by dependency
Within the foundation bucket, some topics depend on others. Covering them out of order wastes time. For a short list you can work this out by hand; for a longer one, Python's standard library can sort it for you.
from graphlib import TopologicalSorter
# Hypothetical missed topics -> the topics each depends on
depends_on = {
"logistic regression": {"train/test split", "feature scaling"},
"confusion matrix": {"logistic regression"},
"precision and recall": {"confusion matrix"},
"feature scaling": {"pandas basics"},
"train/test split": {"pandas basics"},
"pandas basics": set(),
}
# Estimated catch-up hours for each (recall attempt + targeted rewatch + exercise)
hours = {
"pandas basics": 1.0,
"train/test split": 1.0,
"feature scaling": 1.0,
"logistic regression": 2.5,
"confusion matrix": 1.5,
"precision and recall": 1.5,
}
order = list(TopologicalSorter(depends_on).static_order())
running = 0.0
for topic in order:
running += hours[topic]
print(f"{topic:<22} {hours[topic]:>4} h cumulative {running:>4} h")
assert order[0] == "pandas basics"
assert order.index("confusion matrix") < order.index("precision and recall")
assert running == 8.5In this hypothetical case, 8.5 hours of focused work covers the foundations. Spread over a week alongside current classes, that is realistic. Rewatching the same sessions in full might have taken twelve hours or more and still left you unable to do the exercises.
A ten-day catch-up plan
Assume you can find about 1.5 extra hours on weekdays and 3 hours on one weekend day, on top of attending live classes.
| Days | Focus | Output by the end |
|---|---|---|
| 1 | Message mentor, gather materials, sort buckets | Ordered topic list with hour estimates |
| 2–4 | First half of foundations, in dependency order | Each topic's class notebook re-run and one exercise done from blank |
| 5 | Current live class; note which missed ideas came up | Short list of gaps that actually hurt |
| 6–7 | Rest of foundations, prioritising what day 5 exposed | Foundations bucket empty |
| 8–9 | Assessed work: the missed assignment | Submitted, even if not perfect |
| 10 | Buffer, and ask the doubts you collected | A written list of anything still unclear |
Depth topics go on a list for the following fortnight. Some of them you will find you never need.
How to catch up on a single missed session quickly
For each foundation topic, follow the same short loop instead of watching the full recording:
- 1Read the class notebook or slides first — 10 minutes — to see what was covered.
- 2Watch only the segments where code was written or a new idea introduced. Use the chapter markers or scrub through at speed to find them.
- 3Close everything and redo the key exercise from a blank notebook.
- 4Note one question you still have.
The redo is what tells you whether you have caught up or only watched.
Talking to your mentor about the missed assignment
Ask, rather than assume, what the rules are. Useful questions:
- Can I submit the missed assignment late, and is there a final date?
- If I have to choose, which of the missed exercises matters most for the capstone?
- Is there a doubt session or lab this week where I could get through the foundations faster?
If the course also has optional in-person labs, a lab day can be an efficient place to clear several doubts at once.
Preventing the next gap
A two-week gap often starts as one missed week that nobody noticed. Two habits help:
- Keep a weekly progress check — how many sessions attended, exercises completed from blank, doubts asked. Our weekly progress measure sets this out.
- When you know a busy period is coming — an audit, a wedding, exams — tell your mentor in advance and ask what to prioritise.
For using recordings efficiently once you are back on track, see how to use class recordings without rewatching everything. Because every live online session of the Data Science programme is recorded, a two-week gap there is recoverable rather than terminal.
Frequently asked questions
Should I skip current classes to catch up on missed ones?
No. Keep attending the current live classes, even if parts go over your head, and catch up in separate time. Skipping current classes to rewatch old ones means the gap never closes; you just move it forward.
How long does it take to catch up after missing two weeks?
It depends on how many sessions you missed and how much time you can add, but a common target is to close the gap within ten to fourteen days by covering only what upcoming classes depend on first. Tell your mentor early so they can point out which parts can wait.
Pankit Kumar has 10 years in Data Science & AI, building and shipping production systems in regulated pharma and clinical environments. He is a freelance trainer at Boston Institute of Analytics, AnalytixLabs and Scaler, and has taught this material to thousands of working professionals.
This article is part of our Data Science programme — 6 months. From data foundations to machine learning, deep learning and deployment.
Explore Data Science