Skip to main content

Estimated Revenue by Event Report

Learn how to use the Estimated Revenue by Event report.

Updated over 11 months ago

Use Cases:

Revenue Forecasting: The report provides a detailed breakdown of estimated revenue by month and by event. This helps the sales team to forecast future revenue and identify peak periods.

Pipeline Tracking: The report categorizes revenue by status (Preliminary, Potential, Uninvoiced, Invoiced, Received). This helps the sales team track the progress of each event from initial quote to final payment. By monitoring these statuses, the team can identify bottlenecks and take action to move events through the sales pipeline more efficiently.

Event Analysis: By analyzing the close rate and revenue generated by different types of events and divisions, the sales team can identify which types of events drive the most revenue. This information can be used to focus sales efforts on high-revenue event types and optimize the event portfolio.

Strategic Planning: The report provides insights into the average estimated revenue per event and per event day. This data can be used for strategic planning, such as setting sales targets and budgeting.

Field Information:

Field Name

Data Type

Filter

Description

Event Code

String

The Event Code or "Event ID" is a system-generated or customer-generated identifier for events. There can only be one Event Code/ID per Event. Settings for the Event Code/Event ID are located in Company Settings>General>Event Settings

Event Name

String

Y

The Event Name or "Event" field is the common title of an Event; visible in calendar views, orders, reservations, and crew-facing communications

Event Type

String

Y

Event Type is a Customer-generated list used to classify events for filtering and reporting purposes; examples include "Corporate, Concert, TradeShow" etc.

Event Division

String

Y

Event Division is not used by all customers, but is commonly used to deliniate different business units or departments. Divisions are different than warehouse locations and can either mirror the setup of warehouse locations in a multi-warehouse environment, or represent a different grouping (Southeast vs Northeast, etc). Event Divisions can be used as a calendar filter and can also be used on crew profiles. There can only be one Division per Event, and if used on crew profiles, one Division per crew member.

Event Status

String

Y

Event Status is commonly used as the Sales status of an Event. The Event Status can be used as a filter in calendars as well as in reports.

Event Account Manager

String

Y

Event Account Manager is the resource listed in the "Account Manager" field on the event.

Event Lasso Code

String

The Event LASSO Code is the Event Code generated by the LASSO System, generally used for API integrations

Event Start Date

Date

Y

The Event Start Date is the first date listed for the event in "event dates" in the 'General Info' Spoke in an Event

Event End Date

Date

Y

The Event End Date is the last date listed for the event in "Event Dates" the 'General Info' Spoke in an Event

Event Client Name

String

Y

Event Client Name is the Client listed on the 'General Info' Spoke in an Event. This is primarily the name of a company, not the primary contact

Event Client Email

String

Event Client Email is the Email Address for the Primary Client Contact on an Event

Event Venue Name

String

Event Venue Name is the primary Venue listed on the 'General Info' Spoke of an Event

Revenue Status

String

Y

There are 5 Revenue Statuses Available: -1 - Canceled
0 - Declined
1 - Preliminary
2 - Potential
3 - Uninvoiced
4 - Invoiced
5 - Received

Estimated Revenue

Currency

Estimated Revenue is the saved Quote value

Did this answer your question?