<?xml version="1.0"?>
<rss version="2.0">
<channel>
  <title>Schinnerer&#039;s RM Blog - ejcdc tag</title>
  <link>http://www.schinnerer.com/blogs/rm/tags/ejcdc/</link>
  <description>Shortening our publishing cycle</description>
  <language>en</language>
  <copyright>Paul Riccardi</copyright>
  <lastBuildDate>Tue, 15 May 2012 11:56:00 GMT</lastBuildDate>
  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>EJCDC Adds Teaming Component to Revised Joint Venture Agreement</title>
    <link>http://www.schinnerer.com/blogs/rm/2011/12/20/ejcdc_adds_teaming_component_to_revised_joint_venture_agreement.html</link>
    
      
        <description>
          &lt;p&gt;Recognizing that firms are in many cases teaming with others to pursue business opportunities, &lt;a href=&#034;http://www.ejcdc.org/images/stories/E580December62011.pdf &#034;&gt;the Engineers Joint Contract Documents Committee (EJCDC) has added a Teaming Agreement &lt;/a&gt;to a new revised version of the joint venture document. The EJCDC E-580, &lt;i&gt;Teaming Agreement to Pursue Joint Business Opportunity&lt;/i&gt; and &lt;i&gt;Joint Venture Agreement Between Engineers&lt;/i&gt; has two components&amp;mdash;the Teaming Agreement can be used for two firms that wish to join together to pursue an opportunity to obtain work, and the Joint Venture Agreement can be used to define the relationship of the firms when they are providing professional services to a client.&lt;/p&gt;
&lt;div&gt;&amp;nbsp;EJCDC documents can be obtained at the online stores of the four sponsoring organizations of EJCDC: the American Society of Civil Engineers (ASCE), the Associated General Contractors of America (AGC), the National Society of Professional Engineers (NSPE), and the American Council of Engineering Companies (ACEC). They can also be purchased at &lt;a href=&#034;http://www.ejcdc.org/&#034;&gt;www.ejcdc.org&lt;/a&gt;.&lt;/div&gt;
        </description>
      
      
    
    
    
    <comments>http://www.schinnerer.com/blogs/rm/2011/12/20/ejcdc_adds_teaming_component_to_revised_joint_venture_agreement.html#comments</comments>
    <guid isPermaLink="true">http://www.schinnerer.com/blogs/rm/2011/12/20/ejcdc_adds_teaming_component_to_revised_joint_venture_agreement.html</guid>
    <pubDate>Tue, 20 Dec 2011 13:20:00 GMT</pubDate>
  </item>
  
  <item>
    <title>Right to rely on information provided by your client</title>
    <link>http://www.schinnerer.com/blogs/rm/2011/02/22/right_to_rely_on_information_provided_by_your_client.html</link>
    
      
        <description>
          &lt;p&gt;&lt;img align=&#034;left&#034; width=&#034;140&#034; height=&#034;160&#034; alt=&#034;&#034; src=&#034;http://www.schinnerer.com/blogs/rm/images/contract%20review%20blog%20icon.jpg&#034; /&gt;&lt;/p&gt;
&lt;div style=&#034;margin: 0in 0in 0pt&#034;&gt;The standard AIA and EJCDC form documents state that the client will provide surveys and other information to the consultants and that the consultants are entitled to rely on the accuracy of such information. This allows you to describe the scope of services you are providing correctly since you are referencing information on which you are entitled to rely. Client-drafted contracts, however, may change the responsibilities. Recently, we came across the following clause in a contract review:&lt;/div&gt;
&lt;div style=&#034;margin: 0in 0in 0pt 0.5in&#034;&gt;&amp;nbsp;&lt;/div&gt;
&lt;div style=&#034;margin: 0in 0in 0pt 0.5in&#034;&gt;&amp;nbsp;&lt;/div&gt;
&lt;div style=&#034;margin: 0in 0in 0pt 0.5in&#034;&gt;&lt;i&gt;Client shall furnish surveys describing physical characteristics, legal limitations and utility locations for the site of the Project. However, the Consultant remains fully responsible for verifying the accuracy of this information.&lt;/i&gt;&lt;/div&gt;
&lt;div style=&#034;margin: 0in 0in 0pt&#034;&gt;&amp;nbsp;&lt;/div&gt;
&lt;div style=&#034;margin: 0in 0in 0pt&#034;&gt;If you agree to this provision, it means that you have taken on the responsibility of verifying the accuracy of the information provided. Depending on the project and the information provided you have to decide whether this is a reasonable responsibility to assume under the circumstances. From a risk management perspective, it is prudent to examine your scope of services and increase the fees you are charging for the increased risks if the client is unwilling to provide you with a right to rely on the information provided.&lt;/div&gt;
        </description>
      
      
    
    
    
    <comments>http://www.schinnerer.com/blogs/rm/2011/02/22/right_to_rely_on_information_provided_by_your_client.html#comments</comments>
    <guid isPermaLink="true">http://www.schinnerer.com/blogs/rm/2011/02/22/right_to_rely_on_information_provided_by_your_client.html</guid>
    <pubDate>Tue, 22 Feb 2011 19:59:00 GMT</pubDate>
  </item>
  
  <item>
    <title>Monitoring Changes in Standard Industry Documents</title>
    <link>http://www.schinnerer.com/blogs/rm/2010/02/09/monitoring_changes_in_standard_industry_documents.html</link>
    
      
      
        <description>
          &lt;div style=&#034;MARGIN: 0in 0in 0pt&#034;&gt;Standard industry contracts generally reflect prevailing customs, practice, and experience. They are internally coordinated and consistent and provide a comprehensive framework for the agreement between the parties. Design professionals should note, however, that since these standard industry contracts are drafted for broad applicability, they must be adapted to project-specific circumstances.&lt;/div&gt;&lt;p&gt;&lt;a href=&#034;http://www.schinnerer.com/blogs/rm/2010/02/09/monitoring_changes_in_standard_industry_documents.html&#034;&gt;Read more...&lt;/a&gt;&lt;/p&gt;
        </description>
      
    
    
    
    <comments>http://www.schinnerer.com/blogs/rm/2010/02/09/monitoring_changes_in_standard_industry_documents.html#comments</comments>
    <guid isPermaLink="true">http://www.schinnerer.com/blogs/rm/2010/02/09/monitoring_changes_in_standard_industry_documents.html</guid>
    <pubDate>Tue, 09 Feb 2010 14:13:00 GMT</pubDate>
  </item>
  
  </channel>
</rss>

