<?xml version="1.0" encoding="iso-8859-1"?>

<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/"
 >
<channel>
<title>Ahlers &amp; Cressman Lawyers</title>
<link>http://www.ac-lawyers.com/blogs.php?topic=8</link>
<description>Delay Claims</description>
<language>en-us</language>
<pubDate>Tue, 02 Mar 2010 21:10:42 GMT</pubDate>
<item>
<title>Bell BCI Co. v. United States - Release of Cumulative Impact Claims</title>
<link>http://www.ac-lawyers.com/blog_article.php?article=157</link>
<description><![CDATA[ <p>Bell involved a construction contract under which the government issued an extensive series of change orders. Following the first of those change orders, the parties executed Modification 93, which stated in part the increased contract amount set forth in the Modification represented "full and equitable adjustment for the remaining direct and indirect costs of the [changed work] . . . and full and equitable adjustment for all delays resulting from any and all Government changes transmitted to the Contractor on or before August 31, 2000." Modification 93 also included the following "release" language: "the Modification agreed to herein is a fair and equitable adjustment for the Contractor's direct and indirect costs. This Modification provides full compensation for the changed work, including both Contract costs and Contract time. The Contractor hereby releases the Government, including all liability under the Contract for further equitable adjustment attributable to the Modification." </p> 
]]></description>
<pubDate>Mon, 17 Aug 2009 00:00:00 GMT</pubDate>
 <dc:creator>John P. Ahlers</dc:creator>
 <content:encoded><![CDATA[ <p>Bell involved a construction contract under which the government issued an extensive series of change orders. Following the first of those change orders, the parties executed Modification 93, which stated in part the increased contract amount set forth in the Modification represented "full and equitable adjustment for the remaining direct and indirect costs of the [changed work] . . . and full and equitable adjustment for all delays resulting from any and all Government changes transmitted to the Contractor on or before August 31, 2000." Modification 93 also included the following "release" language: "the Modification agreed to herein is a fair and equitable adjustment for the Contractor's direct and indirect costs. This Modification provides full compensation for the changed work, including both Contract costs and Contract time. The Contractor hereby releases the Government, including all liability under the Contract for further equitable adjustment attributable to the Modification." </p><p>Following a trial on the merits, the Court of Federal Claims (COFC) awarded Bell $2,058,456 for "labor inefficiency costs attributable to the cumulative impact of the [series of government] changes. <i>Bell BCI Co., v. </i><i>United States</i><i>, </i>81 Fed.Cl. 617, 619, (2008). As noted by the Federal Circuit: </p><p>"In finding for <i>Bell</i><i>, </i>the Court of Federal Claims drew a distinction between a "delay" claim and a "disruption" for "cumulative impact" claim . . . ." </p><p>The Court then looked to the contract's "Changes" clause and determined that "[u]nless provided otherwise, the bi-lateral modifications will compensate the Contractor for the changed work, but no for the impact for the multiple change orders on the unchanged work." </p><p>Because in the court's view, Modification 93 did not "provide otherwise," the Court concluded that Bell did release its cumulative impact claims. The Federal Circuit reversed the COFC, however, the Federal Circuit examined the plain language of the release and, after determining that its terms were ambiguous, ruled that "Bell released the government from any <i>and all</i> liability for equitable adjustments attributable to Modification 93." The Federal Circuit then remanded the issue to the COFC to determine "which of Bell's cumulative impact claims, if any, are "attributable to" modifications other than those modifications that contain the release language discussed above. </p><p>To read the case click <a target="_blank" href="http://www.cafc.uscourts.gov/opinions/08-5087.pdf">here</a> </p> 
]]></content:encoded>
<guid>http://www.ac-lawyers.com/blog_article.php?article=157</guid>
</item>
<item>
<title>Idaho Court denies GC's claim against project engineer</title>
<link>http://www.ac-lawyers.com/blog_article.php?article=101</link>
<description><![CDATA[ In <a target="_blank" href="/_fetch.php?file=beco.pdf">Beco Constr. v. J-U-B Engineers, Inc</a>., the Idaho Supreme Court denied a general contractor's claim against the project engineer on a public project located in Pocatello.  The general had alleged that the engineer's improper conduct and delays resulted in delays to the general's work on the project and liquidated damages assessed against the general contractor.  The general had alleged that the engineer intentionally interfered with the general's contract with the owner.  The Supreme Court denied the general's intentional interference claim because the engineer, as an agent of the owner, was acting on behalf of the owner.   
]]></description>
<pubDate>Wed, 07 May 2008 00:00:00 GMT</pubDate>
 <dc:creator>Brett Hill</dc:creator>
 <content:encoded><![CDATA[ <p>The project involved the development of an area of downtown Pocatello, and the scope of work for Beco Construction, the general contractor, included street and sidewalk improvements as well as installation of utilities.  The contract was awarded to Beco by the City of Pocatello.  The City also hired J-U-B Engineers to serve as the project engineer.  J-U-B was also tasked with administering the City's contract with Beco, and J-U-B's role was described in the City/Beco contract. </p><p>During the course of the project, Beco alleged that J-U-B improperly tested asphalt with the intent of promoting failed tests, unreasonably shut down the project causing delays to Beco, and unreasonably delayed the commencement of the project.  Beco alleged breach of contract, negligence, and intentional interference with contract claims against J-U-B.  Beco's breach of contract claim and negligence claims against Beco were dismissed early in the case, and the only issue on appeal was whether Beco could make a claim for intentional interference against J-U-B. </p><p>The Idaho Supreme Court reasoned that Beco could not make a claim against J-U-B for intentional interference.  In Idaho, a party cannot make a claim for intentional interference against another party to the same contract.  The cause of action is only applicable when a third party interferes with one party's contract with another.  In this case, J-U-B was acting as an agent of the City on the project because it was designated as the owner's representative and tasked with administering the general contract.  The Court reasoned that because J-U-B was the City's agent, and the actions that were the basis of Beco's claims occurred during J-U-B's administration of the contract, J-U-B was not a third party to the general contract, and therefore, Beco could not make a claim against J-U-B for intentional interference.  </p><p>The case represents the difficult task that general contractors have in making claims against the design professionals on projects.  Because the contractor does not have a contract with the design professional, it cannot allege breach of contract against the design professional.  In this case, Beco's sole remedy was to sue the City for breach of contract due to the actions caused by its agent, J-U-B.  </p><p>Court opinion:  <a target="_blank" href="/_fetch.php?file=beco.pdf">Beco Constr. Co. v. J-U-B Engineers, Inc.</a> </p> 
]]></content:encoded>
<guid>http://www.ac-lawyers.com/blog_article.php?article=101</guid>
</item>
<item>
<title>“Pay When Paid” vs. “Pay If Paid” Clauses: Mystery vs. Myth</title>
<link>http://www.ac-lawyers.com/blog_article.php?article=82</link>
<description><![CDATA[ A "Pay When Paid" clause provides that payment to the Subcontractor will be made within a certain period of time after the contractor has been paid by the owner, rather than within a period of time after the subcontractor has performed its work.  Generally, "Pay When Paid" clauses are interpreted to merely <b>postpone</b> payment for a <b>reasonable</b> time.  "Pay When Paid" clauses do not excuse an unpaid prime contractor from all obligations to pay the valid invoices of subcontractors and suppliers.   
]]></description>
<pubDate>Mon, 17 Mar 2008 12:27:09 GMT</pubDate>
 <dc:creator>John P. Ahlers</dc:creator>
 <content:encoded><![CDATA[ <p>A "Pay When Paid" clause provides that payment to the Subcontractor will be made within a certain period of time after the contractor has been paid by the owner, rather than within a period of time after the subcontractor has performed its work.  Generally, "Pay When Paid" clauses are interpreted to merely <b>postpone</b> payment for a <b>reasonable</b> time.  "Pay When Paid" clauses do not excuse an unpaid prime contractor from all obligations to pay the valid invoices of subcontractors and suppliers.  An example of a "Pay When Paid" clause is: </p><p><b>Payment Not Contingent on Owner Payment</b>.  It is agreed that payment by Contractor to Subcontractor hereunder is not due until ten (10) days after payment has been received by Contractor from Owner, or until the passage of a reasonable time from when payment from Owner is due, whichever is sooner.  "Reasonable time" as used herein shall not exceed ninety (90) days.  </p><p>By contrast, a "Pay If Paid" clause establishes that payment by the Owner to the Contractor is a <b>condition precedent </b>to the Contractor's duty to pay its Subcontractors and Suppliers.  To be enforceable, the assignment of the risk of non-payment must be clear and unambiguous.  Any doubt will be construed against the prime contractor.  </p><p><b>Payment Contingent on Owner Payment</b>.  It is agreed that as a condition precedent to any payment by Contractor to Subcontractor hereunder, the Contractor must first receive payment from the Owner for the work of Subcontractor for which payment is sought.  Subcontractor specifically agrees that it is relying on the Owner's credit (not the Contractor's) payment.  Subcontractor specifically accepts the risk of non&amp;#8209;payment by Owner.  </p><ul><li><b><i>"Pay If Paid" Clauses Are Not Favored By Courts Or Legislators: </i></b></li></ul><p>The New York Court of Appeals refused to enforce a "Pay If Paid" clause on public policy grounds.  The court reached its result by noting first that the Subcontractor's lien right depended upon its contract rights and then observed that a "Pay If Paid" clause could indefinitely suspend a Subcontractor's contractual right to payment.  It, therefore, concluded that a "Pay If Paid" clause amounted to a forfeiture of the Subcontractor's lien right and will quote <i>West Fair Electric Contractors v. Aetna Casualty &amp; Surety Co.</i>, 666 NE 2d 967, 972 (N.Y. 1995).  Courts in California and Florida have reached similar conclusions.  Other states have addressed the conditional payment provisions by way of legislation.  Payment by an Owner to a Contractor is not allowed to be a condition precedent for payment to a Subcontractor in the states of North Carolina, Wisconsin, Maryland, Illinois and Missouri.  </p><ul><li><b><i>Bonding Companies May Not Be Able To Rely On The General Contractor's Pay If Paid Clause:</i></b></li></ul><p>Bonding companies cannot enforce a subcontract's "Pay If Paid" clause and must compensate an unpaid Subcontractor when the General Contractor has not been paid by the Owner.  <i>See Moore Brothers Co. v. Brown &amp; Root, Inc.</i>, 207 F.3d 717 (4<sup>th</sup> Cir. 2000) and <i>U.S.</i><i> Ex Rel. Walton Technology v. Weststar Engineering, Inc.</i>, 290 F.3d 1199 (9<sup>th</sup> Cir. 2002).  Courts have hinted, however, that if the bonding companies insert the "Pay If Paid" language in the payment bond itself, the surety will be permitted to delay payment until the General Contractor has been paid by the Owner.  Another way for General Contractors to protect their bonding companies is to specifically refer to the payment bond surety in "Pay If Paid" clause itself.  Finally, General Contractors should include an express Miller Act or Little Miller Act (state bond claim act) waiver as part of the "Pay If Paid" provision.  Miller Act waivers are generally not valid unless they mention the Miller Act by name.  </p><ul><li><b><i>Prevention Doctrine</i></b></li></ul><p>Finally, where the General Contractors' own actions or in-actions contribute to the non&amp;#8209;occurrence of a condition precedent, the condition precedent to pay out is deemed waived or excused - this is known as the "Prevention Doctrine."  <i>Moore Brothers Co. v. Brown &amp; Root, Inc.</i>, 207 F.3d 717 (2000).  The Prevention Doctrine provides that the general contractor cannot cause the non-payment to occur and then rely on that same condition as a basis not to pay its Subcontractor.  If the Owner fails to pay the general contractor because of the general contractor's own fault, the general contractor will not be able to rely on the "Pay If Paid" clause to withhold payment to the subcontractor. </p> 
]]></content:encoded>
<guid>http://www.ac-lawyers.com/blog_article.php?article=82</guid>
</item>
<item>
<title>Impact of Shift Work on Labor Productivity for Labor Intensive Contractors</title>
<link>http://www.ac-lawyers.com/blog_article.php?article=81</link>
<description><![CDATA[ <p>Generally, a contractor has three options in accelerating a construction schedule: working longer hours, increasing the number of workers, or creating an additional shift of workers. </p> 
]]></description>
<pubDate>Fri, 14 Mar 2008 00:00:00 GMT</pubDate>
 <dc:creator>John P. Ahlers</dc:creator>
 <content:encoded><![CDATA[ <p>Generally, a contractor has three options in accelerating a construction schedule: working longer hours, increasing the number of workers, or creating an additional shift of workers. </p><p>Although there has been a significant amount of research conducted on scheduled overtime on constructional labor productivity, little information exists addressing the labor inefficiency associated with working a second shift.  University of Wisconsin researchers have come up with a formula and table to estimate the productivity loss of a second shift.  Their conclusion is that small amounts of well organized shift work can serve as a very effective response to schedule acceleration.  Based on the data analyzed, the researchers determined that the productivity loss and percentage shift work could be expressed as follows: </p><p>Productivity Loss = 0.22052 + 0.07152 ln (% shift work expressed as a decimal). </p><p>Figure three is a graphical representation of the equation and table four shows the productivity multiplier of shift work depending on the amount of shift work.  For example, assume the project has a budgeted man hour requirement of 30,000 hours.  Due to increased scope changes the contractor employs a second shift.  The total number of shift hours is 6,000 hours, or 20% shift work. </p><p>Inserting the 20% shift work into the formula as a decimal: </p><p>Productivity loss = 0.22052 + 0.07152 ln (0.2) = 0.1054 </p><p>Multiplying the productivity loss by the total project hours spent in shift work (6,000 hours on the second shift and overlapping with 6,000 on the first shift equals 12,000 hours): </p><p>Efficiency loss = 12,000 hours x 0.1054 = 12,600 hours of productivity lost. </p><p>The equation can be used as a beginning point for negotiations between owners and contractors for adjustments due to an owner-initiated schedule acceleration and compression.  The formula also allows a contractor to select the most cost effective option (i.e., over-manning, over-time and shift work) when schedule acceleration is required.  The positive effects of shift work on productivity makes it the preferable option in place of over&amp;#8209;time or over&amp;#8209;manning.  The major source of labor inefficiency in shift work stems from overlapping the first and second shift, thus the authors recommend to overlap supervision of the two shifts by asking the supervisors of the first shift to stay longer and the supervisors of the second shift to arrive earlier.  They also recommend, if at all possible, to assign completely different tasks at different locations to the second shift workers than those of the first shift.  </p><p><i>Journal of Construction Engineering and Management, March 2008.  Awad S. Hanna, Impact of Shift Work on Labor Productivity for Labor Intensive Contractor. </i></p><p><em><a href="{SG_URL_PREFIX}_fetch.php?file=Labor-Intensive-Contractors.pdf">Click here for additional labor productivity information and charts</a></em></p> 
]]></content:encoded>
<guid>http://www.ac-lawyers.com/blog_article.php?article=81</guid>
</item>
<item>
<title>Delays by a Contractor’s Supplier Do Not Fall Within the Prime Contract's Force Majeure Clause</title>
<link>http://www.ac-lawyers.com/blog_article.php?article=63</link>
<description><![CDATA[ <p>During the construction of a tower and fiber optic line, the contractor was delayed by its supplier, causing the contractor to incur an assessment of liquidated damages.  The prime contract <i>force majeure</i> clause defined a <i>force majeure </i>event as: "Any reasonable delay which is due exclusively to causes <b>beyond the control and without the fault of contractor . . ."</b> (emphasis added).  According to the general contractor, it was entitled to a time extension because its supplier delayed the project.  The delay of the supplier was "beyond the control and without the fault of" the contractor. </p> 
]]></description>
<pubDate>Tue, 26 Feb 2008 14:16:38 GMT</pubDate>
 <dc:creator>John P. Ahlers</dc:creator>
 <content:encoded><![CDATA[ <p>During the construction of a tower and fiber optic line, the contractor was delayed by its supplier, causing the contractor to incur an assessment of liquidated damages.  The prime contract <i>force majeure</i> clause defined a <i>force majeure </i>event as: "Any reasonable delay which is due exclusively to causes <b>beyond the control and without the fault of contractor . . ."</b> (emphasis added).  According to the general contractor, it was entitled to a time extension because its supplier delayed the project.  The delay of the supplier was "beyond the control and without the fault of" the contractor. </p><p>The court held as a matter of law that the delay of a subcontractor was not a <i>force majeure </i>event, reasoning that a prime contractor could excuse itself from responsibility for delay simply by subcontracting the work out.  The court reasoned this interpretation would give a perverse incentive to contractors to outsource work and supplies, and would undermine an owner's reasonable entitlement to legal remedies (owners normally do not have third party beneficiary rights against subcontractors and suppliers).  On the other hand, if the general contractor remains liable for its suppliers' delays, the general contractor can transfer that liability to the supplier with whom it is in privity.  The general contractor is the party in the best position to avoid supplier delays by paying the supplier a higher price in obtaining a delay damages clause in its subcontracts.  The court held while the general contractor was not at fault in its choice of supplier, the general contractor is nevertheless responsible to the Owner for the supplier's delays when those delays are not themselves excused by a <i>force majeure </i>event. </p><p><a target="_blank" href="/_fetch.php?file=Hutton-Contracting-Co.-Inc.-v.-City-of-Coffeyville.pdf"><i>Hutton Contracting Co., Inc. v. </i>City<i> of </i><i>Coffeyville</i><i>, </i>487 F.3d 772 (10<sup>th</sup> Circ. 2007)</a> </p> 
]]></content:encoded>
<guid>http://www.ac-lawyers.com/blog_article.php?article=63</guid>
</item>
<item>
<title>American Safety v. City of Olympia:  Supreme Court Affirms and Clarifies Mike M. Johnson</title>
<link>http://www.ac-lawyers.com/blog_article.php?article=51</link>
<description><![CDATA[ Last month, the Washington State Supreme Court affirmed its holding in Mike M. Johnson and reversed the Division 2 Court of Appeals in Am. Safety Cas. Ins. Co. v. City of Olympia, __ Wn.2d __, __ P.3d. __ (2007). The case again demonstrates the Washington State Supreme Court's position that contractors must strictly comply with the notice and claim procedures in their contracts, absent an "unequivocal" waiver of those procedures by the other party to the contract.  
]]></description>
<pubDate>Wed, 02 Jan 2008 16:19:56 GMT</pubDate>
 <dc:creator>Ryan Sternoff</dc:creator>
 <content:encoded><![CDATA[ <p>In the 2003 Mike M. Johnson decision the Supreme Court held that absent waiver, failure to strictly comply with claims procedures in construction contracts bars relief and that waiver by conduct "requires unequivocal acts of conduct evidencing an intent to waive." Mike M. Johnson, Inc. v. Spokane County, 150 Wn.2d 375, 391, 78 P.3d 161 (2003). American Safety successfully argued before the Court of Appeals that its case was distinguishable from Mike M. Johnson and sufficient to resist summary judgment because the parties engaged in continued negotiations and the City only reserved its right to demand compliance with the contractual claim provisions on three separate occasions. </p><p>The Supreme Court reversed, and emphasized that, at most, the City's actions constituted "equivocal" evidence of waiver. "Equivocal conduct by its definition cannot be unequivocal" as required by Mike M. Johnson. Because the City on occasion expressly asserted it was not waiving its contractual defenses no juror could find the City unequivocally did the exact opposite. The Court further affirmed Mike M. Johnson and held continued settlement negotiations will not establish waiver, as such a finding would frustrate the settlement process. </p> 
]]></content:encoded>
<guid>http://www.ac-lawyers.com/blog_article.php?article=51</guid>
</item>
<item>
<title>Flour v. Walter - Severin Doctrine in WA?</title>
<link>http://www.ac-lawyers.com/blog_article.php?article=48</link>
<description><![CDATA[ The case had a complicated procedural history and facts are largely irrelevant for most of us, but there is one issue that may appeal to prime contractors. The Division I trial court applied the Severin doctrine to dismiss Flour's attempt to assert its subcontractor's claim against the owner.  
]]></description>
<pubDate>Fri, 28 Dec 2007 18:52:09 GMT</pubDate>
 <dc:creator>Brett Hill</dc:creator>
 <content:encoded><![CDATA[ The Severin doctrine is taken from federal authorities that hold generally that a prime contractor cannot assert a claim against the government unless the prime has either reimbursed the sub for the damages or remains liable for such reimbursement in the future. In the Flour case, the trial court dismissed Flour's claim against the owner under the Severin doctrine because Flour apparently had been wholly released from liability by Walter.  
]]></content:encoded>
<guid>http://www.ac-lawyers.com/blog_article.php?article=48</guid>
</item>
<item>
<title>Mike M. Johnson v. Spokane County - Contract Notice and Claim clauses are strictly enforceable</title>
<link>http://www.ac-lawyers.com/blog_article.php?article=33</link>
<description><![CDATA[ <p>The seminal case in Washington regarding change orders and the enforceability of notice provisions in construction contracts.  The Washington State Supreme Court held contractual notice provisions are strictly enforceable unless the clause has been waived by the party who benefits from the clause.  The waiver must be "clear and unequivocal" for it to be valid.  </p> 
]]></description>
<pubDate>Wed, 02 Jan 2008 17:47:58 GMT</pubDate>
 <dc:creator>Brett Hill</dc:creator>
 <content:encoded><![CDATA[ In Mike M. Johnson, Inc. v. Spokane County, 150 Wn.2d 375, 78 P.3d 161 (2003), the Washington State Supreme Court held that actual notice is not an exception to compliance with mandatory contractual protest and claim provisions. The Court went on to hold that a party may waive such provisions for its benefit, but waiver by its conduct requires unequivocal acts or conduct evidencing an intent to waive. In April 1998, Spokane County awarded Mike M. Johnson, Inc. ("MMJ") contracts to construct two sewer projects, the Apple Valley Sewer Project and the Wolfland Project. The contracts incorporated WSDOT's Standard Specifications for Road, Bridge and Municipal Construction. Both the County and MMJ anticipated that MMJ would perform the projects in sequence. Construction of the Apple Valley Project was to begin on May 27, 1998, and be completed in 88 working days, and construction of the Wolfland Project was to begin on June 29, 1998, and last 70 working days. At the preconstruction conference on April 23, 1998, the County informed MMJ that a road improvement district project was in progress to redesign Seventh Avenue, a roadway in the Apple Valley Project. The redesign would not affect the sewer installation, but would double the width of Seventh Avenue and add gutters and curbs. MMJ began construction on the Apple Valley Project, starting on Fourth Avenue, with a plan to follow with Sixth Avenue and then Seventh Avenue. On June 4, 1998, the County submitted the revised design of Seventh Avenue to MMJ and issued Change Order 3 which required MMJ to widen Seventh Avenue and change the elevation and grade. The change order proposed to increase MMJ's compensation by $69,319, and add eight working days to the project. MMJ did not object or protest the design change, proposed compensation, or altered schedule, and began the work under Change Order 3. In late June, MMJ began subgrade preparations for the roadway on Seventh Avenue, and encountered buried U.S. West phone lines, which were not shown on the drawings furnished by the County. MMJ's work on Seventh Avenue came to a halt while the County and U.S. West worked out the utility conflict. Both contracts incorporated Standard Specification § 1-04.5 which required written notice of protest of work required by a change order, other written order, or oral order from the engineer before doing any work, and supplemental information within 15 calendar days providing: (a) the date of the protested order; (b) the nature and circumstances which caused the protest; (c) the contract revisions that support the protest; (d) the estimated dollar cost, if any, of the protested work and how that estimate was determined; and (e) an analysis of the progress schedule showing the schedule change or disruption if the contractor is asserting a schedule change or disruption. The contracts further provided that MMJ accepted all requirements of a change order by endorsing it, writing a separate acceptance, or by not protesting it as required by § 1-04.5. Failure to protest constituted "full payment and final acceptance of all claims for contract time and for all costs of any kind, including costs of delays, related to any work either covered or effected by the change." Standard Specification § 1-04.5. In addition, the contracts referenced Standard Specification § 1-09.11, which provided a mandatory formal claim procedure if § 1&amp;#8209;04.5 failed to resolve a dispute. Full compliance by MMJ with § 1-09.11 was a contractual condition precedent to MMJ's right to seek judicial relief. MMJ never filed a certified claim as required by § 1-09.11. MMJ did not file a written protest nor provide the supplemental information within 15 days as required by § 1-04.5. MMJ, by correspondence, did advise the County that it believed it was entitled to additional compensation. After MMJ struck the unanticipated buried phone lines in Seventh Avenue, the County verbally instructed MMJ to stop work until the County could redesign the project. This prevented MMJ from starting work on other streets during the approximately six weeks it took to complete its redesign. When MMJ sought to do work on other streets to try to keep on schedule, the County forced MMJ to quit. On August 7, 1998, the redesign was complete, and the County told MMJ to go back to work. However, a week later, on August 14, it was discovered that the County's design grades were erroneous. The County required MMJ to shut down again while the County corrected the problem. Daily and other periodic meetings took place between MMJ personnel and County personnel. MMJ later filed a lawsuit seeking compensation for its extra work. The County moved for summary judgment on the grounds that MMJ's claims for additional compensation were barred because MMJ failed to comply with the contractual protest and claim provisions. The trial court granted the County's motion and dismissed MMJ's clams. MMJ appealed and the Division Three Court of Appeals ruled in favor of MMJ on the ground that issues of fact existed regarding whether the County's "actual notice" of MMJ's claims excused MMJ from complying with the mandatory contractual protest and claim procedures. The County then appealed to the Washington State Supreme Court. Justice Madsen wrote the Court's five-to-four majority opinion. She was joined in that opinion by Justices Alexander, Bridge, Owens, and Fairhurst. The majority stated that "Washington law generally requires contractors to follow contractual notice provisions unless those procedures are waived," citing Absher Construction Co. v. Kent School District #415, 77 Wn. App. 137, 152, 890 P.2d 1071 (1995). 150 Wn.2d at 386. The majority went on and stated that: A party to a contract may waive a contract provision, which is meant for its benefit, and may imply waiver through its conduct. [Citations omitted.] Waiver by conduct, however, "requires unequivocal acts of conduct evidencing an intent to waive." Id. at 386. In rendering its decision, the majority addressed MMJ's contention that when an owner has actual notice of a contractor's protest or claim, that notice, in and of itself, excuses the contractor from complying with mandatory contractual protest and claims procedures, citing Bignold v. King County, 65 Wn.2d 817, 822, 399 P.2d 611 (1965). The majority disagreed, and with regard to Bignold stated: Rather, it was the owner's knowledge of the change conditions coupled with its subsequent direction to proceed with the extra work that evidenced its intent to waive enforcement of the written notice requirements under the contract. Id. at 388. The majority obviously found no direction to proceed from Spokane County to MMJ. The majority went on and found that the County had not waived MMJ's compliance with the contractual protest and claims provisions through its conduct. Important to the majority's conclusion in this regard was the fact that the County repeatedly asserted that it did not intend to waive any claim or defense or any contract provision. The Court rejected MMJ's contention that the County's continued negotiations evidenced the County's intent to waive MMJ's compliance with the contractual provisions. Justice Chambers provided an informative and vigorous dissent, which dissent was joined in by Justices Johnson, Sanders, and Ireland. Since this opinion was released there have been a number of attempts in the Legislature to create new law in response to this case, none of which have been successful. Posted in Change Orders, Claim/Notice Issues  
]]></content:encoded>
<guid>http://www.ac-lawyers.com/blog_article.php?article=33</guid>
</item>
<item>
<title>Biwell Construction v. City of Seattle</title>
<link>http://www.ac-lawyers.com/blog_article.php?article=27</link>
<description><![CDATA[ In Biwell Construction v. City of Seattle, 1005 WL 763250 (Wash. App. Div. 1 April 4, 2005) (Unpublished Opinion), the Division One Court of Appeals held that a trial court improperly dismissed a claim for unpaid contract balance for failing to comply with the contract's claim requirements and the time limitation for suit provision.  
]]></description>
<pubDate>Thu, 03 Jan 2008 11:04:45 GMT</pubDate>
 <dc:creator>Brett Hill</dc:creator>
 <content:encoded><![CDATA[ Biwell Construction commenced suit for a delay claim in the amount of $13,217.89 and its unpaid contract balance, $34,893, against the City of Seattle. The contract provided that if Biwell's performance was delayed, it had five days following the event giving rise to the delay to request a time extension, and 20 days to submit documentation supporting the request and any delay damages. The contract provided that any failure to comply with this procedure constituted a waiver of delay damages. If the request by Biwell was denied, the contract further required a protest, a claim, and mediation prior to filing suit. The City moved for summary judgment, arguing that Biwell failed to comply with the contract's dispute resolution procedures. The trial court dismissed Biwell's claims. On appeal, Biwell did not challenge the dismissal of its delay claim. However, Biwell did challenge the dismissal of its claim for money due under the contract. The City could not point to any dispute resolution provisions, similar to those that barred Biwell's delay claim, that would bar Biwell's claim for its contract balance. The City did contend that Biwell's claims were barred because it did not file suit within 180 days of the completion date, as required by the contract. The contract defined "completion date" as follows: The date, certified in writing by the Owner, when the Work specified in the Contract Documents is completed and all the obligations of the Contractor under the contract were fulfilled by the Contractor. All documentation required by the Contract and required by law must be furnished by the Contractor before establishment of this date. The City contended that the contract was completed when it terminated Biwell's performance. The Court noted that while this may be true as a practical matter, the "completion date" is defined in specific terms in the contract. The Court found that the record did not support the City's contention that it was entitled to judgment as a matter of law that Biwell failed to timely commence its suit.  
]]></content:encoded>
<guid>http://www.ac-lawyers.com/blog_article.php?article=27</guid>
</item>
</channel>
</rss>