What is the primary purpose of a game design document (GDD)?

• A. To capture and communicate the game's vision, scope, mechanics, and requirements to the team.
• B. To market the game to publishers.
• C. To store source code.
• D. To instruct players on gameplay.

Answer: (A)

A game design document exists to capture and communicate the game's vision, scope, mechanics, and requirements to the team. It acts as a single source of truth that guides design decisions and keeps everyone aligned on what the game should be and how it should come together. By laying out the overarching goals, target audience, core gameplay loop, and each system the game will include, the GDD helps designers, artists, programmers, and producers stay on the same page as ideas evolve. It also details practical requirements like platform targets, performance goals, art style, and control schemes, so teams can plan tasks, estimate timelines, and manage resources effectively. Importantly, the document is a living reference that can be updated as decisions change, which helps prevent miscommunication and scope creep as the project progresses.

Marketing to publishers, storing source code, and instructing players are handled by other tools and documents. A GDD isn’t primarily a marketing pitch, it isn’t a code repository, and it isn’t meant to be the player-facing instruction manual; its main job is to guide the internal design and development process.