Monday, July 18, 2011

Clause Elements

Each time I review a set of clauses for the Clause of the Day, I am stuck by their common features, even though the source material is drawn from a wide range of different agreement types, drafted by different firms, for different clients.

The clauses all share common characteristics. They frequently use the same terms of art or common phrases.

Deeper analysis shows that they are composed of common sub-elements. For example, the Non-Disclosure Obligation in confidentiality agreements contains four components: (a) confidentiality, (b) non-use; (c) non-disclosure; and (d) protection of information. The Conduct of the Business clause in acquisition agreements typically contains four elements requiring the seller to: (a) conduct business in the ordinary course consistent with past practice; (b) preserve its business organization (or assets); (c) keep its directors and employees; and (d) keep its customer and supplier relationships and preserve the goodwill of the business.

Clauses, just like the agreement as a whole, are a checklist of elements, detailing required and optional clause terms.

Of course, the existence of common features is really not surprising. The clauses are all seeking similar objectives. The language has evolved over time, much like common law, into a well used reference. But while, commonality exists, it has not been codified.

By contrast, in the field of architecture, design and build standards are codified. MasterSpec, by ARCOM, provides comprehensive documentation that “automates specification production tasks and simplifies creating custom office masters for specific regions, clients, and products.” (MasterSpec). My architecture friends tell me that standards are required because the lawyers would otherwise sue them.

Analysis of clause elements highlights the value of precedent and the related contentious issue of garbage-in; quality-out. Words are important. Precedent is important. What is included (or omitted) in the clause is just as important as how the language is expressed.

Tuesday, July 5, 2011

Organizing the Covenants Article in Legal Agreements

A covenant is an agreement to perform, or to refrain from performing, a specified action. It exercises a continuing interest over an asset, property interest, or performance obligation. For example, a covenant on real estate "running with the land" imposes restrictions upon the use of property regardless of the owner. Covenants may be applied to a property license (e.g. a software license,) or a license to use money (a loan), or a license to use real property (a lease) to limit the use of the asset. A covenant can also be applied to a performance obligation to restrict the actions of a party bound by the covenant, such as a non-compete provision.

The covenants article in legal agreements is, however, frequently unorganized. Related provisions may not be located near each other making it difficult to determine if the article contains all required clauses and does not contain duplicate or overlapping provisions.

Where a high-level organizing theme is found, it is sometimes an arbitrary classification that cannot neatly group all the terms. For example, where a pre-closing/post-closing classification is used, where should the confidentiality covenant appear? An analysis of legal agreements shows that the Covenants article is generally grouped into 5 different, high-level organizing themes:

  • Single Covenants Section
  • Covenants and Additional Agreements
  • Covenants of the Seller and the Buyer
  • Affirmative and Negative Covenants
  • Pre-Closing and Post-Closing Covenants
An alternative classification considers the purpose or goals of the covenants. While some goals may overlap and serve multiple purposes, the principal objectives are:

  • Perform actions to consummate the agreement
  • Keep the parties informed
  • Preserve and protect property
  • Comply with laws, regulations and obligations
  • Limit or control actions
Applying this scheme, ContractStandards proposes the following organizing theme that can be applied to all agreements.

1. Perform Actions (Consents, Approvals and Filings)

1.1. Best Efforts
1.2. Cooperation
1.3. Consents and Approvals
1.4. Stockholder Meeting (Approval)
1.5. Third Party Consents
1.6. Regulatory Filings
1.7. Governmental Approval
1.8. Securities-Related
1.9. Listing Approvals
1.10. Exclusive Rights
1.11. Fees and Expenses
1.12. Assistance

2. Information and Notification

2.1. Access to Information
2.2. General Information Obligation
2.3. Financial Statements
2.4. Information Regarding Collateral
2.5. Title Information
2.6. Casualty and Condemnation
2.7. Notice of Developments
2.8. Notice of Default
2.9. Notice of Litigation
2.10. ERISA Notices
2.11. Environmental Notices
2.12. Regulatory Notices
2.13. Officer’s Certificates
2.14. Inspection

