Now presumably, the interpretation of "notice" and termination would depend on the wording of the schedule? If for example it said "provide services on project Foo" - then as long as project Foo is active, I could reasonably expect to be billing my services on a daily rate, as the master contract states. And if the client wanted to terminate - at 5 days notice as specified, for whatever reason, other than Project Foo being cancelled - then could I reasonably expect to be paid for those 5 days? On the other hand, if Project Foo is canned, then the master contract can be terminated, but I can have no expectation of payment.
Similarly, if the schedule said "Implement Bar and Baz on project Foo" - and the client decides that Bar was a duff idea all along, bins it, and reassigns Foo to a permie - then again, no matter what the termination clause, I can have no expectation of getting paid.
That's the opinion that I've formed in my extensive contracting career of 4 WEEKS
(incorporate my co. on June 10) so might be barking entirely up the wrong fish. But something I've been thinking about is the wording of such schedules - the more open ended they are, the more inside IR35 they become (aww, come in on Monday, we'll find you SOMETHING to do). On the other hand, who wants to sign a contract that could have you (in theory) working a two day week... or worse?

Now there is something I didn't think I would see as a contractor. Definately not complaining though. 
Leave a comment: