AMER. SAF. CAS. INS. CO. v. City of Olympia

174 P.3d 54
CourtWashington Supreme Court
DecidedDecember 27, 2007
Docket79001-9
StatusPublished
Cited by9 cases

This text of 174 P.3d 54 (AMER. SAF. CAS. INS. CO. v. City of Olympia) is published on Counsel Stack Legal Research, covering Washington Supreme Court primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
AMER. SAF. CAS. INS. CO. v. City of Olympia, 174 P.3d 54 (Wash. 2007).

Opinion

174 P.3d 54 (2007)

AMERICAN SAFETY CASUALTY INSURANCE COMPANY, a foreign corporation, Respondent,
v.
CITY OF OLYMPIA, Petitioner.

No. 79001-9.

Supreme Court of Washington, En Banc.

December 27, 2007.

*55 BRIDGE, J.

¶ 1 This case arises from a contract dispute between American Safety Casualty Insurance Company (American Safety)[1] and the city of Olympia (City) and the trial court's award of summary judgment in favor of the City.[2] There is no dispute that American Safety did not follow the contract's provisions when it sought additional compensation for work it had performed and that it filed suit after the 180-day time limit established in the contract. However, American Safety argues that the City implicitly waived its right to demand compliance with the contract's provisions when it agreed to negotiate and try to reach a settlement. American Safety argues that the trial court erred in granting summary judgment to the City, and that the Court of Appeals was correct to reverse because an issue of material fact existed as to whether the City waived its contractual defenses. The City maintains that it expressly reserved its rights; that any waiver of rights must be unequivocal; and that, at most, its acts were equivocal and thus did not constitute a waiver. We agree with the City and reverse the Court of Appeals.

I

Facts and Procedural History

¶ 2 In 2000, the City awarded contractor Katspan, Inc. (Katspan) a contract to construct a segment of the LOTT southern connection pipeline project. Under the terms of the contract, the contractor was required to follow the contractual procedures if it wished to file a protest, formal claim, or lawsuit.[3] Katspan agreed that protests to any change orders or compensation issues were to be brought to the attention of the project engineer immediately. If Katspan disagreed with the project engineer's resolution of the protest, it could file an administrative claim. Any cause of action under the contract was to be brought within 180 days of the final acceptance and closeout of the project. Pursuant to the contract, failing to follow the *56 procedures constituted a waiver of the claims. Clerk's Papers (CP) at 47 ("By failing to follow the procedures of this section [Procedure and Protest by the Contractor] and Section 1-09.11 [Disputes and Claims], the Contractor completely waives any claims for protested work."); CP at 55 ("[T]he Contractor's failure to bring suit within the [180-day] time period provided, shall be a complete bar to any such claims or causes of action.").

¶ 3 From the beginning, the City was frustrated with Katspan's work — the City had to direct Katspan to fix deficient work, and Katspan failed to meet the scheduling requirements. On April 2, 2001, the City sent Katspan a letter stating that it considered Katspan to be in breach of the contract, as Katspan had not completed the work according to the time frame established in the contract. The City indicated that, pursuant to the contract, it was entitled to collect liquidated damages from Katspan for the breach. The City also stated that it "reserve[d] its right to demand strict compliance with all other terms of the contract documents, including . . . the required procedure for protest by the Contractor." CP at 338. On April 18, 2001, the City sent Katspan a letter in which the City stated that because Katspan failed to follow the procedures set forth in the contract, it had waived its claims. Katspan never disputed this letter.

¶ 4 When the work was finished, the City began the process of finally accepting the project as complete. On May 10, 2001, the project engineer, Parametrix Inc. (Parametrix), sent Katspan a letter asking Katspan to submit its final cost proposals in order to close out the project. Katspan did not respond. On May 25, 2001, Parametrix sent Katspan another letter, again asking for Katspan to provide the information by June 4 so it could begin the closeout. Katspan responded on June 11, 2001, saying that it was "in the final stages of compiling data" and that the requested information "should be ready shortly." CP at 95. Parametrix did not receive the information, so it reviewed the files and changes to the original contract and computed what it considered to be reasonable costs for the additional work. On June 18, 2001, Parametrix sent Katspan a letter with the change order it prepared to cover the additional work. Parametrix asked Katspan to sign the final payment estimate and return it if it was acceptable. Katspan never responded, and on July 2, 2001, the City sent Katspan a letter stating that if Katspan did not return the final payment request, the City would unilaterally establish final acceptance of the project. The City received no response, and on September 10, 2001, the City unilaterally closed out the project.

¶ 5 On November 26, 2001, American Safety, surety for Katspan,[4] sent the City a "Request for Equitable Adjustment on Southern Connection Pipeline Project" (Request). CP at 116-321. The document did not comply with the standards set out in the contract for filing a claim. American Safety received no response to the Request until March 14, 2002 (more than 180 days after the final acceptance date), when American Safety left a voicemail message for the City's counsel, stating that it had some ideas for "some possible quick solutions." CP at 329.

¶ 6 The City agreed to enter negotiations, but asked American Safety to provide further information so it could determine whether a quick resolution was possible. American Safety subsequently sent the City two three-ring binders of documents; however, it did not include all of the information that the City needed to evaluate the request. On August 1, 2002, the City sent American Safety a letter in which it asked for further documentation. American Safety indicated that it was having trouble obtaining the requested information. On October 2, 2002, the City reiterated that it was willing to negotiate, but that it would not do so unless American Safety could provide adequate backup information for its claims. The City received no response, and on November 12, 2002, sent American Safety a letter in which it stated that "[w]ithout waiving any of its *57 defenses, LOTT has stated several times that it is willing to negotiate these claims in order to come to a quick resolution." CP at 354. The City asked whether American Safety was still interested in negotiations, as the City had received no response from its last request for information.

¶ 7 On January 22, 2003, American Safety informed the City that it had received four or five boxes of documents from Katspan for the City to review. Upon review, the City discovered that some information was still missing. On April 23, 2003, the City sent American Safety yet another letter requesting certain documentation. The City stated that if it did not receive the requested information by May 16, 2003, it would deny American Safety's claim. On May 14, 2003, American Safety wrote to the City that although it believed it had provided sufficient information, "we are presently determining the feasibility of accommodating LOTT's request for supplemental cost information, or creating the equivalent." CP at 368. The documentation never arrived, and on May 16, 2003, the City denied American Safety's Request.

¶ 8 On July 31, 2003, Thomas Presnell, a claims consultant representing American Safety, e-mailed Paul Pedersen, the City's forensic accountant, asking him whether they could meet to discuss the project and the information the City needed to complete its audit.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Calkins v. City of Seattle
Ninth Circuit, 2026
C.A. Carey Corporation, V. City of Snoqualmie
Court of Appeals of Washington, 2024
Graham Contracting, Ltd., V. City Of Federal Way
Court of Appeals of Washington, 2023
Saleh Elgiadi v. Washington State University
Court of Appeals of Washington, 2022
Gary G. Gregg v. JRCC Inc.
Court of Appeals of Washington, 2022
NOVA Contracting, Inc. v. City of Olympia
426 P.3d 685 (Washington Supreme Court, 2018)
Realm, Inc. v. City of Olympia
277 P.3d 679 (Court of Appeals of Washington, 2012)

Cite This Page — Counsel Stack

Bluebook (online)
174 P.3d 54, Counsel Stack Legal Research, https://law.counselstack.com/opinion/amer-saf-cas-ins-co-v-city-of-olympia-wash-2007.