# Level Design Document Template

_One level, one document. Fill in what your level needs, delete the rest. Grey boxes are guidance: remove them once the section is written._

| Field | Value |
|---|---|
| Game |  |
| Level name and slot |   (position in the game, levels before and after it) |
| Owner (designer) |  |
| Reviewers |   (lead, art, tech, QA) |
| Version and date |  |
| Status |   (draft / greybox / validated / art / locked) |

## 1. Overview and goals

> The page everyone reads. Keep it to a few lines: why the level exists, what the player can do by the end, and how you will know it is finished.

**Purpose (one sentence):** 

**Mechanic it introduces, tests or twists:** 

**Target playtime, first time / expert:** 

**Layout type:** linear  /  hub with spokes  /  open sandbox

**Definition of done:** 

> Example of a definition of done: "Fresh testers finish in 18 to 22 minutes without help, the frame-time target holds on the weakest platform, no blocker bugs on the critical path."

## 2. Narrative context and player objectives

> Write objectives in the player's words, not the writer's. Mark points of interest that carry story without dialogue, so environment art knows which props matter.

**Why the player is here / what changed since the last level:** 

| Type | Objective | How the player learns about it |
|---|---|---|
| Primary |  |  |
| Optional |  |  |
| Fail condition |  |  |

| Point of interest | Space # | What it tells the player |
|---|---|---|
|  |  |  |
|  |  |  |

## 3. Player flow

> Boxes and arrows before any geometry: which spaces connect, which are locked, where each key sits, which paths are one-way. Paste or link the diagram here.

**Flow diagram (link or image):** 

| Lock | Key or condition | Where the key is | Can the player get stuck? |
|---|---|---|---|
|  |  |  |  |
|  |  |  |  |

## 4. Top-down map and player metrics

> Critical path, optional routes, landmarks and sightlines, with numbered spaces the rest of the document can refer to. Add a scale bar. A map without scale cannot be built from.

**Map (link or image, with date and greybox version):** 

| Metric | Value | Notes |
|---|---|---|
| Jump distance / height |  |  |
| Cover height (low / high) |  |  |
| Corridor and door width |  |  |
| Camera view distance |  |  |
| Player speed (walk / run) |  |  |

## 5. Beat chart

> Every beat gets an intensity from 1 to 10. Look for long flat stretches and peaks with no rest behind them. If the level teaches a mechanic, the beats can follow introduce, develop, twist, master.

| # | Beat | Space | Intensity 1-10 | What the player learns or feels |
|---|---|---|---|---|
| 1 |  |  |  |  |
| 2 |  |  |  |  |
| 3 |  |  |  |  |
| 4 |  |  |  |  |
| 5 |  |  |  |  |
| 6 |  |  |  |  |

## 6. Encounters and puzzles

> One row per encounter or puzzle. Say what it tests. For puzzles, list solution steps and dependencies so QA can test every order a player might try.

| Space | Enemies or puzzle | Trigger | Max active | What it tests | If entered from elsewhere |
|---|---|---|---|---|---|
|  |  |  |  |  |  |
|  |  |  |  |  |  |
|  |  |  |  |  |  |

## 7. Items, rewards and checkpoints

| Item or checkpoint | Space | Why it is there |
|---|---|---|
|  |  |  |
|  |  |  |
|  |  |  |
|  |  |  |

> Rule of thumb for checkpoints: a failed attempt should never cost more than a few minutes of replay. Write the number you chose.

## 8. Art, audio and mood references

**Mood board (link):** 

**Palette, lighting, time of day:** 

**Signature props and landmarks:** 

**Music states and ambient bed:** 

## 9. Accessibility and readability

> How the route reads without relying on color alone, how big landmarks look on the smallest target screen, which subtitle, contrast and difficulty options the space has to work with.

- [ ] Route cues readable without color
- [ ] Key landmarks tested on the smallest target screen
- [ ] Barks and story audio subtitled
- [ ] Colorblind-safe pickups and hazards
- [ ] Difficulty options do not break encounter triggers

## 10. Technical budget

> Agree these numbers with the person who owns performance before art starts.

| Budget | Target | Weakest platform | Agreed with |
|---|---|---|---|
| Memory |  |  |  |
| Frame time |  |  |  |
| Max active AI |  |  |  |
| Physics objects |  |  |  |
| Streaming points |  |  |  |

## 11. Shopping list

| Item | Type (asset / script / VO / VFX / audio) | Owner | Status |
|---|---|---|---|
|  |  |  |  |
|  |  |  |  |
|  |  |  |  |
|  |  |  |  |

## 12. Open questions and change log

| Open question | Owner | Decide by |
|---|---|---|
|  |  |  |
|  |  |  |

| Date | What changed | Why (playtest, review, tech) | By |
|---|---|---|---|
|  |  |  |  |
|  |  |  |  |
|  |  |  |  |

## Appendix A. Review before greybox validation

> A single "no" means the level is not ready, whoever wrote it. Works for documents written by an outside team too.

- [ ] Someone outside the team can say why this level exists after reading only the overview.
- [ ] Every beat has an intensity, with a rest after each peak.
- [ ] The map has a scale and a metrics table behind it.
- [ ] Each encounter says what it is testing.
- [ ] The person who owns performance has agreed to the technical budget.

## Appendix B. Brief for an external level team

- [ ] Which levels or spaces are theirs, and which interfaces with your team they must respect
- [ ] This template, the metrics sheet and the greybox kit they must use
- [ ] Who signs off each level on your side, and in which tracker
- [ ] Definition of done per level, including the playtest result and performance target
- [ ] What stays with your lead: difficulty targets and pacing rules
