OneNDA Anatomy

OneNDA Owner’s Manual™ A Jolly Contrarian owner’s manual™ Go premium Overview — Summary — See also — Wikitext NDA Showdown OneNDA Homemade NDA What is Confidential Information? Confidential information Exclusions from confidential information Who can I share it with? Affiliates Permitted receivers Disclosure to regulators What are my obligations? Confidentiality obligation Procure compliance Return of information How long do my obligations last? Term Other important information Boilerplate Remedies Don’t go there girlfriend topics Non-solicitation Exclusivity Indemnity Sample text What is Confidential Information? Confidential Information means information that is disclosed: by a party to this Agreement (the Discloser) or on the Discloser’s behalf by its authorised representatives or its Affiliates, to the other party to this Agreement (the Receiver), its Affiliates or Permitted Receivers, and in connection with the Purpose. Affiliates means any: entity that directly or indirectly controls, is controlled by, is under common control with or is otherwise in the same group of entities as a party to this Agreement, or fund or limited partnership that is managed or advised, or whose general partner or manager is managed or advised, by the Receiver or its Affiliate or which the Receiver or its Affiliate controls. Permitted Receivers means the Receiver’s Affiliates and the Receiver’s or its Affiliates’ officers, employees, members, representatives, professional advisors, agents and subcontractors. Confidential Information does not include information that is: in the public domain not by breach of this Agreement, known by the Receiver or its Permitted Receivers at the time of disclosure, lawfully obtained by the Receiver or its Permitted Receivers from a third party other than through a breach of confidence, independently developed by the Receiver, or expressly indicated by the Discloser as not confidential. Who can I share it with? The Receiver may share the Confidential Information with its Permitted Receivers, but only if they: need to know it, and only use it, for the Purpose, and have agreed to keep it confidential and restrict its use to the same extent that the Receiver has. The Receiver is liable for its breach of this Agreement and any act or omission by a Permitted Receiver which would constitute a breach of this Agreement if it were a party to it. The Receiver may share the Confidential Information if required by law or regulation but must promptly notify the Discloser of the requirement if allowed by law or regulation. What are my obligations? The Receiver must: only use the Confidential Information for the Purpose, keep the Confidential Information secure and confidential and only disclose it as allowed by this Agreement, promptly notify the Discloser if it becomes aware of a breach of this Agreement, and within thirty days of the Discloser’s request, take reasonable steps to destroy or erase any Confidential Information it holds, except the Receiver may retain copies of Confidential Information: that are securely stored in archival or computer back-up systems, to meet legal or regulatory obligations, or in accordance with bona fide record retention policies, subject to this Agreement’s terms. How long do my obligations last? The Receiver’s duty to protect Confidential Information starts on the date Confidential Information is disclosed and lasts until the end of the Confidentiality Period. Either party may terminate this Agreement with thirty days’ prior written notice, but this will not affect the parties’ obligations in relation to Confidential Information disclosed before termination, which continue until the Confidentiality Period expires. Other important information Notices. Formal notices under this Agreement must be in writing and sent to the email addresses on the Agreement’s front page as may be updated by a party to the other in writing. Third parties. Except for the Discloser’s Affiliates, no one other than a party to this Agreement has the right to enforce any of its terms. Entire agreement. This Agreement supersedes all prior discussions and agreements and constitutes the entire agreement between the parties with respect to its subject matter and neither party has relied on any statement or representation of any person in entering into this Agreement. Amendment. Any amendments to this Agreement must be agreed in writing. Assignment. Neither party can assign this Agreement to anyone else without the other parties’ consent. Waiver. If a party fails to enforce a right under this Agreement, that is not a waiver of that right at any time. Equitable relief. The Discloser may seek injunctive relief or specific performance to enforce its rights under this Agreement. Counterparts. This Agreement may be executed in any number of counterparts and this has the same effect as if the signatures on the counterparts were on a single copy of this Agreement. Governing Law. The Governing Law (excluding any conflicts of laws principles) applies to this Agreement and related issues. Dispute Resolution. Any dispute arising in connection with this Agreement must only be resolved by the Dispute Resolution Method. Resources and Navigation Index: Click ᐅ to expand: OneNDA TOC OneNDA NDA

Overview

Here is the OneNDA in all its glory. So good that you can easily set the whole thing out on a sheet of A4.

1. What is Confidential Information?
2. Who can I share it with?
3. What are my obligations?
4. How long do my obligations last?
5. Other important information

Summary

SYNOPSIS: Some cheeky little hobbits form a fellowship and set out on a perilous adventure to confront the fearsome Smarkup, a wingèd dragon made out of boilerplate that jealously guards the huge pile of rent it has appropriated from nearby merchants.

First act goes well.

In Bozo Baggins’ burrow, there was a sign above his desk, carefully hand-painted by his uncle Dildo:

“The quotidian is a utility, not an asset.”

Boilerplate. No legal form has more of it than an NDA. To read one is to behold pure, abstracted, essence of boilerplate. In an NDA, boilerplate is all you get.

Yet generations of legal eagles, back to the time of the First Men — lo, even unto the very Children of the Forest — have, week in, week out, dug themselves into slit trenches to argue the toss over this workaday tract. It has been some kind of insane compulsion: not one of them enjoyed it; not one of them saw any point in it; they found themselves compelled to do it; drawn to it, like moths to a gaslight; lemmings to a chalky cliff.

