Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Zoning Variances Exceptions topic
No spam. Unsubscribe anytime.
Lago Vista board reviews how to handle variances and special exceptions in training session
Summary
At an Aug. 11 special meeting, Lago Vista’s Board of Adjustment received training from City Attorney Brad Bullock on the differences between variances and special exceptions, application completeness, timelines and appeals, plus practical guidance on height exceptions, privacy considerations and floodplain measurement.
Get email alerts on the Zoning Variances Exceptions topic
No spam. Unsubscribe anytime.
Lago Vista’s Board of Adjustment held a special training session Aug. 11 to review the board’s powers and procedures for handling variances and special exceptions, including application requirements, decision timelines and appeal paths.
City Attorney Brad Bullock led the session and told the board that, under the city ordinance, both variances and special exceptions are requests by a property owner to deviate from zoning or development standards. “Variances and special exceptions are really two flavors of the same thing,” Bullock said. He explained that the ordinance treats certain matters (for example, specific accessory‑structure standards and height exceptions up to a defined threshold) under the special‑exception process, while other departures use the variance procedure.
The training emphasized procedural rules and the applicant’s responsibilities. Bullock said applications must be administratively complete before the city’s review timeline begins and that staff should not put incomplete applications on an agenda. “If all of the material is not submitted and that is the duty of the applicant, then they don't get on an agenda,” he said. He told the board that the ordinance gives staff some discretion in determining what ancillary information is necessary, but the applicant bears the burden to provide the information and pay fees.
Bullock reviewed the statutory and ordinance timeframes the board must respect: once a complete application is filed the board normally must consider variances and special exceptions within a 60‑ to 180‑day window. If the board fails to act within that period, an applicant may have legal recourse; failure to act does not automatically approve an application. He also outlined post‑approval time limits: special exceptions lapse after one calendar year if not incorporated into a building permit, and variances lapse in six months unless the applicant timely requests an extension. The board may grant limited extensions in accordance with the ordinance and board action.
The session explained the different appeal routes. For variances, the board serves as the initial appellate body (an applicant denied a variance may file a timely appeal to the BOA and request a rehearing). “For a variance, they get one redo — if they get 75% of the vote, then they get the variance; if you deny it again, they go to court,” Bullock said. Special exceptions do not follow the same BOA appellate path and, if appealed, the remedy is generally to the courts. The training stressed the need for clear findings: the ordinance requires the board to make and record the factual findings that justify granting a variance (for example, that the request is not contrary to the public interest, is not self‑imposed, is not solely financial, and relates to a unique property condition).
Bullock walked the board through standards that commonly arise in practice, including height exceptions and privacy concerns. Under the city code, special exceptions can apply to height or accessory‑structure standards; the ordinance makes a distinction at 35 feet. Requests up to that threshold may be handled as special exceptions under the height provisions, while proposals above 35 feet are reviewed under the variance standard and its heightened “undue‑hardship” analysis. The attorney told the board that applicants must provide accurate, scaled depictions of proposed height (building elevations, finished grades, roof pitches, etc.) and that the board may require supplemental visual materials — for example engineered depictions or modern CAD renderings — to evaluate view and privacy impacts. He cautioned that the board should not impose requirements that exceed the ordinance or that would amount to an unlawful exaction.
Bullock also explained a floodplain measurement rule in the code: when a lot’s highest elevation is at or below the federally designated 100‑year flood elevation, the ordinance allows roof height to be measured from one foot above that flood elevation (an acknowledged accommodation so that mandatory foundation elevation requirements do not automatically deprive an owner of reasonable buildable height). He emphasized this does not permit exceeding the ordinance’s absolute maximum height limits.
On mitigation and conditions, Bullock said the board can impose conditions with approvals — for example, additional landscaping or screening — so long as the conditions do not itself violate the ordinance, create an unlawful exaction or amount to a taking. He contrasted planting vegetation (which can be permissible mitigation) with ordering a structure that the ordinance otherwise prohibits. The board was reminded that any conditions should be tied to the ordinance and the facts of the application.
Board members raised practical concerns including how to handle incomplete applications near the statutory deadlines, whether the board can grant conditional approvals to allow applicants time to supply missing technical materials, and how to treat appeals that include revised plans. Bullock advised that if a dispute arises about administrative completeness and the 60‑ to 180‑day window is approaching, the board can place the item on an agenda and, if it lacks sufficient information, deny without prejudice or approve with conditions; that action satisfies the city’s ministerial duty and protects against an applicant later pursuing court relief. He also noted that if an applicant timely files an appeal of a variance denial, the appeal must be resolved on the rehearing process before court review is allowed.
Bullock repeatedly underscored two practical points for the BOA: (1) variances should be granted sparingly because frequent exceptions can erode the baseline ordinance standards, and (2) the applicant must carry the burden of proof for undue hardship, showing why the ordinance should not apply as written to that unique property. “The purpose of having uniform standards is to have uniformity,” he said. “If you want different standards, change the ordinance; otherwise, variances should be rare and based on exceptional circumstances.”
The session closed after board questions about the interplay among the Planning and Zoning Commission, administrative appeals and the BOA’s jurisdiction. Bullock said he would research a few procedural cross‑references (for example, whether certain planning or plat actions follow a different appeal path) and return with clarifications, and the board adjourned.
Ending: The meeting was a procedural training rather than a decision meeting; no variances or special exceptions were decided or voted upon during the session. The board received guidance on application completeness, timelines, evidentiary expectations for height and privacy analyses, appeal routes for variances versus special exceptions, and the requirement to record findings when granting relief.
