Skip to content
Run SEA

Article

Choosing a Marathon Training Plan That Fits a Full-Time Job

Most published marathon training plans are written as if the runner's day has no employer in it. Here's how to pick a plan tier honestly and structure a training week around a real full-time job.

Last updated August 11, 2026

Matching the Plan Tier to the Time You Actually Have

The biggest mismatch between a runner and their training plan usually isn't fitness -- it's time budget. A finish-focused first-marathon plan typically asks for four to five hours of running a week at its peak, spread across four or five sessions, which is realistic to hold alongside most full-time jobs. A plan aimed at a sub-4-hour marathon usually asks for six to eight hours a week including a genuinely demanding long run and at least one hard quality session, which is a meaningfully bigger ask on a working week. A plan built around a Boston-qualifying time or similar performance goal can ask for eight-plus hours with double-run days, which very few people can sustain around a demanding full-time job without something else in life giving way.

Being honest about this upfront -- picking the plan that fits the job rather than the job that's supposed to somehow fit the plan -- is what actually determines whether a training block gets finished. A runner who picks an ambitious plan tier and quietly drops sessions every time work gets busy ends up with a worse training block than one who picked a more modest tier and actually completed it.

Fitting the Two Sessions That Actually Matter Into a Work Week

Nearly every marathon training plan, regardless of tier, really comes down to protecting two sessions a week: one long run and one quality workout (intervals, tempo, or a hard progression run). Everything else -- easy runs, rest days, cross-training -- is comparatively flexible and can shift around a busy day without much cost. The long run is easiest to protect by anchoring it to a fixed weekend morning slot and treating that slot as close to non-negotiable as a work calendar allows; because it's typically the week's longest session by a wide margin, it's also the one most damaging to skip or badly compress.

The quality session is the one that most often gets lost to a busy work week, precisely because it demands more mental and physical readiness than an easy run does. Runners who protect it successfully tend to schedule it for whichever single weekday is most reliably lighter -- often not the same day every week -- rather than assuming a fixed slot will hold up against a job with variable demands.

How Southeast Asia's Early Race-Morning Culture Actually Helps

One underappreciated advantage of training in a region where races themselves start before dawn (this site has a separate guide on why Southeast Asian races start before dawn) is that the training habit it requires -- waking up genuinely early to run before the day's heat and traffic build -- lines up naturally with fitting a session in before a 9-to-5 workday starts. A runner who's already practicing a 5am or 5:30am wake-up for race-day rehearsal purposes is, in the same motion, solving the much more mundane problem of finding time to run before work.

This is a real structural advantage over training regions where races start at a civilized mid-morning hour and pre-work running isn't part of the local culture at all: in most Southeast Asian cities, running before work isn't an unusual grind a runner has to talk themselves into -- it's simply how a large share of the local running population already trains, which makes it far easier to sustain over a multi-month block.

Setting Realistic Expectations for the Weeks Work Gets Heavy

Even a well-matched plan will collide with an unusually demanding week of work at some point over a 12-to-16-week training block -- a product launch, a closing deadline, a work trip. The plans that survive these weeks intact are the ones where the runner has already decided in advance what gets cut first: typically an easy run or a cross-training session, never the long run or the week's one quality workout, since those two carry most of the actual training benefit.

A single compressed or skipped week rarely derails a marathon block on its own -- what actually derails it is treating every busy week as a reason to abandon the plan's structure entirely rather than triaging down to its two essential sessions and picking the full schedule back up the following week.

Frequently asked questions

How many hours a week does marathon training realistically take with a full-time job?

It depends heavily on plan tier: a finish-focused plan typically peaks around four to five hours a week, a sub-4-hour plan asks for six to eight hours including a hard quality session, and a performance-focused plan can demand eight-plus hours. Picking a tier that matches your actual time budget matters more than ambition.

Which training sessions matter most to protect during a busy work week?

The long run and one quality workout (intervals, tempo, or a hard progression run) carry most of a plan's actual benefit and are worth protecting first. Easy runs and cross-training are comparatively flexible and can be trimmed or moved without much cost to the overall training block.

Does Southeast Asia's early race-start culture help with training around a 9-to-5 job?

Yes -- since races and daily training both default to early-morning starts across the region, runners are already practicing the pre-dawn wake-ups that also make it easy to fit a session in before work. It's a genuine structural advantage over regions where early running isn't part of the local culture.

More articles