Concept Document | Game Testing All in One (Game Development Series)

As discussed in Chapter 5, this is a more detailed version of the pitch document. It's too large to use in a presentation meeting, but you should leave it for the publishing team to give them a more in-depth understanding of your game.

High Concept. The one - or two- sentence statement of the experience you're trying to create. This shouldn't change from the pitch doc.
Genre. A discussion of the genre your game falls under. This section should include comparisons to other titles in the genre .
Gameplay. A description of the kinds of actions the player can perform during the game, along with some examples.
Features. The pitch doc listed the features that set this game apart. Here, you should go into more detail about why each of these features is important, and how you'll implement them.
Setting. Describe the game world in detail, and explain what makes it and its occupants unique and interesting.
Story. If the game has a story, describe it here in greater detail than in the pitch doc. Include the major characters , their motivations, and how they achieve (or fail to achieve) their goals.
Target Audience. Explain why the game will appeal to the target demographic you've identified.
Hardware Platforms. A list of devices your game can be played on. If you plan to develop different features for the various platforms, use this section to explain how the game will be different on each one.
Estimated Schedule and Budget. Break out the major phases of development, and the level of effort associated with each, to show how you arrived at the estimates in the pitch doc. Also include a P&L estimate if you have one.
Competitive Analysis. List the games you'll be competing with for sales, and explain how your game will stack up against them.
Team. List the names and credentials of the design, tech, and art leads, as well as other key team members . Also, list the games the organization has shipped. Publishers place as much importance on the team as on the concept, so make sure this section convinces them that your organization is capable of delivering the product you're proposing .
Risk Analysis. Explain the risks the project faces, and how you plan to minimize them.
Summary. End on a high note. Emphasize again why this will be a great game, and why the publisher should have confidence in your team's ability to deliver it.