<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: construction doc disclaimer language? in Documentation</title>
    <link>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117070#M18811</link>
    <description>I felt this would be a great resource venue, even if the subject is seldom discussed. I &lt;B&gt;truly &lt;/B&gt;appreciate the input. &lt;BR /&gt;
&lt;BR /&gt;
I cobbled this disclaimer together several years back and haven't really reviewed since. Reading and re-reading it is embarrassing  &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_redface.gif" style="display : inline;" /&gt;  . The language is that of someone who is scared to death to take responsibility for their work. That's not me or my intent..........My work is done on a handshake believe it or not. I came up working with a contractor building million dollar homes that way and have always admired, naively or not, that way of conducting business. To that end I am way off base with my original language. I sincerely doubt any of this, old or new version, could be defended against aggressive legal representation. It's not about that in so much as it's intended to compel participation toward the desired result without disregard for the parameters that guide local residential construction.&lt;BR /&gt;
&lt;BR /&gt;
With your assistance this is where I'm headed. Hopefully appropriately defining who's responsible for what. Any further input is appreciated.........&lt;BR /&gt;
&lt;BR /&gt;
THIS DESIGN AND PLANS ARE THE SOLE RESPONSIBILITY OF WHITECAP3D, [JEFF WHITE], AND HAVE BEEN GENERATED FOR THE CLIENTS LISTED IN THE PROJECT NAME AND ARE NOT TO BE USED, REPRODUCED, COPIED, OR DISTRIBUTED FOR ANY OTHER PROJECT WITHOUT WRITTEN PERMISSION FROM AND OR COMPENSATION DUE WHITECAP3D. &lt;BR /&gt;
&lt;BR /&gt;
UTILIZATION OF THESE DOCUMENTS AND SUBSEQUENT FABRICATION-CONSTRUCTION ARE THE SOLE RESPONSIBILITY OF THE CONTRACTOR. BEFORE STARTING CONSTRUCTION THE CONTRACTOR SHALL REVIEW AND VERIFY ON SITE ALL DIMENSIONS, DETAILS AND THEIR CORRELATION TO ATTACHED ENGINEERING. ANY DISCREPANCIES IN PLANS, DIMENSIONS, NOTES, OR DETAILS SHALL BE BROUGHT TO THE IMMEDIATE ATTENTION OF THE DESIGNER PRIOR TO COMMENCING ASSOCIATED WORK, ALLOWING REQUIRED CORRECTIONS TO BE PERFORMED. ANY ATTACHED ENGINEERING OR LOCAL BUILDING AUTHORITY NOTATIONS SUPERSEDE AND OVERRIDE MATERIALS, FASTENING, NAILING SCHEDULES AND CONSTRUCTION PROCEDURES PRESENTED IN PLAN, SECTION OR DETAIL VIEWS AND SHALL TAKE PRECEDENCE OVER ANYTHING SHOWN, DESCRIBED OR IMPLIED. THE CONTRACTOR ASSUMES LIABILITY FOR ANY PROBLEMS THAT MAY ARISE DUE TO NON-COMPLIANCE. USE OF THESE PLANS CONSTITUTES COMPLIANCE WITH THE ABOVE TERMS.</description>
    <pubDate>Fri, 20 Jun 2008 16:02:01 GMT</pubDate>
    <dc:creator>Jefferson</dc:creator>
    <dc:date>2008-06-20T16:02:01Z</dc:date>
    <item>
      <title>construction doc disclaimer language?</title>
      <link>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117060#M18801</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;R&gt;Sorry about the probable inappropriate posting here, I didn't know where to post this question............Djorde please redirect the post if you need to.&lt;BR /&gt;
