Have an interesting situation.
Just coming up on the 2 year mark on time with a client. Have had several extensions over that time and each one has involved specifying the project work to be done in that contract.
Now the client doesn't want to do this anymore and wants the contract to be 'generic' so that they can basically tell me what do to during the contract and change the project work as they see fit. This is despite the fact that the basis for entering into the contract is to engage on a specific project.
Now whilst that project can change, be cancelled, suspended, etc, it should be for the parties to agree on a change to the scope of work when that happens but it seems to make sense for the contract to be 'as specific' as possible for the benefit of all concerned. It also ensures from contract to contract that the work is clearly agreed upfront.
Problem is, the client is basically being lazy and doesn't want to be tied down like that. They don't care that the contractor could be caught inside IR35, and the agency is simply rolling with it, even though they know the downside for the contractor.
So, how to get the contract generic AND still keep it inside IR35 as to the work to be performed ? Anyone got any suggestions as to how to ensure the contract stays project-specific rather than 'BAU' and ensure my side is covered IR35 wise without ticking off the client who clearly wants things their own way or the highway ?
If an IR35 audit occurred, the client would definitely not say anything other than the work was BAU, which I believe it isn't. Its project work from my perspective as a supplier.
All suggestions welcomed.
Just coming up on the 2 year mark on time with a client. Have had several extensions over that time and each one has involved specifying the project work to be done in that contract.
Now the client doesn't want to do this anymore and wants the contract to be 'generic' so that they can basically tell me what do to during the contract and change the project work as they see fit. This is despite the fact that the basis for entering into the contract is to engage on a specific project.
Now whilst that project can change, be cancelled, suspended, etc, it should be for the parties to agree on a change to the scope of work when that happens but it seems to make sense for the contract to be 'as specific' as possible for the benefit of all concerned. It also ensures from contract to contract that the work is clearly agreed upfront.
Problem is, the client is basically being lazy and doesn't want to be tied down like that. They don't care that the contractor could be caught inside IR35, and the agency is simply rolling with it, even though they know the downside for the contractor.
So, how to get the contract generic AND still keep it inside IR35 as to the work to be performed ? Anyone got any suggestions as to how to ensure the contract stays project-specific rather than 'BAU' and ensure my side is covered IR35 wise without ticking off the client who clearly wants things their own way or the highway ?
If an IR35 audit occurred, the client would definitely not say anything other than the work was BAU, which I believe it isn't. Its project work from my perspective as a supplier.
All suggestions welcomed.


Comment