First of all, thanks for doing this. I don't think what goes into running a good tournament is much of a mystery to a lot of these guys like doe, magic, or Waidman, etc etc etc. The only thing our club lacks is exactly what u are developing, a good set of SOPs. If u talk to some of these guys, pool the info, and come up with a detailed set of guidelines for all Tds we will see much improvement at or club's tourneys. I was discussing this during one of our last cluster f&$%s happening at tourney central. Universal guidelines are just as important for competitors as they are for the Tds. Once our local players see consistency at our tourneys they will do what people do, and start going with the flow. Presently, we have large groups of people talking over each other and blasting Tds with random questions while they are trying to sign people up or put cards together. Matt Augustine (sp?), raised perhaps the most simple, yet constructive idea to aid In solving this problem when I brought this up to him. Every tourney (NO MATTER WHAT) must have a large board displaying all the general tourney info. This includes but is not limited to: tee time, # of rounds, entry fee, divisions, lunch situation, ctp info, ace pool info, side game info, payout predictions, ryder cup update perhaps, etc, etc. So when your trying to spell out Misuraca on a card and someone starts yelling at u regarding some of this very general information u can just remain looking down and point to the glorious board. People waiting in line will know exactly what they want to sign up for as soon as they get to the
table. I have just one more possible guideline. Whenever possible the sign up table should always be a u shape as to prevent a cluster f%#~ behind the people trying to work. This is usually the case, but when it's ignored it causes big problems. The Tds/volunteers who arrive first should very strategically set up tournament central so that it allows for an organized flow during signups and prize outs. I'm sure there is someone in our club with an operations mngt background that can help refine this process lol.
Figured I'd post it here cause this is a good discussion.
There is no wrong way to eat a Reeces