This file Jobs.txt is used to generate the main part of jobs.html.  It's in sections, separated by 8 "=" signs, and you can use the Sections menu to position to the job description you're interested in and then modify it as required.

Within a section, the Title must be a single line, but the full description can be several paragraphs.
The entries are:
Title.
[Optional] The word "Needed".  This causes the "Needed" arrow to be displayed against the entry which the user sees.
Multi-line long description which is displayed when the user clicks on the Title.
========
Programme Director
<B>March</B>: Arrange headline artist line-up for following year (needed for the T-shirt which needs to be ordered in mid-April), discuss fees (ask past director for guidance) and requirements (we offer a bed with a 'friend of the festival' - Brian or Meg - indoor or outdoor camping, we do not pay for performers' accommodation), record negotiation results in spreadsheet (needed for contracts later).  Have a budget to hand (previous budgets available from director/treasurer) and stick to it as much as possible.

<B>April</B>: Help with final preparations for festival, finalise programme, arrange for A3 prints of programmes (in colour) and workshop descriptions, 5 each to put on display outside the four major halls and the festival office.  <B>At the Festival</B>: Be available for trouble- shooting/queries, make announcements, mingle.

<B>May</B>: Deal with post-festival correspondence (often including feedback), analyse the attendance figures for the events to see what worked and what didn't.

<B>June to September</B>: Network at festivals, fill the rest of the slots with recommended performers (make sure to keep a tally and don't overbook), aim for a balanced programme:
<UL>
  <LI>English (must include Playford and Modern): 10 workshops.</LI>
  <LI>American: usually at least one caller from the US: 10 workshops</LI>
  <LI>Mixed English/American: 10 workshops (be clear to callers that a mix is required) - try to have one of each of these categories at all times of the festival.</LI>
  <LI>Evening dances: 3 American dances, 2 Playford Balls, 1 mixed dance is the core requirement, if more than 300 attendees, an extra dance can be added on Saturday and Sunday; these should be Mixed (this to be done in April when numbers are clearer).  Friday evening tends to be relatively quiet as people are still arriving.</LI>
  <LI>Scottish: 2 workshops and one dance in a workshop slot (or ask the teacher if they prefer 3 workshops).</LI>
  <LI>International: one major Balkan teacher (ideally native to the country whose dances they teach, Bob Robinson is a good adviser) (6 classes) additionally other genres like Argentine Tango, Indian etc.  (see previous programmes) 4 classes, 3 evening dances (one Western European/Balkan mix, two mainly Balkan).</LI>
  <LI>French/Scandi: two to four workshops, one or two (Euro-)Bals, usually in the Large Hall in the evening break on Saturday and Sunday.</LI>
  <LI>Singing: 2 to 4 workshops (watch take-up).</LI>
  <LI>Music workshops: 2 to 4 (find out which of the musicians you have on site does music teaching workshops).</LI>
  <LI>Callers' workshop(s) and Showcase.</LI>
  <LI>Have at least one new event every year.</LI>
</UL>
<B>September/October</B>: Fill the programme grid.  Currently the director fills in the online grid (tuition by Colin or past director available).  As there tend to be a lot of changes, this is the most time-efficient way of dealing with the programme (rather than having to explain to Colin where a change is needed - quicker to fill it in yourself).  First programme draft needs to be complete by end of October, tickets go on sale on 1 November, dancers really appreciate having a programme to look at when they book.

<B>January</B>: Send out contracts, give performers a deadline, say end of January, always include a link to the programme grid and tell performers to look at it.  There are often queries (wrong room, wrong band, wrong time etc.) - you want corrections now, not three days before the festival!

<B>February</B>: send a mass reminder to those who haven't returned their contract.

<B>March</B>: second reminder

Forward returned contracts to ticketing and treasurer as they come in.
========
Treasurer
The Treasurer's role is to reconcile incoming payments to the tickets sold, to pay bills in relation to the administration of the festival, to ensure prompt payment of amounts due to the performers and to provide the Director with an annual report detailing income and expenditure to facilitate planning of future events.
========
Tickets Overseer
Needed
September/October
<UL>
  <LI>setting next year's ticket prices with Programme Director and Treasurer</LI>
  <LI>agreeing and updating application forms</LI>
</UL>
All year
<UL>
  <LI>liaison with Ticketing Agency Coordinator</LI>
</UL>
From November:
<UL>
  <LI>receipt of booking forms from Ticket Agency or direct from customers/stewards</LI>
  <LI>processing concessionary tickets including from roll-overs, performers' groups and 'specials' agreed by Programme Director</LI>
  <LI>maintaining files of customer/steward booking forms</LI>
  <LI>handling any issues/problems with customer bookings</LI>
  <LI>forwarding steward forms to Pre-Festival Steward Coordinator</LI>
  <LI>liaison with Ticket Designer</LI>
  <LI>announcements to long-term supporters and each year's ticket purchasers</LI>
  <LI>reporting on sales, and paperwork for on-site ticket sales, collating requirements such as indoor/outdoor camping, T-shirts</LI>
</UL>
========
Ticket Agency Coordinator
Needed
September/October:
<UL>
  <LI>agreeing ticket options with Programme Director</LI>
  <LI>setting up the ticket options on the agency site</LI>
</UL>
All year:
<UL>
  <LI>liaison with the selected ticket agency (currently TicketTailor)</LI>
  <LI>giving advice on production of reports etc. - ideally taking on the role of producing selected reports/updates as needed</LI>
</UL>
========
Ticket Designer/Distributor
Needed
<UL>
  <LI>designing tickets in liaison with Tickets Overseer</LI>
  <LI>producing tickets for dancers, staff and performers plus concessionary tickets in-house or via out-sourcing</LI>
  <LI>preparing ticket lists and tickets on lanyards for on-site collection, including extracting information provided by Ticket Overseer</LI>
</UL>
========
School Liaison
Needed
<UL>
  <LI>keeping school aware of our needs (such as performance rooms, indoor/outdoor camping)</LI>
  <LI>checking for changes the school may have made (security, access, agreeing support such as 6th form parking assistance), overnight school security</LI>
  <LI>Obtaining price for next school hire</LI>
  <LI>Visiting school about a week before event (there is often a change we haven't been told about)</LI>
</UL>
========
General Admin
Needed
From March/April:
<UL>
  <LI>Updating festival paperwork such as</LI>
  <LI>on-site signs, posters, maps</LI>
  <LI>collating contents of the Festival Office and Venue Folders</LI>
  <LI>preparing attendance tally sheets (to be filled in by stewards)</LI>
</UL>
Allocate rooms for Indoor Camping to staff, stewards and performers
<UL>
  <LI>Liaise with school about number of rooms available in January</LI>
  <LI>Information needs to be extracted from contracts and steward forms to allocate rooms as per the specified requirements</LI>
</UL>
========
Catering Coordinator
Needed
<UL>
  <LI>Find caterers for event, Friday evening to Monday lunchtime</LI>
  <LI>For Sunday and Monday: ideally sandwiches, cake and coffee/refreshments plus hot food at least at lunchtime and dinnertime.  Friday:&nbsp;something simple in the evening, Monday lunchtime hot food plus sandwiches for people to take away for their journeys home</LI>
  <LI>Get this information on the website as early as possible (dancers don't like 'food insecurity')</LI>
</UL>
========
Volunteer Coordinator
Needed
<UL>
  <LI>Coordinate the smooth running of all the admin; make sure tasks are carried out as required</LI>
  <LI>Convene team meetings as required</LI>
  <LI>Troubleshoot issues during the festival</LI>
</UL>
========
Steward Coordinator - pre-festival
From November:
<UL>
  <LI>Receive steward booking forms and send standard welcoming letter to the volunteer(s).</LI>
  <LI>Keep an eye on numbers: once there are enough (and a few to spare) to run the festival, tell Webmaster to close bookings on Stewards web page and Tickets Agency Coordinator to ensure sales are stopped by the Agency</LI>
</UL>
Starting in April:
<UL>
  <LI>Allocate stewards to events.  This is based on stewards' declared preferences.  If unclear, or too many people want to steward for the same events, communicate with stewards and find out where else they wouldn't mind working.</LI>
  <LI>Create a draft rota, liaise with Programme Director, tweak rota.  There are often late programme changes, so an eye has to be kept on the live programme online.</LI>
  <LI>Send draft out to stewards and ask for their feedback.  If swaps are suggested, try to accommodate them (it is important to have happy stewards).</LI>
  <LI>Finalise rota in the week before the festival and send out to all stewards and Programme Director.</LI>
</UL>
========
On-site Steward Coordinator
This role is to be the troubleshooter and coordinator for stewards during the festival.

Deal with queries, guide, call Director only when absolutely necessary.
========
Venue Stewards
For those who like to be at the dance / singing / music events etc.

See the <A Href="stewards.html">Stewards</A> page for more information.
========
Office Stewards
A small, dedicated group who would like to work 'behind the scenes' but who would have a more in-depth knowledge of the ticketing / information etc.

See the <A Href="stewards.html">Stewards</A> page for more information.
========
Refreshments Stewards
Staffing of tea / coffee stations during the breaks.

See the <A Href="stewards.html">Stewards</A> page for more information.
========
Publicity Manager
Advertising the festival via flyer and T-shirt design, use of social media, arrange for adverts in selected folkdance publications both hard-copy and on line, info to Evesham Tourist Information, sorting the best festival photos to put onto the website, sourcing and updating information to go on website (Tourist Office data on local transport, hotels, B&Bs, cafes, restaurants, etc).
========
Webmaster
The Webmaster needs a good knowledge of HTML, as the site doesn't use a Content Management System.  Instead it uses Colin Hume's <A Href="https://colinhume.com/download.htm#WebEdit">WebEdit</A> program, which has many advantages.  Pages are quick to load because they're static rather than generated on the fly by a CMS.  You can update pages on your own machine, check that they look the way you want them, and then upload them to the server to be available to the world.  There is special code in WebEdit to simplify updating the programme grid, used by both Webmaster and Programme Director.  There is also special code to generate the Performers page from an RTF (rich text format) file containing all performers past and present, so updating this can be as easy as switching on some entries and switching off others.  These two functions are linked together, so when you update the programme grid and then run Performers.rtf the Performers page automatically shows what events each performer is appearing at.  You will probably also be searching Facebook and other websites for photos and descriptions to go on the Performers page, and the photos may need to be cropped, resized and possibly edited.  When the programme is finalised I go through the page and juggle things around so that it fits on two A4 pages when printed out.

There are also a number of PHP programs - error handler, sending emails, receiving and displaying feedback, processing orders from the Tickets page and other odd things.  You can install the PHP system on your hard disk, and again test any changes locally before making them available on the server.
========
First Aiders
Provide First Aid on-site.

Full description not yet available.