Train for a 5K with ChatGPT or Claude.

First 5K versus a faster 5K: two different goals

Completing a 5K is mainly about building enough easy, continuous running that 5 km feels manageable. A faster 5K keeps that base and adds work at and around race effort, which needs more careful recovery.

If you’ve only just finished a beginner programme, the Couch to 5K page covers that stage. This page picks up from there, whether the next target is running the whole way or a time that starts with a 1.

What determines useful 5K training advice

Three facts do most of the work: where your 5K is now, how much you’re running, and how many days you have. A plan for a runner on three days a week looks nothing like one for a runner on six, even at the same PB.

Constraints come next. A recurring calf strain, a job with early starts or a local area with no flat routes all change which sessions are realistic. An AI that doesn’t know them will plan around a runner who doesn’t exist.

Your current PB and recent fitness

A PB records your best day. Recent fitness is what the next block starts from. A 19:58 from four years ago and a 21:30 last month describe different runners, and pace targets built from the old number can leave every session feeling too hard.

Athmex stores PBs and current performances with the dates they were set, so ChatGPT or Claude can tell the difference. When a new time comes in, tell the assistant and ask it to update your profile.

Easy running, faster work and recovery in context

Good 5K training still rests on plenty of easy running. Faster sessions, such as reps at around 5K effort, short hill reps or a steady run near threshold, sit on top. The mix depends on the runner, and more hard sessions aren’t automatically better.

Recovery is where context matters most. A 45-year-old with a physical job and a 25-year-old with a desk job and free evenings recover differently. Your AI can only allow for that if it knows who you are.

Using parkrun as a goal or a benchmark

Standard Saturday parkruns are 5 km, which makes parkrun a natural first goal and a repeatable benchmark. Running the same course regularly gives you comparable times, as long as you allow for weather, mud and how busy the start was.

Courses differ, though. A flat tarmac loop and a hilly grass course can produce meaningfully different times for the same runner. If you add your home parkrun as a race or a note in Athmex, the assistant can read your times in context rather than comparing them with somebody else’s course.

From completion to PB

Many runners start parkrun hoping to get round and later decide they want a time. That’s a change of goal, and it’s worth recording. The training that got you round won’t necessarily take you under 25 or 20 minutes.

When pace zones or threshold information become useful

For a first 5K, perceived effort is enough. Once you want a time, pace information helps the assistant pitch sessions accurately. A recent 5K or 10K race time is a good starting point, and a threshold pace from a test or a coach adds precision.

Heart-rate zones can help too, especially for keeping easy runs easy. If you know your threshold heart rate or maximum heart rate, add it. If you don’t, leave it blank. Athmex keeps unknown values unknown rather than guessing.

Adapting when your training days change

A new job, a holiday or a child starting school can turn a five-day week into three. Ask ChatGPT or Claude to rework the plan and it should keep the sessions that matter most for your goal and drop what matters least.

Update your availability in Athmex when it changes and future conversations start from the new reality. If 5K is going well and you’re eyeing a longer race, the 10K training page covers what changes when the distance doubles.