Your first marathon week needs three things: one long run, one quality run, and easy runs for every other day. Whether that adds up to three, four or five run days is a choice about your life, not a rule from science.
Here’s the honest part. We found no trial that compares 3-day, 4-day and 5-day plans for first-timers. Every day-count you’ve seen online is coaching judgment. This post gives you all three weeks and says which claims have data behind them.
Marathon training week basics: what the data say about volume
The best data on first-timers’ weeks is about total volume and the longest run. A study of 997 recreational runners (441 marathoners) compared them to a group running 40 to 65 km a week. Runners under 40 km finished about 6.3 minutes slower. Runners over 65 km finished about 14.1 minutes faster.
In short: more weekly distance bought a faster finish, and the gain was bigger than the penalty for running less.
The same study found no clear injury penalty for low mileage. The odds ratio for runners under 40 km was 1.29, and the range (0.79 to 2.09) crossed 1. Some sites claim low mileage doubles your risk. This paper doesn’t show that.
Large-scale data tell a similar story. Across 119,452 runners, the average was 45.1 km (28 miles) a week in the 16 weeks before a marathon. The fastest group ran more than three times the volume of slower runners. Most of that extra volume was easy running.
You don’t need heroic mileage. You need a week you can repeat.
The three parts of every week
Think of your week as a three-legged stool. Pull one leg out and it tips.
- Long run. The anchor. It teaches your body to keep going when it’s tired.
- Quality run. One tempo or interval session. “Tempo” means comfortably hard, about the pace you could hold for an hour.
- Easy runs. Slow enough to chat. These build volume without wrecking you.
In a 2007 study of 12 sub-elite runners, the group spending 80.5% of its time at low intensity improved a 10.4 km race by 157 seconds. The group at 66.8% improved by 121.5. Translation: easy days are where most of the fitness gets built. The sample was tiny, so treat it as a direction. For the full case, see why easy running builds your base.
Space your hard days. Most coaches want about 48 hours between a quality run and the long run. That’s convention, not a proven number. It works because you start hard days with fresh legs.
Template 1: the 3-day week
This is the FIRST-style layout. FIRST (Furman Institute of Running and Scientific Training) uses three runs plus at least two hard cross-training days. Its authors report gains in fitness and race times. We couldn’t confirm those claims in an independent trial, so read them as the program’s own numbers.
Note the catch: three runs plus two cross-training days is still five training days.
| Day | Session | Example |
|---|---|---|
| Mon | Rest | Walk if you like |
| Tue | Quality run | 6 mi with 3 mi at tempo |
| Wed | Cross-train | 45 min bike or elliptical, firm effort |
| Thu | Easy run | 5 mi |
| Fri | Rest | |
| Sat | Cross-train | 45 min bike or elliptical, firm effort |
| Sun | Long run | 12 mi |
About 23 miles of running. The long run is roughly half of it, which is high. With fewer days, each run has to carry more.
Best for: busy weeks and joints that dislike pounding. Trade-off: less total run volume, and fewer chances to practice easy running.
Template 2: the 4-day week
For most self-coached first-timers, this is the sweet spot. It adds an easy run without adding a second hard day.
| Day | Session | Example |
|---|---|---|
| Mon | Rest | |
| Tue | Easy run | 5 mi with 4 short strides |
| Wed | Rest or cross-train | Optional 30 min easy |
| Thu | Quality run | 6 mi with 3 mi at tempo |
| Fri | Rest | |
| Sat | Easy run | 5 mi |
| Sun | Long run | 12 mi |
About 28 miles, right at the 28-mile average from the big dataset. Strides are 15-second pickups to a quick, relaxed pace. The long run is roughly 43% of the week.
Best for: 4 to 8 hours a week. Trade-off: two rest days leave little slack when work gets busy.
Template 3: the 5-day week
Add a fifth day only when four days feel easy. Don’t add it just because the plan looks better on paper.
| Day | Session | Example |
|---|---|---|
| Mon | Rest | |
| Tue | Quality run | 6 mi of intervals (e.g., 5 x 800 m) |
| Wed | Easy run | 4 mi |
| Thu | Tempo run | 7 mi with 4 mi at tempo |
| Fri | Rest | |
| Sat | Easy run | 4 mi |
| Sun | Long run | 14 mi |
About 35 miles. The long run is 40% of the week, in line with a common coaching rule of thumb, not a research number.
Best for: runners with a base of 25-plus miles a week. Trade-off: two quality runs plus a long run means three hard days. Skip the second quality run if you feel flat.
All three tables are stylized examples, not research results. Scale distances down if you’re starting lower.
Build it up without breaking
The famous “10% rule” says never add more than 10% a week. It’s weakly supported. In 874 novice runners, jumps over 30% a week carried a hazard ratio of 1.59 for injury. The range (0.96 to 2.66) just touched 1, so it wasn’t statistically solid.
A randomized trial of 532 novices found a gentle 13-week ramp injured 20.8% of runners. A faster 8-week plan injured 20.3%. So slow ramps alone didn’t protect anyone.
A better habit: keep jumps modest, and drop to about 75% of your volume every third or fourth week. Your body adapts while you rest, like a phone charging overnight.
Strength work gets the same honest treatment. In a trial of 720 first-time marathoners, a 10-minute routine three times a week didn’t change injuries (7.1% vs 7.3%) or finish time. Strength helps running economy in highly trained runners. Do it if you enjoy it. Don’t count it as a shortcut.
A first-timer who picked the right week
Take a runner I’ll call Marcus. He’s 36, works a desk job, and can’t commit past four days. He started with Template 1 at 18 miles a week because his knees felt creaky. By week 6 his easy runs felt boring, so he moved to Template 2.
By week 12 he was at 36 miles with a 16-mile long run. He missed one week with a cold and resumed at about 70% of normal volume. He finished in 4:12. (This is an example, not a real client.)
He didn’t pick the perfect plan. He picked one he kept doing.
When the week falls apart
Missed a run? Skip it. Don’t stack it onto tomorrow. Protect the long run, then drop an easy run before you drop a quality one.
If a bad week hits, here’s the 12-week reality check. Running a faster goal? See what a sub-4 marathon week looks like. When race month arrives, follow the taper.
AthleteOS builds your training plan from the days you can run and puts the long run and quality run on non-consecutive days. When you miss a session, the AI coach adjusts the week and explains why. Start a plan on AthleteOS and see which template fits.