<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>FestivalSystems</title>
	<atom:link href="http://www.festivalsystems.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.festivalsystems.com</link>
	<description>management software for music festivals</description>
	<lastBuildDate>Tue, 19 Feb 2013 11:18:03 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Merchant Module</title>
		<link>http://www.festivalsystems.com/2013/02/merchant-module/</link>
		<comments>http://www.festivalsystems.com/2013/02/merchant-module/#comments</comments>
		<pubDate>Tue, 19 Feb 2013 11:18:03 +0000</pubDate>
		<dc:creator>Kris</dc:creator>
				<category><![CDATA[Development]]></category>

		<guid isPermaLink="false">http://www.festivalsystems.com/?p=372</guid>
		<description><![CDATA[Most festivals enable vendors to sell products and services to their audience, whether it be clothing, food, drink, music, body or soul. We&#8217;re pleased to announce the first release of our new Merchant Module, that will allow you to handle their acquisition and management simply, quickly and painlessly. It starts with our tried-and-tested questionnaire builder, [...]]]></description>
				<content:encoded><![CDATA[<p><img class="alignnone size-full wp-image-374" alt="merchant.list" src="http://www.festivalsystems.com/wp-content/uploads/merchant.list_.jpg" width="660" height="265" /></p>
<p>Most festivals enable vendors to sell products and services to their audience, whether it be clothing, food, drink, music, body or soul.</p>
<p>We&#8217;re pleased to announce the first release of our new Merchant Module, that will allow you to handle their acquisition and management simply, quickly and painlessly.</p>
<p>It starts with our tried-and-tested questionnaire builder, that enables you to create a number of forms &#8211; either one for all your merchants, or different ones depending on the category of the applicant. You can ask a set of pre-defined questions (dimensions required, previous history, utility requirements, site access&#8230;) and as many additional questions as you require.</p>
<p>The form is then created to a unique url (that you can have &#8220;skinned&#8221; so that it replicates your public website&#8217;s look and feel) which you can promote online, via your website, twitter and/or in direct conversation with prospective merchants/service providers.</p>
<p>Applicants can then be reviewed and rated and, once you&#8217;re ready, you can promote them into the main Merchant system.</p>
<p>Once promoted you can track their financial details (fees and deposits), generate and send contracts, set the number of staff passes they receive, automatically send them a link so that they can provide their staff names, ask for vehicle details so you can approve and manage site access, allocate and manage their guest tickets and more.</p>
<p><img class="alignnone size-full wp-image-375" alt="merchant.layout" src="http://www.festivalsystems.com/wp-content/uploads/merchant.layout.jpg" width="660" height="314" /></p>
<p>However the thing that we&#8217;re most proud of is the ability for you to manage the site layout using our unique online visual drag-and-drop system. You start by uploading a map, or series of maps, of your festival site into the module. You can then display a list of all your approved Merchants and drag individual names onto the map. The merchant list has all the filtering you need &#8211; category, utilities,</p>
<p><img class="alignnone size-full wp-image-378" alt="merchant.list.options" src="http://www.festivalsystems.com/wp-content/uploads/merchant.list_.options.gif" width="660" height="145" /></p>
<p>If you&#8217;ve asked for dimensions in the questionnaire, then the system will <em>automatically</em> build the right sized stall for that merchant, color-coded depending on their category (food, clothing, etc). You can then drag them around the map, rotate them, and resizing if required. At the click of your mouse you can see which of your Merchants need water/electricity. There&#8217;s even a search function that will scroll around your map finding the location of  anyone you&#8217;ve placed.</p>
<p>Oh, and there&#8217;s all the standard reports and communications systems that we generally provide to ensure that you can instantly talk to whomever you need, and instantly get the information that you require.</p>
<p>If you&#8217;d like a guided tour of how this all works so that you can see the benefits for yourself  - please <a title="Contact" href="http://www.festivalsystems.net/contact.html">get in touch</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.festivalsystems.com/2013/02/merchant-module/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Historic Artist Database</title>
		<link>http://www.festivalsystems.com/2013/02/historic-artist-database/</link>
		<comments>http://www.festivalsystems.com/2013/02/historic-artist-database/#comments</comments>
		<pubDate>Tue, 19 Feb 2013 08:51:21 +0000</pubDate>
		<dc:creator>Kris</dc:creator>
				<category><![CDATA[Development]]></category>

		<guid isPermaLink="false">http://www.festivalsystems.com/?p=368</guid>
		<description><![CDATA[One of the many things we&#8217;ve been up to over the winter break is to add the ability for festivals to search through their past performers. Whether you&#8217;re looking for contact details for an artist who played four years ago, or wanting to find someone who&#8217;ll fit a hole in your line-up, the Historic Artist [...]]]></description>
				<content:encoded><![CDATA[<p><img class="alignnone size-full wp-image-370" alt="historic artist database" src="http://www.festivalsystems.com/wp-content/uploads/historic.png" width="660" height="285" /></p>
<p>One of the many things we&#8217;ve been up to over the winter break is to add the ability for festivals to search through their past performers. Whether you&#8217;re looking for contact details for an artist who played four years ago, or wanting to find someone who&#8217;ll fit a hole in your line-up, the Historic Artist Database is the tool that can fulfil that need.</p>
<p>What it does is list your artists who are not part of the current line-up. You can see when they played, which stage and how much you paid them. You can view their contact details and email them directly from the system.</p>
<p>There are a range of filters too, so that you can, for instance, show only those artists who&#8217;ve been on the main stage, performed as a band and cost you under $500.</p>
<p>Then, once you&#8217;ve found the act that you&#8217;re wanting, you can promote them to the main artist module, automatically carrying across their contact and biography information, saving you time, effort and energy.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.festivalsystems.com/2013/02/historic-artist-database/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to Recruit and Manage Volunteers</title>
		<link>http://www.festivalsystems.com/2012/02/how-to-recruit-and-manage-volunteers/</link>
		<comments>http://www.festivalsystems.com/2012/02/how-to-recruit-and-manage-volunteers/#comments</comments>
		<pubDate>Thu, 02 Feb 2012 10:03:10 +0000</pubDate>
		<dc:creator>Kris</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://www.festivalsystems.com/?p=364</guid>
		<description><![CDATA[Most festivals that we work with wouldn&#8217;t survive without volunteers. They help with car parking, putting up décor, greeting people at the gates, litter picking and countless other jobs around the site. The ability to acquire, approve and manage your volunteers should be a part of any festival management software. The Only Essential Function The [...]]]></description>
				<content:encoded><![CDATA[<p>Most festivals that we work with wouldn&#8217;t survive without volunteers. They help with car parking, putting up décor, greeting people at the gates, litter picking and countless other jobs around the site. The ability to acquire, approve and manage your volunteers should be a part of any festival management software.</p>
<h4>The Only Essential Function</h4>
<p>The only essential element to a volunteer system is registration &#8211; everything else is optional. Important optional of course, but if you can&#8217;t get the names in there&#8217;s no point in lots of bells and whistles. So the questionnaire has to be rock solid, it has to ask for the right details and it has to be simple to use. I know some festivals that use multiple questionnaires for different roles, others that just have one, but none that turn away free labour.</p>
<h4>Useful Features for your Questionnaire</h4>
<p>A few ideas to make recruitment more painless: Make sure that&#8230;</p>
<ul>
<li>your candidates get an email when they register</li>
<li>they can return and edit their details &#8211; make sure that you include instructions how to do this in their registration email</li>
<li>you can switch off the ability for them to edit their details, as you may not want them to be changing things just before your event</li>
<li>you ask them whether they can be contacted for future events</li>
</ul>
<p>It can be useful if there&#8217;s the option for your team to be notified when a volunteer registers, prompting you to keep on top of incoming applicants. The ability to amend the questionnaires as you go means you&#8217;re not stuck when you find that an important question has been missed, or an additional question needs to be asked.</p>
<h4>Approval and Filtering</h4>
<p>The next step is the approval process, checking through the names and, if required, setting roles/teams. There are not very many ways you can show names other than in a list, but including some sensible filtering will help make the job easier. Can you select those who&#8230;</p>
<ul>
<li>you&#8217;ve not viewed before?</li>
<li>have prior work experience with festivals?</li>
<li>have helped in the past with your festival?</li>
<li>have first-aid qualifications?</li>
</ul>
<p>When you approve someone, do you want the system to automatically send him or her an acceptance email? Is that email configurable? Can you see a running total of how many people have been approved and into which teams/roles so that you can see where the holes are?</p>
<h4>Communication and Reporting</h4>
<p>As you&#8217;ve got the names and emails in the system, plus their acceptance status and, potentially, their role/team, it would be useful to have a messaging system that can automatically filter and communicate to specific volunteers. You&#8217;ll also need some form of outputting this information into a spreadsheet for reference.</p>
<h4>Scheduling</h4>
<p>The final piece in a volunteer management system could be the scheduling of names into their various rotas. It is, after all, one of the more complicated processes for your volunteer manager to cope with. Unfortunately it&#8217;s also a complex problem for a system to cope with, which means that it&#8217;s never going to easy to deliver. We&#8217;ve looked at this in the past, but the different rules that have to be put in place are so tricky to manage that I&#8217;ve yet to release anything that works. If anyone has an example of this working, I&#8217;d love to see it!</p>
<h4>Finally, Make Sure You Own Your Data</h4>
<p>If you use a third party software product to manage your volunteers, please make sure that they guarantee that your content is yours, that they&#8217;re not going to market to your database, or sell your names to anyone else. And make sure that they&#8217;re signed up to any Data Protection requirements (in the UK they need to be registered with the Information Commissioner&#8217;s Office, and anyone operating in Europe has to adhere to the EU Data Protection Directive).</p>
<p><em>This is part 4 of a 6 part series. To receive these articles directly to your inbox, <a href="http://www.festivalsystems.net/list.html">sign up to our mailing list</a>.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.festivalsystems.com/2012/02/how-to-recruit-and-manage-volunteers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Stage Tech Specs &#8211; Explained</title>
		<link>http://www.festivalsystems.com/2012/02/stage-tech-specs-explained/</link>
		<comments>http://www.festivalsystems.com/2012/02/stage-tech-specs-explained/#comments</comments>
		<pubDate>Wed, 01 Feb 2012 08:20:55 +0000</pubDate>
		<dc:creator>Kris</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://www.festivalsystems.com/?p=359</guid>
		<description><![CDATA[]]></description>
				<content:encoded><![CDATA[<p><img class="alignnone" title="Stage Tech Specs" src="http://www.fms4.net/images/reality_check.jpg" alt="" width="653" height="840" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.festivalsystems.com/2012/02/stage-tech-specs-explained/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Getting Others To Do Your Work For You</title>
		<link>http://www.festivalsystems.com/2012/01/getting-others-to-do-your-work-for-you/</link>
		<comments>http://www.festivalsystems.com/2012/01/getting-others-to-do-your-work-for-you/#comments</comments>
		<pubDate>Tue, 31 Jan 2012 11:18:36 +0000</pubDate>
		<dc:creator>Kris</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://www.festivalsystems.com/?p=356</guid>
		<description><![CDATA[And no, I don&#8217;t just mean delegating to your team, I mean getting others to do stuff so that your team doesn&#8217;t have to. A New System Should Mean Less Work Taking on a new festival system can seem like a big step; if it&#8217;s any good it probably looks a little daunting. It needs [...]]]></description>
				<content:encoded><![CDATA[<p>And no, I don&#8217;t just mean delegating to your team, I mean getting others to do stuff so that your team doesn&#8217;t have to.</p>
<h4>A New System Should Mean Less Work</h4>
<p>Taking on a new festival system can seem like a big step; if it&#8217;s any  good it probably looks a little daunting. It needs to handle a huge  range of different jobs, some of which you want now, some of which you  may want in the future. A key goal of any system must be to help improve  productivity, so even though it may first seem like a lot of work, it  should strive to do the opposite.</p>
<h4>How to Make Life Much Easier</h4>
<p>Let&#8217;s take a look at gathering the production requirements*. The first  step is the creation of an online questionnaire, tailored for your event  and allocated to each performer. It&#8217;s best if you can use multiple  forms so that you can set different questions depending on the stage  they&#8217;re on, or the type of performance they&#8217;re giving. The system should  be able to automatically send the unique links to each performer (or  their management). Once they click on the link they can fill in their  requirements which are posted straight into the system, ready for review  and approval.</p>
<p>* We could just as easily look at other areas, like volunteer  recruitment, performer applications to play, or guest list management&#8230;</p>
<h4>No Passwords Please</h4>
<p>I&#8217;ve been helping festivals gather production details for over 10 years  and my one core piece of advice is to it as simple as possible for  people to provide content. This means no passwords, no logging in and no  hoops to jump through. The more difficult you make it, the less likely  they are to do your work for you.</p>
<h4>Reuse, Recycle</h4>
<p>Now, whilst you&#8217;ve got the artist online and providing their production  requirements, we should take the opportunity to get them to do some of  your other work stuff too. How about getting them to submit their  biography, publicity photos, links to their website and details of their  social media pages? Throw that info into some sort of press module so  that there&#8217;s a centralised area for PR. Now, as you&#8217;ve got all this  content about the artist and their performance times, you could use the  system to drive your public website without having to enter this  information all over again. Oh, that means the system will need  publishing functionality so that you can control the release of  information. How about using the same feeds for an iPhone or Android  app, all off the one set of content that you&#8217;ve not even had to  provide&#8230; Okay, you&#8217;ve probably had to do some editing, but at least  you&#8217;ve not started with a blank page.</p>
<h4>Security, Security, Security</h4>
<p>To get others to do this work for you, you&#8217;ll need to open a window into  the main system. There are a lot of different ways to do this, but we  feel that the best idea is to keep the window small, and access to the  window simple. The approach we take is to provide each visitor with a  unique link so that the system can identify who is who. All the  performer has to do is click the link (which can be resent) and they&#8217;re  back at their window. People don&#8217;t care enough to remember passwords and  usernames &#8211; you&#8217;re asking them to do your work for you, so it has to be  as painless as possible. This approach does means building massive  security on the other side of the window, just out of sight, to make  sure everyone behaves, but it&#8217;s worth it for the work it will save you.</p>
<p><em>This is part 4 of a 6 part series. To receive these articles directly to your inbox, <a href="http://www.festivalsystems.net/list.html">sign up to our mailing list</a>.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.festivalsystems.com/2012/01/getting-others-to-do-your-work-for-you/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Managing Festival Finances</title>
		<link>http://www.festivalsystems.com/2012/01/managing-festival-finances/</link>
		<comments>http://www.festivalsystems.com/2012/01/managing-festival-finances/#comments</comments>
		<pubDate>Thu, 26 Jan 2012 12:06:50 +0000</pubDate>
		<dc:creator>Kris</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://www.festivalsystems.com/?p=353</guid>
		<description><![CDATA[In the fifteen years that I&#8217;ve been working with festivals, the number one issue for our clients has been managing their cash flow in the lead-up to their event. Countless hours are spent finding ways to realise the income from ticket sales to cover performer&#8217;s deposits, staff wages, equipment hire, and marketing and PR funding&#8230; [...]]]></description>
				<content:encoded><![CDATA[<p>In the fifteen years that I&#8217;ve been working with festivals, the number  one issue for our clients has been managing their cash flow in the  lead-up to their event. Countless hours are spent finding ways to  realise the income from ticket sales to cover performer&#8217;s deposits,  staff wages, equipment hire, and marketing and PR funding&#8230; Help with  budgets is pretty much the first question I&#8217;m asked when a prospective  client approaches us. I understand your pain.</p>
<h4>Let&#8217;s Not Recreate the Wheel</h4>
<p>There are plenty of great financial systems around &#8211; <a href="http://sage.com/ourbusiness/sageworldwide">Sage</a> and <a href="http://www.intuit.co.uk/">QuickBooks</a> are the main products we encounter &#8211; so the approach of a festival  system shouldn&#8217;t be to replicate what they offer. It should add to your  toolkit, not try to replace everything that&#8217;s already there. However  there are other things that a good festival system can do to help.</p>
<h4>Don&#8217;t Let the Programming Team Overspend</h4>
<p>A decent festival software product should include a comprehensive  scheduling system. We&#8217;d recommend including a small budgeting module,  embedded within the scheduler, that provides your programming team with a  running total of their spending. In our experience performance fees are  a key area for overspending, so keeping this central and in BIG NUMBERS  is essential. Including a breakdown of where the money is being spent,  by both day and stage, ensures that maintaining spending targets for  different parts of your event is much easier.</p>
<h4>Stay In Control of Your Artist Budget</h4>
<p>Each performance record should include financial information: total fee,  deposits, and whether the fee is liable to taxes and, if so, at what  rate. An artist should be able to have multiple performances with either  a single fee, or individual amounts for each show. They might require a  single deposit, or a number spread over several months. All this needs  to be easily managed, tracked and highlighted when due. Identification  of those performers who have not had a fee set; automatic checks when  you alter fees to see whether contracts and/or deal memos need to be  resent; reminder emails to relevant staff as deposits are payable; and  auto-emails to performers or their management when you make a payment &#8211;  just some of the ways a system can try to keep financials on track.</p>
<h4>Make Sure Everything is At Your Fingertips</h4>
<p>There can be a lot of different people who need to be kept &#8220;in the loop&#8221;  where financial information is concerned &#8211; senior management,  programming and accounts &#8211; however there also has to be watertight  controls so that these details are kept confidential. Some of your team  may need access to some aspects of the contracts, like how many guest  tickets have been allocated, but not others. The software has to be able  to cope with this. And it needs to provide reports, in Excel, instantly  and without struggling to translate them or get them to open.</p>
<p>So when we&#8217;re approached by festivals, we&#8217;re always asked whether we &#8220;do festival financials&#8221;.</p>
<p>&#8220;Sort of,&#8221; we reply, &#8220;but it&#8217;s more that we help your team to be financially aware.&#8221;</p>
<p>As any Festival System should.</p>
<p><em>This is part 3 of a 6 part series. To receive these articles directly to your inbox, <a href="http://www.festivalsystems.net/list.html">sign up to our mailing list</a>.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.festivalsystems.com/2012/01/managing-festival-finances/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How To Build A Festival Scheduling System</title>
		<link>http://www.festivalsystems.com/2012/01/how-to-build-a-festival-scheduling-system/</link>
		<comments>http://www.festivalsystems.com/2012/01/how-to-build-a-festival-scheduling-system/#comments</comments>
		<pubDate>Tue, 24 Jan 2012 10:04:04 +0000</pubDate>
		<dc:creator>Kris</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://www.festivalsystems.com/?p=349</guid>
		<description><![CDATA[I&#8217;ve been building big computer systems for years, and one thing that I can guarantee is that nothing looks less creative than a long list of names, numbers and times, with a few buttons to click and maybe some things to process. Creative People Require Creative Tools Without exception, the festival bookers I&#8217;ve met say [...]]]></description>
				<content:encoded><![CDATA[<p>I&#8217;ve been building big computer systems for years, and one thing that I can guarantee is that nothing looks less creative than a long list of names, numbers and times, with a few buttons to click and maybe some things to process.</p>
<h4>Creative People Require Creative Tools</h4>
<p>Without exception, the festival bookers I&#8217;ve met say that their job is a creative process and lists of information just don&#8217;t work. This is why developing a visual scheduling system is essential to any Festival System. Times, stages, artists and performance styles need to be represented visually so that you can gauge the flow, quickly see what&#8217;s happening elsewhere, and judge the best changes and additions to make.</p>
<h4>Will Any Scheduler Do?</h4>
<p>There&#8217;s a wide range of festival specific elements that make festival programming unique and, as a result, requiring bespoke handling. For example, after midnight doesn&#8217;t necessarily mean that we&#8217;re into a new day &#8211; a performance scheduled at 1am Saturday morning is often part of Friday night&#8217;s line-up. So you either have to create your schedule in a spreadsheet, with minimal functionality, or use purpose built software.</p>
<h4>Can We &#8220;Pencil It In&#8221;</h4>
<p>A scheduler needs to have the ability to include &#8220;unconfirmed&#8221; performances &#8211; for when you&#8217;re discussing a specific time slot and need to reserve it while you&#8217;re still negotiating. These unconfirmed performances shouldn&#8217;t appear elsewhere in the system and should only be visible to the programmers otherwise chaos will reign.</p>
<h4>Everything At Your Fingertips</h4>
<p>So, if you have a scheduler, each stage with a time-line, and each performance represented as a block on that time-line, the programme becomes easy to read, quick to see where the holes are and simple to identify what&#8217;s going on elsewhere. If the scheduler has the ability to move the performance blocks around, change the length of each show and have those changes instantly reflected in the rest of the system, then it will transform how you work. And remember to put all the tools that your programming team needs within easy reach &#8211; instant access to performer budgets, stage details and other important reference content.</p>
<h4>Show Me What You&#8217;ve Got</h4>
<p>You&#8217;ll need the ability to view certain stages, or only show specific times, while you&#8217;re working on sections of the program. Color-coding the blocks to illustrate different performance styles will help with judging flow and pace. And don&#8217;t forget the small but vital things, like not losing your place each time you save.</p>
<h4>Understand the Workflow</h4>
<p>Make sure that each performance can be added directly within the scheduler, rather than having to visit a series of different pages. Include the option of setting the fee and contact information as part of the process. If it&#8217;s an existing performer, with a fee or performance time already set, it should check to see whether the fee is in addition, or as a new total. When you start typing their contact name, the system should automatically search through your existing contacts and make suggestions, auto-filling their details if the right person is found. If it&#8217;s a new name, then it gets added to the address book and is there for this festival, and the next, and the one after that too. Finally, after submitting a new performance, the scheduler could even generate and send the appropriate documents &#8211; a contract or deal memo, for example.</p>
<p>So there you have it, a fully featured Festival Scheduler. Simple.</p>
<p>If you can&#8217;t face the idea of building your own then, surprisingly enough, we have one that does this and more. If you&#8217;re interested in having trying it, then you&#8217;re more than welcome to take a look at our <a href="http://www.fms4.net/setup.new.html">free demo</a>.</p>
<p><em>This is part 2 of a 6 part series. To receive these articles directly to your inbox, <a href="http://www.festivalsystems.net/list.html">sign up to our mailing list</a>.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.festivalsystems.com/2012/01/how-to-build-a-festival-scheduling-system/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How To Manage Your Festival</title>
		<link>http://www.festivalsystems.com/2012/01/how-to-manage-your-festival/</link>
		<comments>http://www.festivalsystems.com/2012/01/how-to-manage-your-festival/#comments</comments>
		<pubDate>Fri, 20 Jan 2012 09:36:13 +0000</pubDate>
		<dc:creator>Kris</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://www.festivalsystems.com/?p=341</guid>
		<description><![CDATA[Every festival will have some type of system in place to manage their event, whether it is the back of an envelope, or an advanced project management program. And while your current system will get you through &#8211; it&#8217;s what you know after all &#8211; sometimes it can be worthwhile to take a quick look [...]]]></description>
				<content:encoded><![CDATA[<p>Every festival will have some type of system in place to manage their  event, whether it is the back of an envelope, or an advanced project  management program. And while your current system will get you through &#8211;  it&#8217;s what you know after all &#8211; sometimes it can be worthwhile to take a  quick look at the other options. I&#8217;ve been working with festivals for  over ten years, helping them develop ways to make their lives easier, so  here are my three key points of what to look for.</p>
<h4>Local or Online &#8211; What&#8217;s right for my event?</h4>
<p>Let&#8217;s assume that we&#8217;re too big to be running things on the back of the  envelope and that some sort of software is required. Your first decision  is the scope of the software &#8211; who can use it and where? A local option  is one that is installed on the office computers, and generally  licensed on a machine-by-machine basis. Solutions range from Excel  through to sophisticated event management software, such as that  provided by <a href="http://www.artifax.net/">Artifax</a>.  The downsides of going local are when your team doesn&#8217;t all work in the  office or when you&#8217;re onsite and need to check what&#8217;s been agreed on a  system that&#8217;s sitting back in the office. Local also prevents third  parties (artist management, volunteers, etc) inputting their details  directly into the system, so everything that comes in has to be typed-in  by someone on your team. The upside is that you are in control of your  data and, provided that there are regular back-ups, that information  should be safe.</p>
<p>The alternative route is to go &#8220;into the cloud&#8221; with an online solution.  Online means that you&#8217;re not tied to a machine (or an office), rather  if there&#8217;s Internet and a web browser you&#8217;re sorted. <a href="http://docs.google.com/">Google Docs</a> and <a href="http://basecamphq.com/">Basecamp</a> are two examples of generic online solutions. Problems can arise when  the infrastructure isn&#8217;t in place to ensure 24/7 access, and there will  always be concerns about hacking and data loss. You&#8217;re putting your  business into their hands, so it better be rock-solid.</p>
<h4>Collaborating &#8211; Can&#8217;t we all just work together?</h4>
<p>Most online options, and the more expensive local ones, enable  collaboration; several people working together on the same task. Anyone  who has tried to share a master Excel document knows that it only takes  one forgetful moment before chaos reigns &#8211; multiple versions of the same  document floating around, people referring to outdated copies and a  constant fear of overwriting someone else&#8217;s changes. A priority for any  system must be to make our job easier &#8211; putting on a festival is a hard  enough task without having to deal with software induced incompetence.</p>
<h4>Specialisation &#8211; The more generic the tool is, the less useful* it will be.</h4>
<p>Specialisation generally brings better, more productive tools. You can  fix a computer with a sledgehammer, but sometimes it&#8217;s more effective**  to use a torque t6 screwdriver and some heat resistant paste.  Specialisation for our software shouldn&#8217;t just mean that there&#8217;s a set  place to enter riders, or guest lists; it should also bring a sense of  thoughtfulness to the content the system holds. Excel is good; I can  create a set of spreadsheets for my entire festival, but will it email  Accounts when deposits are due? Does it provide the facility for  performers to upload their tech specs? Will it support users when they  make changes that will impact others (like a last minute stage change)?  Finding a specialist system that stores the right details is only half  the battle, getting one that thinks intelligently about the information  it contains should be the Holy Grail.</p>
<p>* gaffer tape is the obvious exception to this rule<br />
** although not as satisfying</p>
<h4>The Ideal World</h4>
<p>There is no solution that&#8217;s perfect for everyone &#8211; even if you  commission a tailor-made system for your event, you&#8217;ll just be at the  beginning of an unending stream of changes and improvements as your  company and event evolves, which is both expensive and time consuming.  In a market that is increasingly competitive, finding those tools that  give you the space to concentrate on what makes your event successful  has to be the priority. I believe that online, collaborative and very specialised is the ultimate path, but then I&#8217;m biased.</p>
<p><em>This is part 1 of a 6 part series. To receive these articles directly to your inbox, <a href="http://www.festivalsystems.net/list.html">sign up to our mailing list</a>.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.festivalsystems.com/2012/01/how-to-manage-your-festival/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Quick Catch-up</title>
		<link>http://www.festivalsystems.com/2012/01/332/</link>
		<comments>http://www.festivalsystems.com/2012/01/332/#comments</comments>
		<pubDate>Thu, 12 Jan 2012 21:43:59 +0000</pubDate>
		<dc:creator>Kris</dc:creator>
				<category><![CDATA[Development]]></category>

		<guid isPermaLink="false">http://www.festivalsystems.com/?p=332</guid>
		<description><![CDATA[Not even going to burden myself with the &#8220;must update blog&#8221; guilt-trip-in-waiting, but I will try to cover off why we&#8217;ve been rather intermittent. It&#8217;s not that we&#8217;re not busy, far from it, we&#8217;re about as busy as we&#8217;ve ever been and that, I guess, is the problem. Yes, we should be spending time marketing, [...]]]></description>
				<content:encoded><![CDATA[<p><img title="office window" src="../wp-content/uploads/office_window.jpg" alt="" width="660" height="400" />Not even going to burden myself with the &#8220;must update blog&#8221;  guilt-trip-in-waiting, but I will try to cover off why we&#8217;ve been rather  intermittent. It&#8217;s not that we&#8217;re not busy, far from it, we&#8217;re about as busy as we&#8217;ve ever been and that, I guess, is the problem. Yes, we should be spending time marketing, tweeting, writing news stories and letting you know what we&#8217;ve been up to&#8230; but there&#8217;s barely enough time in the day to get the core development work done, let alone all that promotional stuff.</p>
<p>Not great business practice, I guess, but I&#8217;ll let you be the judge when you see what we have achieved since the last update.</p>
<ul>
<li>We moved offices from one side of the UK to the other. A fairly big move, brought about by personal circumstances, but we&#8217;re now in what must be one of the nicest offices around (the photo above is the view I have from my desk)</li>
<li>We&#8217;ve added the ability for prospective clients to trial the system, use it and see whether it fits for them.</li>
<li>We&#8217;ve added a new management layer that sits above each event system, tying them together with client control over adding, archiving and upgrading systems.</li>
<li>We&#8217;ve made the address books work across the whole account (rather than being independent for each event), which means that each contact need only be supplied once and changes to a contact are reflected wherever they are used.</li>
<li>The new management layer also means that we can now share contracts and boilerplate documents, accommodation hotels and rooms, stage details and more.</li>
<li>We&#8217;ve added the ability to &#8220;hibernate&#8221; your account, so that you can put your account to bed when you&#8217;ve finished for the year and, whilst hibernating, receive a 50% discount on any subscription fees.</li>
<li>We&#8217;ve added additional subscription levels so that it makes it clearer for clients to select the payment plan that fits their needs.</li>
<li>We&#8217;ve redesigned the Volunteer module so that it&#8217;s easier to use for applicants.</li>
<li>We&#8217;ve rebuilt the graphical Scheduler so that the system can now cope with festivals that run over multiple weeks.</li>
<li>We&#8217;ve added a completely new Support and Help system</li>
<li>We&#8217;ve rebuilt the Permission and Security modules so that they&#8217;re easier to understand and use.</li>
<li>We&#8217;ve added a new Dashboard so that you can see instantly what&#8217;s going on and where.</li>
</ul>
<p>We have got a <a href="https://twitter.com/intent/follow?original_referer=https%3A%2F%2Ftwitter.com%2Fabout%2Fresources%2Fbuttons&amp;region=follow_link&amp;screen_name=FestivalSystems&amp;source=followbutton&amp;variant=2.0">new twitter a/c,</a> which we&#8217;re using for help, support and upgrade notices. We&#8217;ve written a series on How to Manage Your Festival, more of which in future posts, and there&#8217;s a complete marketing plan in existence.</p>
<p>And we&#8217;re not finished yet.</p>
<p><img class="alignnone size-full wp-image-334" title="todo" src="http://www.festivalsystems.com/wp-content/uploads/todo_large.jpg" alt="" width="660" height="260" /></p>
<p>Here&#8217;s the development/project list for the next few months. More than enough to keep us busy.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.festivalsystems.com/2012/01/332/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Artist&#8217;s Apply to Play</title>
		<link>http://www.festivalsystems.com/2011/03/apply/</link>
		<comments>http://www.festivalsystems.com/2011/03/apply/#comments</comments>
		<pubDate>Wed, 23 Mar 2011 16:06:14 +0000</pubDate>
		<dc:creator>Kris</dc:creator>
				<category><![CDATA[Development]]></category>

		<guid isPermaLink="false">http://www.festivalsystems.com/?p=321</guid>
		<description><![CDATA[We&#8217;re really happy to announce that we&#8217;ve just completed another important module to the site &#8211; Artist&#8217;s Apply to Play. What the module enables you to do is to build a form for prospective artists to fill out with all their biog details, links to various web resources (MySpace, Youtube, Soundcloud, etc), and a range [...]]]></description>
				<content:encoded><![CDATA[<p><img class="alignnone size-full wp-image-322" title="apply" src="http://www.festivalsystems.com/wp-content/uploads/apply.gif" alt="" width="660" height="164" /></p>
<p>We&#8217;re really happy to announce that we&#8217;ve just completed another important module to the site &#8211; Artist&#8217;s Apply to Play. What the module enables you to do is to build a form for prospective artists to fill out with all their biog details, links to various web resources (MySpace, Youtube, Soundcloud, etc), and a range of other questions that you can control using our Form Builder (see <a href="http://www.festivalsystems.com/2011/02/form-builder-upgrade/">below</a>).</p>
<p>These applications are then stored in a separate part of the system where the programming team can review and rate the submissions. You can even write notes for each, with categories (such as Scheduling or Contracts).</p>
<p>Those successful applicants can then be promoted into the main system, carrying with them all the biog and other details that they&#8217;ve already provided, saving you from having to re-enter all that information all over again. Oh, and any of the notes that you&#8217;ve made about them will automatically appear in the appropriate places within the main Artist module, ensuring that you don&#8217;t lose track of anything important.</p>
<p>Again, it&#8217;s all part of our standard service. <a href="http://www.festivalsystems.net/contact.html">Get in touch</a> to take a look for yourselves.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.festivalsystems.com/2011/03/apply/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