3. Business and Operations

3.1. Corporate Existence
3.2. Charter Documents; Amendment of Material Documents
3.3. Nature of the Business; Lines of Business
3.4. Conduct of the Business (Ordinary Course)
3.5. Goodwill
3.6. Company Name; Company Headquarters
3.7. Maintain Books and Records
3.8. Accounting Changes
3.9. Fiscal Year; Fiscal Quarters
3.10. Limitations on Changes; Fundamental Changes
3.11. Ownership of Subsidiaries
3.12. Transactions with Affiliates

4. Equity; Ownership Interests

4.1. Capital Structure
4.2. Transfer of Equity Interests
4.3. Dividends; Distributions
4.4. Issuance of Securities
4.5. Stock Option Plans
4.6. Capital Expenditures
4.7. Restricted Payments

5. Assets

5.1. Acquisition of Property
5.2. Disposition of Property
5.3. Limitations on Leases
5.4. Limitations on Sale Leasebacks
5.5. Maintain Properties
5.6. Maintain Insurance
5.7. Intellectual Property

6. Liabilities

6.1. Pay Obligations
(a) Payment of Taxes
(b) Payment of Debt
6.2. Limitations on Indebtedness
(a) Leverage Ratio
(b) Fixed Charge Coverage Ratio
(c) Liquidity
6.3. Subordinated Debt
6.4. Limitations on Liens
6.5. Limitations on Loans, Advances and Investments
6.6. Limitations on Guaranty Obligations
6.7. Limitations on Contingent Obligations
6.8. Limitation on Negative Pledges
6.9. Limitations on Swap Agreements / Hedging
6.10. Restrictive Agreements / Burdensome Agreements
6.11. Protection of Lender’s Priority Status
6.12. Additional Collateral
6.13. Additional Guarantors
6.14. Pledged Assets
6.15. Appraisals

7. Personnel & Employment

7.1. Compensation
7.2. Employee Benefit Plans
7.3. Directors and Officer’s Insurance
7.4. Resignation of Directors
7.5. Severance Arrangements
7.6. Employee Matters; Hiring Employees
7.7. Employee Inventions Agreements
7.8. Employee Confidentiality Agreements

8. Compliance with Laws and Obligations

8.1. Comply with Laws and Regulations
(a) Environmental Compliance
(b) Bulk Sales Law
(c) Blue Sky Laws
8.2. Comply with Agreements and Obligations
8.3. Performance of Obligations

9. Use of the Transferred or Licensed Asset

9.1. Use of Proceeds
9.2. Restrictions on Use of Licensed Property

10. Restrictive Covenants

10.1. Confidentiality
10.2. Non-Competition
10.3. Non-Solicitation of Business
10.4. Non-Solicitation of Employees
10.5. Non-Disparagement
10.6. Enforcement
10.7. Acknowledgement
10.8. Publicity and Announcements

11. Further Assurances

11.1. Further Assurances
11.2. Disclosure Supplements

Sunday, June 26, 2011

Garbage-in, Quality-out

The common think expression “garbage-in, garbage-out” is often thrown out without any vigorous thought. Proponents believe it just has to be true.

First, I have to agree with Charles Babbage who famously said: "On two occasions, I have been asked [by members of Parliament], 'Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?' I am not able to rightly apprehend the kind of confusion of ideas that could provoke such a question."

Second, if we do try to make some sense of the concept, the expression can hold true only if all the source materials are completely rubbish. I believe there is much to be learned from all sources of information. If there are any gems in the collection, then there is the possibility that “good” material can be identified. Indeed, we are all exposed to an enormous amount of data. How well we process this information depends on the sophistication of our filters. And, machines can also develop filters. IBM’s Watson, the Jeopardy playing computer, deduced mostly correct answers from unwashed Internet resources—and it trounced its human competitors.

Third, while the expression has been applied to legal agreements, such as those filed on EDGAR, for my part, I do not think of any of them as garbage. They are precedents. They are expressions of real transactions.