&lt;BR /&gt;
I have a contractor, new to me, who is balking at my rather extensive disclaimer which goes on every set of plans I turn out. [In fact refusing to sign a contract with the clients if the language appears. Never had this issue before.] It is a composite of language I have culled from disclaimers of other long time architects and designer friends of mine. I am curious what kind of language is common with my fellow ArchiTalkers for residential plan sets if you are willing to share I would &lt;B&gt;really&lt;/B&gt; appreciate some help-advice-opinion here. &lt;BR /&gt;
&lt;BR /&gt;
Mine is below. As I said it &lt;B&gt;&lt;U&gt;&lt;/U&gt;&lt;/B&gt;&lt;S&gt;&lt;B&gt;&lt;U&gt;&lt;U&gt;&lt;/U&gt;&lt;/U&gt;&lt;/B&gt;&lt;/S&gt;is&lt;E&gt;&lt;/E&gt; extensive and intended to get the contractor to assist in oversight, as well as compliance to what is put forward by me, my engineer and local code authorities. All of that said I spend an inordinate amount of time "proofing" my plans, and I am conciseness to the point of absurdity. Knock on wood I have yet to have any issue with my plans. This is not a pass the buck as much as cover your ass kind of thing.........&lt;BR /&gt;
&lt;BR /&gt;
GENERAL NOTES&lt;BR /&gt;
&lt;BR /&gt;
THIS PLAN HAS BEEN PREPARED TO MEET PROFESSIONAL STANDARDS AND PRACTICES. HOWEVER, BUILDING CODE REQUIREMENTS VERY WITH LOCATION AND CHANGE FROM TIME TO TIME. BEFORE STARTING CONSTRUCTION THE CONTRACTOR MUST REVIEW AND BE RESPONSIBLE FOR ALL DIMENSIONS AND OTHER DETAILS AND SHOULD REVIEW PLANS TO INSURE THEY MEET CURRENT REQUIREMENTS. THE CONTRACTOR ASSUMES FULL RESPONSIBILITY TO VERIFY THE CONDITIONS, DIMENSIONS, AND STRUCTURAL DETAILS OF THE BUILDING, AND ASSUMES FULL LIABILITY FOR ANY PROBLEMS THAT MAY ARISE DUE TO POSSIBLE ERRORS ON THESE PLANS. ALL FEDERAL, STATE AND LOCAL CODES. ORDINANCES, REGULATIONS, ETC.,SHALL BE CONSIDERED AS PART OF SPECIFICATIONS FOR THIS BUILDING AND SHALL TAKE PRECEDENCE OVER ANYTHING SHOWN, DESCRIBED OR IMPLIED WHERE SAME ARE AT VARIANCE. USE OF THESE PLANS CONSTITUTES COMPLIANCE WITH THE ABOVE TERMS.&lt;BR /&gt;
THESE PLANS HAVE BEEN GENERATED FOR THE CLIENTS LISTED IN THE PROJECT NAME AND ARE NOT TO BE USED, REPRODUCED, COPIED, OR DISTRIBUTED FOR ANY OTHER PROJECT WITHOUT WRITTEN PERMISSION FROM AND OR COMPENSATION DUE WHITECAP3D. &lt;BR /&gt;
&lt;BR /&gt;
ANY ATTACHED ENGINEERING OR LOCAL BUILDING AUTHORITY NOTATIONS &lt;BR /&gt;
SUPERSEDE AND OVERRIDE MATERIALS, FASTENING, NAILING SCHEDULES AND &lt;BR /&gt;
CONSTRUCTION PROCEDURES PRESENTED BELOW &lt;BR /&gt;
AND OR IN PLAN, SECTION OR DETAIL VIEWS.&lt;/R&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 30 May 2023 10:28:58 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117060#M18801</guid>
      <dc:creator>Jefferson</dc:creator>
      <dc:date>2023-05-30T10:28:58Z</dc:date>
    </item>
    <item>
      <title>Re: construction doc disclaimer language?</title>
      <link>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117061#M18802</link>
      <description>Hi Jeff!&lt;BR /&gt;
