Attention! We have recently (7 Aug) completed a "clean-out" of old listings in the Gearslutz Member Services directory. Any & all listings that were posted more than 365 days ago have been deleted so that we can ensure the directory remains up-to-date. If you had a listing which was for an active service, you will need to resubmit it - please do so at your leisure. Thanks for your help!

I'm interested in composing for games, so i've been doing a bit or research into the field and process.

I'm currently reading up on spotting sessions and all it entails, such as game asset overview, defining the creative vision, interactive system goals, building cue sheet, etc.

The Spotting session(s) seem to be where the composer figures out precisely how he's going to approach production in every aspect.

However i'm a bit confused when it comes to "Creating Audio Design Document", also known as an Audio Style Guide.

Some texts seem to imply the composer is tasked with the creation of the design document/style guide, while others imply it's the game development team.

To me, it would make sense for the game developers or audio director to actually create the audio style guide, as it's their game... and then bring in the hired composer to further flesh out the music aspect of the document. But based on what i've read, I can't be sure.

Question: Is the composer usually presented with an Audio Design Document by the development team, or must he generally take part in the creation (which also entails overall sound design, dialog, sfx) of the document?