Do/Should you always accept extensions?!

[SimonMac]

In my line of work I am usually there for a specific purpose, after the project initialisation and my goal is to get the service live, after that its BAU handled by the support teams and all Continual Service Improvement is handled in the processes that I create so I usually think its a good time to leave rather than take an extension and get stuck in the loop of CSI.

Now everyone on hear bleats on about how good id looks on your CV to take continual extensions, but my theory is as long as I leave the client on good terms, the offer of an extension is just as good for my reputation.

What is the consensus of opinion, do you like to stay in a comfort zone which you have fostered, or do you like to break into something new?

[pmeswani]

In my line of work I am usually there for a specific purpose, after the project initialisation and my goal is to get the service live, after that its BAU handled by the support teams and all Continual Service Improvement is handled in the processes that I create so I usually think its a good time to leave rather than take an extension and get stuck in the loop of CSI.

Now everyone on hear bleats on about how good id looks on your CV to take continual extensions, but my theory is as long as I leave the client on good terms, the offer of an extension is just as good for my reputation.

What is the consensus of opinion, do you like to stay in a comfort zone which you have fostered, or do you like to break into something new?

I work on the assumption that if I don't take the extension, then you are closing the door, irrespective on whether you leave on good or bad terms. If you enjoy the work, and have nothing better to go to, take it, unless you have a healthy warchest. If I am offered an extension, and have nothing better offered, I would take it, unless the contract was making me ill.

[cojak]

The projects I work on generally last a couple of years so I'm happy to accept extensions until the project ends. After that I don't accept any extensions.

And in my last contract I left when the project got canned (a month after accepting a 3rd extension).

It's all about the project.

[bless 'em all]

I tend to accept extensions, and so far I have been offered them for every contract I've had. If you were really intending to leave then I'd suggest letting the hiring manager know you WON'T be accepting an extension and allow them the time to find your replacement.

[Sands of Time]

If I enjoy the work, people, location, rate, blue chip client - I'll take the extension, if not, I might as well go elsewhere.

I guess it depends if you have ten contracts all lasting only 3 months or not?



Tone

[BolshieBastard]

The projects I tend to work on can last for upto a year but the client always seems to offer contracts in 3 month tranches! So, if you want to see the project out, you have to take the extensions.

What does hack me off though is at my last two clients, the first ran out of budget so had to let all contract resource go at the end of the contract while the second, has decided the 'up to 2 years work' mentioned at interview has now been re located so cannot offer an extension. First thing agents do when they see short contracts on the cv is say 'why weren't you kept on?'

I dont see why I should be disadvantaged simply because clients cant work out their budgets or decide to re allocate the work somewhere else.

[BrilloPad]

I never get offered an extension.

Seriously, it all depends what is on offer elsewhere. I always take a look round every time contract comes up for renewal.

But accepting an extension quite important on a first contract. Renewal is often seen as important guide to how good you are.

[Old Greg]

I've always taken extensions in the past. Have had one extension at my main current contract but I've told them 2 months out that I'll be leaving. Too much travelling and I have an old client who is happy to wait until July for me.

[Sockpuppet]

In my line of work I am usually there for a specific purpose, after the project initialisation and my goal is to get the service live, after that its BAU handled by the support teams and all Continual Service Improvement is handled in the processes that I create so I usually think its a good time to leave rather than take an extension and get stuck in the loop of CSI.

Now everyone on hear bleats on about how good id looks on your CV to take continual extensions, but my theory is as long as I leave the client on good terms, the offer of an extension is just as good for my reputation.

What is the consensus of opinion, do you like to stay in a comfort zone which you have fostered, or do you like to break into something new?

Depends on the project. From an IR35 point of view being a normal resource on multiple projects is bad.

I tend to do one project, then if they want me for another leave for a few months and come back when that project is ready to rock.

[bobspud]

Length of your stints can vary. So for instance I know a couple of chaps that do three or four week work packages that look at a small aspect then end in a report. So to them it's no problem. However if you are a windows engineer, then not sticking around much longer than a few months doesn't look so good.

My stints for the last few years were

18 months
1 year
2 and a half years.

All 6 month extensions.

All in all. Try a balance your cv so you don't look like a dumbass that gets canned a lot.