&lt;BR /&gt;
I think you're in the right forum (here or ArchiCAD+) - since BIM Manager might not get small office input into this issue.  I changed your subject line a bit - if you edit your initial post, you can change the subject further if you think it will draw more attention.&lt;BR /&gt;
&lt;BR /&gt;
The 'contractor responsible for all dimensions', for example, seems a bit strong to me ... and 'other details' seems a bit vague. The dimensions on the plans should be correct.  I've seen language that instructs the builder to not measure dimensions from the plans, but to contact the architect if any dimensions required are not present.&lt;BR /&gt;
&lt;BR /&gt;
A friend uses a variant of the following block which I think came from Monte Chapin, and I'm not sure where he might have gotten it from:&lt;BR /&gt;

&lt;BLOCKQUOTE&gt;The use of these plans shall be restricted to the original project site for which they were created, and publication thereof is expressly limited to such use. Reuse, reproduction or publication by any method, in whole or in part, is prohibited.  This drawing is classified as part of an unpublished collection of visual &lt;BR /&gt;
art under the 1978 copyright act. It is an exclusive work of original authorship. None of the pictorial graphic or technical charts or drawings depicted on this sheet may be reproduced by any method, includung tracing or photocopying, stored in a retrieval system, or transmitted in any form or by &lt;BR /&gt;
means electronic, mechanical or otherwise; nor may they be used or re-used for any purpose without the express prior written permissionof the author. Title and ownership remains with the author without prejudice. Visual contact with these plans shall constitute prima facie evidence of the acceptance of these restrictions.  &lt;BR /&gt;
ALL RIGHTS RESERVED. Copyright ©2008 &amp;lt;your firm&amp;gt;&lt;/BLOCKQUOTE&gt;

That block is basically a copyright block, rather than a disclaimer.  Hopefully some folks have some good disclaimer examples....&lt;BR /&gt;
&lt;BR /&gt;
I also suspect that the language might vary for designers vs licensed architects who are stamping their drawings?&lt;BR /&gt;
&lt;BR /&gt;
Cheers,&lt;BR /&gt;
Karl&lt;BR /&gt;
&lt;BR /&gt;
[Edit: typos]</description>
      <pubDate>Fri, 20 Jun 2008 00:17:06 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117061#M18802</guid>
      <dc:creator>Karl Ottenstein</dc:creator>
      <dc:date>2008-06-20T00:17:06Z</dc:date>
    </item>
    <item>
      <title>Re: construction doc disclaimer language?</title>
      <link>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117062#M18803</link>
      <description>"THE CONTRACTOR ASSUMES FULL RESPONSIBILITY TO VERIFY THE CONDITIONS, DIMENSIONS, AND STRUCTURAL DETAILS OF THE BUILDING, AND ASSUMES FULL LIABILITY FOR ANY PROBLEMS THAT MAY ARISE DUE TO POSSIBLE ERRORS ON THESE PLANS"&lt;BR /&gt;
&lt;BR /&gt;
No wonder he won't sign.&lt;BR /&gt;
Making the contractor responsible for your errors is not very nice. &lt;BR /&gt;
Since i know you personally, I know that you are stand-up kind of guy, but can you clarify exactly what you ARE responsible for if not drawing errors?</description>
      <pubDate>Fri, 20 Jun 2008 00:51:06 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117062#M18803</guid>
      <dc:creator>Dwight</dc:creator>
      <dc:date>2008-06-20T00:51:06Z</dc:date>
    </item>
    <item>
      <title>Re: construction doc disclaimer language?</title>
      <link>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117063#M18804</link>
      <description>I agree. There's a big difference between a copyright protection and what you're asking for.&lt;BR /&gt;
&lt;BR /&gt;
I'd refer to the the AIA General Conditions A201 for an industry accepted definition of roles, responsibilities and liabilities. If you don't include the conditions as part of the construction contract you could crib some of the more important concepts for your waiver.</description>
      <pubDate>Fri, 20 Jun 2008 01:52:50 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117063#M18804</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2008-06-20T01:52:50Z</dc:date>
    </item>
    <item>
      <title>Re: construction doc disclaimer language?</title>
      <link>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117064#M18805</link>
      <description>&lt;BLOCKQUOTE&gt;Jefferson wrote:&lt;BR /&gt;