“I must negotiate this NDA, because this is what I do. It is in my nature.”

Kudos, therefore, to the team at TLB for doing something about it.

The JC put his sclerotic old shoulder to the wheel, for whatever that was worth, and commended his friends, relations and readers to do the same; especially those who occupy places in the firmament, or up the fundament, higher than his own.

Start with the NDA, who knows where it may lead?

Later ...

The hobbity fellowship resisted the impulses to which we tragic agents of the commons resort by habit: the bickering, the special pleading, committee drafting, pursuit by ring-fixated goblins muttering baffling ancient curses: despite cannons to the left and right, onward rode the OneNDA Steering committee, and generated a nice, simple, pleasant first edition.

Not perfect — is anything? — but absolutely good enough.

It’s too early to stand on the poop-deck in front of a mission-accomplished banner, but OneNDA is getting there. We remain hopeful and optimistic. So, here some observations about what it could all mean.

Simplification beats technology — and helps it.

If you simplify, you may not need technology. There is no need for automation, document assembly, even a mail-merge gilds the lilly. Despite what the thought-leaders say, the problem facing modern legal eagles is not service delivery, but service itself.

Fix the content, and the delivery challenges fix themselves.

An ironic consequence: if you fix the content, you need less technology, and the technology tends to work better. To design for technology, design for no technology. The fewer options, subroutines, caveats and conditions precedent in your legal forms, the easier they will be to automate. You will get all kinds of second-order benefits too: fewer complaints, fewer comments and less time auditing your monstrous catalogue of hateful templates.

First, cut out the pies.

It’s not the form, or even the content, but consensus that matters

Once upon a time — until 2021 — if you devised your own NDA, however brief or elegant, you could expect it to be rejected or marked up to oblivion by the rent-seeking massive. Your voice was but a guttering candle in a gale of special pleading. Collectively we despaired of NDAs, but, taken individually, we found ourselves curiously invested in them. Hence, slit trenches.

But an outbreak of public spiritedness can change that, and that was OneNDA: interested people came from far and wide to help; everyone checked their agendas at the door. This was what Wikipedians call a “barn-raising”. The community came together for the greater good of all.

Now once a barn is raised and community feels ownership in it, it is the very fact of the barn, rather than how it was built or what it is made of, that is its value. Community assets accrue to the benefit of everyone. The structure might not be perfect but nor is there any interest in undermining it, much less setting fire to the roof: everyone has a stake in the barn. Everyone has skin in the game. The more it is used, the stronger it gets.

The more people use it, the more “good enough” becomes “perfection”.

Thus, tiresome complaints that, for example, it refers to “information that is in the public domain” and not just “information that is public” — I mean, what a zinger — fall away because no-one cares. Who would take that point? Why? Everyone knows what it means.

Community consensus, like an internet protocol, benefits everyone.

The hard lines discourage rentsmithing around the edges

And it gets better. Once a common standard exists, the hard lines around it dampen peripheral legal-eaglery around edge cases, because it isn’t worth it to argue them. Not even for a pedant.

We all know the common fripperies thrown into an NDA negotiation by way of a dominance display: indemnities; exclusivities; non-solicitation and so on. These are quickly rejected out of hand, but the courtship ritual of inserting then removing them is not just tedious: It is costly, distracting, and takes time.

By insisting on hard lines around itself, OneNDA makes itself unavailable to host that kind of pointless rutting. And it is hard to rentsmith without a “host” contract. To do it, the rentsmithor must find a new host agreement, or make one, for a plainly cosmetic purpose. It will be discouraged from doing that for fear of looking stupid.

A standardised form discourages peripheral negotiation.

Shifting the knee of the curve

The more a contract costs to negotiate, the fewer of them you can do. There’s no free option if everything is negotatiated.

Adding a free, no-negotiation option creates a range of customers you couldn't afford to onboard, but incentivises marginal cases to take the free option too

Creating a simple and standard alternative affects the “legal complexity curve”. It pulls it down and to the right, being the directions you want it going in.

Let us tell you a story, through the prism of some fancy charts. They are simulations of a real-life case.

The problem: a broken contracting process: too slow, too costly, too many errors. The “complexity distribution’ was just as you would expect: lots of low-value contracts, a few high-value ones. The errors were spread evenly throughout: most, therefore, in the low-value contracts.

The idea: reduce the negotiation workload and somehow give the team more time to focus on the higher value contracts.

The approach: standardise just the lowest value contract. It was easiest to fix, most boring and had the highest volume. Leave the rest be.

Outcome: Overnight, half the contract volume was automated.

But then:

• Volumes in the automated contract doubled overnight: as it was faster easier and error-free, the marginal cost plummeted, so the volumes spiked.
• Some “marginal” customers in adjacent categories chose to move to the free contract: they were happy to trade speed and cost for customisation. It’s a simple trade: sign this and trade now, or tie your legal team up for three weeks. Thus the “knee” of the curve deepened and shifted to the right.
• Volumes of the highest value categories went up, as the team had more bandwidth, processed the contracts more quickly and with fewer errors.
• As a result, total output of the team doubled.

The one thing that did not happen was the forced redundancy of the team. They were busier than ever, only on more challenging stuff.

See also

• Confidentiality agreement
• Perfection is the enemy of good enough
• The quotidian is a utility, not an asset