Am wondering how most IT contractors here deal with clients who like to think that they are hiring temporary employee devs who they can get to jump onto different projects as they see fit.
So far, it's been my opinion that from a DAC point of view, for a fixed-length of time contract it's best if I can at least agree up front the project that I will be assigned so that this can go into the assignment schedule, rather than have a more generic "Supplier of development services." or something similar, which seems to me to demonstrate DAC. Do you think it really does make a difference?
That said, even with that in place it's all too easy for someone to pop by your desk when you're there to say that they're in a bind as someone is off sick and could you assist with a particular issue that afternoon / next 2 days. "Could" is not often really a question
What is the best approach to this? Do you:
- Politely point out that you're contracted to just work on project X and you can't assist
- Politely point out that you're not meant to but after some hand-wringing, do the work anyway
- Help out without raising an issue
If it's not the first, doesn't this display a distinct lack of DAC? Have you managed the first and still maintained a good relationship with the client and not been seen as a problematic worker, given that the other contractors who don't give two stuffs about IR35 will likely just do it without thinking.
Or, am I just simply overthinking things? Can you agree to more generic dev contracts that would still stand good from an IR35 view? I imagine some clients could get testy even about having a specific assignment schedule, and would you treat this as a dealbreaker?
So far, it's been my opinion that from a DAC point of view, for a fixed-length of time contract it's best if I can at least agree up front the project that I will be assigned so that this can go into the assignment schedule, rather than have a more generic "Supplier of development services." or something similar, which seems to me to demonstrate DAC. Do you think it really does make a difference?
That said, even with that in place it's all too easy for someone to pop by your desk when you're there to say that they're in a bind as someone is off sick and could you assist with a particular issue that afternoon / next 2 days. "Could" is not often really a question
What is the best approach to this? Do you:
- Politely point out that you're contracted to just work on project X and you can't assist
- Politely point out that you're not meant to but after some hand-wringing, do the work anyway
- Help out without raising an issue
If it's not the first, doesn't this display a distinct lack of DAC? Have you managed the first and still maintained a good relationship with the client and not been seen as a problematic worker, given that the other contractors who don't give two stuffs about IR35 will likely just do it without thinking.
Or, am I just simply overthinking things? Can you agree to more generic dev contracts that would still stand good from an IR35 view? I imagine some clients could get testy even about having a specific assignment schedule, and would you treat this as a dealbreaker?
Comment