• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Collapse

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "Turning down work/extensions"

Collapse

  • AnthonyQuinn
    replied
    Originally posted by psychocandy View Post
    Since we're on the subject, my reasons for contracting are:-

    1. More money for same job, same job security ultimately.
    2. No more worrying about internal politics/reviews and tulip.

    But not :-

    1. More time off - I actually take less time off.
    my reasons in a nutshell.

    Leave a comment:


  • Old Hack
    replied
    Originally posted by rootsnall View Post
    I'm not sure anybody mentioned it earlier in the thread but one of my motivations for turning down extensions was to limit my time with any one client for IR35 reasons. Keep each contract as a small target for Hector and they won't bother. Seemed to work for me.

    I also think you are getting stale after a year or so and gradually getting drawn into politics and petty squabbles no matter how hard you try to avoid it.
    I'd always be as polite as possible when turning it down and invent some personal/family reason if needed, you never know down the line.
    Pretty much nailed it for me. Stayed with one contract for 3 years and by the end, my standards had slipped, I couldn't really give a tulip about the role, or my work and decided to leave to challenge myself again.

    Best thing I ever did. Now I keep to a year max, although I have just signed a 6 month gig and then it was indicated it's a 6 year project...

    Leave a comment:


  • rootsnall
    replied
    I'm not sure anybody mentioned it earlier in the thread but one of my motivations for turning down extensions was to limit my time with any one client for IR35 reasons. Keep each contract as a small target for Hector and they won't bother. Seemed to work for me.

    I also think you are getting stale after a year or so and gradually getting drawn into politics and petty squabbles no matter how hard you try to avoid it.

    I'd always be as polite as possible when turning it down and invent some personal/family reason if needed, you never know down the line.

    Leave a comment:


  • yasockie
    replied
    subcontract, simple really

    Leave a comment:


  • BolshieBastard
    replied
    Originally posted by d000hg View Post
    I find it really hard to do! I had one client lined up at the start of this year leaving me plenty of plan B time, but an old customer asked me for some time and I couldn't turn down the money. Then I renegotiated with them for even less hours next year but then the first client wants me to carry on and as it's a 1-man dev-team I'd be leaving them somewhat in the lurch.

    It's OK, I'm not after advice - but do you find it easy to turn down work? I always feel I should take any opportunity to maximise the warchest since I've only been doing this 5 years...
    Depends on how the client is IMO! I kept taking extensions for 3.5 years with one client yet 2 out of the last 3, I turned down because the roles werent what Id been lead to believe and had no chance to develop into something better.

    Leave a comment:


  • bless 'em all
    replied
    Originally posted by bobspud View Post
    You have to think about what protects your skills in the long term.

    I got a new job this morning after having an interview last week. So two weeks on the bench for being a premodonna was not too bad really.
    I'm going through the same thing with my current client. No work to do most of the time and when something does come along it's some tulip task that no one else can be bothered with. They've been told they have until tomorrow PM to sort it out or I'm off (there's a new contract from an old client in my Inbox just waiting for me to accept).

    I am not prepared to sit around doing sod-all whilst my skill-set gets diluted by time away from proper work.

    Leave a comment:


  • cojak
    replied
    Originally posted by bobspud View Post
    Turned one down last year. For a couple of reasons:
    1) the client wasn't taking the advice they paid for, and that will result in bad publicity when it all goes wrong.
    2) The client has the tax compliance issues that all departments have.
    3) spent more time arguing than applying my knowledge

    You have to think about what protects your skills in the long term.

    I got a new job this morning after having an interview last week. So two weeks on the bench for being a premodonna was not too bad really.

    Leave a comment:


  • bobspud
    replied
    Turned one down last year. For a couple of reasons:
    1) the client wasn't taking the advice they paid for, and that will result in bad publicity when it all goes wrong.
    2) The client has the tax compliance issues that all departments have.
    3) spent more time arguing than applying my knowledge

    You have to think about what protects your skills in the long term.

    I got a new job this morning after having an interview last week. So two weeks on the bench for being a premodonna was not too bad really.

    Leave a comment:


  • Project Monkey
    replied
    I became a contractor for the flexibility and variety of work, but I have to admit turning down an extension with nothing to go to is a scary prospect. A bird in the hand.... !

    Only done it once because I got fed up with the weekly commute, but even then it was difficult.

    Leave a comment:


  • jmo21
    replied
    Originally posted by psychocandy View Post
    Since we're on the subject, my reasons for contracting are:-

    1. More money for same job, same job security ultimately.
    2. No more worrying about internal politics/reviews and tulip.
    These are the main reasons for me too. I get to stay programming, but earn more.

    Where I am based there aren't many high paying permie programming job options.

    Another factor for a programmer is it avoids being stuck on maintenance of the same crap legacy systems year in, year out. I know some people say we contractors get lumped with all the rubbish jobs, but that has not been my experience so far. I pick and choose the roles I take.

    And even if you did, you are more used to just handing in notice if a contract was not what you were expecting than your typical entrenched permie might be.

    Leave a comment:


  • psychocandy
    replied
    Since we're on the subject, my reasons for contracting are:-

    1. More money for same job, same job security ultimately.
    2. No more worrying about internal politics/reviews and tulip.

    But not :-

    1. More time off - I actually take less time off.

    Leave a comment:


  • curtis
    replied
    I find this one of the hardest things and have been in a situation many times where I hope I don't get offered an extension so I don't have to make the decision.

    My main objectives for contracting are 'more time off', 'more variety' and the main one' not feeling stuck anywhere for too long' but there is an underlying pressure to keep myself in work for fear of being out of it too long, which has made me take extensions in the past which given the choice I probably would not have and moved on or had some time off.

    I'm hoping this mindset will change when I get my finances all setup the way i want.

    Leave a comment:


  • jmo21
    replied
    So far, I've been pretty lucky and have not wanted to turn down any extensions I've been offered.

    I read some of the horror stories on here and I'm glad I have been at a gig like any of those yet. Long may that continue too.

    Leave a comment:


  • supersteamer
    replied
    I find it a difficult call.

    My main two objectives for contracting are (1) enjoy more time off than in normal employment and (2) have more variety of work/locations/industries.

    So if I get offered an extension I'm concerned that I'm (1) turning down an easy source of money, (2) casting myself at the mercy of a terrible market for finding future income, and (3) damaging my prospects of going back to the original client in future.

    But sometimes, in the balance, to achieve my objectives it's just necessary to turn them down. My rule of thumb is when travel expenses can no longer be claimed, it's a hint that it's time to go.

    Leave a comment:


  • eek
    replied
    Originally posted by JoeyD View Post
    Are you the poster who used to be called 'Gentile' may I ask ?
    She isn't but I'm sure she'll appreciate the comparison (not).

    Leave a comment:

Working...
X