To start running from scratch: run three days a week, never on back-to-back days, and make every session a run-walk — alternate a short jog with a walking recovery instead of trying to run continuously. Start at roughly 60 seconds of jogging and 90 seconds of walking, repeated eight times, and progress by lengthening the jog and shrinking the walk rather than by running faster. Eight to ten weeks of that is what turns a first jog into a continuous 5K for most people, and it is the whole method behind every couch-to-5K-style plan you have seen.
The part those plans leave out is the part that actually decides whether you finish week three: how hard the running is supposed to feel, and what to do on the day the plan says one thing and your legs say another. That is where a coach beats a printed schedule, and it is what ChatRPE is — an AI coach on a Universal Logbook that can run the intervals out loud while you are moving, then keep every session in the same history as your lifting, weight, and sleep.
The short version
- Run-walk is the method, not the beginner version of it. Shrinking the walk break is how the dose goes up.
- Three days a week, never consecutive. The adaptation happens on the off days, and the injuries happen when there are none.
- Easy means conversational. If you cannot speak a full sentence while jogging, you are running your easy runs too hard — which is the single most common reason new runners quit in week two.
- Progress time, not pace. Speed is a result you get later; duration is the input you control now.
- Eight to ten weeks to a continuous 5K is a normal timeline from a standing start. Repeating a week is not failure; it is the plan working.
- Sore is expected, sharp is not. Persistent or localized pain is a question for a clinician, not for a training plan.
Why most beginners quit in week two
Almost nobody quits running because it is boring. They quit because it hurt, or because it felt impossible, and both usually trace back to the same two decisions.
Running the easy runs too hard. New runners have no calibration for "easy," so they run at the only speed they know — the speed running looked like when they watched someone else do it. At that effort, twenty minutes is genuinely brutal, recovery takes days, and the honest conclusion is "I am not a runner." At the correct effort, the same twenty minutes is boring, which feels like cheating and is exactly right.
Running on consecutive days. Running loads tissue that adapts slowly — tendon, bone, connective tissue — far slower than the cardiovascular system that will feel ready to go again tomorrow. Feeling recovered is not the same as being recovered, and stacking days early is how a beginner ends up on the couch in week four wondering what happened to their shins.
The run-walk structure fixes both at once. The walk break caps how hard the running gets, and three sessions a week with a day between them caps how fast the volume climbs.
The run-walk method, and why it is not a compromise
A run-walk session is an ordered list of intervals: jog for a set time, walk for a set time, repeat. That is it. Its reputation as a beginner crutch is backwards — it is the cleanest dose control available to a new runner, because you can raise the running load in small, precise steps without ever changing your speed.
Here is what progressing actually looks like across a session, using the same total time:
| Progression | Jog | Walk | Rounds | Running in the session |
|---|---|---|---|---|
| Starting out | 60 sec | 90 sec | 8 | 8 minutes |
| Two weeks in | 90 sec | 2 min | 6 | 9 minutes |
| A month in | 3 min | 90 sec | 5 | 15 minutes |
| Six weeks in | 8 min | 2 min | 3 | 24 minutes |
| Nearly there | 20 min | — | 1 | 20 continuous minutes |
Notice what never changes in that table: how fast you are moving while jogging. Every step of the progression is the same easy effort, held for longer. That is progressive overload applied to running — same idea as adding five pounds to a lift, with time as the variable instead of load.
An eight-week beginner running plan
This is a conventional run-walk progression, written the way most beginner plans structure it. Do each session three times in its week, with at least one rest day between, and add a five-minute walk before and after every session.
| Week | The session | Total running |
|---|---|---|
| 1 | 8 × (jog 60 sec, walk 90 sec) | 8 min |
| 2 | 6 × (jog 90 sec, walk 2 min) | 9 min |
| 3 | 4 × (jog 3 min, walk 2 min) | 12 min |
| 4 | 3 × (jog 5 min, walk 2 min) | 15 min |
| 5 | 2 × (jog 8 min, walk 3 min) | 16 min |
| 6 | 2 × (jog 10 min, walk 3 min) | 20 min |
| 7 | jog 15 min, walk 3 min, jog 8 min | 23 min |
| 8 | jog 25–30 min continuous | 25–30 min |
Two rules that matter more than the numbers in the table. Repeat any week that felt like a struggle — a plan you repeated a week of and finished beats a plan you followed exactly and abandoned. And the walk breaks are walks, not standing rests: keep moving so your heart rate settles gradually rather than dropping off a cliff.
Most people cover a 5K somewhere between 30 and 40 minutes at the end of a progression like this. That is an estimate, not a promise — starting fitness, age, bodyweight, and how much walking you already do all move it.
How fast should a beginner run?
Slow enough to talk. That is the whole test, and it is more reliable for a beginner than any heart-rate zone: if you can speak a full sentence out loud while jogging without gasping between words, the effort is right. If you can only manage two or three words, slow down — and if slowing down means your jog is barely faster than a walk, that is fine and extremely common.
If you already train with RPE, an easy run is roughly a 3 to 4 out of 10 — the same scale you would use on a warm-up set. The advantage of effort over pace is that it self-adjusts: the same RPE 4 is a slower jog on a hot day, on four hours of sleep, or on the third session of a hard week, which is exactly the behaviour you want and exactly what a fixed pace target cannot do.
That effort rating is worth logging with every run. ChatRPE keeps it next to the distance and duration you reported and tells you when the same easy effort started covering more ground, which is the improvement you were actually looking for.
From a printed plan to a coach that runs the session
| The old workflow | The ChatRPE upgrade |
|---|---|
| Keep the week's intervals on a screenshot and count them in your head | The live session holds the intervals and calls each one |
| Set a phone timer for every jog and every walk | One session with the timers built in, restarting between intervals |
| A plan that says "week 3" no matter how week 2 felt | Say week 2 was rough and the next block is rewritten |
| Log the run afterward in a separate running app | Finishing the session archives it as cardio automatically |
| A running history that knows nothing about your lifting | One logbook holding runs, lifts, weight, sleep, and habits |
Let the coach run the intervals
A run-walk session is the exact shape of a ChatRPE live session: an ordered list of steps with timers attached. Ask for it in plain language — "start a run-walk: 5 minutes walking, then 8 rounds of 60 seconds jogging and 90 seconds walking" — and the coach opens a live session that carries the current interval, what comes next, your progress through the rounds, and a countdown for the interval you are in.
On iPhone, that surface follows you to the Lock Screen and Dynamic Island as a Live Activity, so you glance at your phone rather than unlocking it mid-stride. And when an interval's countdown reaches zero, iOS delivers a time-sensitive alert with sound — scheduled for the timer's own end time, so it arrives whether the app is open, in your pocket, or closed. That is what makes a run-walk usable without staring at a screen: you get told when to jog and when to walk. In a browser the same live panel sits above the chat box, but the countdown there is visual rather than audible.
On iOS you can start the whole thing without touching your phone at all. "Start a run with ChatRPE" is a real registered Siri phrase, and the full hands-free setup — including logging by voice mid-session — is covered in the hands-free workout logging guide. The guided workout app guide covers the live-session system in full, including how the same mechanism drives interval work in the gym.
Try this: "I'm starting running from scratch, three days a week. Start a live run-walk session for me: 5 minutes of walking to warm up, then 8 rounds of 60 seconds jogging and 90 seconds walking, then 5 minutes of walking to cool down. Call each interval and log it as cardio when I finish."
Log the session, then let it argue with the plan
When you finish, the session archives itself into your logbook as a cardio entry — activity, duration, distance if you reported one, and whatever you said about how it went. Nothing to retype. From there a beginner running plan stops being a printed schedule and starts being a conversation with evidence behind it:
- Say how it actually felt, in the same sentence. "Ran the week-3 session, third round was rough, RPE 7." Cardio entries carry your note alongside the numbers, so "rough" is findable later rather than half-remembered. The cardio tracker guide covers the logging path in full.
- Ask whether to repeat a week. Three sessions of the same intervals with rising effort is a different answer from three with falling effort, and the coach reads the sessions rather than the calendar.
- Watch effort fall at the same distance. Ask for a chart of your run duration or distance with a moving-average overlay, or plot two saved metrics against each other — weekly running minutes against sleep hours, for instance, when the easy runs stop feeling easy.
- Keep the consistency visible. Logged runs count toward streaks and show up in the same consistency heatmap and dashboard as everything else you train.
Running alongside lifting
You do not have to choose. Two things are worth knowing if you also lift. Put the run after the lift on a day you do both, or separate them by a few hours, so the running does not spend the energy the heavy sets need. And do not read a slightly slower squat during a running block as a lifting problem — running is training, it costs recovery, and the rest days guide covers how to spend what you have.
If your reason for starting is bodyweight rather than fitness, read the best workout to lose weight before you build the week around running. Running is a fine tool for it; it is not the lever most people think it is, and the page explains which one is.
Gear, shoes, and the things beginners worry about
Running shoes that fit and are not a decade old cover almost everything. Beyond that, most gear questions are less important than the two decisions at the top of this page. A few honest notes:
- Shoes: get a pair that fits comfortably with a thumbnail of room at the toe. There is no evidence that a particular shoe category prevents injury; comfort is the criterion that has held up.
- Where to run: softer surfaces are gentler but uneven ones ask more of your ankles. A flat, well-lit route you will actually use beats an ideal one you drive to.
- Side stitches: usually settle with slower breathing and a slower jog. Eating a large meal close to a run makes them more likely.
- Pain: general soreness for a day or two after a new session is expected. Sharp pain, pain that gets worse during a run, or pain in one specific spot that keeps coming back is a question for a clinician — not something to log your way through or push past.
Frequently asked questions
How do I start running when I'm out of shape?
With a run-walk, starting at intervals short enough to feel easy — 60 seconds of jogging and 90 seconds of walking is a normal place to begin, and 30 seconds is fine too. Being out of shape changes the starting interval, not the method. Three sessions a week with a rest day between them, progressing by adding running time rather than speed, works from any starting point.
Is this the same as a couch to 5K plan?
Yes, in structure. Every couch-to-5K plan is a run-walk progression run three days a week for eight to ten weeks, and the eight-week table above is a conventional version of one. What ChatRPE adds is the part a fixed plan cannot do — running the intervals live with timers, and rewriting next week based on how the last three sessions actually went rather than on what the schedule says.
How do I run without stopping?
By practising running for longer, not by trying to run continuously sooner. The reason a run-walk gets you to a continuous 5K faster than gutting out unbroken runs is that it lets you accumulate far more total running time at a sustainable effort. Keep shrinking the walk break — 90 seconds to 60 to 30 — until the last one disappears.
How long should a beginner run?
Start by counting minutes of running, not distance: eight to ten minutes of actual jogging spread across a session is a reasonable first week. Distance takes care of itself once the running time is there, which is why every plan on this page is written in minutes.
How many days a week should I run as a beginner?
Three, with a day off between them. That is enough to adapt and few enough that the slow-adapting tissue keeps up. If you want to move on the off days, walk, lift, or cycle — the rest days guide covers what an off day is actually for.
Can an app run the intervals for me?
Yes. ChatRPE turns a run-walk into a live session with the intervals and their timers built in, shows the current one on your Lock Screen on iPhone, sounds a time-sensitive alert when each countdown ends, and saves the session to your history when you finish. It does not map your route or measure distance from your phone's location — you report distance and time, and the coach turns it into a structured entry.
What is the best app for a beginner running plan?
One that adapts the plan instead of just displaying it. A schedule in a notes app or a fixed program cannot know that your third session felt terrible; ChatRPE can, because you tell it in the same conversation that runs the session and holds the log. That is the difference between following a beginner running plan and being coached through one.
Do I need to warm up before an easy run?
Five minutes of brisk walking is enough before an easy run, and the first jog interval doubles as the rest of the warm-up. Save the longer routine for faster running later on; at this stage, starting slowly is the warm-up.