<?xml version="1.0"?>
<rss version="2.0">
<channel>
  <title>Schinnerer&#039;s RM Blog - writtenagreement tag</title>
  <link>http://www.schinnerer.com/blogs/rm/tags/writtenagreement/</link>
  <description>Shortening our publishing cycle</description>
  <language>en</language>
  <copyright>Paul Riccardi</copyright>
  <lastBuildDate>Mon, 21 May 2012 12:26:00 GMT</lastBuildDate>
  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>New Contract Review Series</title>
    <link>http://www.schinnerer.com/blogs/rm/2011/01/05/new_contract_review_series.html</link>
    
      
        <description>
          &lt;p&gt;&lt;font size=&#034;2&#034;&gt;Now that it is 2011, we are adding a new feature to our blog, in addition to continuing to bring you the same type of content we provided in 2010. Our new feature will be written by the risk managers&amp;nbsp;who review contracts for our insured design professionals. &lt;/font&gt;&lt;/p&gt;
&lt;p&gt;&lt;font size=&#034;2&#034;&gt;In performing contract reviews, our risk managers often come across interesting provisions&amp;mdash;both good and bad. We are going to highlight some of these provisions in a series of entries that will hopefully serve to inform the reader as to the different types of issues that can arise in professional services agreements. &lt;/font&gt;&lt;/p&gt;
&lt;p&gt;&lt;font size=&#034;2&#034;&gt;Our next entry will be the first in this contract review series. It will discuss a liquidated damages clause. In the future, be on the lookout for more entries dealing with various unusual contractual provisions.&lt;/font&gt;&lt;/p&gt;
        </description>
      
      
    
    
    
    <comments>http://www.schinnerer.com/blogs/rm/2011/01/05/new_contract_review_series.html#comments</comments>
    <guid isPermaLink="true">http://www.schinnerer.com/blogs/rm/2011/01/05/new_contract_review_series.html</guid>
    <pubDate>Wed, 05 Jan 2011 18:03:00 GMT</pubDate>
  </item>
  
  </channel>
</rss>

