<!DOCTYPE html>
<html><head>
<meta charset="UTF-8">
</head><body><p>In the past it has been suggested that LOGC simplify its entry fee structure. I disagreed then and still do.</p><p>For 2019 we want 100 entrants (now we've sorted out how to do it) the late entry fee is expensive to get people to register early.</p><p>Tournament (or club) attendees sometimes can tend to see themselves as customers. I take every opportunity to disabuse those that seem to take that attitude.</p><p>Similarly I am not running a business.</p><p> It's "us" making F2F happen with a healthy collective attitude.</p><p>So budget for early and take late as "gravy" for recycling for future events.</p><p> But please don't talk about punitive action. </p><p>Please don't even think it. </p><p>Late tournament attendees are not recidivists perhaps a bit more focus on the "we" might improve things.</p><p><br></p><p><br></p><p><br></p><p><br></p><p><br></p><blockquote type="cite">On 18 March 2019 at 11:31 Paul Smith via tournament-org <tournament-org@lists.britgo.org> wrote: <br> <br><div dir="ltr"><div dir="ltr"><div dir="ltr">Geoff wrote: <br style="text-align: left; color: #222222; text-transform: none; text-indent: 0px; font-family: Arial,Helvetica,sans-serif; font-size: 13.33px; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; word-spacing: 0px; white-space: normal;"> <span style="font: small/1.5 Arial,Helvetica,sans-serif; text-align: left; color: #222222; text-transform: none; text-indent: 0px; text-decoration: none; word-spacing: 0px; display: inline; white-space: normal; font-stretch: normal; float: none; background-color: #ffffff;"> A. Close entry a week before the date.</span> <br style="text-align: left; color: #222222; text-transform: none; text-indent: 0px; font-family: Arial,Helvetica,sans-serif; font-size: 13.33px; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; word-spacing: 0px; white-space: normal;"> <br style="text-align: left; color: #222222; text-transform: none; text-indent: 0px; font-family: Arial,Helvetica,sans-serif; font-size: 13.33px; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; word-spacing: 0px; white-space: normal;"> <span style="font: small/1.5 Arial,Helvetica,sans-serif; text-align: left; color: #222222; text-transform: none; text-indent: 0px; text-decoration: none; word-spacing: 0px; display: inline; white-space: normal; font-stretch: normal; float: none; background-color: #ffffff;"> B. A very punitive late entry fee kicking in a week before the date.</span> <br style="text-align: left; color: #222222; text-transform: none; text-indent: 0px; font-family: Arial,Helvetica,sans-serif; font-size: 13.33px; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; word-spacing: 0px; white-space: normal;"> <br style="text-align: left; color: #222222; text-transform: none; text-indent: 0px; font-family: Arial,Helvetica,sans-serif; font-size: 13.33px; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; word-spacing: 0px; white-space: normal;"> <span style="font: small/1.5 Arial,Helvetica,sans-serif; text-align: left; color: #222222; text-transform: none; text-indent: 0px; text-decoration: none; word-spacing: 0px; display: inline; white-space: normal; font-stretch: normal; float: none; background-color: #ffffff;"> C. An incrementing late entry fee e.g. start at £2 on the Monday incrementing by £2 every day.</span></div><div dir="ltr"><br></div><div>I would go with C, it sounds like a great idea - it doesn't stop people entering, and there isn't a big step change if they miss one particular deadline, but it should stop the late surge.</div><div><br></div><div>Paul</div></div><br><div class="ox-51f8c59f76-gmail_quote"><div class="ox-51f8c59f76-gmail_attr" dir="ltr">On Sun, Mar 17, 2019 at 10:20 PM Neil Sandford via tournament-org < <a href="mailto:tournament-org@lists.britgo.org">tournament-org@lists.britgo.org</a>> wrote: <br></div><blockquote>Hi, Geoff. Here's a few random thoughts. <br> <br> 1) 16 additional registrations _on the day_ would be scary, but two days to go should not be too bad. <br> <br> 2) You, Matt, Helen, Martin and I think I saw Paul Smith. That's a good team. Plenty of scope for delegation. <br> <br> 3) Was it demand end-to-end or bottlenecks en route? Keeping GoDraw up to date (Chinese names finally imported and ratings applied) and ready to draw when everything else is ready? Money (the wrong float). Lots of first-time players. Handling language problems. <br> <br> 4) I know you were running the registration, that makes good sense. But one suggestion I liked was two registration desks - either two identical queues <br> <br> 5) or one for people who have the wrong money or want you to change something just before we start. Regularly printing the registration info so you both know what is done and what is outstanding. <br> <br> Anyway - it's a good problem to have! <br> <br> A. Close entry a week before the date - YES Most people would have their accommodation booked ahead of time, so they know they are coming. Everything loaded up on GoDraw, so the only things to do are process the money and click the 'registered' button. Charge a punitive alterations fee if GoDraw has to be updated on the day. <br> <br> B. A very punitive late entry fee kicking in a week before the date. - NO. I'd rather focus on avoiding work on the Thursday before the tournament than turning people off a week before. <br> <br> C. An incrementing late entry fee e.g. start at £2 on the Monday incrementing by £2 every day. NO - outlandish to do. <br> <br> Neil <br> <br> <br> -----Original Message----- <br> From: Geoff Kaniuk via tournament-org < <a href="mailto:tournament-org@lists.britgo.org" target="_blank" rel="noopener">tournament-org@lists.britgo.org</a>> <br> Sent: 17 March 2019 20:32 <br> To: TOUR List < <a href="mailto:tournament-org@lists.britgo.org" target="_blank" rel="noopener">tournament-org@lists.britgo.org</a>> <br> Subject: [tournament-org] TrigantiusLessonI <br> <br> I think there were three lessons to be learnt from last week's Trigantius: <br> <br> Late Surge, Registration Time, Trophy Management. <br> <br> Lesson I - Late surge. <br> Entries were dribbling in steadily in the weeks before the date and had got close to last years entry. However two days before the date I suddenly got 16 entries, breaking our previous entry and getting scarily close to our maximum of 80 for the main tournament. It is great to get more entries than usual, but if they come in good time it is easier to manage. <br> <br> Sourcing extra sets was not a major headache thanks to willingness of Helen and Martin Harvey to load some in their car. We had plenty of clocks thanks to the Fischer time trial managed by Matt Marsh and his supply of digital clocks. <br> <br> A particular issue faced at Trigantius is that the venue is opened only at 10 am so we can never start registration early. The late surge induced the problem of locating sufficient tables in the venue for use by the extras. This took time, delayed the start of registration and we were not able to recover the time. <br> <br> The question is how to stop the late surge? <br> <br> A. Close entry a week before the date. <br> <br> B. A very punitive late entry fee kicking in a week before the date. <br> <br> C. An incrementing late entry fee e.g. start at £2 on the Monday incrementing by £2 every day. <br> <br> All organisers have so far been very resigned to players entering at the last minute. I believe this is not tolerated in other competitions. <br> <br> I will be interested to hear your views? <br> <br> -- <br> Geoff <br> <br> 33 Ashbury Close, Cambridge CB1 3RW 01223 710582 <br> <br> _______________________________________________ <br> tournament-org mailing list <br> <a href="mailto:tournament-org@lists.britgo.org" target="_blank" rel="noopener">tournament-org@lists.britgo.org</a> <br> <a href="http://lists.britgo.org/cgi-bin/mailman/listinfo/tournament-org" target="_blank" rel="noopener">http://lists.britgo.org/cgi-bin/mailman/listinfo/tournament-org</a> <br> <br> <br> _______________________________________________ <br> tournament-org mailing list <br> <a href="mailto:tournament-org@lists.britgo.org" target="_blank" rel="noopener">tournament-org@lists.britgo.org</a> <br> <a href="http://lists.britgo.org/cgi-bin/mailman/listinfo/tournament-org" target="_blank" rel="noopener">http://lists.britgo.org/cgi-bin/mailman/listinfo/tournament-org</a> <br></blockquote></div></div>_______________________________________________ <br>tournament-org mailing list <br>tournament-org@lists.britgo.org <br>http://lists.britgo.org/cgi-bin/mailman/listinfo/tournament-org <br></blockquote></body></html>