The whole idea of game design is to outsource the content of your mind so that other people can understand and follow what is it that you want to present. As with any kind of human interaction this poses a mountain of problems but I wont get to them here.

This beforementioned practical aim dictates in part the scope, shape and the content of the game design document. Not having got any look at professional design document templates I have one idea to guide me in shaping the design document for The Apprentice. My document will progress in increasing order of abstraction. The document begins with what is most apparent for the player and progresses toward the technical execution of the game. From quite a freeform explanation of the player sees, hears and interacts with to pseudo-code and descriptions and lists of the game objects. So, the index might look something like the following:

1. (Metastuff)

2. a.) Free form explanation of Nokkapokka (in the order of a thorough game review)

b.) Description of game mechanics and elements

c.) Game algorithms and game objects

3-4. (same  for Kärhämät and Vihollisuudet)

5.-n.) (more metastuff, some reflection on the process, open problems, other notes)

+ possible Appendices