GENERAL NOTES&lt;BR /&gt;
&lt;BR /&gt;
... BUILDING CODE REQUIREMENTS &lt;B&gt;VARY&lt;/B&gt; WITH LOCATION ....&lt;/BLOCKQUOTE&gt;

or is that a COLOR v COLOUR type thing?</description>
      <pubDate>Fri, 20 Jun 2008 03:31:11 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117064#M18805</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2008-06-20T03:31:11Z</dc:date>
    </item>
    <item>
      <title>Re: construction doc disclaimer language?</title>
      <link>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117065#M18806</link>
      <description>Thanks for the replies!!...........I have left myself open to some good old fashioned ridicule here and I am temped to let this post ride for a while just to see where it goes.............also temped to pull it, for the same reasons  &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_confused.gif" style="display : inline;" /&gt;  I've got Dwight talking nice about me, kinda, and that's good! &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_biggrin.gif" style="display : inline;" /&gt;   And Dom thanks for the link. Reading through that maze mine seems like the easy reader version! GOD, that would frighten most lawerys! I'll peruse it for the type of language I'm after.&lt;BR /&gt;
&lt;BR /&gt;
This disclaimer is definitely severe, and at a &lt;B&gt;bare&lt;/B&gt; minimum needs rewording, and &lt;B&gt;that &lt;/B&gt;is actually what I am after..............assistance and guidance toward a fair and balanced disclaimer compelling the contractor to perform as intended and be responsible to both the client, me and spirit of the design. Not the  "it's all on you" disclaimer but something appropriate..........keep it coming, I can take it!</description>
      <pubDate>Fri, 20 Jun 2008 03:42:01 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117065#M18806</guid>
      <dc:creator>Jefferson</dc:creator>
      <dc:date>2008-06-20T03:42:01Z</dc:date>
    </item>
    <item>
      <title>Re: construction doc disclaimer language?</title>
      <link>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117066#M18807</link>
      <description>Jefferson,&lt;BR /&gt;
&lt;BR /&gt;
While I don't think you can ask the builder to bear the burden of errors in your drawings, you could ask that the contractor check the dimensions and conditions on the drawings prior to construction and &lt;B&gt;report back to the architect&lt;/B&gt; any conditions that may interfere with or otherwise prevent the work as indicated. Such a condition will hopefully produce the cooperative results you are after and should not be seen as too onerous. &lt;BR /&gt;
&lt;BR /&gt;
You may also want to consider, and perhaps you already have, a statement to the effect that changes made in the field without the acknowledgment of the architect will void the responsibility of the architect for such changes.&lt;BR /&gt;
&lt;BR /&gt;
Now, for my disclaimer... &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_biggrin.gif" style="display : inline;" /&gt; ... I am not a lawyer and am only providing you the above generalizations based on things I have seen and used in my practice.  We tend to have our lawyer review any disclaimers we use on our drawings as they must be able to defend us should any project end up in dispute.  To me this seems like money well spent. &lt;BR /&gt;
&lt;BR /&gt;
HTH</description>
      <pubDate>Fri, 20 Jun 2008 05:20:39 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117066#M18807</guid>
      <dc:creator>Erich</dc:creator>
      <dc:date>2008-06-20T05:20:39Z</dc:date>
    </item>
    <item>
      <title>Re: construction doc disclaimer language?</title>
      <link>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117067#M18808</link>
      <description>Hi Jefferson,&lt;BR /&gt;
