A Game Concept Document (GCD), originally known as a Concept Design Document (CDD), is a concise document that defines what a game is, what experience it aims to create, who it is for, and why the project is worth making. It establishes the game's overall direction before the team moves into detailed design and production documentation.
The terminology is not completely consistent across the industry. You may find this document described as a Game Concept Document, Game Concept, Concept Design Document, or, in some contexts, a High Concept Document. In game development, “Game Concept Document” is often the clearest term because it distinguishes the concept from the Game Design Document (GDD) that describes how the game works in detail.
When to Use a Game Concept Document (GCD)
A Game Concept Document is most useful at the beginning of a project, when the team needs to define and evaluate the idea before investing heavily in detailed design or production.
The document answers questions that should be resolved before writing hundreds of pages of specifications:
What game are we making?
What experience are we trying to create?
Who is the game for?
What makes it different?
Why would players want to play it?
What characteristics should guide our design decisions?
A GCD can also become a shared reference throughout development. When new team members join, they can use it to understand the project's identity and intended experience without reading every design document.
This is particularly useful as a team grows. Without a shared definition of the game, different departments can gradually develop their own interpretation of the project. Programming, art, narrative, design, and other disciplines may all make individually reasonable decisions that nevertheless move the game in different directions.
The GCD provides a common frame of reference.
Game Concept Document vs. Game Design Document
A Game Concept Document and a Game Design Document serve different purposes.
The GCD defines the concept and direction of the game. The GDD documents the design and implementation of its systems in much greater detail.
A simple way to think about the distinction is:
The GCD defines what the game is and what experience it should provide. The GDD defines how that experience works.
For example, a GCD might say:
“Players explore a hostile 3D world where movement and uncertainty are central to the experience.”
The corresponding GDD might specify:
“The player dash moves 4.5 meters in 0.18 seconds, has a 1.2-second cooldown, and can be cancelled under these conditions…”
The first statement establishes a design direction. The second defines a specific mechanic.
The same principle applies to other areas. A GCD can establish that combat should feel fast and aggressive, while the GDD can document attack properties, damage values, recovery times, enemy states, hit reactions, and combat rules.
Some teams also use a Proposal Design Document (PDD) between the concept and detailed design. A PDD can be useful when a team needs to propose and validate a specific feature before investing the time required to document it fully. However, this is a workflow choice rather than a mandatory stage of game development.
Different studios organize their documentation differently. The important thing is that each document has a clear purpose and that the team knows where information belongs.
Essential Sections of a Game Concept Document (GCD)
There is no universally correct Game Concept Document template. The document should adapt to the project rather than forcing every game into the same structure.
The following sections provide a practical foundation. Some projects may need all of them; others may combine, remove, or add sections depending on their needs.
The key principle is to define the idea, not the implementation.
1. Game Title
Give the project a clear name.
The title does not need to be final. A working title is perfectly acceptable during early development.
For example, Catalepsy immediately suggests a connection to temporary paralysis or death, which can reinforce the identity of a game built around resurrection.
2. Concept
Summarize the game in one or two sentences.
The concept should communicate what the game is and why its experience is interesting. Think of it as the shortest useful description of the project.
For example:
“A horror action game where players use death and resurrection as tools to navigate a hostile world.”
The concept should communicate the game's core idea without explaining every mechanic.
3. Genre
Define the game's primary genre and any relevant subgenres.
For example:
Action Roguelike / Third-Person / Horror
The purpose is not to create a definitive classification. Genre helps establish expectations about the type of experience you are designing.
4. Target Audience
Describe the players the game is intended for.
Depending on the project, this can include age range, interests, playing habits, reference games, motivations, or relevant player profiles.
For example:
Players who enjoy challenging action games, exploration, dark environments, and systems that reward experimentation. Reference games include Hades and Dark Souls.
The level of detail should reflect how much is actually known about the intended audience. Avoid inventing a detailed demographic profile simply to fill the section.
5. Vision and Design Pillars
This is one of the most important sections of the GCD.
The vision describes the experience you want the game to deliver. The design pillars identify the characteristics that make that experience distinctive and guide design decisions throughout development.
A good design pillar should be specific enough to influence a decision.
“Fun”, “immersive”, or “good gameplay” are not useful pillars because they could apply to almost any game.
A stronger pillar might be:
Aggressive movement: The player should be rewarded for staying mobile and taking risks rather than waiting for safe opportunities.
The pillars can then influence mechanics, level design, art direction, audio, progression, and other areas of the game.
6. Aesthetic
Describe the game's visual and artistic direction.
Include references, moodboards, concept art, or other visual material when they help communicate the intended style.
The important part is not simply describing what the game should look like, but explaining how its aesthetic supports the intended experience.
For example, a game designed around uncertainty might use restricted visibility, strong contrasts, unusual silhouettes, or environmental details that make players question what they are seeing.
7. World
Provide a concise overview of the game's setting and universe.
Depending on the project, this may include:
Setting and environment
Basic premise
Main characters
Relevant narrative context
Important world-building concepts
The GCD does not need to contain the complete lore or narrative documentation. Its purpose is to provide enough context to understand the game and its intended experience.
8. Platforms
Define the platforms you are targeting.
For example:
PC and PlayStation 5
Platform decisions can affect the concept itself, so this information can be useful even at an early stage.
9. Business Model
Describe how the game is intended to generate revenue when this is relevant to the project.
Examples include:
Premium
Free-to-play
Subscription
Early Access
Advertising
DLC or expansions
Not every GCD needs a detailed business model. For some projects, particularly prototypes or experimental games, this may still be undecided.
10. Player Goals
Describe what the player is trying to achieve at different timescales.
You can divide these into short-, medium-, and long-term goals.
For example:
Short term: Win the current encounter.
Medium term: Complete an area and unlock new abilities.
Long term: Complete the game and master its systems.
The section should also consider the motivations behind those goals. A player may pursue progression, mastery, exploration, competition, collection, discovery, or other forms of motivation.
11. Core Gameplay Loop
Describe the main cycle of actions that creates the game's experience.
A visual diagram is often more useful than several paragraphs of text.
For example:
Explore → Fight → Overcome obstacle → Gain ability → Access new area → Explore
The core loop should connect to the player goals defined above. The purpose is to show how the game's moment-to-moment actions contribute to the larger experience.
It should remain conceptual at this stage. Detailed rules for each system belong in the GDD.
12. Main Systems
List the major systems required to create the intended experience.
For example:
Combat
Exploration
Progression
Inventory
Abilities
Enemy AI
At CDD level, these should remain descriptions of what systems exist, rather than complete specifications of how they work.
13. Gameplay and Interactivity
Describe the fundamental ways the player interacts with the game.
Depending on the project, this might include:
Core player actions
Camera perspective
Movement
Combat
Interaction
Physics
Basic interface
This section can benefit greatly from visual material. An annotated sketch of the main gameplay screen, for example, can communicate the intended interaction model more effectively than a long written explanation.
Again, the distinction is important: the GCD establishes the intended interaction and experience; detailed controls, state machines, numerical values, and implementation rules belong in later documentation.
How Detailed Should a Game Concept Document Be?
A Game Concept Document should be concise enough to communicate the entire concept quickly.
There is no universal page count. A small game might need only a few pages, while a more complex project may require more space to communicate its vision.
The important limitation is not the number of pages. It is the level of detail.
Use this principle:
Define the idea, not the implementation.
Compare these two examples.
GCD:
“Combat is fast and aggressive, rewarding players who stay close to enemies.”
GDD:
“The light attack deals 20 damage, has 0.35 seconds of recovery, and can chain into…”
The GCD establishes the intended experience. The GDD turns that intention into a concrete system.
If a section starts filling with detailed values, technical constraints, complete state definitions, or exhaustive rules, it is probably moving beyond the purpose of the concept document.
Common Mistakes
Confusing the GCD with the GDD. A concept document should establish the game's direction rather than document every system in detail. If you find yourself writing complete mechanics specifications, consider moving that information into the GDD.
Including premature technical details. Code architecture, production pipelines, technical specifications, shader implementation, and similar information generally do not belong in a concept document. These can be documented in technical or production documentation when necessary.
Trying to make every section mandatory. A template is a starting point, not a contract. If a section does not provide useful information for your project, remove it. If your project needs something that is not in the template, add it.
Using generic design pillars.“Fun”, “immersion”, and “smooth gameplay” do not provide much guidance because they apply to almost every game. Good pillars should describe something distinctive about the experience and help the team make concrete decisions.
Forgetting the “why”. It is not enough to describe what the game contains. The GCD should communicate why those characteristics matter and what experience they are intended to create.
Writing the document once and forgetting about it. The GCD can change as the concept develops. Early assumptions may be invalidated during prototyping or testing. Updating the document when the fundamental direction changes keeps the project's reference point useful.
From the Game Concept Document to the GDD
Once the game's concept and direction are sufficiently defined, the team can begin expanding that vision into detailed design documentation.
The relationship between the two documents should be traceable.
The GCD's design pillars become criteria for evaluating individual systems. The conceptual core loop can be expanded into detailed systems, mechanics, rules, states, and flows. The intended audience can inform decisions about difficulty, accessibility, progression, and other aspects of the design.
For example, if a GCD establishes that aggressive movement is one of the game's core pillars, a GDD system should support that intention rather than accidentally encouraging a completely defensive playstyle.
The GCD therefore does not replace the GDD. It provides the direction against which the detailed design can be evaluated.
A solid Game Concept Document defines what you are building and why. The Game Design Document defines how it works.
If you are ready to move from the concept into detailed design, see our guide on how to write a professional Game Design Document.