Fourth, common thinkers tend to fixate on language, sometimes debating the difference between ‘will’, ‘shall’ and ‘must’. While this is important, there are many other dimensions to legal agreements, including—and most importantly—the application of legal terms to business transactions. In fact, it is not uncommon for those focusing on the words to miss some key clause or accidentally duplicate clause language. Without a broader view—a checklist—we cannot see the forest for the trees.”

Fifth, and most importantly, we can now see the power of aggregation and filters in practice. Contract analysis reviews a set of agreements and determines how the document is organized, what clauses it contains, and the range of standard and non-standard language. The first task of contract analysis is to aggregate all the source documents into one common outline, creating the agreement checklist. Next, the analysis finds all the matching clause elements, and for each branch of the outline, it constructs a clause library. Finally, algorithms examine all the clauses and identify the core (non-negotiated or deal neutral) language for each provision, together with the full range of deal-specific or alternative terms.

When creating a new model form, the process will sometimes start by identifying the most conforming document in the set: the one containing the most common clause elements and the most standard language. This is done for reasons of expediency. If we start with single conforming document, then we can spend less time normalizing the clause language, and particularly the definitions. (See The Fastest Way to Create a Form).

However, situations arise where we do not find a good (or conforming) document containing all the standard elements of a transaction. These situations are quite apparent from the software analysis. The software shows the source agreements are highly divergent in structure and content. If there are no good examples, then we can assume that we face a situation of sub-optimal source documents. In this case we can use contract analysis to identify the most common deal elements and for each provision find the most conforming clause. The remarkable result is that while no one document represents best practice, the aggregate of all documents does. Or, to end with another bumper-sticker expression: we are smarter than me.”

In conclusion, part of reason for a shift from wordsmithing to transactional analysis is an expanding world view. When our world is limited to handful of precedents that we personally drafted or gathered from trusted colleagues, this tiny universe can be carefully dissected word-by-word. In the last few years, our universe has massively expanded to include all documents filed on EDGAR, enormous volumes financial transactions, and vast collections of agreements generated from an interconnected global marketplace.

We cannot be masters of the digital universe based solely on our personal reading experiences.

Friday, June 24, 2011

Intellectual Property Rep

The Intellectual Property Representation (on ContractStandards) appears to have been built over time, incrementally adding more and more language. All clauses example share common elements, such as the disclosure of registered IP, declaration of rights of ownership and representations regarding non-infringement. However, with respect to less frequently appearing clause elements there is a very wide range of optional provisions and little consistency in their occurrence. The result is a listing of overlapping representations, without a clear reference to what technology platforms they apply, other than a generic concept of “intellectual property” that spans everything from inchoate ideas to commercial software packages.

The proposed organizing theme (a work in progress) builds the clause components from a business framework, offering a matrix of configurable clause components that can be inserted if applicable to the representing party.


Disclosure
Ownership
Warranties
Sufficiency
IP Protection
Compliance
Proprietary IP






Registered IP
ü
ü

ü
ü
ü
Commercial IP
ü
ü
ü
ü
ü
ü
Proprietary Operational IP
ü
ü
ü
ü
ü
ü
Conceptual IP




ü
ü
Licensed IP






Licensed Operational IP
ü

ü
ü
ü
ü

Registered IP: patents, trademarks, copyrights, and domain names protected by registration.
Commercial IP: intellectual property products and services sold or licensed.
Operational IP: intellectual products, services and content developed, commissioned, acquired or customized used to manage business operations, separated into commercially available technology and customized technology. Operational IP may be owned or licensed.
Conceptual IP: inventions, ideas, concepts and trade secrets.

(Note: optional clause language should be added whether the representing party has re-seller or distribution rights to IP owned by a third party).

Using the framework, the IP representations can be applied to each definitional category, adjusting the reps appropriately based on proprietary rights. For example, in the case of an acquisition agreement, warranties given for commercial IP (out-bound license agreements) should mirror the warranties in the party’s software license agreements. However, there are frequently significant differences between the warranties offered by a business to its licensees (typically very limited) and the warranties given by the same company to a buyer of the business (often including performance and error-free warranties). On the hand, warranties given for licensed software used to run a business (in-bound license agreements) and customized technology may require that the technology is substantially error-free.

