The following is a document by ACF member Andrew Hart. It was intended to help teams write difficulty appropriate questions for ACF Winter, but generally the content is helpful for teams writing questions for any “regular difficulty” tournament.
This guide attempts to elucidate just what editors envision by “regular difficulty.”
Before we start, I want to produce some understanding about the basic distinction between a novice or “easy” tournament (e.g. ACF Fall) and a regular tournament (eg. ACF Regionals.) At a regular tournament, there is a basic threshold of knowledge that will be required to get ten points on a bonus, or to convert a tossup, and some teams will probably not be up to that threshold. Some tossups and some easy bonus parts will be on very easy answers, and some will be on less easy answers, and that’s not a problem.
There are going to be teams playing a regular tournament who simply fall below the basic threshold of knowledge so much that they are not part of this tournament’s target audience; we surely encourage them to play if they are enthusiastic about doing so, but we cannot write regular tournaments with them in mind. When you consider how easy or difficult a tossup answer or bonus part is, it is not necessary to take into consideration these teams.
- Editors will often state a length limit for the final tournament; for example, that tossups will not exceed seven lines. Many editors allow submissions to exceed this amount, because they appreciate having more quality clues to work with.
- Tossup answers should be chosen to maximize an ideal distribution of buzzes. This means that there should be a few very knowledgeable people buzzing on the first few clues, a significant number of players buzzing on the middle clues, and that a vast majority of teams will have buzzed by the end of the question. Tossup answers should not be chosen such that only a few very knowledgeable players are buzzing on the middle clues, and most teams are waiting until the end to buzz.
- Do not pick tossup answers that will result in the tossup going dead for a significant number of rooms.
- Your clues should gently slope from difficult to the giveaway; there should be no drastic difficulty cliffs. In order to accomplish this, you should always describe something before you give its name. The larger the contingent of players you think will be buzzing on the name, the more detailed the description of the thing should be.
- Regular-difficulty tournaments often have specific conversion goals for bonuses as a whole, as well as specific difficulty standards to ensure that each bonus will be uniform.
- On the whole, editors often want the very best teams to be able to well exceed 20 points per bonus; all well-balanced and knowledgeable teams to be able to get 20 points per bonus; the median bonus conversion to be around 15; and few, if any, teams in the target audience to fall below 10 points per bonus.
- For each individual bonus, there should be a clear easy, middle, and hard part.
- The easy part should be something that any team with basic knowledge of the subject at hand will know. Note that this means that the subject you pick has to somehow lend itself to an acceptably easy part (we’re going off of the standard that 90% of teams in the target audience should convert the easy part).
- The middle part should test for beyond-basic knowledge of the subject at hand. It should also be eminently answerable to any team with more than the bare minimum of knowledge. Numerically, the median team in the target audience should be converting just over half of these parts, and the best teams should be converting this part almost all the time.
- The hard part should test for deep knowledge of the subject at hand, but it should not be impossible. It should also be important and not trivial to the subject at hand. It should also not be a “stock” answer that is very guessable based on recent packets. Numerically, the median team should be getting these parts sporadically when they have deep knowledge of a subject, while the best teams convert them regularly but not perfunctorily.
A general rule to sum this all up: When in doubt, err on the side of making your answers easier.