SeedsConf 2015 COTMProd Docs
As with most of our events, the key to communicating Seeds Conference 2015 information to the team relied heavily on the paperwork we generated to articulate our set design, stageplots, runsheet info, and audio input lists. These documents are generally regarded as a mainstay of almost any mainstream production and I’ve never understood why there would be ANY difference with what we do in the church.
That being said, I want to share for reference and example only what we distributed for this year’s Seeds Conference. We ARE NOT suggesting everyone should run out and buy complicated programs to create a slew of paperwork if you don’t have the need. But, if you ARE looking for a more effective way to communicate your event information, perhaps these can serve as a decent reference point. Over the last several years, we’ve migrated to our current software choices, which have proven to serve our specific needs quite well. If something better comes along, we will certainly investigate using those as well. Anything we can put in our arsenal to help us work more efficiently is a plus.
So as you peruse these documents, fight the urge to immediately ping us back asking HOW we created all of it, but rather focus more on WHY we put this information together. The distribution of knowledge to a team is perhaps the most important, yet most elusive point to master when putting together the logistics for an event. The following links go into a lot more detail on some of the HOW in case that does interest you:
Here’s a bit of info on the programs used to create these particular documents:
Created using VectorWorks. This program can take many years to master and is, honestly, fairly advanced for what most churches actually need. Google Sketch-Up is much more appropriate for most church productions and MUCH easier to master. We do have a certain level of complexity involved with our building and events making VectorWorks a necessity.
Created using Planning Center Online. Not only does PCO have many custom print templates that can help you print great runsheets, but they’ve allowed you to use HTML coding to create or customize your own. I’ve become quite picky over the years about the specific nomenclature we use on our runsheets, so ours were created using HTML.
Created using Adobe Illustrator. Illustrator is amazing for stageplots and I’ve gotten pretty fast at knocking them out BUT there is nothing wrong with a great pencil and some graph paper (shhh, I have some in my desk drawer RIGHT NOW!).
Created using Numbers. Simple as it gets for this document. The only reason we’re not using Excel is that it’s a bit easier to deal with our Apple platform by sticking with the Numbers software.