CONFERENCE  

Submission Form

The submission form will ask you for these five key items:

1. Contact information
   Please provide full contact information and include a short biography
    
2. Session description
   A description of your presentation as you would have it appear in the conference program in 100 words or less.
    
3. Intended audience and prerequisites
   In 40 words or less, describe what section of our audience would best benefit from this session. Is prerequisite knowledge necessary for understanding the content of the session?
    
4. Session takeaway
   In 40 words or less, describe what attendees will learn from your session.
    
5. Outline/Extended abstract
   Provide a description of your presentation in greater detail, absolutely no proposal will be considered without it. You can either enter your extended abstract in the provided text box, or upload a text file (in .txt format). For submissions using the input box, please limit your expanded description to 500 words. For submissions using the file upload, limit your expanded description to one to two pages.
   

Submission Process

The Advisory Board will review and rate submissions based on the following criteria:

• Concept: This is the basic idea of your submission. Is it interesting? Is it relevant? Will it be beneficial for game developers to hear? There is plenty of room for innovative ideas and also the tried and true.
• Depth: Is the basic idea well considered and thought out? To what extent will the audience gain insight? The more in-depth, the better.
• Organization: Are your ideas conducive to present in front of an audience? Will the Advisory Board understand what you are trying to say? Organization helps.
• Credentials: How do your credentials qualify you to speak on the topic you have proposed?

How do I propose a vendor-specific session?
We want our talks to be opportunities for professional game developers to share their ideas and experiences. Proposals that are commercial or marketing in nature will not be considered. In general, content specific to proprietary products and technologies is considered sponsored material. The Advisory Board and conference management reserve the right to exercise their editorial discretion. If you would like to publicize a product, please contact our sales team for more information on sponsorship opportunities, including sponsored sessions (single lecture, full-day/half-day tutorial or developer day).

When will I be notified of the status of my submission?
You will receive an automated email response once your submission is received. We will notify you of the status of your submission via e-mail within 60 days of the submission deadline. If you do not hear from us, please contact Meggan Scavio at meggan.scavio@ubm.com (US) or Maggie Xia at maggie.xia@ubm.com (China).

Speaker Expectations

When you agree to speak at GDC China, you are making a commitment to deliver a well prepared talk and to speak on the topic you have proposed. We ask that you do not drastically change the submitted topic or content. The talk you present must be the talk that was submitted and accepted. 

We expect our speakers to submit a presentation in both English and Chinese for the online conference archives.

The submitter also  agrees to be available to present his/her session during any day of GDC China (September 15-17, 2013).

Track Descriptions and Topics

Below is the list of tracks that GDC China 2013 will focus on:

Presentation Formats

As you can see below, there are multiple time period choices. It's up to you to select the appropriate duration for your session.

Format	Duration	Description
Lectures	60 minutes	Lectures are issue-oriented, provide concrete examples, and contain both practical and theoretical information. They are 60 minutes long (including answering questions from the audience). We generally prefer only one speaker but we may accept two if you can demonstrate the second person is necessary.
Panels	60 minutes	Panels take many different viewpoints on a topic or issue and combine them in one venue. Debate among panelists (with very different opinions) is most welcome and audience participation time should be accounted for.
Tutorial	Half-Day/Full-Day	Tutorials (simply) must teach attendees new skills. Think of this as (informal) classroom training. It can be interactive; you can have them work in teams; you can give them challenges; you can include competitions. The result of the time period MUST be that they'll feel they've learned something truly useful in the world of game development. It can be a skill, an ability, a method or even the mastery of a tool.

NOTE: We do NOT supply any hardware (like laptops) for the attendees.  If you need the attendees to bring anything with them, this must be CLEARLY stated in your abstract.