Boy you get points for bringing up a topic that scares everyone.&lt;BR /&gt;
&lt;BR /&gt;
Contractors at least in California are not responsible for architects'/designer's mistakes. I am not a lawyer and each state varies.&lt;BR /&gt;
&lt;BR /&gt;
My understanding is the contractor is responsible for materials, methods of constructions and being able to build the 'Design Intent' of your work. To that end, as Erich said they have to familiarize themselves with the drawings and specifications that make up the bid package. Most general notes also call for some variation of  'discrepancies should be brought to your attention in a timely manner'. &lt;BR /&gt;
&lt;BR /&gt;
I agree with others here; your wording is too harsh in asking [contractors] to take full responsibility for your work. But, that this is the first time in all your years of practice that your words have been questions demonstrates what we all know, that you are a good and decent person, not out to get them, just struggling with words like any good artichoke. &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_wink.gif" style="display : inline;" /&gt;</description>
      <pubDate>Fri, 20 Jun 2008 06:16:13 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117067#M18808</guid>
      <dc:creator>Erika Epstein</dc:creator>
      <dc:date>2008-06-20T06:16:13Z</dc:date>
    </item>
    <item>
      <title>Re: construction doc disclaimer language?</title>
      <link>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117068#M18809</link>
      <description>Here's another example&lt;BR /&gt;

&lt;BLOCKQUOTE&gt;NOTE:&lt;BR /&gt;
   The contractor shall verify all dimensions on the job site according to the contract documents. Notes and dimensions on architectural plans shall be checked and verified with structural, mechanical, plumbing and any other drawings included in the contract documents. Any discrepancies in notes and or dimensions shall be broght to the immediate attention of the designer prior to commencing work, so that any required remedial work can be performed.&lt;BR /&gt;
&lt;BR /&gt;
   All drawings, specifications and other documents prepared by the designer and his consultants for this project are instruments of the designers service for use solely with respect to this project and unless otherwise provided, the designer shall be deemed the author of these documents and shall retain all common law, statutory and other reserved rights, including the copyrights. Copies of architectural drawings, specifications and other documents for information and reference are prohibited unless expressly authorized by XXX in writing.&lt;/BLOCKQUOTE&gt;

As always check with your lawyer</description>
      <pubDate>Fri, 20 Jun 2008 11:11:00 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117068#M18809</guid>
      <dc:creator>Eduardo Rolon</dc:creator>
      <dc:date>2008-06-20T11:11:00Z</dc:date>
    </item>
    <item>
      <title>Re: construction doc disclaimer language?</title>
      <link>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117069#M18810</link>
      <description>&lt;BLOCKQUOTE&gt;Jefferson wrote:&lt;BR /&gt; Reading through that maze mine seems like the easy reader version! GOD, that would frighten most lawerys! I'll peruse it for the type of language I'm after. &lt;/BLOCKQUOTE&gt;

Yeah, you let lawyers get a hold of anything and it becomes almost unintelligible! There are, however some areas that are similar to some of the language in your waiver. For example, as mentioned earlier, the contractor should be solely responsible for construction means, methods, techniques, procedures and safety precautions; that by entering into the contract the contractor warrants that he has made himself familiar with the existing conditions and the information provided in the contract documents; that the contractor shall not KNOWINGLY perform work in violation of building codes or regulations; discrepancies in the contract documents shall be brought to the attention of the architect; in the event of conflicts between the specifications and drawings - the more stringent condition shall apply; the architect shall not be liable or work not in accordance with the contract documents etc....&lt;BR /&gt;
&lt;BR /&gt;
There is another issue here as well. The items included need to be enforceable should litigation arise. Around here - there is somewhat less weight given to a laundry list of liability definitions and requirements if they are just pasted onto a drawing package where the contractor had no chance to review and negotiate. Signing blind, so to speak. Even if the contractor signed your example "THE CONTRACTOR ASSUMES FULL RESPONSIBILITY TO VERIFY THE CONDITIONS, DIMENSIONS, AND STRUCTURAL DETAILS OF THE BUILDING, AND ASSUMES FULL LIABILITY FOR ANY PROBLEMS THAT MAY ARISE DUE TO POSSIBLE ERRORS ON THESE PLANS" I doubt he could be legally held liable because some of these items are clearly the professional responsibility of the Architect and Structural Engineer.&lt;BR /&gt;
&lt;BR /&gt;
Finally, if you end up with a set of requirements and definitions that differ substantively from accepted common practice in your area, then having a lawyer review the boiler plate set of notes -as suggest earlier- is definately money well spent.</description>
      <pubDate>Fri, 20 Jun 2008 15:41:48 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117069#M18810</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2008-06-20T15:41:48Z</dc:date>
    </item>
    <item>
      <title>Re: construction doc disclaimer language?</title>
      <link>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117070#M18811</link>
      <description>I felt this would be a great resource venue, even if the subject is seldom discussed. I &lt;B&gt;truly &lt;/B&gt;appreciate the input. &lt;BR /&gt;
