The business danger is that your plain English suggests, or is ambiguous with regards to, the meaning of something which your legal code is not ambiguous about, and the court holds that the meaning extracted from the plain English is controlling because, well, if you hadn't intended it that way you're a billion-dollar corporation with a dream team and you should have been able to phrase what you actually wanted in the contract you had drafted.
What's something which could easily be misconstrued... ooh, vesting schedules. "We grant you 10,000 options with a 4 year vesting schedule of 2,500 options per year." Lawyers will probably not be that loose with language. For one thing, this doesn't address the somewhat significant issue of when those 2,500 options accrue -- if I end my employment on day 1,000, do I end up with 5,000 options? Or 6,843 options? Or, perhaps more significantly, is the maximum number of options accrued under this 10,000? Or 20,000? (Lawyers don't get a DWIM operator any more than we do, and "with" is one treacherous little beastie now isn't it.)
Patrick, it's not unheard of for lawyers to include simple hypothetical examples to illustrate how the legal language is supposed to work.
And sometimes I've included footnotes explaining why certain provisions are phrased the way they are. I do so mainly to educate the other side, but also with later readers in mind [read: litigation counsel and judges].
That assumes that the legalese is less ambiguous than plain English. Quite often it's the other way around.
This is a common misconception held by most people. It is wrong.
One of the most important goals of a contract drafter is to avoid all ambiguity and to provide certainty.
So I think the only answer is that if you do not understand a contract, hire your own lawyer to explain it to you. There are a lot of solo practitioners or small firms that will gladly do this for you for a small fee.
On the contrary, lawyers exist who can draft "plain English" contracts without pointlessly impenetrable copypasta legalese.
We've found that at the end of the day, plain English contracts create fewer problems because both sides understand what's on the page and don't object to it later.
Granted, such lawyers are hard to find.
NOTE: In the UK, in unequal contracts (business vs individual, for example), plain English is a legal requirement[1]:
"According to the UTCCRs, a standard term must be expressed in plain and intelligible language. A term is open to challenge if it could put the consumer at a disadvantage because he or she is not clear about its meaning - even if its meaning could be worked out by a lawyer. If there is doubt as to what a term means, the meaning most favourable to the consumer will apply."
1. http://www.oft.gov.uk/about-the-oft/legal-powers/legal/unfai...
Of course if it is possible to write the entire contract in plain English only that is to be preferred. But that is not always possible. There are certain things that simply cannot be worded in plain English with sufficient precision.
No offense, but that's exactly what I was talking about too. Please see my other comment in this thread, providing a real world example of such an "unlikely" document:
> But that is not always possible. There are certain things that simply cannot be worded in plain English with sufficient precision.
That is false.
Honestly (and I'm guilty of this as much as anyone), I doubt they even read the terms. Here we have this huge thread about contract language being hard to understand, but if one doesn't take the time to read through, understand, and _remember_ all the terms of the agreement, how can one act on that information?
Complex, perhaps, but it's a complex subject.
This would make it important for ppl to read the contract, and would push lawyers to make them simpler to read, and would also make it harder for ppl to push contracts onto people who don't really understand them.
Like docco for legal contracts.
For most contracts I suspect that the overhead on a plain English version would be very small, as the lawyers' understanding of the topics is necessarily deep to formulate the contract (or they're just shitty lawyers, another topic).
Plain English versions of contracts, with their plain English meanings of clauses, should be included in any contract between two parties of vastly different bargaining power, i.e. a corporation with loads of legal resources and a non-millionaire potential employee.
Update w.r.t. comments—I understand the points you're making, but I don't think it invalidates the argument. I'm racking my brain to find the examples I've seen, but there do exist in the wild "plain English" versions of contracts that are not binding (and they specify that) but instead contain comprehensible summaries of the salient parts.