# \[Web\] New Course Analysis tab — pace your events from the actual course

**URL:** <https://tempo.discourse.group/t/web-new-course-analysis-tab-pace-your-events-from-the-actual-course/59>\
**Category:** What's New\
**Created:** [September 17, 2026, 8:35pm UTC](https://tempo.discourse.group/t/web-new-course-analysis-tab-pace-your-events-from-the-actual-course/59 "2026-09-17T20:35:37Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marc](https://sea1.discourse-cdn.com/flex039/user_avatar/tempo.discourse.group/marc/32/56_2.png) [@Marc](https://tempo.discourse.group/u/Marc)\
**Post date:** [September 17, 2026, 8:35pm UTC](https://tempo.discourse.group/t/web-new-course-analysis-tab-pace-your-events-from-the-actual-course/59/1 "2026-09-17T20:35:37Z")

</div>

**What’s new**

Every event in your calendar now has a **Course Analysis** tab beside **General**. Upload the route as a GPX file, pick how hard you intend to ride, and Tempo simulates the ride segment by segment and fills in **Distance** , **Climbing** , **Est. Time** , **Avg Speed** , **Norm Power** , **Avg Power** , **Intensity** , **Load** , **Calories** and **Carbs**.

Effort is one choice you can express three ways: the **Effort** slider ( **Easy** , **Moderate** , **Steady** , **Hard** , **Very Hard** , **Threshold** , **Time Trial** , **Criterium** ), a **Norm Power** , or an **Estimated Time**. Set any one and the server solves for the other two. **Rider & Setup** shows what it assumed — **FTP** and **Body Weight** from your profile, **Riding in a Group** , and under **Adjust Setup** the **Bike & Gear Weight** , **Temperature** , **Surface** and **Position** , each starting from a default for the event type. The numbers come from the Martin et al. power equation applied to every segment of the course — gravity against the gradient, rolling resistance for the surface, aerodynamic drag for your position, air density scaled for altitude and temperature — not a flat-road average speed.

With a GPX course you also get the **Route** map with each climb numbered and shaded green-to-red by difficulty, matching its row in the **Climbs** table, the **Elevation & Power Guide** with the zone to ride over the profile, and the **Climbs** and **Descents** tables. Hover a climb row or a point on the profile and the same stretch highlights on the other two. Without a GPX file you still get the headline numbers. Whatever the plan says is what gets saved on the event, so your fitness projection and fuel plan read the same numbers.

**Why it helps**

The duration and load on an event used to be a guess, and the taper and the fuel plan inherited the guess. Now they come from your route at your FTP, on your bike, at the temperature you expect. And the power guide gives you a number for each climb before you are on it, which is where most events are won or lost: a 50.6 mi coastal loop with 5,335 ft of climbing ridden **Steady** comes back as 3 h 52 m at 180 W, 212 Load and 239 g of carbs, with 194 W on the seven-mile climb at mile 37.8.

**How to try it**

Open **Calendar** → a date → **Add event entry** (or open an existing event), fill in the event type and distance on **General** , then switch to **Course Analysis** and click **Upload a GPX course**.

Note: The **Elevation & Power Guide** , **Climbs** and **Descents** require a Premium subscription. The course metrics, the **Effort** slider and **Rider & Setup** are visible to everyone.

**Example**

 ![Screenshot 2026-09-17 at 12.23.17 PM](https://us1.discourse-cdn.com/flex039/uploads/tempo/original/1X/6e5cfc2e8f5e59f896340989e076b23c1e3b0321.jpeg)