Haha. Okay that's seriously ridiculous. I'd have a field day berating any org that tried to push that on me.
> ... and any created during employment regardless of whether or not it was written for the company or on company time.
I'd disagree with you on the non-company time. Depending on the nature of the work whether it happens on the clock or not isn't clear cut. Hence the default of the company owning everything while you're doing work for them as an employee.
The best defense for this as an employee is to get a written exemption for anything non-company related that you're working on, or a generic exemption as a matter of company policy for things like off-clock FOSS contributions.
Just about every large scale FOSS project requires contributors to attest to IP ownership and assign copyright of contributions. Most also explicitly ask if your employer has granted you permission to offer you contribution. There are many stories of projects that don't do this trying to track down individuals years after the fact to facilitate relicensing.
Now in a more specific work for hire (i.e. contracting / consulting) situation, it does need to be tightened to reflect the actual work at hand. Otherwise you can't work on anything else
> I'm surprised they didn't include any future IP as well.
Be even funnier if they did and also required to actually create some too. Instead of a golden parachute it'd be lead anchor.