Wednesday, May 18, 2011

Developing CAD for Law—Part 2

Contract Building Blocks

There are two main approaches to document automation. First, a Programmatic approach inserts If-Else-Then statements into a document to select different deal terms based on configuration options. Second, a Modular approach constructs an agreement from a hierarchy of standard and alternative sentences, clauses, and document sections.

At first blush, the approach of creating standard and a range of alternate provisions likely repeats much of the same core terms, thereby producing significant duplication of language. While this is true, the burden is borne by the computer. On the other hand, the approach of embedding If-Else-Then statements into lengthy documents becomes exceedingly challenging where the statements are nested inside one another, sometimes spanning many pages. This burden of complexity is borne by the human operator. As a programmer, I think of the programmatic approach as very brittle and highly susceptible to error.

This same rationale caused a shift many years ago in computer languages away from linear approaches—such as the C language—to modular, object-orientated programming in C++ and C#, widely used today.

Moreover, the modular approach most closely reflects the organizing structure of legal agreements. Contracts are organized in a consistent modular hierarchy. Each agreement has an explicit or implicit table of contents. Collectively, they organized upon similar building blocks. For this reason, ContractStandards proposes a Unified Contract Structure for organizing bi-lateral exchange agreements. 

A modular hierarchy is an approach that allows us to handle highly complex systems, such as an organizing framework for all legal agreements. In his seminal work, The Architecture of Complexity, Herbert Simon demonstrates that hierarchy is the organizing theme for a science of complexity. His parable—written nearly 50 years ago—of the watchmakers is highly relevant to our current needs to address complexity, efficiency, but without sacrificing quality.

“There once was two watchmakers, named Hora and Tempus, who manufactured very fine watches. Both of them were highly regarded, and the phones in their workshops rang frequently. New customers were constantly calling them. However, Hora prospered while Tempus became poorer and poorer and finally lost his shop. What was the reason?

The watches the men made consisted of about 1000 parts each. Tempus had so constructed his that if he had one partially assembled and had to put it down—to answer the phone, say—it immediately fell to pieces and had to be reassembled from the elements. The better the customers liked his watches the more they phoned him and the more difficult it became for him to find enough uninterrupted time to finish a watch.

The watches Hora handled were no less complex than those of Tempus, but he had designed them so that he could put together sub-assemblies of about ten elements each. Ten of these subassemblies, again, could be put together into a larger subassembly and a system of ten of the latter constituted the whole watch. Hence, when Hora had to put down a partly assembled watch in order to answer the phone, he lost only a small part of his work, and he assembled his watches in only a fraction of the man-hours it took Tempus.”

Once the modular hierarchy is established, which allows selection of the core contract building blocks, a CAD system for law must then permit fine tuned configuration of deal terms tailored to client-specific needs. And, that will be the topic of the next blog post.

Monday, April 25, 2011

Developing CAD for Law—Part 1

Unified Contract Structure

One of the core characteristics of a computer aided drafting (CAD) system is the development of modular, reusable building blocks. Just as computer programming progressed from linear, procedural methods of languages such as C to the object-orientated programming methods of languages like C++, CAD will break the silos of discrete document types and construct agreements based on modules.

I propose a Unified Contract Structure (UCS) based on 10 contractual building blocks reflecting the organization of clauses in bi-lateral and multi-lateral exchanges. The USC is comprised of the 10 core objects, a listing of document types, cross-referenced to a hierarchical clause library of terms and provisions. The result is a Contract Matrix.

It is hoped that in addition to reusability, the matrix can help contract drafters “see the forest for the trees.” This is one of the reasons why Atul Gawande’s 3 part Operating Room checklist can reduce surgical complications by one-third. Click here to view the Surgical Safety Checklist.

Monday, April 4, 2011

Design and Production—Separate Values

Richard Susskind and others predict the inevitable commoditization of legal services through the twin pressures of automation and competition. I agree in principle. However, I do not see the trend as an across-the-board reduction in value, but rather a process that separates high and lower value activities.

