How to Host a Conference

'''

CONGRATULATIONS! YOU'RE GOING TO HOST AN OWASP EVENT!
''' Now what? Read on for some helpful guidelines to assist you in putting together a successful conference.

Preamble
Our intent in posting the guidelines at the OWASP web site is to give conference planners something more than "Good Luck" as they prepare to host an event. Just ask anyone who has put together an event of any size and they will tell you it's hard work, but can also be a lot of fun. We are an open community, so your peers are often a great resource. Refer to some of the other conference pages and contact the conference planners directly for advice. While it is almost impossible to cover EVERY detail of planning, we think we have put together a fairly comprehensive series of recommendations. We have included some issues that arise only at the larger conferences. We’ve left the comments mixed together so you can use what you need and to appreciate what you don't have to use.

We’ve also prepared a [Conference Planning Table] that summarizes these guidelines and gives you a check sheet to use as you plan your conference.

In addition to general guidence, we have also developed a set of tools and compiled a series of resources to help you plan a successful event.

STEP ONE - EVENT DEFINITION
OWASP AppSec Conference

These conferences are the flagship of the OWASP outreach effort. This will be an international conference sponsored by OWASP and approved by the Global Conferences Committee. AppSec Conferences include multiple days of multi-track plenary sessions in addition to pre-conference training offerings. AppSec Conferences, schedules, and trainings must be approved by the OWASP Global Conference Committee and will receive the full support of the OWASP Foundation. In any calander year, there will be no more than 4 AppSec Conferences of this size. Locations will be determined the prior year and planning must begin at a minimum of 12 months in advance.

OWASP Regional Conference

Regional conferences typically have lower attendance than AppSec conferences and typically include multiple days of single track plenary sessions. Training may or may not be offered at the descression of the regional conference planning team. Regional conferences are not subject to the same rigor as AppSec conferences in terms of planning and only require the local planning team deconflict scheduling with the Global Conferences Committee. Regional teams are free to brand their conference as they wish, as long as the OWASP affiliation is maintained. OWASP Foundation support may be available for large expenses at the discression of the Global Conference Committee.

OWASP Events

Events are typically single day or "OWASP Day" type events that are generally local in nature. Events typically have only one track and span anywhere from a half to a full day. Planning for these events are at the sole discression of the event team and may be branded in any manner so long as the OWASP affiliation is maintained. In general, significant OWASP Foundation support will not be available for these events.

STEP TWO - MAKE YOUR PLAN
The amount of planning, committee work, advance deadlines, etc., in part depends on the size conference you are planning. A general rule is to allow about a month for every 20 participants. For example, if you are expecting 200 attendees, you should begin to prepare at least 10 months in advance.

The general dates and time of the conference should be suggested by local variables as well as OWASP speaker availability. For example, it may not be a good idea to schedule a conference in Wisconsin in January or Texas in August due to potential weather conditions. Check the OWASP calendar to make sure there are not any conflicting events. If you plan to invite out of town speakers, it’s best to arrange them months in advance. Good speakers and instructors are often booked up to a year in advance.

Consider the size and scope of your conference. Small groups can be hosted nearly any time. But larger groups will require housing, transportation, and food services that might conflict with other events. Make sure to check the local community events to ensure there will be adequate accessibility to these needs.

BUDGET
has been developed by the Global Conferences Committee to assist in the budget planning process. The tool was originally designed for AppSec conferences but can be used for a conference of any size. When submitting a budget to the GCC, you are required to use this format.

Attendees should be expected to pay their registration fees in advance. This helps provide an accurate picture of the number who will attend because the attendees are more committed to attending. You can consider a slightly higher fee for late registrations or registrations onsite, if your food and facilities planning can handle extra last-minute registrations.

Your conference costs should be handled through the Foundation. Sponsorship funds, venue deposits, travel reimbursements, printing, etc will be managed for you. This allows you to focus more on the event content! Contact [mailto:kate.hartmann@owasp.org Kate Hartmann] as soon as possible to get this set up. Don't minimize the importance of a detailed accounting of your conference funds. Setting things up right before you begin to receive registrations fees can make things a lot easier during and after the conference.

VENUE
One of your very first items of business should be to reserve necessary rooms for plenary sessions, breakout sessions, classroom sessions, tech expo, breaks, receptions, and conference headquarters/registration. Adapt your conference to the facilities you have available. For example, good plenary sessions can be better than breakout sessions that don't have adequate facilities.

Try to keep conference costs down by using rooms that are free. Again, this may require some adapting or negotiating. Partnering with a local university is a great way to obtain free space.

