Service intervals

A service interval is recurring maintenance you schedule and we remind
you about when it becomes due. Set them at two levels:

• Per-component — chain lube every 300 km, brake bleed every
  6 months, and so on.
• Per-bike — bike-level services like an annual tune-up, a bearing
  service every 5,000 km, or a frame inspection every year. Managed
  under Bike → Service.

Service intervals are included on every plan. Steel (free) covers up
to 5 intervals in total across all your bikes and components; Alloy
and Carbon are unlimited. We alert you when one becomes due, and the
countdown resets when you
record the service.

Service intervals vs. component lifespan

These two look similar but answer different questions, so it's worth
being clear on the difference:

• Component lifespan (the wear bar) tracks a part wearing out.
  You set an expected lifespan — say a chain good for 5,000 km —
  when you add the component; we show
  a wear progress bar and alert you at 80% (warning) and again past
  100% (critical). It's a one-time countdown: once you replace the
  part, it's a fresh component starting from zero.
• A service interval is recurring upkeep that keeps a part
  healthy — lube, bleed, sealant top-up, a periodic service. It resets
  every time you record the service and immediately starts counting
  toward the next one.

In short: lifespan answers "when do I replace this part?"; a service
interval answers "when do I next maintain it?" The same chain can have
both — a 5,000 km lifespan and a 300 km lube interval.

Three kinds of intervals

Distance-based

Example: Replace chain every 3,000 km.

• Best for components that wear predictably with use.
• Updates automatically when your bike is linked to Strava.
• We alert you as you approach the limit.

Time-based

Example: Replace brake pads every 6 months.

• Choose the unit: days, weeks, months, or years.
• Good for components that age regardless of use (rubber, sealant).
• Useful for periodic maintenance tasks (lube, sealant top-ups).

Riding-time-based

Example: Service suspension every 50 riding hours.

• Counts actual moving time from your rides, not calendar days or
  distance.
• Best for parts that wear with hours in use — suspension, or a
  drivetrain that sees a lot of indoor-trainer time.

Extra options

When you create or edit an interval you can also set:

• Reset on transfer — should the countdown restart when the
  component moves to a different bike? On for things tied to a
  bike (e.g. cable service), off for things tied to the part
  itself (e.g. chain wear).
• Baseline date — the reference point the time-based interval
  counts from (install date, last service, or a custom date).

Suggested intervals (general guidance)

These are rules of thumb. Your real intervals depend on riding
conditions, component quality, and how aggressively you ride.

Related

• Add a component to set its expected
  lifespan (the wear bar).
• Record a service when you finish
  the work.
• Maintenance alerts explains
  exactly when we email you.