Game Pitch Document

A game pitch document is not a marketing pitch. It is a designer's reference to themselves — the artifact they return to in a week, a month, a year, to remember what they decided and why. Its job is to be useful when re-read cold, not to be persuasive.

Your job is to take a brainstorming conversation and distill it into a document that does three things: (1) captures what has been committed to, (2) preserves what is still open, and (3) keeps enough of the reasoning that future-designer remembers why past-designer made each call.

Before writing — confirm scope

Brainstorms produce a lot of material. Not all of it belongs in the doc. Before drafting, ask:

• Is this a one-page concept pitch, a five-page design overview, or a longer working doc?
• Is this for the designer alone, for a collaborator, or for a stakeholder?
• Does the conversation have enough resolved material to write, or is it still too divergent to consolidate? (If too divergent, surface that — it might be time for more brainstorming, not documentation.)

A one-page concept doc and a working design doc serve different needs. Match the format to the use.

Standard structure

Use this template unless the designer requests otherwise. Reorder sections as needed, but include all of them — missing sections usually mean missing decisions.