Difference between revisions of "How to organise an event at Makespace"

From Makespace
Jump to: navigation, search
m (formatting)
Line 1: Line 1:
'''If you want to run an event in Makespace which is open to people who are not FOunder Members, before we are properly open (ie now, because we are not properly open yet)'''
+
'''If you want to run an event in Makespace which is open to people who are not Founder Members, before we are properly open (ie now, because we are not properly open yet)'''
  
 
1. work out who would attend (what types of people, grown ups or kids, and how many, and when) and which bits of makespace they might want to visit, and when the event will occur
 
1. work out who would attend (what types of people, grown ups or kids, and how many, and when) and which bits of makespace they might want to visit, and when the event will occur
Line 8: Line 8:
  
 
4. Don't be annoyed if the answer is no - instead, plan something for once we are open!
 
4. Don't be annoyed if the answer is no - instead, plan something for once we are open!
 +
 +
 +
  
 
'''How to run an event after Makespace opens'''
 
'''How to run an event after Makespace opens'''
  
 
There are several things to think about if you want to run an event:
 
There are several things to think about if you want to run an event:
  * What the event is
+
* '''What''' the event is
  * Who attends [age range, necessary experience]
+
* Who '''attends''' [age range, necessary experience]
  * Who is running it - course designer, other presenters/enablers, and any additional staff (first aiders, fire marshals, etc) who might be needed
+
* Who is '''running it''' - course designer, other presenters/enablers, and any additional staff (first aiders, fire marshals, etc) who might be needed
  * Whether there’s any need to charge attendees (for example for materials or to cover speaker expenses)  
+
* Whether there’s any need to '''charge''' attendees <br /> (for example for materials or to cover speaker expenses)  
  * Whether any special equipment might be needed (eg consumables such as lots of bits of wood, or more significant items such as Arduinos, or possibly a need to pre-book the 3D printer to make sure other jobs aren't running on it and so on)
+
* Whether any '''special equipment''' might be needed <br /> (eg consumables such as lots of bits of wood, or more significant items such as Arduinos, or possibly a need to pre-book the 3D printer to make sure other jobs aren't running on it and so on)
  * When the event might happen (considering audience demographics, other events in Cambridge, Makespace bookings and so on)
+
* '''When''' the event might happen <br /> (considering audience demographics, other events in Cambridge, Makespace bookings and so on)
  * How we publicise it (target audience, publicity method) - remember, a badly attended event can be depressing for everyone!
+
* How we '''publicise''' it (target audience, publicity method) - remember, a badly attended event can be depressing for everyone!
  * Whether prebooking is needed (for instance if the event has restricted space but may be popular, or if you can only train a certain number of people, or there's only a certain number of Arduinos available, or whatever)
+
* Whether '''prebooking''' is needed <br /> (for instance if the event has restricted space but may be popular, or if you can only train a certain number of people, or there's only a certain number of Arduinos available, or whatever)
  * Whether repeat attendance is likely (eg a course over several nights)  
+
* Whether '''repeat attendance''' is likely (eg a course over several nights)  
  * What you will do if something goes wrong (for example, if far too many people turn up, or a vital bit of equipment breaks just before the event)
+
* What you will do if '''something goes wrong''' <br /> (for example, if far too many people turn up, or a vital bit of equipment breaks just before the event)
  * How you'll know who came along (this is *vital* because Makespace receives funds based on public engagement, so we need to track who does activities in the space and for how long)
+
* How you'll '''know who came along''' <br /> (this is *vital* because Makespace receives funds based on public engagement, so we need to track who does activities in the space and for how long)
  * Whether there's any specific risk assessment or health and safety preparation needed
+
* Whether there's any '''specific risk assessment''' or '''health and safety preparation''' needed
  
 
At the moment we expect only Full Members (£40/month, inc Founders) will be allowed to organise events. You'll need to book the space in advance in some way and if you are an event organiser you are RESPONSIBLE for making sure that the event follows our safety rules and so on.
 
At the moment we expect only Full Members (£40/month, inc Founders) will be allowed to organise events. You'll need to book the space in advance in some way and if you are an event organiser you are RESPONSIBLE for making sure that the event follows our safety rules and so on.

Revision as of 17:15, 5 January 2013

If you want to run an event in Makespace which is open to people who are not Founder Members, before we are properly open (ie now, because we are not properly open yet)

1. work out who would attend (what types of people, grown ups or kids, and how many, and when) and which bits of makespace they might want to visit, and when the event will occur

2. email management@makespace.org with that info

3. *Wait* for a decision! Without explicit permission you can't have a public event. Even if we think it's OK to go ahead you might need to ensure that there's a certain number of trusted founder members to run the event, etc. Some events might not be possible at all, because we aren't ready to run proper events yet (for instance, we do not have trained first aiders on site).

4. Don't be annoyed if the answer is no - instead, plan something for once we are open!



How to run an event after Makespace opens

There are several things to think about if you want to run an event:

  • What the event is
  • Who attends [age range, necessary experience]
  • Who is running it - course designer, other presenters/enablers, and any additional staff (first aiders, fire marshals, etc) who might be needed
  • Whether there’s any need to charge attendees
    (for example for materials or to cover speaker expenses)
  • Whether any special equipment might be needed
    (eg consumables such as lots of bits of wood, or more significant items such as Arduinos, or possibly a need to pre-book the 3D printer to make sure other jobs aren't running on it and so on)
  • When the event might happen
    (considering audience demographics, other events in Cambridge, Makespace bookings and so on)
  • How we publicise it (target audience, publicity method) - remember, a badly attended event can be depressing for everyone!
  • Whether prebooking is needed
    (for instance if the event has restricted space but may be popular, or if you can only train a certain number of people, or there's only a certain number of Arduinos available, or whatever)
  • Whether repeat attendance is likely (eg a course over several nights)
  • What you will do if something goes wrong
    (for example, if far too many people turn up, or a vital bit of equipment breaks just before the event)
  • How you'll know who came along
    (this is *vital* because Makespace receives funds based on public engagement, so we need to track who does activities in the space and for how long)
  • Whether there's any specific risk assessment or health and safety preparation needed

At the moment we expect only Full Members (£40/month, inc Founders) will be allowed to organise events. You'll need to book the space in advance in some way and if you are an event organiser you are RESPONSIBLE for making sure that the event follows our safety rules and so on.