(Jul. 29, 2011 5:23 AM)Uwik Wrote: Quote:If all other suggestion fails, the first logical step is to create a stickied thread about the 'beypoints processing checklist' ie:
July 24 - Silver Spring, Maryland: The July Joust
Result receipt
Spelling of names
Payments
Battles
Faces
Credits
etc etc. When a bullet point is done, you can always delete that particular bullet point.
Any thoughts on this?
This is an idea we have discussed before, but we're thinking of the best way to implement it at at the moment. I agree that more transparency would help matters, absolutely.
I realise that this is a point which has been raised before, but the entire process of processing results is not as easy as it looks. Considering we have nearly 50,000 members, any potential spelling error will likely take us to a completely different user. If there was a mistake halfway through a tournament's results, we would have to first delete everything after it (which alone, takes a long time), and then reprocess everything. This is extremely time-consuming.
To speak from my own experience, what Kei said absolutely nails it. If a tournament occurs in a completely different region, say, in the UK, then it's fine to process them whenever we receive them. As Blitz or I will normally have attended said tournament, we'll just go ahead and do it the night of the tournament if we have time, since we can be sure everything is checked out and fine, and that all money has been received. It's worth noting that again, it is about the confidence we have in your results and the situation surrounding them - I'm not targetting anyone in particular, but the more organised all your results are, the easier and more smoothly your results can be processed.
Unfortunately, only Committee members can access the interface which is used for Beypoint processing, so I hope you'll all understand when we say that we can't just recruit volunteers or tournament organisers to process their own results.
However, th!nk's suggestion to have a central inbox is a great idea, and I would be fully behind supporting and implementing something like that.