Skip to main content
All CollectionsBudget Builder questions
What do the columns on the event summary table mean?
What do the columns on the event summary table mean?

Understanding Participant Breakeven, Projected Participants on Race Day and other event summary table metrics.

Updated over a week ago

Entry fee

The weighted average entry fee for the event.

For events that have a single entry fee for the entire registration period, this is simply the value of that entry fee.

For events with multiple pricing periods (e.g. an early-bird period followed by one or more price increases), Entry fee is calculated as the weighted average of your different entry fees, weighted by the number of projected participants for each period.

Reg. participants

The number of people already registered for the event.

Proj. participants

The number of people expected to have registered for the event by race day.

% Full

The percentage of your projected participants that has already registered for your race.

% Full is calculated simply as the number of registered participants divided by the number of projected participants.

How to use % Full:

You can use % Full to track your event's capacity utilization, i.e. how "full" your event is at any one time. You want this number to be as close as possible to 100% on race day.

Participant breakeven (PB)

The minimum number of participants required to ensure an event turns a profit.

PB is calculated using an event's P&L (see below) and it is the minimum number of participants that, if used as the number of Proj. participants for a given event, will result in a positive event P&L.

How to use PB:

You can use PB as a profitability threshold: aim to have this number of participants in your event to avoid financial loss. If Reg. participants exceeds your event's PB number, your event is profitable, and vice versa.

Race Day Participants Estimate (RDPE)

An estimate of the number of participants expected on race day, based on the number of currently registered participants.

The RDPE calculation uses the number of Reg. participants (i.e. the number of people currently registered for the event) and data on when participants register for different types of events (5Ks, 10Ks, marathons etc) to provide an estimate of how many participant signups you are likely to have by race day.

Note that:

  • PPRD is an estimate, based on statistical averages for your type of race, and should only be used as a rough guide on race day participation.

  • The underlying data used in the calculation of PPRD come from RunSignup's RaceTrends report, and PPRD results will only appear over the last 180 days to race day.

How to use RDPE:

You can use RDPE to evaluate how far ahead/behind your current registrations are against your projected participants number. If RDPE is higher than your Proj. participants number, it means your registrations are ahead of where they should be at the current time, and vice versa.

Participant Profit Margin (PPM)

The net profit made on each additional participant registration.

When you increase the number of Proj. participants by 1, your event's P&L should increase by this amount.

How to use PPM:

PPM is the profit margin you make on each additional sign-up, so you can use it as a guide to determining your customer acquisition cost (i.e. how much money you'll willing to spend to acquire an additional participant) and your return on advertising spend (ROAS).

Profit & loss (P&L)

The profit or loss made on a specific event.

An event's P&L is calculated from the sum of all the revenues and costs associated with that event. Revenues and costs that use a specific event in the Event column are attributed to that event's P&L, whereas revenues and costs attributed to All events are split equally between your race's events for the purposes of P&L attribution.

The sum of all event P&L values adds up to your total budget profit or loss.

How to use P&L:

You can use P&L to understand which events in your race might be making you money and which events in your race might be losing you money.

Did this answer your question?