Others, notably Ron Friedmann, Toby Brown and Jordan Furlong, have focused on the difference between types of representation. They distinguish high-value bet the farm situations from low-value factory work. However, in any representation there is some proportion of high value design work and some elements of lower value production activities, even in high risk matters.

In practice today, rates are determined primarily by who does the work rather than the nature of the work. It is true that most deal structuring is performed by higher priced partners and most document drafting is undertaken by somewhat lower cost associates. Nevertheless, each lawyer, across the entire billing rate spectrum, generally charges the same rate for structuring a transaction, drafting a document, or typing an email (Rate ranges are applied at the matter level, not the task level).

More significantly, over time production costs have increased. It is true that transactions have become increasingly more complex, requiring more time to prepare. But if we examine a related profession—architecture—we can see different approaches to cost control and different outcomes where risks are borne either by the profession or the client.


1940’s

Architecture--75 years ago, when Frank Lloyd Wright designed Falling Water, there was no separation between building design and production of the working drawings.

Design and production was one and the same process. The famous architect oversaw all the details, even designing the tables, chairs and door knobs. And, since the activities were blended, the fee for his services was likely charged at one aggregate rate.

1980’s

Law--When I first started practice in a venerable London firm of solicitors, I marveled at the ability of the partners to dictate a will and other legal agreements in one session; with corrections only in the form of backing up the tape. Likewise, secretaries typed wills flawlessly. In fact, corrections—in the form of whiteout—were not allowed. The page had to be re-typed.

Structuring the will and producing the document was a single activity. Accordingly, a single blended rate was justified because design and production were combined. Moreover, the entire process was completed in a few hours.

With the introduction of computers, we can now refine our documents through multiple drafts. And, by drawing on available precedent, lengthen our agreements to cover all possible scenarios. Litigation has embraced a scorched earth approach, leaving no stone unturned and every document read; cumulating in today’s electronic discovery, which has massively increased the volume of documents reviewed.

Architecture—In the 1980’s, pressure to control soaring production costs shifted squarely to the profession as fixed fees were introduced and widely applied. Even as buildings became bigger and more complex, the challenge to control costs was born largely by the profession.

2010’s

Architecture—In architecture today, design and production is automated with sophisticated computer aided design (CAD) software. Powerful technologies, such as Autodesk’s Revit, allow design-and-build to take place simultaneously, and in a relatively short period of time. Building specifications are highly standardized through content services, such as ARCOM’s Master Spec.

Despite heavy automation, friends in architecture practice confirm that fixed fees arrangements sometimes have the effect of decreasing the return on design work. This situation may occur because production tasks must be completed in order to finish the work and submit a bill; and since production runs lean with lower margins, there is frequently pressure to take value from the design tasks—yet design is what distinguishes the project and the firm.

Law—Law operates in a largely unautomated world. Computer assisted drafting has not been broadly implemented. Email and blackberries do not count as automation systems. As a result, lawyers continue to command high rates for drafting, reviewing and editing documents. The act of crafting the deal and drafting the documents is still one-and-the-same process. Moreover, the amount of time spent producing supporting documents and other materials has steadily, and significantly, increased over time, with the full burden of these cost increases borne by clients.

Of course, you can hear the collective chorus pointing out that the “devil is in the details” because the art and soul of lawyering is to handle every consequence no matter how unlikely, because some consequences can be very, very bad. But, I wonder if the same opinion would be voiced if fixed fees became the norm.

Next…True CAD is coming to law. It is a manner of when. The burden to control costs is also shifting to the legal profession, who, like architects, are in a better position to implement technologies and processes to more efficiently manage production tasks because of their professional expertise.

The challenge for law firm leaders is to assess what percentage of their current workload falls into lower value categories and how will this work be handled? Should it be out-sourced or in-sourced? Or, will innovation be lead by emerging law firms, content providers and technology firms?

In the next post, I’ll attempt to define what it takes to develop true CAD for law (at least for transactional practice), and estimate the time needed for its development.