Target browsers and operating systems—Do you care about 4.0 browsers? Only modern browsers? Handheld devices? Do you care whether your site works on a PC, or are your users on Macs? Be sure to list these receiving devices explicitly, accurately, and carefully. Use this list to test browser performance as you go. (Don't wait until the project is finished to test it in the targeted browsers and devices. Fixing problems that late in the game is far more costly than spotting them earlier in the process.)

HTML and CSS—Do you have a particular HTML and Cascading Style Sheet specification in mind? (Hint: The answer is "yes." I go over this topic and how it can save you money in Chapter 7, "Save Time and Money with Web Standards.")

Scripting—Be explicit about how your professionals should use JavaScript. I personally believe that every function must work when JavaScript is turned off. This keeps a broader range of users happy, including those who lack access to JavaScript-capable browsers.

Servers and databases—Make sure that you are explicit about the server on which the site will run, and the middleware and database applications that are supported.

Bandwidth requirements—Take the time to determine whether your audience is primarily using low- or high-speed Internet connections. If most are on some kind of broadband connection such as DSL or cable, you will not have to worry about speed optimization as much as you would if most users were on dial-up connections. On intranets, everyone might be on the same high-speed network. With public sites, as of this writing, at least half of your visitors are likely to be at dial-up speeds of 56K and less. Web Site Optimization's free online bandwidth report keeps track of public connection speeds at work and at home (http://www.websiteoptimization.com/bw/).