Palwal, Rewari and Bhiwadi learners: fitting study around shifts

The shift problem is scheduling, not distance

Learners in these towns often assume the obstacle is distance from Noida. As of September 2026, the nearest metro ends are a long way off. The Violet Line's southern end is Raja Nahar Singh at Ballabhgarh, the station you would use from Palwal. From Rewari or Bhiwadi, just over the Rajasthan border, the usual option is the Yellow Line at Millennium City Centre Gurugram. But the live sessions are online, and in-person labs at Noida are optional, so distance matters only on the few days you choose to travel.

What actually derails shift workers is the roster. A week of mornings suits evening classes. A week of nights leaves you asleep during a weekend morning session. A general shift followed by overtime leaves you with nothing left for evening class. Plan around the roster, not around the map.

Build the clash map

Enter your rotation and the course timetable, and let the code tell you which sessions you can attend live. The shift times and class slots below are hypothetical. Replace them with your actual roster and the timetable your cohort receives.

from datetime import date, timedelta

# Hypothetical three-week rotation: morning, evening, night, then repeat
SHIFTS = {
    "M": (6, 14),   # 06:00-14:00
    "E": (14, 22),  # 14:00-22:00
    "N": (22, 30),  # 22:00-06:00 next day, written as 30 for arithmetic
}
rotation = ["M"] * 7 + ["E"] * 7 + ["N"] * 7

# Hypothetical live sessions: weekday -> (start hour, end hour); 0 = Monday
CLASSES = {1: (20, 22), 3: (20, 22), 5: (10, 13)}

SLEEP_AFTER_NIGHT = 7   # hours you need after a night shift ends
COMMUTE = 1             # hours each way, your own figure

def status(day_index, weekday):
    start, end = CLASSES[weekday]
    shift = rotation[day_index % len(rotation)]
    s_start, s_end = SHIFTS[shift]
    busy = [(s_start - COMMUTE, s_end + COMMUTE)]
    if shift == "N":
        busy.append((0, 6 + COMMUTE + SLEEP_AFTER_NIGHT))  # asleep until early afternoon
    prev = rotation[(day_index - 1) % len(rotation)]
    if prev == "N":
        busy.append((0, 6 + COMMUTE + SLEEP_AFTER_NIGHT))
    for b_start, b_end in busy:
        if start < b_end and end > b_start:
            return "RECORDING"
    return "LIVE"

first = date(2026, 10, 5)  # a Monday
for i in range(21):
    d = first + timedelta(days=i)
    if d.weekday() in CLASSES:
        print(d.isoformat(), rotation[i], status(i, d.weekday()))

Here is the output for the first two weeks:

2026-10-06 M LIVE
2026-10-08 M LIVE
2026-10-10 M RECORDING
2026-10-13 E RECORDING
2026-10-15 E RECORDING
2026-10-17 E LIVE

Each week is different. In the morning week you can attend both weekday evening sessions, but the Saturday morning session falls inside your shift. In the evening week it flips: the weekday classes clash with work and Saturday is free. The third week surprises most people. The script marks all three night-week sessions as recordings. The weekday classes run into the commute before a 22:00 shift, and the Saturday session falls in the hours you are asleep after one. Plan the night week as a catch-up week from the start, not a week you hope to manage.

The model is deliberately simple. It treats shifts as fixed, ignores overtime and assumes you sleep straight after a night shift. Add what applies to you. If your plant regularly adds two hours of overtime, extend the shift end times.

Rules for a "RECORDING" session

A session you watch as a recording is only useful if you watch it soon. Set yourself three rules:

1. 1Watch within 48 hours. After that, the next session builds on material you have not seen.
2. 2Post your questions in the cohort channel before the next live session. Mentors can answer them, and other learners on shifts will often have the same questions.
3. 3Do the exercise before the recording is fully over. Pause at the task, attempt it, then watch the solution. Watching the whole thing first and planning to "do it later" is how shift workers fall behind.

Make your shift weeks work in your favour

Each shift type leaves a different part of the day free. Plan the work to match.

Night weeks are the hardest, because the clash map leaves you with recordings only. Watch them in the afternoon window, in short parts. Do not force the exercises on a tired afternoon. Take them into the following morning week, when your evenings are free again.

Your shop-floor data is a head start

If you work in production, stores, quality or dispatch, you already deal with the kind of data analysts work on: shift-wise output, rejection counts, downtime logs and stock movements. A portfolio project built on a synthetic version of a shift production log is more convincing than a generic sales dataset. For example, you could compare output per shift and chart the main reasons for downtime. Never use your employer's actual data without written permission. Recreate the structure with made-up numbers instead.

Tell the counsellor about your roster before enrolling

Share your rotation with the counselling team. Ask how soon recordings are available after each live session, and whether recordings are counted as attendance for any programme criteria. Bring the clash map to that conversation; it makes the question concrete. Course content and duration (3–4 months) are on the Data Analyst programme page, and if you want to know how your shop-floor experience reads to an analytics recruiter, run your resume through the free skill check.