[another-dave]

What I always wonder is why we don't have more standardisation around end-user contracts. E.g. something equivalent to YC's SAFE (https://www.ycombinator.com/documents) but for employment agreements, leaseholds etc.

We understand what we can & can't do with software licences and creative commons because we know "this is MIT" or "that is CC, no commercial, with attribution" and we don't need to delve further.

If we had similar for employment terms - ACME Ltd want to hire me for £x at Y location using the standard "UK employee contract" - it feels like you could sidestep a lot of the need for AI parsing individual documents that are all subtly different.

Lawyers are _already_ using templates, but they're all using bespoke templates and it means that you've got ambiguity by virtue of the fact that the sentence in my contract has never been tested in court.

[NoboruWataya]

Interestingly this already does happen a lot, but usually in more complex and high-value B2B contexts. ISDA Master Agreements, (G)MRAs, GMSLAs, LMA documentation, EFET General Agreements, Incoterms, etc. The fact that it is more common in B2B contexts than B2C is IMO a reflection of the power imbalance in the latter as it benefits a large corporation to have consumers contract on its terms. Where there is standardisation in consumer contracts it is usually driven by law or regulation as the market isn't otherwise incentivised do it. For example some countries do have template tenancy agreements published by the government or a regulatory body.