Logging a run manually
Logging is where the magic happens: every run you record is matched to your plan, feeds your shoe mileage, and powers your analytics. Here's how to log manually.
[[SCREENSHOT OF THE LOG-RUN SCREEN]]
Forecast vs. Actual
Two words you'll see throughout Løbeapp:
- Forecast — a planned session from your active programme.
- Actual — a run you actually did.
When you log a run against a planned session, the Forecast is marked logged (derived automatically — never something you toggle). That pairing is what lets the analytics compare plan vs. reality.
Log a run against a planned session
This is the main flow once a programme is active:
- From your Dashboard or Planned sessions (list or calendar view), open the session you completed.
- Choose to log it, and fill in what you did — distance, time, and segment splits.
- Save. The planned session now shows as logged, and your run is recorded as the Actual.
Løbeapp also helps from the Log run screen: if your run matches a planned session, you'll see "Matches planned session" with a one-tap Log against this plan — so a spontaneous log still lands against the right plan.
[[SCREENSHOT OF THE "MATCHES PLANNED SESSION" PROMPT]]
Log an open run
No plan, or just ran for the joy of it? Open Log run and record it directly — date, distance, time, and any segments. It's saved as an Actual with no planned session attached. Open runs still count toward your shoe mileage and analytics.
Log other training
Not every workout is a run. Use Other training for strength, cycling, swimming, or anything cross-training. Here duration is the headline — there's no distance, surface, or shoe — so your effort still shows up in your history without distorting your running metrics.
Add segments and splits
A run is more than one number. Break it into segments to capture the detail that makes analytics useful:
- Each segment can hold distance, pace, duration, heart rate, and a label.
- For interval sessions, label your work segments as reps — that's what the Interval analysis reads to chart your pacing and spread.
- For long runs, logging your splits lets the analytics show your progressive finish.
:::tip Log heart rate when you can Pace tells you how fast; heart rate tells you how hard. Together they unlock your efficiency trend — the clearest signal that real fitness is building. :::
Attach a shoe
Pick the shoes you ran in, and Løbeapp adds the distance to that pair's accumulated mileage automatically. (Other-training entries don't take a shoe.)
Mark effort (RPE)
RPE stands for Rate of Perceived Exertion — a simple, honest score for how hard a run felt, on a scale of 1 to 10:
| RPE | Feels like |
|---|---|
| 1–3 | Very easy — you could talk in full sentences or hold this all day |
| 4–6 | Moderate — comfortably hard, conversation gets choppy |
| 7–8 | Hard — a tough tempo or threshold effort, talking is a struggle |
| 9–10 | Very hard to maximal — near or at all-out, a sprint finish |
Pace and heart rate tell you the numbers; RPE captures everything they miss — poor sleep, heat, stress, a head cold — that makes a run feel harder than it looks on paper. Log it right after the run, while the feeling is fresh, and base it on the session as a whole.
It feeds your training-load and long-run views, and helps catch fatigue before it catches you — effort creeping up while your pace holds steady is an early warning sign.
Skip or undo a planned session
Didn't run a planned session? Skip it to keep your week honest — skipped sessions are excluded from your streak and follow-through. Changed your mind? Undo returns it to planned.
Skip the typing
Two shortcuts take the manual work out of logging:
- Co-driver Pro — add screenshots of your watch or training app's lap list and let Co-driver pre-fill the segments for you to review.
- Apple Health import — in the iOS app, runs detected in Apple Health are staged for you to confirm and log in a tap.
Next steps
- Track your shoes.
- See it all add up on the Analytics dashboard.