LILAC is generally held in the weeks prior to/following the Easter bank holiday weekend. As well as a lecture theatre seating 350+ delegates, we also require 5 break out rooms, exhibition and reception space, a large room for the Lagadothon, a PC lab and poster space. For full details of our requirements please download our application form which has a more detailed checklist appended.
The most important aspect of organising LILAC each year is that we need a strong 'home team' supporting the committee at the venue. If your venue is accepted to host the conference we require two people to be co-opted onto the LILAC committee for the year. Our local representatives are expected to do the following;
Due to the time commitments when organising LILAC we also require proof of support from your institution. We also need a team of at least 12 volunteers to help out in the week prior to the conference, as well as at the conference itself; to help out in break out rooms, during keynotes, staffing the cloakroom and manning the reception desk.
Hosting LILAC is hard work, but is also a highly rewarding experience. We look forward to receiving your applications.
LILAC is great opportunity for our fellow professionals to present their ideas, share best practice and show case new thinking in our sector. If you have an idea then we'd love to hear about it. We have many options for the types of sessions you might run from a symposium to a workshop. Visit our Call for papers page to find out how to apply.
Places at this year's conference are likely to be in demand more than ever before. Each year our conference grows increasingly popular and this year promises to be no different. Don't miss out and book your place now for this year's conference.
We look forward to seeing you there!
RT @PaulaGoodale: Going to @LILAC_conf? Interested in doing an MA or PhD? Visit @InfoSchoolSheff exhibition stand for info on courses, inc…
RT @jsecker: I love the fact it was attending @LILAC_conf and speaking to @LibGoddess about ANCIL was what inspired @mhensle1#acrl2017 #acr…