&lt;BR /&gt;
I cobbled this disclaimer together several years back and haven't really reviewed since. Reading and re-reading it is embarrassing  &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_redface.gif" style="display : inline;" /&gt;  . The language is that of someone who is scared to death to take responsibility for their work. That's not me or my intent..........My work is done on a handshake believe it or not. I came up working with a contractor building million dollar homes that way and have always admired, naively or not, that way of conducting business. To that end I am way off base with my original language. I sincerely doubt any of this, old or new version, could be defended against aggressive legal representation. It's not about that in so much as it's intended to compel participation toward the desired result without disregard for the parameters that guide local residential construction.&lt;BR /&gt;
&lt;BR /&gt;
With your assistance this is where I'm headed. Hopefully appropriately defining who's responsible for what. Any further input is appreciated.........&lt;BR /&gt;
&lt;BR /&gt;
THIS DESIGN AND PLANS ARE THE SOLE RESPONSIBILITY OF WHITECAP3D, [JEFF WHITE], AND HAVE BEEN GENERATED FOR THE CLIENTS LISTED IN THE PROJECT NAME AND ARE NOT TO BE USED, REPRODUCED, COPIED, OR DISTRIBUTED FOR ANY OTHER PROJECT WITHOUT WRITTEN PERMISSION FROM AND OR COMPENSATION DUE WHITECAP3D. &lt;BR /&gt;
&lt;BR /&gt;
UTILIZATION OF THESE DOCUMENTS AND SUBSEQUENT FABRICATION-CONSTRUCTION ARE THE SOLE RESPONSIBILITY OF THE CONTRACTOR. BEFORE STARTING CONSTRUCTION THE CONTRACTOR SHALL REVIEW AND VERIFY ON SITE ALL DIMENSIONS, DETAILS AND THEIR CORRELATION TO ATTACHED ENGINEERING. ANY DISCREPANCIES IN PLANS, DIMENSIONS, NOTES, OR DETAILS SHALL BE BROUGHT TO THE IMMEDIATE ATTENTION OF THE DESIGNER PRIOR TO COMMENCING ASSOCIATED WORK, ALLOWING REQUIRED CORRECTIONS TO BE PERFORMED. ANY ATTACHED ENGINEERING OR LOCAL BUILDING AUTHORITY NOTATIONS SUPERSEDE AND OVERRIDE MATERIALS, FASTENING, NAILING SCHEDULES AND CONSTRUCTION PROCEDURES PRESENTED IN PLAN, SECTION OR DETAIL VIEWS AND SHALL TAKE PRECEDENCE OVER ANYTHING SHOWN, DESCRIBED OR IMPLIED. THE CONTRACTOR ASSUMES LIABILITY FOR ANY PROBLEMS THAT MAY ARISE DUE TO NON-COMPLIANCE. USE OF THESE PLANS CONSTITUTES COMPLIANCE WITH THE ABOVE TERMS.</description>
      <pubDate>Fri, 20 Jun 2008 16:02:01 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117070#M18811</guid>
      <dc:creator>Jefferson</dc:creator>
      <dc:date>2008-06-20T16:02:01Z</dc:date>
    </item>
    <item>
      <title>Re: construction doc disclaimer language?</title>
      <link>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117071#M18812</link>
      <description>Hello Jeff,&lt;BR /&gt;
You and others might be interested in the article at this address.&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="http://www.aia.org/aiarchitect/thisweek05/tw0902/tw0902bp_riskmgmt.cfm" target="_blank"&gt;&lt;LINK_TEXT text="http://www.aia.org/aiarchitect/thisweek ... skmgmt.cfm"&gt;http://www.aia.org/aiarchitect/thisweek05/tw0902/tw0902bp_riskmgmt.cfm&lt;/LINK_TEXT&gt;&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
Peter Devlin</description>
      <pubDate>Sat, 21 Jun 2008 20:06:12 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117071#M18812</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2008-06-21T20:06:12Z</dc:date>
    </item>
    <item>
      <title>Re: construction doc disclaimer language?</title>
      <link>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117072#M18813</link>
      <description>This may be an instance where the advice of an attorney familiar with construction law could be very helpful. Your client hires you, a professional, to do your work. Why not engage the services of a professional skilled in the formulation of protective language to do his/her work?&lt;BR /&gt;
&lt;BR /&gt;
The use of some parts of the body of AIA documents may not be a bad thing, either. There is a family of agreements tailored to the needs of "small projects" that are not too onerous, yet offer a modicum of protection to all parties in the process of designing and building projects.</description>
      <pubDate>Sun, 22 Jun 2008 01:13:00 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117072#M18813</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2008-06-22T01:13:00Z</dc:date>
    </item>
    <item>
      <title>Re: construction doc disclaimer language?</title>
      <link>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117073#M18814</link>
      <description>Thanks Jefferson for bringing this up.&lt;BR /&gt;
Very brave; you are to be commended.   &lt;BR /&gt;
Maybe the most important topic ever, for architects   &lt;BR /&gt;
and designers.   &lt;BR /&gt;
Without a great agreement you might not even want to draw the &lt;BR /&gt;
first line. &lt;BR /&gt;
After having been a contractor/designer for 30yrs in Calif.   &lt;BR /&gt;
I must say, my Terms and Conditions, along with what is on   &lt;BR /&gt;
plans, is very strong, (equivalent to 9 full typed pages) much too long to post here,  &lt;BR /&gt;
with the most important items said a least  twice and written in plain "english".   &lt;BR /&gt;
Also in your agreement to owner, call out that the contractor is to    &lt;BR /&gt;
read and agree to all the conditions set forth in you agreement with owner &lt;BR /&gt;
as pertains to plans.  Also call this out on plans. &lt;BR /&gt;
However, the most important statement is that "if any part of   &lt;BR /&gt;
these "terms and conditions/plans" are found to be invalid, illegal,(etc)   &lt;BR /&gt;
that particular "term and or condition" shall be as if it does not exist and all other provisions set forth herein, shall be fully enforceable.  &lt;BR /&gt;
Next most important thing, is that ALL discrepancies (not just dimensions) shall be brought to the attention of the architect/designer, IN WRITING!  (That means words, not drawings), because that is my responsibility. &lt;BR /&gt;
In my opinion, that is enforceable, and should they not provide clear, written-down issues they have   &lt;BR /&gt;
found, and &lt;U&gt;legally transferred them to me&lt;/U&gt;, then that's on them. &lt;BR /&gt;
I can’t go around chasing, he said, she said, he said,…….But you must spell this out. &lt;BR /&gt;
Of course, very, very, abbreviated with all legal disclaimers, that I’m not a lawyer, bla, bla, bla.&lt;BR /&gt;
"all parties" is not my concern, protect your shelf, for no-one else will!&lt;BR /&gt;
I’m sure someone will disagree with things I've said here, but what the hell, fire away. &lt;BR /&gt;
Enough said for now, maybe more latter. &lt;BR /&gt;
Peter, great article. &lt;BR /&gt;
Think I'll add some of those ideas also.&lt;BR /&gt;
Bier</description>
      <pubDate>Mon, 23 Jun 2008 00:53:22 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/construction-doc-disclaimer-language/m-p/117073#M18814</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2008-06-23T00:53:22Z</dc:date>
    </item>
  </channel>
</rss>

