Just saw results posted for 201201246492.
Submitted as Regular, automatically switched to Dual.
No complaints!
However it was G/30;+30 and I thought I saw a rule that said over 15 seconds of delay or increment dis-allows quick rating.
That was the 2011 rule.
In 2012, the total time per player (MM, in minutes) and the increment or delay time (SS, in seconds) are used:
MM must be >= 5 for the event to be USCF ratable.
if MM + SS < 30, the event is quick-rated only.
if MM + SS is between 30 and 65, the event is dual rated.
if MM + SS > 65, the event is regular-rated only.
Events that have no final sudden death time control are regular-rated only.
This has been discussed quite a bit on the Forums since the rule change was passed by the Delegates in August. In addition, current certified TDs and affiliates were notified of this change in September via email.
Now we just need to get it changed in the FAQ at TD/A. Maybe someone can simply zap the following text, (from the FAQ) until we devise proper replacement language that fits into the master plan.
What time control do I report?
Let’s handle the easy case first: If all games in a section are played at the same time control, that’s what you should report. (Remember to report primary Sudden Death time controls like this: Game/10, Game/30, Game/90, Game/120, etc.)
If there are multiple schedules for a round, or if not all rounds use the same time control, in general the slowest time control used for any game in any round determines whether the event can be regular rated only, dual-rated, or quick rated only.
Adjustments to the initial time period because of an increment or delay mode clock do not change the primary time control for ratings purposes. Thus, if the time control is Game/30 with 5 seconds delay and players are permitted to set clocks supporting delay mode at 25 minutes (per rule 5F in the USCF rulebook), this is still a Game/30 time control for ratings purposes. (See the final paragraph of this entry for further complications.)
To determine whether the event is quick, dual or regular rated:
First, look at the increment or delay used. If it is 16 or more seconds, then the event must be regular-rated only.
If the increment or delay is less than 16 seconds, then look at the total time per player.
If the total time per player is between 5 and 29 minutes, then it must be quick-rated.
If all games have a total time per player of between 30 and 60 minutes, then the event must be dual-rated. This is not an option that the organizer or TD can choose, it is a USCF regulation. Contrary to what it may say on older rating report forms (which may also have the wrong fees on them), there is no additional fee to dual rate events, even if submitting them on paper.
If the total time per player is greater than 60 minutes, then the section must be regular-rated only.
Here’s the complicated part: If some rounds are faster than 30 minutes per player and other rounds are 30 minutes or more per player, then you must break the event into two sections for rating purposes. The rounds played at time controls faster than 30 minutes would be quick-rated only, the others would be dual-rated or regular-rated, depending upon the slowest time control for any of those rounds.
See the sections in the FAQ for TD/A entitled:
How do I enter time controls?
and
How do I report time controls for events that began (or are being rated) in 2012?
The old section has been renamed to refer to events from 2011, since most of that information is still applicable. However, as of earlier this month all time controls, even for 2011 events, must include increment or delay information.
The FAQ should probably be split into two separate files, one for the procedural issues dealing with access to TD/A and the other for event-related issues.
Nice work, Mike. Good catch to leave in the info for events that started in 2011—probably a few of them still out there…
If past years are any guide, we will continue to get 2011 events for several months. We still get even older events every now and then. (However, the office will have to override the date warnings on events older than 9 months. That’s done in part to catch events entered with the wrong year, eg, 2011 instead of 2012.)
The FAQ has just been split into two parts, but further refinements are probably needed.