<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Annesley Business Consulting Ltd &#187; practical</title>
	<atom:link href="http://www.abc-ltd.org/tag/practical/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.abc-ltd.org</link>
	<description></description>
	<lastBuildDate>Wed, 11 Jan 2012 16:33:02 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Contractual One-Upmanship</title>
		<link>http://www.abc-ltd.org/2011/02/contractual-one-upmanship/</link>
		<comments>http://www.abc-ltd.org/2011/02/contractual-one-upmanship/#comments</comments>
		<pubDate>Wed, 09 Feb 2011 18:19:46 +0000</pubDate>
		<dc:creator>Margaret Burrell</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[client relationships]]></category>
		<category><![CDATA[contract]]></category>
		<category><![CDATA[disputes]]></category>
		<category><![CDATA[practical]]></category>
		<category><![CDATA[reasonableness]]></category>
		<category><![CDATA[terms and conditions]]></category>
		<category><![CDATA[trust]]></category>

		<guid isPermaLink="false">http://www.abc-ltd.org/?p=436</guid>
		<description><![CDATA[How do you proceed when faced with a long-winded, very one-sided contract presented to you by a potential customer or supplier? And what does the contract – and your response – say about your respective attitudes to business? Contracts are often called Agreements – and for good reason: The whole basis of a contract is [...]]]></description>
			<content:encoded><![CDATA[<p>How do you proceed when faced with a long-winded, very one-sided contract presented to you by a potential customer or supplier? And what does the contract – and your response – say about your respective attitudes to business?</p>
<p>Contracts are often called Agreements – and for good reason: The whole basis of a contract is that it represents the agreement which has been reached between the parties. So the first question to spring to mind might be &#8211; why is the other party starting out upon their relationship with me by behaving like a bully, and does this behaviour really bode well for a successful working relationship? In contrast, the second question might be ‘What does accepting these terms say about how I value my contribution to this arrangement?’</p>
<p>In reality, (leaving aside the minority who are greedily looking for short-term gain over long-term relationships,) most people neither want nor actually understand the complexities of ‘clever’ contracts. So, this type of problem is often caused by the advisers, some of whom engage in ‘contractual one-upmanship’ – who can impose the most unreasonable clauses – either as part of an ego trip, or because it’s what they feel their clients want.</p>
<p>In these situations, what tends to happen is that the parties lose patience with the negotiation process. This leads to one of two outcomes: Either the whole deal falls through, or the parties start working together outside of the agreement which is being negotiated &#8211; ie, under their own unwritten rules.</p>
<p>Good contracts lead to profitable long-term relationships because they accurately record the details of the agreement which the parties have reached in a way both parties understand – preventing the disputes which result from a failure to properly manage expectations, and which end up destroying reputations. However, to create a good contract, you need to start from a position of trust and reasonableness.</p>
<p>So, in the situation described above, a good start would be to arrange a round-table discussion rather than batting emails backwards and forwards. Explain that you don’t want to ‘play games’, and that you simply want to achieve a contract which is fair and reasonable, and which reflects what BOTH parties actually want. Having the other party present for this helps them to understand your point of view (something which won’t be passed on if it’s their adviser causing the problem), and having your own adviser present means that there’s no opportunity for the other adviser to blind you with (legal) science.</p>
<p>Of course, being ‘fair and reasonable’ doesn’t mean giving all your rights away. It simply means understanding that there will be risks to both parties in any potential arrangement and that the best course of action is to balance those risks with the benefits to be derived under that arrangement. Accordingly, knowing your risks – and to what extent you are prepared to accept them – as well as thinking the position through from the other party’s perspective, will be good preparation for your negotiation.</p>
<p>By working together collaboratively in this way, all parties achieve the ideal solution &#8211; a win:win situation leading to long-term trust and a reduced likelihood of disputes. The whole process is also much faster and less expensive than playing ‘contractual one-upmanship’. So, if it’s your contracts that are causing the problems, now might be a good time to re-assess what they are saying about <strong>your</strong> business.</p>
<div class="tweetthis" style="text-align:left;"><p> <a class="tt" href="http://twitter.com/home/?status=Contractual+One-Upmanship+http%3A%2F%2Fabc-ltd.org%2F%3Fp%3D436" title="Post to Twitter"><img class="nothumb" src="http://www.abc-ltd.org/wp-content/plugins/tweet-this/icons/en/twitter/tt-twitter-big4.png" alt="Post to Twitter" /></a></p></div>]]></content:encoded>
			<wfw:commentRss>http://www.abc-ltd.org/2011/02/contractual-one-upmanship/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>&#8220;Is this contract OK?&#8221;</title>
		<link>http://www.abc-ltd.org/2010/02/is-this-contract-ok/</link>
		<comments>http://www.abc-ltd.org/2010/02/is-this-contract-ok/#comments</comments>
		<pubDate>Tue, 16 Feb 2010 16:35:20 +0000</pubDate>
		<dc:creator>Margaret Burrell</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[client relationships]]></category>
		<category><![CDATA[contract]]></category>
		<category><![CDATA[Cut and Paste]]></category>
		<category><![CDATA[disputes]]></category>
		<category><![CDATA[practical]]></category>
		<category><![CDATA[terms and conditions]]></category>
		<category><![CDATA[Uncertainty]]></category>

		<guid isPermaLink="false">http://www.abc-ltd.org/?p=255</guid>
		<description><![CDATA[This is a question which anyone who advises on contracts or terms and conditions is frequently asked. It seems quite reasonable at first &#8211; but then, what does &#8216;OK&#8217; mean? There are several things which may stand out as being &#8216;not OK&#8217; or unacceptable in a contract &#8211; unreasonable liability provisions, restrictive covenants etc &#8211; [...]]]></description>
			<content:encoded><![CDATA[<p>This is a question which anyone who advises on contracts or terms and conditions is frequently asked. It seems quite reasonable at first &#8211; but then, what does &#8216;OK&#8217; mean?</p>
<p>There are several things which may stand out as being &#8216;not OK&#8217; or unacceptable in a contract &#8211; unreasonable liability provisions, restrictive covenants etc &#8211; but these can sometimes pale into (almost) insignificance, if we ask a different and wholly more important question: <strong>&#8220;Does this contract achieve what I want it to?&#8221;</strong></p>
<p>In the last few days, I have looked at three separate contracts in relation to which the anser to the first question was &#8216;yes&#8217;, but the answer to the second question was a loud and definite &#8216;NO!&#8217;</p>
<p>In 2 of the 3 cases, whilst in totally different industries, the agreements effectively involved the clients setting up supply chain arrangements under short-term agreements. On the face of it, whilst there were some drafting issues, these could easily have been resolved. However, on digging deeper into what the clients actually believed they were signing up to, I found that in both cases, they were expecting long term, exclusive, product supply agreements &#8211; with a long term income stream to match. They were therefore quite shocked when I explained what their contracts actually meant and how limited their rights would be.</p>
<p>In the third case, I was being asked to review terms and conditions, and these were generally &#8216;OK&#8217; in relation to the products which the client sells. However, the client&#8217;s greatest source of income comes from the provision of services &#8211; and these were not even mentioned.</p>
<p>As well as creating a huge amount of uncertaintly, the above examples highlight a common problem &#8211; which is the tendency to focus upon what a contract <strong>contains</strong>, rather than what is <strong>omitted</strong>. This is an especially easy trap for lawyers with no practical commerical experience, and business people with no legal experience, to fall into. It is also a serious side-effect of cut and paste drafting (as to which, see my earlier article: <strong><a href="http://www.abc-ltd.org/2009/11/cut-and-paste-trap/" target="_blank">The Cut and Paste Trap</a>.)</strong></p>
<p>So, when reviewing or constructing a contract or a set of terms and conditions, what <strong>is</strong> the best approach?</p>
<p>Firstly, put any drafts on one side, and get a blank piece of paper!</p>
<p>Write down your own understanding of the arrangement (in English, not &#8216;legalese&#8217;), and try to think chronologically. Then ask how long the arrangement will last, and what each party hopes to get out of it. Finally, think about what the other party (or their successors!) could do which would make the arrangement less profitable or acceptable to you &#8211; for example, using your ideas to create a product of their own, or not providing you with the information you need to be able to provide your services on time.</p>
<p>Once you have a clear structure, it is much easier for your or your advisors to answer that all-important question: Does this contact achieve my objectives?&#8217; &#8211; and to suggest amendments based upon ensuring that the opportunities for misunderstandings are minimised.</p>
<p>This approach results in a win-win situation and is the basis for building great business relationships &#8211; which is the objective of all of us in business!</p>
<div class="tweetthis" style="text-align:left;"><p> <a class="tt" href="http://twitter.com/home/?status=%E2%80%9CIs+this+contract+OK%3F%E2%80%9D+http%3A%2F%2Fabc-ltd.org%2F%3Fp%3D255" title="Post to Twitter"><img class="nothumb" src="http://www.abc-ltd.org/wp-content/plugins/tweet-this/icons/en/twitter/tt-twitter-big4.png" alt="Post to Twitter" /></a></p></div>]]></content:encoded>
			<wfw:commentRss>http://www.abc-ltd.org/2010/02/is-this-contract-ok/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Circular Definitions</title>
		<link>http://www.abc-ltd.org/2009/09/circular-definitions/</link>
		<comments>http://www.abc-ltd.org/2009/09/circular-definitions/#comments</comments>
		<pubDate>Tue, 29 Sep 2009 18:23:27 +0000</pubDate>
		<dc:creator>Margaret Burrell</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[certainty]]></category>
		<category><![CDATA[Definitions]]></category>
		<category><![CDATA[flexibility]]></category>
		<category><![CDATA[practical]]></category>

		<guid isPermaLink="false">http://www.abc-ltd.org/?p=121</guid>
		<description><![CDATA[It seems as if the list of definitions at the beginning of contracts gets longer and longer, and often they are very useful. However, they must be carefully constructed. I have come across the following example today of a &#8216;circular&#8217; definition: Definition: &#8216;Protocol&#8217; means the protocol which the supplier must provide to the client in [...]]]></description>
			<content:encoded><![CDATA[<p>It seems as if the list of definitions at the beginning of contracts gets longer and longer, and often they are very useful. However, they must be carefully constructed.</p>
<p>I have come across the following example today of a &#8216;circular&#8217; definition:</p>
<p>Definition: &#8216;Protocol&#8217; means the protocol which the supplier must provide to the client in accordance with Clause 2</p>
<p>Clause 2: The supplier will provide the client with the Protocol</p>
<p>This definition creates a perpetual loop. As the supplier, you would read to clause 2 and see that you have to provide a Protocol &#8211; you would then look to the definition to see what it means, and find that it is the document you have to provide under clause 2!</p>
<p>As a lawyer who focuses on the practicalities of contractual agreements &#8211; and on making them as short as is reasonably possible &#8211; if I was re-drafting this, I would firstly decide whether a definition was required at all. If it was, I would probably re-word it along the lines of the following:</p>
<p>&#8216;Protocol&#8217; means a protocol in the form set out in Schedule 1, or in such alternative form as the parties shall agree in writing from time to time.</p>
<p>The first part of the wording gives the parties certainty as to what is meant, and the second part gives them the flexibility to make future changes.</p>
<p>Do you have definitions in your agreements which don&#8217;t make sense to you or go around in circles? If so, I&#8217;d be pleased to hear about them.</p>
<div class="tweetthis" style="text-align:left;"><p> <a class="tt" href="http://twitter.com/home/?status=Circular+Definitions+http%3A%2F%2Fabc-ltd.org%2F%3Fp%3D121" title="Post to Twitter"><img class="nothumb" src="http://www.abc-ltd.org/wp-content/plugins/tweet-this/icons/en/twitter/tt-twitter-big4.png" alt="Post to Twitter" /></a></p></div>]]></content:encoded>
			<wfw:commentRss>http://www.abc-ltd.org/2009/09/circular-definitions/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>new blog</title>
		<link>http://www.abc-ltd.org/2009/07/new-blog/</link>
		<comments>http://www.abc-ltd.org/2009/07/new-blog/#comments</comments>
		<pubDate>Fri, 17 Jul 2009 18:14:29 +0000</pubDate>
		<dc:creator>Margaret Burrell</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[confidential information]]></category>
		<category><![CDATA[confidentiality]]></category>
		<category><![CDATA[contract]]></category>
		<category><![CDATA[practical]]></category>

		<guid isPermaLink="false">http://www.abc-ltd.org/?p=111</guid>
		<description><![CDATA[I&#8217;ve resisted it for a long time, but I&#8217;ve finally succumbed to having a blog! Whilst solicitors do an excellent job of protecting their clients&#8217; legal interests, I still come across too many examples of unnecessarily long-winded contracts, full of complex legal phraseology, and which do not reflect the practical needs of the parties. Sometimes [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve resisted it for a long time, but I&#8217;ve finally succumbed to having a blog!</p>
<p>Whilst solicitors do an excellent job of protecting their clients&#8217; legal interests, I still come across too many examples of unnecessarily long-winded contracts, full of complex legal phraseology, and which do not reflect the practical needs of the parties.</p>
<p>Sometimes this type of contact is simply the result of sloppy drafting &#8211; the &#8216;here&#8217;s one I prepared earlier&#8217; approach. However, mostly, it&#8217;s down to the fact that the solicitor does not know enough about the nature of the businesses and the transaction involved &#8211; and the client can&#8217;t afford the time it would take for him or her to find out &#8211; to be able to draft a better document. In either case the client, not being legally trained, won&#8217;t realise the limitations of the document &#8211; unless and until it is too late.</p>
<p>I&#8217;ve therefore decided to share some examples of poor drafting I come across and to look at how these can be remedied. (Confidentiality is obviously paramount though, so certain details will be changed where necessary.)</p>
<p>So, to start:</p>
<p>Last week I reviewed an 8 page (yes, 8 page!) confidentiality agreement for a client. It had been drafted by reputable and expensive lawyers, but they clearly did not understand the structure of the client&#8217;s organisation &#8211; and the client did not understand the complexity of the agreement.</p>
<p>This created 2 major problems:</p>
<p>1. Much of the information to be disclosed by my client would not have been protected because it belonged to organisations not covered by the agreement;</p>
<p>2. Disclosure of the other party&#8217;s confidential information to my client&#8217;s associated companies &#8211; which was always what was intended &#8211; would have put them in breach of the agreement.</p>
<p>In other words, the agreement was utterly and totally useless for the purpose for which it was intended. 8 pages of wasted rain forest!</p>
<p>Ideally, it would have been better to have had separate agreements with the associated companies, but &#8211; let&#8217;s get real &#8211; this was never going to happen. Accordingly, remedying the contract involved drafting tighter definitions, and providing rights for the associated companies to be able to rely upon the terms of the agreement under the Contracts (Rights of Third Parties) Act 1999.</p>
<p>More examples to come. Watch this space!</p>
<div class="tweetthis" style="text-align:left;"><p> <a class="tt" href="http://twitter.com/home/?status=new+blog+http%3A%2F%2Fabc-ltd.org%2F%3Fp%3D111" title="Post to Twitter"><img class="nothumb" src="http://www.abc-ltd.org/wp-content/plugins/tweet-this/icons/en/twitter/tt-twitter-big4.png" alt="Post to Twitter" /></a></p></div>]]></content:encoded>
			<wfw:commentRss>http://www.abc-ltd.org/2009/07/new-blog/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

