What is the best time to go?

[LostInTheCity]

Hi there,

Just wondering what is the best time go?

As myself did it twice in the past:
1) after 4+ years at the same client, understood "time to go" and give a notice, otherwise "job for life" :-/
3) extension delayed due to a projection about to "sink" nowhere, so found another gig

What about you?

Ops, realised 2 months until the end of current gig and sounds like another extension, but another 4 years gone oh dear

[GlenW]

Can anyone translate this for me please?

[Bunk]

Can anyone translate this for me please?

I think he's talking about planning a one-way trip to Switzerland

[BolshieBastard]

I once stayed at a client for over 3 years. Not a good idea. The longer you stay somewhere, the more you become 'part and parcel' of the client's organisation by default.

Others may disagree, that's up to them but the longer you are there, the more HMRC and the client's HR will see you as part of the organisation.

[SueEllen]

I once stayed at a client for over 3 years. Not a good idea. The longer you stay somewhere, the more you become 'part and parcel' of the client's organisation by default.

Others may disagree, that's up to them but the longer you are there, the more HMRC and the client's HR will see you as part of the organisation.

You need to have a contract/contract amendment stating every single project you work on. So if HMRC come sniffing round you can prove that you aren't part and parcel of the organisation.

[TheFaQQer]

Just wondering what is the best time go?

Normally about 815 for me.

[supersteamer]

For me there's another dimension beyond IR35 concerns, and that's just getting a bit of variety and not getting stuck in a rut.

I'm coming up to 24 months on my current contract and I've told them I'm not renewing. This is nothing to do with losing travel expenses (although that hurts a bit) nor nebulous concerns about IR35. Perhaps foolishly I'm leaving with nothing else lined up, but I like to take a long-ish break between contracts. Even though it's a decent gig, and I've a good chance of getting a lower rate / worse work on the next one, I don't like being sat in the same place doing the same thing with the same people for too long. I've done this before and always give fair notice and a decent handover so I don't burn bridges - this has allowed me to go back to the same client again in future once I've stretched my wings elsewhere.

[TykeMerc]

For me there's another dimension beyond IR35 concerns, and that's just getting a bit of variety and not getting stuck in a rut.

I'm coming up to 24 months on my current contract and I've told them I'm not renewing. This is nothing to do with losing travel expenses (although that hurts a bit) nor nebulous concerns about IR35. Perhaps foolishly I'm leaving with nothing else lined up, but I like to take a long-ish break between contracts. Even though it's a decent gig, and I've a good chance of getting a lower rate / worse work on the next one, I don't like being sat in the same place doing the same thing with the same people for too long. I've done this before and always give fair notice and a decent handover so I don't burn bridges - this has allowed me to go back to the same client again in future once I've stretched my wings elsewhere.

Perfectly reasonable and a classic example of one of the benefits of working as a contractor.

[d000hg]

I once stayed at a client for over 3 years. Not a good idea. The longer you stay somewhere, the more you become 'part and parcel' of the client's organisation by default.

Others may disagree, that's up to them but the longer you are there, the more HMRC and the client's HR will see you as part of the organisation.

I'm entering my 3rd year with current client (reminds me to post a boom thread!) and though I WFH and choose my own hours, I am specifically there as an overflow dev resource, not for specific tasks. We all "pull tasks off the conveyor belt" but I don't think that makes me an employee. The flexibility that they can tell me "no work this month" is the benefit to them.

[BolshieBastard]

You need to have a contract/contract amendment stating every single project you work on. So if HMRC come sniffing round you can prove that you aren't part and parcel of the organisation.

Not many people will do this.

I'm entering my 3rd year with current client (reminds me to post a boom thread!) and though I WFH and choose my own hours, I am specifically there as an overflow dev resource, not for specific tasks. We all "pull tasks off the conveyor belt" but I don't think that makes me an employee. The flexibility that they can tell me "no work this month" is the benefit to them.

Its not you, you have to convince that you're not an employee. Its HMRC and the inevitable appeal tribunal afterwards.