I would add a few things:
- Set a rush rate with your customers, and demand it for rush jobs. When you set a rush rate, also remember to define what a rush job is for you, for example:
"Rush/weekend rate: from +30% to +50% of base rate, depending on the project. Rush: projects that require the translation of more than 2,500 words, or the editing of more than 7,500 words, or the proofreading of more than 10,000 words in a day. Weekend: projects that require a substantial part of the work to be done on Saturday, Sunday or other holidays."
- The importance of QA is greater on rush jobs - the quality is already going to be lower because of the time constraints, and the chance of making errors increase when we work faster. All the more reason to devote the necessary time to QA.
- If you are translating with a CAT program, use a Translation QA tool (XBench is a good one, and is free; you can find a list of other QA tools in this post from Translation Quality Blog). A QA tool helps catching such errors as untranslated and inconsistent segments. The latter are particularly slippery: in the flux of fast translation you may accept a fuzzy match without changing the translation, but you do not notice that a small word completely changes the meaning of the sentence. A QA tools is also very useful to catch inconsistent numbers and measurements, and wrong terminology (if you have a key terms glossary).
- Both in your source segments and in your target ones, search for those words which, by themselves, are liable to completely change the meaning of a sentence. It is just too easy to forget (or add) a short word such as "not" and completely change the meaning. After all, "Do not pay attention to him" and "Do pay attention to him" look remarkably similar, when you are in a hurry (especially when you see them as suggested matches in a CAT tool).