Idaho Falls council reviews staff statement documenting impact-fee appeal for Terrace Gate

Idaho Falls — City officials on a regular council agenda reviewed a staff-drafted statement intended to memorialize the council’s December 18 hearing and decision on an impact-fee appeal tied to the Terrace Gate development.

The draft, staff told council, consolidates the impact-fee administrator’s recommendations and the council direction taken at the December 18 public hearing so the city will have a clear written record if the decision is later questioned. “This documents the recommendations from the city’s impact-fee administrator in regards to the Terrace Gate development,” a council member said during the meeting.

Why it matters: Councilors pressed staff to confirm why the developer’s request for credit related to a right-of-way dedication was denied. “There’s no reference to the denial of the right-of-way request that was in the letter that Director Alexander wrote to them,” Councilor Freeman said, noting the denial was a major point in the earlier hearing. City attorneys and staff responded that the denial rests on a procedural basis — the developer failed to enter into a required written agreement — and that the draft intentionally frames the decision in that broader, procedural term rather than itemizing every denied credit type.

City attorney Zach told the council the only substantive drafting change he recalled was logistical — changing the signature block so the mayor would sign on behalf of council after authorization — and otherwise the body of the document reflects what was discussed. “The only change that I can recall making is, change it from city council signing individually to the mayor signing on behalf after being authorized by city council,” he said.

Officials clarified the difference between credit and reimbursement. Staff and councilors agreed that an impact-fee credit is typically available to offset future development-related fees rather than reimbursing fees already paid: credit applies forward to future phases or future projects, while reimbursement would return money already paid. Staff noted that developer-provided bids offered at the December 18 hearing could be used to satisfy development-agreement terms and that some permits for the project remain under review.

Staff also explained how development agreements and owner-participation agreements (OPAs) are prepared and recorded. A department director described the standard workflow: a consulting engineer requests a development agreement, special conditions are drafted for that development, legal completes the front portion of the agreement, then the document is signed, notarized and recorded with the county so it becomes part of the property record. Councilors asked whether the city records OPAs and how obligations transfer if a project changes hands; staff said they would confirm whether OPAs are routinely recorded and report back.

Because the council heard about cases where a development changed ownership midstream, members discussed offering a nonbinding predevelopment consultation and a short checklist to help new owners identify outstanding obligations recorded against a parcel. Staff supported a limited, nonbinding consultation option — provided the city documents written advice and avoids informal verbal commitments that could later complicate appeals. One councilor suggested a one-page checklist to standardize information given at predevelopment meetings.

No final vote on the statement was recorded during the discussion. Staff indicated the statement and a resolution would be on the council’s agenda for Thursday for formal consideration and any further edits.

Background: The draft statement is intended to preserve the council’s December 18 actions and the rationale for denying certain impact-fee credits. Staff noted the city’s new work-tracking system will need updates to record credits and reimbursements consistently after council action.

What’s next: Council is expected to take formal action on the statement and related resolution on Thursday; staff will also follow up on whether OPAs are recorded and return with a recommended approach to a standardized predevelopment checklist and consultation process.