[tournament-org] TrigantiusLessonI

[Paul Smith]

Geoff wrote:
A. Close entry a week before the date.

B. A very punitive late entry fee kicking in a week before the date.

C. An incrementing late entry fee e.g. start at £2 on the Monday
incrementing by £2 every day.

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.

Paul

On Sun, Mar 17, 2019 at 10:20 PM Neil Sandford via tournament-org <
tournament-org at lists.britgo.org> wrote:

> Hi, Geoff. Here's a few random thoughts.
>
> 1)  16 additional registrations _on the day_ would be scary, but two days
> to go should not be too bad.
>
> 2) You, Matt, Helen, Martin and I think I saw Paul Smith. That's a good
> team. Plenty of scope for delegation.
>
> 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.
>
> 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
>
> 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.
>
> Anyway - it's a good problem to have!
>
> 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.
>
> 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.
>
> C. An incrementing late entry fee e.g. start at £2 on the Monday
> incrementing by £2 every day. NO - outlandish to do.
>
> Neil
>
>
> -----Original Message-----
> From: Geoff Kaniuk via tournament-org <tournament-org at lists.britgo.org>
> Sent: 17 March 2019 20:32
> To: TOUR List <tournament-org at lists.britgo.org>
> Subject: [tournament-org] TrigantiusLessonI
>
> I think there were three lessons to be learnt from last week's Trigantius:
>
> Late Surge, Registration Time, Trophy Management.
>
> Lesson I - Late surge.
> 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.
>
> 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.
>
> 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.
>
> The question is how to stop the late surge?
>
> A. Close entry a week before the date.
>
> B. A very punitive late entry fee kicking in a week before the date.
>
> C. An incrementing late entry fee e.g. start at £2 on the Monday
> incrementing by £2 every day.
>
> All organisers have so far been very resigned to players entering at the
> last minute. I believe this is not tolerated in other competitions.
>
> I will be interested to hear your views?
>
> --
> Geoff
>
> 33 Ashbury Close, Cambridge CB1 3RW 01223 710582
>
> _______________________________________________
> tournament-org mailing list
> tournament-org at lists.britgo.org
> http://lists.britgo.org/cgi-bin/mailman/listinfo/tournament-org
>
>
> _______________________________________________
> tournament-org mailing list
> tournament-org at lists.britgo.org
> http://lists.britgo.org/cgi-bin/mailman/listinfo/tournament-org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.britgo.org/pipermail/tournament-org/attachments/20190318/7f14fc05/attachment-0001.html>