River's Edge Investments, LLC v. City of Bend

2 Defendant City of Bend appeals from a limited judgment that granted

3 partial summary judgment and awarded $142,190 to plaintiff River's Edge Investments,

4 LLC (River's Edge). The resolution of this case depends on whether the terms of a

5 development agreement between the city and River's Edge allowed the city to impose

6 system development charges (SDCs) on River's Edge for its construction of a convention

7 facility. River's Edge contends that the agreement precluded such charges absent a

8 triggering event that did not occur in this case. The city asserts that the agreement

9 expressly allowed it to charge the SDCs. After cross-motions for summary judgment, the

10 trial court concluded that the agreement unambiguously precluded the city from assessing

11 the SDCs at issue. The city appeals, assigning error to the trial court's grant of partial

12 summary judgment to River's Edge and its denial of the city's motion for partial summary

13 judgment. Alternatively, the city maintains that the development agreement is

14 ambiguous and the case should be remanded to the trial court for the consideration of

15 extrinsic evidence of the parties' intent. We conclude that the development agreement

16 unambiguously authorizes the SDCs charged by the city and reverse and remand.

17 The underlying controversy between the parties involves River's Edge's

18 planned unit development (PUD). River's Edge began developing the PUD in the early

19 1980s. The parties entered into the development agreement at issue in 2004; by that

20 point, a portion of the PUD had been developed to include a hotel, golf course, and

21 residences. By 2004, the development plan was revised on several occasions and those

2

1 revisions required the city's approval. The revision and approval process led to disputes

2 and litigation between the parties.

3 In an effort to resolve then-pending litigation and other issues related to

4 River's Edge's planned construction of a convention facility in the PUD, the parties

5 negotiated the development agreement at issue in this case. As required by statute, the

6 city adopted an ordinance approving the development agreement. See ORS 94.508(2)

7 (stating that the governing body must "approve a development agreement * * * by

8 adoption of an ordinance declaring approval"). Ordinance NS-1951 included over 160

9 pages of findings and conclusions related to the PUD and the development agreement.

10 As to what happened next, the parties stipulated to the following facts for

11 purposes of the parties' cross-motions for summary judgment. River's Edge constructed a

12 convention facility within the scope of the development agreement. As a result, the city

13 assessed SDCs in connection with that construction in the amount of $142,190. River's

14 Edge, under protest, paid the SDCs. River's Edge filed suit against the city.

15 As pertinent to this appeal, River's Edge brought a claim alleging that the

16 city had breached the development agreement by imposing the SDCs. River's Edge also

17 sought a declaration under ORS chapter 28 that it is not subject to any exactions in

connection with the PUD except as provided in the development agreement.1 18 The parties

1 River's Edge also brought a claim for unjust enrichment and a takings claim under

Article I, section 18, of the Oregon Constitution and the Fifth and Fourteenth

Amendments to the United States Constitution. Neither of those claims were determined

by the limited judgment under review.

3

filed cross-motions f 1 or summary judgment, and the trial court granted partial summary

2 judgment to River's Edge and denied summary judgment to the city. Accordingly, the

3 court entered judgment awarding damages in the amount of the SDCs paid--$142,190,

4 plus interest. The city appealed.

5 We interpret contract provisions according to a three-step process. Yogman

6 v. Parrott, 325 Or 358, 361-64, 937 P2d 1019 (1997). First, we examine the text of the

7 disputed provisions in the context of the document as a whole. Id. at 361. In doing so,

8 we determine as a matter of law whether the provision is ambiguous. If the words or

9 terms of a contract, in context, are susceptible to more than one reasonable interpretation,

10 they are ambiguous. Pacific First Bank v. New Morgan Park Corp., 319 Or 342, 348,

11 876 P2d 761 (1994). Put another way, a contract is unambiguous "if its meaning is so

12 clear as to preclude doubt by a reasonable person." Deerfield Commodities v. Nerco,

13 Inc., 72 Or App 305, 317, 696 P2d 1096, rev den, 299 Or 314 (1985). If a contract

14 contains provisions that are mutually inconsistent, the contract is ambiguous as to that

15 subject unless the inconsistent provisions can be reconciled in reading the contract as a

16 whole. Madson v. Oregon Conf. of Seventh-Day Adventists, 209 Or App 380, 384, 149

17 P3d 217 (2006). If the provision is unambiguous, our analysis ends and we construe the

18 words of the contract as a matter of law. If the provision is ambiguous, we proceed to the

19 second step of the analysis--the examination of extrinsic evidence of the contracting

20 parties' intent. Yogman, 325 Or at 363. If extrinsic evidence does not provide an answer,

21 we proceed to the third step--reliance on appropriate maxims of construction. Id. at 364.

4

1 We begin with the provisions of the development agreement that are central

2 to the parties' dispute. River's Edge contends that Section 7 eliminates its obligation to

3 pay SDCs until the development agreement expires or it exceeds the "Maximum

Density"2 4 of the PUD as that term is defined in the agreement. The relevant portions of

5 Section 7 state:

6 "7.1 The City shall not require any additional off-site transportation

7 mitigation measures or street exactions pursuant to Street Policy 6 or any

8 other land use ordinance or policy, unless River's Edge applies for, and the

9 City approves, modifications to the River's Edge Village 2004 PUD that

10 would increase the total number of Peak Hour Trips beyond the total

11 number of trips in the Maximum Density, in which case, the development

12 that exceeds the Maximum Density may be subject to additional

13 transportation-related exactions.

14 "7.2 River's Edge shall provide additional mitigation for sewer-related

15 impacts by granting the sewer easements to the City (Exhibits A-11, A-12

16 and A-19). The Sewer Easements, together with prior dedications, satisfies

17 River's Edge's obligation to provide sewer impact mitigation in connection

18 with the Maximum Density, expressed as Equivalent Residential Units

19 ('ERUs'). The City shall require no other sewer-related exactions as a

20 condition of approval, unless River's Edge applies for, and the City

2 The development agreement defines "Maximum Density" as

"an overall density in the River's Edge Village 2004 PUD that puts no

greater burden on the City's infrastructure than the sum of (1) the existing

development in the River's Edge Village PUD, (2) the development

authorized by the 2004 Master Plan Amendments and (3) the Remaining

Development at a stated density. It is expressed quantitatively as 585 sewer

EDU credits, 585 water EDU credits, and 505 PM Peak Trips. By way of

illustration, the 2004 PUD Master Plan Amendments allocate the Maximum

Density to 27,058 square feet of meeting space, 10,300 square feet of

restaurant, 101 condominiums, 388 residential units, and a spa and

recreation center."

The parties agree that "EDU" is a typographical error and was intended to mean "ERU,"

the Equivalent Residential Units referenced in Section 7.2.

5

1 approves, modifications to the River's Edge Village 2004 PUD that would

2 increase the total number of ERUs beyond the total number of ERUs in the

3 Maximum Density, in which case, the development that exceeds the

4 Maximum Density may be subject to additional sewer-related exactions.

5 "7.3 Water supply volume and pressure requirements to serve the River's

6 Edge Village 2004 PUD have been satisfied by dedication, and no further

7 improvements or charges shall be assessed or exacted as a condition of

8 approval, unless River's Edge applies for, and the City approves,

9 modifications to the River's Edge Village 2004 PUD that would increase

10 the total number of ERUs beyond the total number of hookups in the

11 Maximum Density, in which case, the development that exceeds the

12 Maximum Density may be subject to additional water-related exactions.

13 "7.4 Other than as specified in this Agreement, there shall be no additional

14 dedications for public use of land or rights-of-way taken as exactions in any

15 City Permit or on account of any component of the Proposed Development.

16 The City's commitment herein does not extend to exactions that might be

17 required by Third Party governmental entities * * *."

18 The city acknowledges that Section 7 waived some "exactions," but asserts

19 that the SDCs charged in this case were not waived in Section 7. Instead, the city

20 maintains that the SDCs were separately addressed and explicitly required by Section 11.

21 Section 11 states:

22 "11. Fees and Charges. River's Edge and the City shall each pay the filing

23 fees and charges in effect at the time any land use or other applications are

24 filed with the City. When building permit applications are filed for all or

25 any portion of the Proposed Development, the applicant shall pay and the

26 City shall collect the System Development Charges ('SDC') in effect at the

27 time of each application."

28 (Underlining in original.) Thus, the question, as framed by the competing contract

29 provisions, is whether the waiver of exactions in Section 7 exempts River's Edge from

30 paying the SDCs that the city charged under Section 11.

31 The city, on appeal, contends that the exactions referenced in Section 7

6

1 relate only to

2 "property and property rights previously transferred and to-be transferred to

3 the City by [River's Edge] for location of the infrastructure necessary to

4 provide water, sewer, and transportation services to [River's Edge's]

5 developments."

6 The city explains that, when the parties entered into the development agreement, they

7 agreed that River's Edge had "done all that was required to create a sufficient

8 infrastructure, up to the Maximum Density, and no more exactions were required[,]" but,

9 if the development exceeded the agreed upon Maximum Density, the plaintiff would

10 become susceptible to exactions for that portion, as set out in Section 7. The city

11 maintains that SDCs are not the type of exactions specified in Section 7 and that,

12 "separate from the provisions addressing the infrastructure for [River's Edge's]

13 development," the parties addressed River's Edge's obligation to pay SDCs in Section 11.

14 Accordingly, the two provisions can be read in harmony--Section 7 excused River's Edge

15 from contributing the specific types of exactions listed in that section unless Maximum

16 Density was reached, but Section 11 explicitly required River's Edge to pay any

17 applicable SDCs when River's Edge filed building permit applications. The city contends

18 that the interpretation advanced by River's Edge would render Section 11 meaningless.

19 River's Edge's argument on appeal, reduced to its core, is that the

20 development agreement was

21 "intended to provide to the [c]ity all infrastructure exactions necessary to

22 allow development of the River's Edge PUD to the 'Maximum Density,' and

23 to prevent the City from requiring any more exactions, of any kind, related

24 to development of the PUD to the Maximum Density."

7

1 Accordingly, River's Edge asserts that SDCs are exactions of the type waived in Section

2 7. River's Edge explains that the text in Section 11 simply established that, "when

3 charges are due, for building permits or other approvals, the amount of those fees and

4 charges will be determined with reference to then current fees and methodologies, not the

5 fees and methodologies in place in 2004, when the Agreement was executed." (Emphasis

6 in original.)

7 Our analysis begins with the text of the competing provisions in the

8 development agreement. As the city points out, Section 7 references very specific types

9 of exactions--all of which appear to relate to a transfer of property interests or property

10 improvements required as a condition of land use approvals. Section 7.1 addresses "off11

site transportation mitigation measures or street exactions pursuant to Street Policy 6 or

12 any other land use ordinance or policy." The first and second sentences of Section 7.2

13 address "mitigation for sewer-related impacts" in terms of sewer easements and prior

14 dedications being granted to the city by River's Edge. The third sentence of Section 7.2

15 states that "no other sewer-related exactions" shall be required "as a condition of

16 approval" unless the Maximum Density is exceeded, thus explicitly tying the waiver of

17 sewer exactions to those already mentioned--easements and land dedications. Similarly,

18 Section 7.3 refers to "[w]ater supply volume and pressure requirements" that have been

19 satisfied by dedication, and "no further improvements or charges shall be assessed or

20 exacted as a condition of approval." Again, like Sections 7.1 and 7.2, Section 7.3 appears

21 to frame the type of exaction addressed as an easement or dedication. Easements and

8

1 dedications both implicate the transfer of a property interest. See Black's Law Dictionary

2 473 (9th ed 2009) (defining dedication as "[t]he donation of land or creation of an

3 easement for public use"). Section 7.4 summarizes that, "[o]ther than as specified in this

4 Agreement, there shall be no additional dedications for public use of land or rights-of5

way taken as exactions in any City Permit or on account of any component of the

6 Proposed Development." Again, the text of Section 7.4 appears to link the use of the

7 term "exactions" with the dedications and easements granted as part of the development

8 agreement. Moreover, Section 7 precludes exactions that are imposed "pursuant to * * *

9 land use ordinance or policy" or "as a condition of approval." Those references plainly

10 pertain to land use permits or approvals.

11 Nevertheless, standing alone, the references to exactions in Section 7 could

12 possibly be construed to include SDCs because SDCs have been classified as "exactions"

13 for purposes of analyzing state and federal takings law. See Rogers Machinery, Inc. v.

14 Washington County, 181 Or App 369, 394, 45 P3d 966, rev den, 334 Or 492 (2002). Our

15 task, however, is not to look at contract provisions in isolation, but to consider them in

16 the context of the agreement as a whole.

17 The text of Section 11 calls into question the plausibility of River's Edge's

18 proffered interpretation. River's Edge contends that Section 11 is simply a timing

19 provision that establishes that, if the provisions in Section 7 ever trigger additional

20 exactions--i.e., if the River's Edge development exceeds the Maximum Density--the

21 amount of the fees and charges will be determined with reference to the then-current fee

9

1 schedule, not the fee schedule in place in 2004. We fail to see how Section 11 can be

2 read in that way. Although the first sentence of the provision plausibly dictates whether a

3 current fee schedule or the fee schedule in 2004 controls, the second sentence does not

4 appear capable of such a limited effect. The first sentence states that the parties "shall

5 each pay the filing fees and charges in effect at the time any land use or other

6 applications are filed with the City." The second sentence, however, states, "When

7 building permit applications are filed for all or any portion of the Proposed Development,

8 the applicant shall pay and the City shall collect the System Development Charges

9 ('SDC') in effect at the time of each application." That text explicitly dictates whether the

10 applicant pays SDCs ("the applicant shall pay") and when the applicant pays SDCs

11 ("[w]hen building permit applications are filed").

12 Further, Section 11 requires the payment of SDCs imposed as part of

13 "building permit applications." Building permits are governed by a code promulgated by

14 a state agency, ORS 455.020, as opposed to land use ordinances, and are not "land use

15 decisions," ORS 197.015(10)(b)(B) (so stating). They are not imposed as a "condition of

16 [land use] approval." In addition, nothing in Section 11 explicitly limits SDCs to only

17 those building permit applications filed after Maximum Density is reached. Similarly,

18 there is no cross-reference to Section 7 that would link "exactions" referenced in Section

19 7 with the SDCs made payable in Section 11, and "exaction" is not defined in the

20 agreement. Accordingly, nothing explicitly links the SDCs referenced in Section 11 with

21 the use of "exactions" in Section 7.

10

1 Therefore, the text of Sections 7 and 11, when read together, indicate that

2 River's Edge is excused from any further real property interest exactions of the kind

3 identified in Section 7, but they are explicitly required to pay any applicable SDCs when

4 building permit applications are filed. River's Edge's proposed interpretation of Section

5 11 as a statement of "timing" is not plausible based on the specific text of the two

6 sections.

7 Nevertheless, River's Edge cites several other provisions in the

8 development agreement that it contends provides contextual support to its proffered

9 reading of the development agreement. We address each in turn to determine if they call

10 into question what appears to be the unambiguous text of Section 11.

11 First, River's Edge points to several paragraphs in the development

12 agreement that it claims would be rendered nugatory if Section 11 is interpreted to

13 require River's Edge to pay SDCs as a matter of course. For example, River's Edge

14 claims that the agreement's recitals unequivocally recognize that the purpose of the

15 development agreement is to "obtain assurances that the developer's infrastructure

16 obligations have been fully discharged" and to give River's Edge the right to continue

17 development "with no further exactions." River's Edge also cites text in the agreement

18 that indicates that, even in areas of the PUD that are still under design and will remain

19 undeveloped for the time being, the city has determined that "no further street, water,

20 sewer and park trail exactions are due from River's Edge to the extent that the Maximum

21 Density is not exceeded." Those provisions beg the question. Although they fortify the

11

1 conclusion that certain exactions are waived in Section 7, they do not call into question

2 the city's proffered interpretation--that the exactions referenced throughout the agreement

3 are linked to the specific exactions described in Section 7 but do not include the SDCs

4 due when building permit applications were filed.

5 The city offers an additional explanation for the different treatment of

6 "exactions" and SDCs in the development agreement. The city asserts that a PUD is first

7 subject to approval through the land use permitting process--a process that may require

8 certain exactions in the form of dedications and easements. A development agreement is

9 often used to set expectations and obligations during the land use permitting process so

10 that the parties are aware of the exactions and infrastructure needs required for approval

11 during the initial process. In this case, the development agreement addressed those

12 exactions and acknowledged that River's Edge had contributed sufficient property

13 interests to the infrastructure to garner approval in the land use permitting process.

14 However, after the PUD received approval in that process, River's Edge was required to

15 submit building permit applications at the time of actual construction, thus triggering the

16 SDCs. The development agreement recognizes that these are separate processes, in that

17 Section 15 treats the building permit application process as a "future discretionary

18 approval" and explains that the agreement is not intended to limit the city's discretion

19 with regard to future building permit approvals. According to the city, the exactions

20 referenced throughout the development agreement were concerned with the land use

21 permitting process; the agreement separately dealt with SDCs related to the building

12

1 permit applications in Section 11.

2 River's Edge also notes that "Maximum Density" is expressed

3 quantitatively in terms of "Equivalent Residential Units" (ERUs), which is also a term

4 used in calculating SDC credits under the city's ordinances. According to River's Edge,

5 the use of ERUs in the definition of "Maximum Density" evinces an intent to grant it a

6 number of SDC credits that must be taken into account when the city assesses SDCs

7 under Section 11. In other words, SDCs are not assessable until Maximum Density is

8 exceeded. Contrary to River's Edge's contention, the agreement does not contain explicit

9 language establishing SDC credits. The definition of "Maximum Density" is simply a

10 recognizable way of quantifying the concept of "Maximum Density" in the agreement. In

11 light of the text of Section 11 and Section 7, the mere use of ERUs in the definition of

12 "Maximum Density" does not convince us that those sections are inconsistent.

13 In summary, the first step of contract interpretation requires us to determine

14 as a matter of law whether the disputed provisions of the contract are ambiguous. In this

15 case, the explicit text of Section 11 is open to only one plausible interpretation--SDCs are

16 due and payable when building permit applications are filed. There are no other

17 provisions in the contract that reasonably link the SDCs due under Section 11 with the

18 exactions waived in Section 7, so as to make Section 7 mutually inconsistent with Section

19 11. Accordingly, we conclude that the development agreement unambiguously

20 authorizes the SDCs charged by the city in this case.



* * *



See: http://www.publications.ojd.state.or.us/A141661.pdf

21 Reversed and remanded.