Coventry parkrun has been very lucky to have been run from concept until now (over 3 years later), by our amazing Event Director, Jason Douglas.
The dedication required for one person to start up and then to keep a parkrun event going should not be unbderestimated. Recently the core team principle, used by many other parkrun events (to share the administrative load), was proposed to the volunteer group at Coventry parkrun.
As a result I believe that we now have two full core teams in place. In case you don't know how this concept works, the idea is that a core team consists of 4 people and these people take responsibility for one parkrun every few weeks and take on four of the main volunteer roles. Those being, Run Director (plus results upload), Timer, Numbers and Registration.
I was brave/foolish/drunk enough at the time of reading that first email request, to gather a few friends and put our names forward as a core team. Last weekend saw our first outing and the first of any core team outing at Coventry parkrun, with me as Run Director for my second time. And what a weekend to pick!
It turned out that Coventry City Council had planned to start some major path resurfacing works in the park, on a section of the parkrun route normally used in both directions twice per parkrun. Oh and they started it just the day before parkrun, on Friday.
Now this is great news long term as it means we will have some fantastic, smooth, flat tarmac surfaces to run on in a few weeks time, but for a core team on their first outing, and with me as Run Director for only the 2nd time, this was an extra challenge that I would not have wished for. But so be it!
So where there were supposed to be parkrunners there were now diggers! An alternative route was required and with a little help from our amazing Event Director a new route was concieved on parkrun eve.
Funnilly enough, parkrun eve also saw 4 of us, our Event Director and 3 of the core team, each take our own separate look at the works and a tour of the park to ensure that the proposed route was clear and long enough. Now that's parkrun dedication for you.
My Run Director introduction speech was a little longer (and ever so slightly more confusing) than usual, with many exclaiming that they were mentally "lost" by the time I had explained turns 6 and 7 (of about 13), but all in all everyone adapted well to the new course and it all seemed to go very smoothly. Thanks of course to all the volunteers out on the course on the day.
I have to say that Saturday was the first time when I have volunteered at parkrun and haven't had the slightest thought of wishing I had been running. I enjoyed Run Directing so much that the thought never entered my mind. I would never have expected that to happen.
Next week the pathway disruption will move to the next section of the park and the headache baton is passed back to our usual Event and Run Director who will no doubt make it all look far more easy than I did.
Even with all the added difficulties I am still very glad that I put our names forward as a new core team. I would encourage every other parkrunner to put their name forward to be a Run Director, part of a core team or take on any other parkrun volunteer position for that matter. All the positions are all far easier and a lot more fun than you might think. Go on, give it a go!
Showing posts with label parkrun volunteering. Show all posts
Showing posts with label parkrun volunteering. Show all posts
Tuesday, 19 March 2013
Thursday, 24 January 2013
parkrun Volunteering made simple....the Barcode Operator
Barcode Operator (also know as Registration)
So the parkrunners have turned up with thair barcodes and run their parkrun. The Timekeeper has started the timing device and recorded times for each finish position. The Numbers role has handed out the finish position tokens in turn.
Now, if all goes to plan, the parkrunners will make their way to the results registration desk, where the Barcode Operator role will be carried out. This role is the final piece in the jigsaw puzzle to link runners, finish positions and finish times together ready for results processing.
Depending on the size of the parkrun event there may be more than one person in the barcode scanning role (at Coventry parkrun we typically have 3). When there are more than one Barcode Operator, any runner can go to any Barcode Operator without causing problems.
The Barcode Operator role will take both an athlete barcode (the personal barcode that each runner brings with them to each event) and the finish position token. The Barcode Operator should only scan where both of these barcodes are available. Where a runner has forgotten their own personal athlete barcode, their position cannot be properly recorded. The premice being "No barcode, no result!". However, it is fine to remind these runners of their finish position and tell them to look at that position in the results to get their time.
To scan a barcode, the button on the barcode scanner should be pressed (causing the red scanning laser to come on) and held until the scanner beeps and the red scanning laser switches off. The brightest of sunny conditions can interfere with the scanners and in these conditions it is wise to shelter from direct sunlight.
Where an event has multiple Barcode Operators, it is wise to position them a little way away from each other so that each can hear the beep of their own scanner, without being confused by any others.
The athlete barcode should always be scanned before the finish position barcode. The athlete barcode should be handed back to the parkrunner for reuse on subsequent weeks. The finish position token should be kept. There will usually be a container to put these into.
Some athlete barcodes do not scan properly, the paper may be damp or creased or the ink may have run. In this case, neither barcode should be scanned and the runner should be sent with both barcodes to the Results Adminstrator who will note down the athlete barcode number, the runner's name and their finish position.
The Barcode Operator role can get quite busy shortly after the most common finish times and at the larger parkrun events. But there is very little pressure on the Barcode Operator as there is no real great rush to scan the barcodes. Most parkrunners are happy to chat to other runners whilst waiting in the queue.
I hope this has helped to convince you that this role is not difficult and hopefully you will be happy to volunteer for this role at you home parkrun event some time soon.
So the parkrunners have turned up with thair barcodes and run their parkrun. The Timekeeper has started the timing device and recorded times for each finish position. The Numbers role has handed out the finish position tokens in turn.
Now, if all goes to plan, the parkrunners will make their way to the results registration desk, where the Barcode Operator role will be carried out. This role is the final piece in the jigsaw puzzle to link runners, finish positions and finish times together ready for results processing.
Depending on the size of the parkrun event there may be more than one person in the barcode scanning role (at Coventry parkrun we typically have 3). When there are more than one Barcode Operator, any runner can go to any Barcode Operator without causing problems.
The Barcode Operator role will take both an athlete barcode (the personal barcode that each runner brings with them to each event) and the finish position token. The Barcode Operator should only scan where both of these barcodes are available. Where a runner has forgotten their own personal athlete barcode, their position cannot be properly recorded. The premice being "No barcode, no result!". However, it is fine to remind these runners of their finish position and tell them to look at that position in the results to get their time.
To scan a barcode, the button on the barcode scanner should be pressed (causing the red scanning laser to come on) and held until the scanner beeps and the red scanning laser switches off. The brightest of sunny conditions can interfere with the scanners and in these conditions it is wise to shelter from direct sunlight.
Where an event has multiple Barcode Operators, it is wise to position them a little way away from each other so that each can hear the beep of their own scanner, without being confused by any others.
The athlete barcode should always be scanned before the finish position barcode. The athlete barcode should be handed back to the parkrunner for reuse on subsequent weeks. The finish position token should be kept. There will usually be a container to put these into.
Some athlete barcodes do not scan properly, the paper may be damp or creased or the ink may have run. In this case, neither barcode should be scanned and the runner should be sent with both barcodes to the Results Adminstrator who will note down the athlete barcode number, the runner's name and their finish position.
The Barcode Operator role can get quite busy shortly after the most common finish times and at the larger parkrun events. But there is very little pressure on the Barcode Operator as there is no real great rush to scan the barcodes. Most parkrunners are happy to chat to other runners whilst waiting in the queue.
I hope this has helped to convince you that this role is not difficult and hopefully you will be happy to volunteer for this role at you home parkrun event some time soon.
Saturday, 22 December 2012
parkrun Volunteering made simple....Numbers
The Numbers role at parkrun is fairly simple, but does require someone with a steady hand and who is calm under pressure.
The Numbers volunteer can spend the first 15 minutes or so at parkrun simply clapping and encouraging parkunners. The Numbers role really comes into effect when the first runners finish their parkrun and continues until the last person finishes.
The Numbers volunteer will be given all the finish position tokens and it is their role to stand at the end of the finish funnel and hand out the finish position tokens, one each to each and every finisher. This sounds a pretty simple task and it is really, so long as you don't panic and can handle the tokens quickly and effectively.
It will not normally be possible to ensure that the finish position tokens are in the correct order whilst they are being handed out, as there simply isn't time. The Numbers role has to rely on the fact that the tokens have already been placed in the correct order.
The Numbers role is not normally responsible for ensuring that runners remain in the correct finishing order. The Funnel Manager would normally do this. Perhaps only at the smallest of parkrun events, where volunteer numbers do not allow a Funnel Manager, the Numbers role may also be asked to keep an eye on runners changing order.
The basics of handing out the finish position tokens is that every finisher that has done the run under their own steam should get a finish position token. They don't have to have run, they may have walked or hopped and skipped. Children and babies in buggies do not get a finish position but wheelchair users obviously do. The most important aspect of this is that the Timekeeper and Numbers roles must both use the same criteria to decide who gets a time and a token. This will ensure that the finish times and positions stay in sync. The Number Checker will be making constant checks to ensure that if and when the two get out of sync it is spotted as early as possible. Neither the Timekeeper or the Numbers role should ever attempt to correct out of sync problems during the run. This will be resolved during results processing by the Results Administrator.
There are often runners who decide that they do not want to take a finish position token. This can be for any number of reasons, perhaps not having their athlete barcode or not wanting the time after a bad run and many more reasons besides. In such cases, rather than dwelling on the fact, the Numbers role should simply pocket the finish position token and carry on to the next person and token. By pocketing the finish position token, it has been kept safe and will not have put the results out of sync as the finisher will still effectively have been given a finish position. If the Numbers role sees or is told of a runner ducking out of the funnel (Funnel Duckers), then the same process of pocketing the relevant finish position token will help to keep positions in sync.
The trickier aspects of this job are:
- readying batches of finish position tokens whilst also handing out earlier tokens (larger events often have a Numbers Assisstant to prepare batches of tokens for the Numbers role).
- coping with the fiddly tokens on cold days. Unfortunately gloves are not normally the answer, as the tokens become tricky to manipulate when wearing gloves. In the winter you just have to grit your teeth and get on with it. Fingerless gloves could be worth a shot.
- coping with the volume of finishers at the peak finish times. I have heard that at the largest parkrun of all (Bushy Park), there is a 10 minute period where they have close to 1 finisher per second. I'm sure you can imagine that handing out 600 tokens in 10 minutes is no mean feat!). Most parkruns do not see anything like this quantity of finishers, nevertheless there are times where the Numbers role has to work flat-out for a short period of time.
The best thing about this role is that you get to be the first to congratulate every single runner immediately after their run.
The Numbers volunteer can spend the first 15 minutes or so at parkrun simply clapping and encouraging parkunners. The Numbers role really comes into effect when the first runners finish their parkrun and continues until the last person finishes.
The Numbers volunteer will be given all the finish position tokens and it is their role to stand at the end of the finish funnel and hand out the finish position tokens, one each to each and every finisher. This sounds a pretty simple task and it is really, so long as you don't panic and can handle the tokens quickly and effectively.
It will not normally be possible to ensure that the finish position tokens are in the correct order whilst they are being handed out, as there simply isn't time. The Numbers role has to rely on the fact that the tokens have already been placed in the correct order.
The Numbers role is not normally responsible for ensuring that runners remain in the correct finishing order. The Funnel Manager would normally do this. Perhaps only at the smallest of parkrun events, where volunteer numbers do not allow a Funnel Manager, the Numbers role may also be asked to keep an eye on runners changing order.
The basics of handing out the finish position tokens is that every finisher that has done the run under their own steam should get a finish position token. They don't have to have run, they may have walked or hopped and skipped. Children and babies in buggies do not get a finish position but wheelchair users obviously do. The most important aspect of this is that the Timekeeper and Numbers roles must both use the same criteria to decide who gets a time and a token. This will ensure that the finish times and positions stay in sync. The Number Checker will be making constant checks to ensure that if and when the two get out of sync it is spotted as early as possible. Neither the Timekeeper or the Numbers role should ever attempt to correct out of sync problems during the run. This will be resolved during results processing by the Results Administrator.
There are often runners who decide that they do not want to take a finish position token. This can be for any number of reasons, perhaps not having their athlete barcode or not wanting the time after a bad run and many more reasons besides. In such cases, rather than dwelling on the fact, the Numbers role should simply pocket the finish position token and carry on to the next person and token. By pocketing the finish position token, it has been kept safe and will not have put the results out of sync as the finisher will still effectively have been given a finish position. If the Numbers role sees or is told of a runner ducking out of the funnel (Funnel Duckers), then the same process of pocketing the relevant finish position token will help to keep positions in sync.
The trickier aspects of this job are:
- readying batches of finish position tokens whilst also handing out earlier tokens (larger events often have a Numbers Assisstant to prepare batches of tokens for the Numbers role).
- coping with the fiddly tokens on cold days. Unfortunately gloves are not normally the answer, as the tokens become tricky to manipulate when wearing gloves. In the winter you just have to grit your teeth and get on with it. Fingerless gloves could be worth a shot.
- coping with the volume of finishers at the peak finish times. I have heard that at the largest parkrun of all (Bushy Park), there is a 10 minute period where they have close to 1 finisher per second. I'm sure you can imagine that handing out 600 tokens in 10 minutes is no mean feat!). Most parkruns do not see anything like this quantity of finishers, nevertheless there are times where the Numbers role has to work flat-out for a short period of time.
The best thing about this role is that you get to be the first to congratulate every single runner immediately after their run.
Wednesday, 5 December 2012
parkrun Volunteering made simple...the Timekeeper
Being the Timekeeper at parkrun sounds ominous doesn't it. It's that role at parkrun that everyone seems to fear. But why?
I suppose there is a bit of pressure in this role. If everything were to go completely wrong then all the parkrunners could end up without a time. But, even then, looking on the bright side, they will still have had their parkrun, they will know their finish position and they will have had another parkrun finish to add towards their 10, 50, 100 or 250 club t-shirts.
But that really is the wrong way to look at the Timekeeper role. It is very rare for a Timekeeper to get things so wrong that no times are recorded. Minor mistakes such as too many or too few times being recorded are relatively simple to resolve at the time of processing the results.
So what does the Timekeeper role actually involve?
The Timekeeper carries out this role using the Timing device. I believe that there are more than one type of timing device in use at parkrun so the specifics may be a little different for each type. There is a little bit of set-up for the timing device, which the Run Director will always be able to help with. There are also good instructions available and these would be made availablle to the Timekeeper ahead of the run. There is normally plenty of time to digest and understand these instructions before the run.
With the timing device set up and ready to go, the Timekeeper will stand near the Run Director at the start line. The Run Director will ensure that the Timekeeper is ready before the "Ready...Go", or whatever method is used for starting the parkrun. At this point the Timekeeper will press the button on the Timing device to signify the start of the run.
The Timekeeper can then take around 15 minutes or so off, whilst waiting for the approach of the first finisher. Seriously though, the Timekeeper only needs to act a minute or so prior to the first finisher. At that time, the Timekeeper will plug the remote button (where available) into the timing device. This can be done earlier, but leaving it until a minute or two before the first finisher ensures less chance of an accidental button press or two. It is possible to use a button on the timing device, but the remote button is just a little easier to use.
The Timekeeper should then position themselves in line with the finish line ready for the runners to finish.
As each parkrunner crosses the line, the Timekeeper must then press the button to signify a finisher and enable the timing device to record a finish time. Each time is automatically associated with the corresponding finish position such that by the end of the run the timing device will have stored the finish time for each finish position.
When the earliest and latest runners are finishing, and at the smaller parkrun events, the Timekeeper has plenty of time to carry out this role accurately. However, at the busiest of parkrun events and at the most popular finish times, this task can be quite taxing. Some Timekeepers will look down and count pairs of feet, whilst others will look up and count heads. Do whatever works for you. The aim is to get one press per human finisher finishing under their own steam. Babies in buggies are not normally given their own time or finish position, but this could be different at each parkrun event. As long as the Timekeeper and the Numbers roles (giving out finish position tokens) stick to the same rules about who gets a time and finish position then it should all work out.
It is important to remember that the Number Checker and Funnel Management roles are in place specifically to notice when and where mistakes occur and this will usually allow these to be easily resolved when the results are processed. The Timekeeper just needs to concentrate on their own role and not worry about mistakes or trying to rectify them as this may cause trickier problems to resolve.
All in all the Timekeeper job is good fun, there is a little bit of pressure, but it is very rare for mistakes to be made that cannot be rectified pretty simply. So there is nothing to worry about. Put your name forward and give Timekeeping a go. If I can do it, then so can you!
I suppose there is a bit of pressure in this role. If everything were to go completely wrong then all the parkrunners could end up without a time. But, even then, looking on the bright side, they will still have had their parkrun, they will know their finish position and they will have had another parkrun finish to add towards their 10, 50, 100 or 250 club t-shirts.
But that really is the wrong way to look at the Timekeeper role. It is very rare for a Timekeeper to get things so wrong that no times are recorded. Minor mistakes such as too many or too few times being recorded are relatively simple to resolve at the time of processing the results.
So what does the Timekeeper role actually involve?
The Timekeeper carries out this role using the Timing device. I believe that there are more than one type of timing device in use at parkrun so the specifics may be a little different for each type. There is a little bit of set-up for the timing device, which the Run Director will always be able to help with. There are also good instructions available and these would be made availablle to the Timekeeper ahead of the run. There is normally plenty of time to digest and understand these instructions before the run.
With the timing device set up and ready to go, the Timekeeper will stand near the Run Director at the start line. The Run Director will ensure that the Timekeeper is ready before the "Ready...Go", or whatever method is used for starting the parkrun. At this point the Timekeeper will press the button on the Timing device to signify the start of the run.
The Timekeeper can then take around 15 minutes or so off, whilst waiting for the approach of the first finisher. Seriously though, the Timekeeper only needs to act a minute or so prior to the first finisher. At that time, the Timekeeper will plug the remote button (where available) into the timing device. This can be done earlier, but leaving it until a minute or two before the first finisher ensures less chance of an accidental button press or two. It is possible to use a button on the timing device, but the remote button is just a little easier to use.
The Timekeeper should then position themselves in line with the finish line ready for the runners to finish.
As each parkrunner crosses the line, the Timekeeper must then press the button to signify a finisher and enable the timing device to record a finish time. Each time is automatically associated with the corresponding finish position such that by the end of the run the timing device will have stored the finish time for each finish position.
When the earliest and latest runners are finishing, and at the smaller parkrun events, the Timekeeper has plenty of time to carry out this role accurately. However, at the busiest of parkrun events and at the most popular finish times, this task can be quite taxing. Some Timekeepers will look down and count pairs of feet, whilst others will look up and count heads. Do whatever works for you. The aim is to get one press per human finisher finishing under their own steam. Babies in buggies are not normally given their own time or finish position, but this could be different at each parkrun event. As long as the Timekeeper and the Numbers roles (giving out finish position tokens) stick to the same rules about who gets a time and finish position then it should all work out.
It is important to remember that the Number Checker and Funnel Management roles are in place specifically to notice when and where mistakes occur and this will usually allow these to be easily resolved when the results are processed. The Timekeeper just needs to concentrate on their own role and not worry about mistakes or trying to rectify them as this may cause trickier problems to resolve.
All in all the Timekeeper job is good fun, there is a little bit of pressure, but it is very rare for mistakes to be made that cannot be rectified pretty simply. So there is nothing to worry about. Put your name forward and give Timekeeping a go. If I can do it, then so can you!
Tuesday, 20 November 2012
Top 5 feelings at parkrun
I'm sure every parkrunner would have their own opinions about this, but here are my suggestions for the top 5 feelings at parkrun:
1) Getting a parkrun PB - That sense of achievement just can't be beaten. The longer your old parkrun PB has stood for, the better the feeling. There is something very special about being better than you have ever been at parkrun before.
2) Pacing a friend to a parkrun PB - It may not be your own PB, but helping someone else to get theirs feels almost as good as getting a PB yourself. And maybe someone else will repay the favour to help you to a PB one day.
3) Volunteering - You may not get to run yourself, but knowing that you have still been part of parkrun and have enabled everyone else to run is still a great feeling. It really is the next best thing to running at parkrun and is a great way to stay involved when injured or resting for another event.
4) Joining the 50 or 100 club - It's a great feeling to get that brand new 50 or 100 (or 250 club I imagine) club t-shirt, especially when you cast your mind back over all those runs and the commitment it has taken to reach that landmark. Then you can show everyone that you are part of the club.
5) Community spirit - That great feeling of being part of something as special as parkrun. Sharing the experience, being cheered on by (and cheering on in return) your new-found parkrun friends.
1) Getting a parkrun PB - That sense of achievement just can't be beaten. The longer your old parkrun PB has stood for, the better the feeling. There is something very special about being better than you have ever been at parkrun before.
2) Pacing a friend to a parkrun PB - It may not be your own PB, but helping someone else to get theirs feels almost as good as getting a PB yourself. And maybe someone else will repay the favour to help you to a PB one day.
3) Volunteering - You may not get to run yourself, but knowing that you have still been part of parkrun and have enabled everyone else to run is still a great feeling. It really is the next best thing to running at parkrun and is a great way to stay involved when injured or resting for another event.
4) Joining the 50 or 100 club - It's a great feeling to get that brand new 50 or 100 (or 250 club I imagine) club t-shirt, especially when you cast your mind back over all those runs and the commitment it has taken to reach that landmark. Then you can show everyone that you are part of the club.
5) Community spirit - That great feeling of being part of something as special as parkrun. Sharing the experience, being cheered on by (and cheering on in return) your new-found parkrun friends.
Subscribe to:
Posts (Atom)