3 ms·
I won't copy paste the terms, but they say any employee can do what they like, as long as it doesn't utilise the resources of the business (which are defined as
by telebone_man 9y ago
I won't copy paste the terms, but they say any employee can do what they like, as long as it doesn't utilise the resources of the business (which are defined as equipment, offices, money, time etc.).
And if it does, then the business operates a 'first-refusal' policy. In cases where the business has decided to utilise the side-project, this is normally combined with financial compensation in some form (a salary raise, a bonus, something like that).
FYI, I'm in the UK (midlands). I think this is quite a liberal approach compared to most. But it seems to motivate staff to think outside the box in the interests of the business.
- Swinx43 9y agoThat is fantastic to hear! I am also in the UK and every single contract I have signed was accompanied with clauses basically stating that the company owns anything I create while I am employed by them. This includes anything outside of work as well. I believe this is the standard terms for UK contracts. I was lucky in getting my current employer to add an addendum to my contract giving me certain exclusions to this clause, it was however a process to get it past their legal department.
- rosbrith 9y agoMine (also UK) is similar to what you describe, minus your addendum. It makes reference to agreeing that inventions (new software, I imagine) developed during the course of my employment must be made available to the company for its use. I've never known the company to call anyone out on this.
- Swinx43 9y agoYes that is true, I have never known anyone that was called out on this. However I am sure if an invention becomes popular and really valuable that some organisations, espcially big ones, would not hesitate to give it a try.
- nmstoker 9y agoMy UK contact has no IP terms but the employer added something into the employee handbook claiming to own everything which was a problem for me as I do a number of non-work projects outside work. I had a discussion and got a clarification on the scope and we agreed that it covered specified things with work applicability, so I'm satisfied now (will start work on the best selling novel and string of number one hits right away!). It was important it wasn't just based on a vague ill-defined idea of "outside work" because typically a portion of what is clearly work related IP I generate doesn't happen in a formal work situation, yet I understand it as work (and am fine with that) whilst equally there is plenty of non-work IP that is just as clearly in no way work (as it doesn't relate to our line of business).