A contract to secure your venue is critical. Only a member of the Board can enter into a contract on behalf of OWASP!!! Please forward contracts to be signed to [mailto:kate.hartmann@owasp.org Kate Hartmann] for signatures.

Training rooms will require space to accomodate generally 10-30 students per class.

Size for conference track rooms is best determined by the size of your event. Strategic agenda planning will ensure that all speaker rooms are full but not overcrowded.

CFP, CFT, PRESENTATIONS
Make sure every presenter knows rules enforced by OWASP Conferences. A signed agreement is required prior to speakers presenting the talk that maybe video taped. See standard OWASP Speaker Agreement. Note that the standard agreement implies you will be providing the presenters with a Powerpoint template. A standard OWASP Powerpoint template is [[Media:Presentation_template.ppt | available here]].

Also note that according to the standard OWASP Speaker Agreement, presenters must submit their presentations (in Powerpoint format) at least 60 days prior to the conference. Submissions should be uploaded to OWASP Presentations after the event.

CATERING
Well-planned meals and snacks are critical to a successful conference. Consult with your venue food services, or with a local caterer, determine what is needed, and what it will cost. Let food services or the caterer do the work.

Be sure to negotiate food services in such a way that you are not liable for food costs beyond what you can cover through conference fees. Usually food planners will allow up to 10% more people than you contract for (e.g., for late registrations), but be sure this is clear up front.

To reduce costs, seek sponsors for specific meals where possible. Some larger vendors are happy to get the publicity that comes from sponsoring a breakfast, lunch, reception, or even a dinner. In any case, it doesn't hurt to ask. If the sponsor desires it, let the sponsor choose the caterer and take care of the arrangements.

For small conferences, many if not most of the meals can be left up to the attendees. Be sure to provide a good list of local eateries. Include information about which are within walking distance, which are not, and how to get to those that are not.

Strategically scheduled snack breaks, with drinks and fruit or cookies, can add a touch of class to your conference. These don't usually cost too much, and can be covered by registration fees. Don't skimp on the time allotted for breaks, since attendees will want to network and will take the time anyway. Be sure to take care of all the caffine junkies in the crowd. If possible, try and arrange for a pre event tasting. You don't want people remembering your event for the bad coffee or sandwiches.

Be sure to allow for special dietary considerations. Always offer some vegitarian options for your meals.

AUDIO VISUAL/RECORDING
This is another critically important part of the conference, especially in our technology-driven organization. You should assign a member of your committee to head this up since it's a demanding and time-consuming responsibility.

To the extent that you can, schedule conference sessions in rooms that have basic AV equipment (overhead projectors and screens, for example). If the rooms already have computers and computer/video projection, that's even better. Then assign conference sessions to the appropriate rooms.

Determine ahead of time what portable equipment you have available, and whether you have to rent equipment. OWASP owns one projector that can be "loaned" out for events. Contact [mailto:kate.hartmann@owasp.org Kate Hartmann] to arrange for the shipping of this and other items. When you confirm conference presentations, ask presenters to provide you with a list of equipment they need.

TRAVEL
Your conference venue usually has maps and travel information on how to get to the location. If there aren't adequate limo or shuttle services to your venue from the airport, you may need to make your own arrangements.

It is customary for conferences to cover the direct travel accommodations of board members and committee members as well as a reasonable per diem for expenses so budget accordingly.

OWASP on the MOVE funds are not to be used for conferences or events. If you are planning on covering ANY speakers travel and/or accomodations, be sure to plan for this in your event budget.

ADVICE FROM THOSE WHO HAVE BEEN THERE
Organize a conference committee as early as possible.

Communicate regularly with the OWASP leadership. There's lots of history that you can use to your advantage such as format, what works and what doesn't, etc. Also, remember that you're the host, but it's not your conference; you should be working with them (the organization's leadership) to meet their objectives.

Establish regular planning/reporting meetings. Set up email lists. Always make it clear who is supposed to do what and when. Keep minutes/notes of your meetings and use them to follow up. The more you communicate with each other, the less likely you'll have slip ups.

Here is a sample wiki page to get you started AppSec Sample Conference

One of your very first items of business should be to reserve necessary rooms for plenary sessions, breakout sessions, classroom sessions, tech expo, breaks, receptions, and conference headquarters/registration.

Adapt your conference to the facilities you have available. For example, good plenary sessions can be better than breakout sessions that don't have adequate facilities.

Try to keep conference costs down by using rooms that are free. Again, this may require some adapting or negotiating.

International meetings usually have a general theme. However, for regional meetings, you may want to choose a theme that reflects your chapter's particular strengths or interests.

A good program is critical. Look for variety, interest, timeliness. What do your members need or want to leave with? Try to balance lectures with discussions, hands on, social activities, and time for colleague interaction.

A general call for presenters should have a deadline that gives you ample time to recruit and to fill in gaps should you not get all the good proposals you need. Network with other members of your organization to identify people who might be invited to make presentations. Immediately after the deadline, begin organizing the conference schedule. Select the proposals you want to use and contact them to verify their availability. Create a tentative schedule, matching presenters to the facilities. You may want to lay out your schedule on a whiteboard, or use 3x5 cards on a corkboard so you can visualize how things fit together. Make sure you plan time for attendees to talk with each other, such as at breaks, before and after dinners, at receptions, etc.

Send a formal acceptance note to each participant, and ask them to confirm by sending an abstract (if you didn't get that as part of their submission) and submitting a request for any special equipment (AV, computer, etc.)

Presenters and Presentations
Make sure every presenter knows rules enforced by OWASP Conferences. A signed agreement is required prior to speakers presenting the talk that maybe video taped. See standard OWASP Speaker Agreement. Note that the standard agreement implies you will be providing the presenters with a Powerpoint template. A standard OWASP Powerpoint template is [[Media:Presentation_template.ppt | available here]].

Also note that according to the standard OWASP Speaker Agreement, presenters must submit their presentations (in Powerpoint format) at least 60 days prior to the conference. Submissions should be uploaded to OWASP Presentations after the event.

Design Components
In designing your own Powerpoint templates, tshirts, bags, badges, banners, flags, carpets and what have you, find the original vector graphic of the OWASP logo (in EPS and AI formats) [[Media:OWASP_Logo.zip | here]]. Please do share them with the other conference chairs!

Promotions
Promoting your conference begins as soon as you have selected a conference site and date. Post the date and location on the OWASP web site. If you have the expertise and resources, you should consider setting up your own conference wiki page for up-to-date information, on-line registration, proposal submissions, etc. Make sure to review pages for other conferences for great ideas and to allow for continuity in page style.

The first wave of publicity comes with the call for presentations.

The next wave comes as you send out the conference announcement, with as much detail as you have, including a tentative program. This is important if you want to convince people they should come. Set a registration deadline that accounts for your own deadlines (food services, etc.) You may have to consider a higher fee for those who are late, especially if that really does incur additional costs for you.

Housing
Estimate the number of people you think might attend (review previous conference attendance) and make arrangements accordingly. In addition to blocking some rooms at a local motel/hotel consider economy lodging (dorms, conference centers, etc., if available), for those who prefer that kind of housing.

When making reservations with local hotels, negotiate other amenities if possible such as shuttle services (from airports, to conference sessions).

Be careful to avoid making reservations that require guarantees or other financial obligations. In fact, it's best to let the housing/hotel organization handle their own reservations and billing. Find out how long reservations can be held, cancellation deadlines, etc.

Travel
Your conference venue usually has maps and travel information on how to get to the location. If there aren't adequate limo or shuttle services to your venue from the airport, you may need to make your own arrangements.

Food
Well-planned meals and snacks are critical to a successful conference. Consult with your venue food services, or with a local caterer, determine what is needed, and what it will cost. Let food services or the caterer do the work.

Be sure to negotiate food services in such a way that you are not liable for food costs beyond what you can cover through conference fees. Usually food planners will allow up to 10% more people than you contract for (e.g., for late registrations), but be sure this is clear up front.

To reduce costs, seek sponsors for specific meals where possible. Some larger vendors are happy to get the publicity that comes from sponsoring a breakfast, lunch, reception, or even a dinner. Your own college may be willing to sponsor one such event. In any case, it doesn't hurt to ask. If the sponsor desires it, let the sponsor choose the caterer and take care of the arrangements.

For small conferences, many if not most of the meals can be left up to the attendees. Be sure to provide a good list of local eateries. Include information about which are within walking distance, which are not, and how to get to those that are not.

Strategically scheduled snack breaks, with drinks and fruit or cookies, can add a touch of class to your conference. These don't usually cost too much, and can be covered by registration fees. Don't skimp on the time allotted for breaks, since attendees will want to network and will take the time anyway.

If you do have group meals, be sure to allow for special dietary considerations.

Management Tools
Larger, OWASP lead conferences can be processed through the Cvent system. For smaller conferences (less than 50 people) an Excel spreadsheet should work fine to manage registrants. If you would like the OWASP office to manage registration for you, please contact [mailto:kate.hartmann@owasp.org Kate Hartmann] as soon as possible to set up your on-line registration process.

Money
Before sending out the conference brochure/announcement, you must determine a conference registration fee. On the one hand, you want to cover your costs. But on the other, you want to keep the costs low so that as many people as possible can afford to come. Try to find a balance between providing the amenities, and keeping costs down. Be sure to include the following costs: Publicity (brochure, printing, mailing), speaker fees or accommodations, facilities (equipment rentals), transportation, meals (snacks, meals), conference materials (packets, name tags, etc.)

Attendees should be expected to pay their registration fees in advance. This helps provide an accurate picture of the number who will attend because the attendees are more committed to attending. You can consider a slightly higher fee for late registrations or registrations onsite, if your food and facilities planning can handle extra last-minute registrations.

A special account can be set up through OWASP just for your conference. You can use this account to process sponsorship, donations, manage expenses, and help you keep tabs on vendor costs. Again, contact [mailto:kate.hartmann@owasp.org Kate Hartmann] as soon as possible to get this set up.

Don't minimize the importance of a detailed accounting of your conference funds. Setting things up right before you begin to receive registrations fees can make things a lot easier during and after the conference.

Vendor Displays
An exhibit hall must be easily accessible and must have adequate space to accommodate vendor booths. There may be costs associated with such a hall. Some facilities require that their own people set things up. Make sure you know what is included with any rental costs, and what you may have to pay extra for.

Make sure that there is adequate time for attendees to visit the exhibits and to talk with vendors. Directing breaks and snacks into the vendor expo will encourage participants to visit the exhibits. Depending on the benefits to the vendors, you may ask that they pay for exhibit space, or leverage their participation by asking them to sponsor one or more conference activities (reception, meal, etc.).

Conference Materials
At a minimum, you need to provide some sort of printed program. For most conferences, the following is usually adequate: a simple folder with program, maps, lists of local restaurants and attractions, a name tag, and writing materials (pen and pad). For larger, conferences you may want to include a conference bag that includes OWASP books or handouts. Be sure to allow ample time for printing and shipping of OWASP materials. International shipping can take several weeks.

Name Tags
If you plan properly, you should be able to generate name tags to be printed from your conference database program. If you process your registrations through the OWASP office, they can create your nametags.

Keep the name tag layout simple: a small conference logo or title, the person's full name in LARGE, readable letters, and the person's institution. Don't make people squint to read names on name tags.

The actual type of name tag (paper stick-on, pin on plastic case, hang-around-the-neck, etc.) depends on your preferences and budget. If you do provide stick-on tags, you may want to generate at least one tag for each day of the conference since they won't be able to reuse the tags. If you use plastic badges, you can invite attendees to recycle them at the end of the conference.

Equipment and Support
This is another critically important part of the conference, especially in our technology-driven organization. You should assign a member of your committee to head this up since it's a demanding and time-consuming responsibility.

To the extent that you can, schedule conference sessions in rooms that have basic AV equipment (overhead projectors and screens, for example). If the rooms already have computers and computer/video projection, that's even better. Then assign conference sessions to the appropriate rooms.

Determine ahead of time what portable equipment you have available, and whether you have to rent equipment. Then when you confirm conference presentations, ask presenters to provide you with a list of equipment they need.

Entertainment
Depending on the size and scope of the conference, you may need to provide for one or more social activities for attendees.

At smaller conferences, organized dinners at local restaurants can be enjoyable. For larger conferences, a banquet may be in order. At the very least, provide a list of recommended local eateries for those who want to venture out on their own.

You should also consider whether your locale has something uniquely interesting to offer. If feasible, you could organize a group outing to a play, local site, etc. Be sure to determine whether costs are included in the registration, or if it is to be a separate (and therefore optional) cost.

Whatever you plan, however, be sure to include some free time for people to do things on their own.

Presenters and Presentations
Overall OWASP Conferences Chair is ([mailto:dave.wichers@owasp.org Dave Wichers], Aspect Security).


 * Standard Speaker Agreement
 * [[Media:Presentation_template.ppt | Standard Powerpoint template]]
 * Slides should be uploaded to OWASP Presentations.
 * Original vector graphic of the OWASP logo (in EPS and AI formats) [[Media:OWASP_Logo.zip | here]]. Please do share them with the other conference chairs!

'''

Helpful links
''' Conference Planning Timeline

Speaker Template

Sponsor information

Suggestions for wiki

Wiki Template