Proposal Checklist

Use the following checklist to help your proposal is the best it can be.

• Information for each speaker has been listed on a separate tab of the proposal submission.
• Title is 65 characters or less.
• Title has been entered in sentence case. Avoid "The First Drupal 8 Release Candidate Is Here." 
Embrace "The first Drupal 8 release candidate is here."
• Title is clear and direct. A potential attendee can understand the general idea without reading the session description.
• Description: Provide a detailed description of the presentation, including interactive elements. Include information on the session content and function. 
• Three learning objectives are listed, state the desired outcome, and finish the sentence “At the end of this session, attendees will be able to…” Action verbs (“apply,” “perform,” “develop,” etc.) rather than “learn” or “understand” have been used. (Learn more about learning objectives. See an example on the sample session page.)
• Target audience is specific about the type of person who will get the most out of your session and finish the sentence “This session is for…” (Stating “anyone” is not helpful to reviewers or attendees. Find examples of target audience in the target audience section of linked Venn diagram.)
• Prerequisites explain what knowledge or experience will you assume an attendee will have when coming into your session and finish the sentence “Attendees will get the most out of this session by being familiar with…” (Stating “none” is not generally helpful to reviewers or attendees.)
• Language is plain, clear, concise, and inclusive.
• Jargon has been avoided or defined.
• Acronyms have been spelled out.
• Session content does not shame competitors, tools, communities, etc.