It's not strictly PHP-related, but I think just about any developer out there (freelance or otherwise) can sympathize with this new list from Andy Budd's weblog today.

One of the great things about being a freelance web designer is the ability to turn down projects. I've come across a few projects recently that sounded interesting but made me feel nervous. It wasn't any one specific thing; rather a series of small little things that set my internal alarm bells ringing. As such I've written up a list of bad project warning signs. Individually none of these signs should be deal breakers. However put a few of them together and it may be worth thinking twice about taking on that project.

Some of my personal favorites: "The client says they want the site to be as cheap as possible, or they have an extremely low budget.", "The client expects much more from the project than their budget will allow.", and "There is no central point of contact." (not that I've experienced any of these first-hand or anything....). Be sure to check out the comments for other suggestions.