Development Maintenance - Current Events tab - Details sub-tab

Event

Code

Code referring to the event.

Description

Description of the event.

Status

Status of attendance for the selected person.

Attendee Date/Time

Start

Start date of attendance for the selected person, if different to the start date of the event.

End

End date of attendance for the selected person, if different to the end time of the event.

Hours

Number of hours which this person is able to attend.

Comment

Any comments relating to this person's attendance at the event.

Delete an event from the grid area.

Launch into the Events Maintenance window for the highlighted event. See Maintaining events.

Status

Status of the attendee. For example, whether attending or unable to attend.

Note: This Status field relates to each attendee, whereas the other Status field above the attendees grid is used for selecting records to view.

Primary Only

Select to include the primary attendee only.

Note: This field is not editable.

The default is to include the attendee and their spouse, if they have one.

Bulk Movable

If selected, this attendee can be moved to the Past Attendees tab once the event is concluded.

Clear if you want this guest to remain in the Current Attendees tab. For example, staff members can attend multiple events.

Table Name

Name that the table is known by, if tables are used at the event. For example, tables can be given humorous names for a trivia night event.

Table Number

Nominate the table that the attendee is seated at, if numbered tables are used at the event.

Table Captain

Select to indicate that the attendee is the nominated leader for the table, if tables are used at the event.

Cost

Cost of each type of ticket.
The costs are defined using the Attributes tab of the Events Maintenance window. See Events Maintenance - Attributes tab in the Development manual.

Tickets

Number of tickets issued to the attendee.

Deposit Rcvd

Amount of the deposit received.

Total Rcvd

Total amount received so far.

Comment

Add any general comments about the attendee and their guests.
If a person was bulk added, this field also contains the line number and constituency, to differentiate bulk-added groups. For example, the first group that is added into the communication has line number 1 and their constituency, and so on.

Dietary Requirements

List any special dietary requirements for the selected person. For example, the primary person may be a vegetarian while their partner may be a vegan.

Note: This field is automatically populated with the value from the Dietary Requirements field on the Other tab of Community Maintenance. See Community Maintenance - Other tab in the Community manual.

Physical Requirements

List any requirements to cater for particular physical needs. For example, wheelchair access is required.

Note: This field is automatically populated with the value from the Physical Requirements field on the Other tab of Community Maintenance. See Community Maintenance - Other tab in the Community manual.

Start Date

Date if the starting date of the person's attendance is different from the event's starting date. For example, an event can cover several days but the person only attends for part of the event.

End Date

Date the person finishes attending the event, if this is different from the event's end date. For example, an event can cover several days but the person only attends for part of the event.

Hours

Number of hours the attendee attends the event.

Ticket type

Lists all the types of tickets available for this event. For example:

• Adult
• Student
• Concession.
  The ticket types are defined using the Attributes tab of the Events Maintenance window. See Events Maintenance - Attributes tab.

Cost

Cost of each type of ticket. The costs are defined using the Attributes tab of the Events Maintenance window. See Events Maintenance - Attributes tab.

Override

Select to override the ticket price. For example, offer a discount to this particular attendee.