When Freelancers Should Turn Down Projects

It’s hard to turn down work, especially in an uncertain economy. But sometimes it’s in your best interests to say no to some projects or clients, such as when those projects might pigeonhole you into an area you don’t want to specialise in.

Photo by Hobvias Sudoneighm.

You may come across situations when you do need the work and can pull it off, but the type of project or area of specialisation isn’t really your career focus or something you would add to your CV or portfolio. Salon reminds us of the old adage: “Be careful what you’re good at.” Taking these kinds of projects can promote you in one area when you would be better off spending time on the areas that you do want to specialise in.

There are several other times when it may be best to decline a project, because it doesn’t fit your goals or your capabilities, or is just too risky. For example, if the client wants you to do work that’s part of their job responsibilities, you may end up spending valuable time and energy going through administrative hoops and politics.

For more kinds of projects you should walk away from, see the full article linked below. Do you turn down projects as a freelancer or perhaps employee? Share your thoughts with us in the comments.

When a designer should turn down a client [Salon]

Discuss

(3 Comments)
  • [–]

    Dr_Stef

    Friday, June 17, 2011 at 8:35 AM

    How about when a client comes to you because he loves your work and can’t get enough of it, but refuses to pay on time. time and time again.
    You do his work, yet he just pays whenever the frakk he wants?

  • [–]

    Rob

    Saturday, June 18, 2011 at 9:29 PM

    I think the most important reason for declining work is missing. The client has no idea what they want or they have no idea of the scope/size of the project.

  • [–]

    Steve

    Thursday, June 23, 2011 at 11:29 PM

    Stef – then they’re not a client, they’re a followup for a debt collection agency.

Join The Discussion