Skip to content
AgendaWire
Articles

Before year-end, developers should track plats, variances, and final approvals

Q4 leaves less room for a missed plat, variance, or final council action. Keep a dated approval ledger tied to agendas and written decisions.

Agenda monitoringSeptember 24, 20266 min read

Late October is when a development schedule can look settled while its public approval path is still moving. A plat may be on a commission agenda. A variance may be waiting for a hearing date. A council item may have been continued, approved with conditions, or placed on consent without the project team updating its closing checklist.

Q4 leaves less calendar room for recovery. Holiday weeks, canceled meetings, staff leave, and notice periods can turn one missed agenda into a January decision. The practical response is not to predict approval. It is to keep a dated record of what has happened, what remains, and which public body controls the next step.

Start with the actual decision path

For each active project, write the approval chain in order. It may include staff completeness review, a planning commission, a board of adjustment panel, city council, execution of an agreement, plat signatures, and recording. The chain differs by city and by application.

Public meeting systems help identify that chain. The City of Dallas meeting calendar, for example, lists the City Plan Commission, three Board of Adjustment panels, the full Board of Adjustment, City Council, and other bodies. Its records can include meeting details, agendas, accessible agendas, minutes, and video. A calendar entry is a lead, not proof of a final approval.

Build backward from the last meeting that can support the deal date. Then add the city's submission cutoff, notice period, staff report date, hearing date, and any later governing-body action. If the calendar has only one usable meeting left before a holiday break, a continuance can change the financing or closing schedule even when the application remains active.

Treat the plat shot clock as a decision clock

Texas Local Government Code Chapter 212 sets a defined municipal plat process. Section 212.009 generally requires the responsible municipal authority to approve, approve with conditions, or disapprove a filed plat within 30 days. If an ordinance also requires governing-body approval, that body generally has 30 days after planning commission approval or approval by inaction. The statute also identifies circumstances for extensions.

That clock measures a decision step. It does not promise plat recording, permit issuance, document execution, or a closing within 30 days.

A conditional approval or disapproval must come with a written statement that identifies each condition or reason, connects it to the governing requirements, and cites the legal basis when applicable. After the applicant submits a written response addressing those points, Section 212.0095 gives the authority 15 days to approve or disapprove the response. The applicant's response, the city's written statement, and the next action date belong in the same tracker.

Do not reduce this process to a single deadline cell. Record the filing date accepted by the city, the decision date, every written condition, the response submission date, and the date the response must be decided. Note any written extension and who approved it.

Keep variance authority separate from appeal deadlines

Chapter 211 authorizes a municipal board of adjustment to decide appeals, special exceptions, and qualifying variances. Section 211.009 requires a 75 percent concurring vote of board members to authorize a variance or decide in favor of an applicant on a matter the board must pass under the zoning ordinance. Section 211.008 also requires open meetings and public records of the board's proceedings.

The timing provisions need careful labeling. Section 211.010 gives an eligible appellant 20 days after an administrative decision to file an appeal. It calls for a hearing at a reasonable time and a decision at the next meeting for which notice can be provided after the hearing, no later than 60 days after the appeal is filed. Those are statutory rules for an appeal from an administrative decision. They are not a universal 60-day promise for every original variance application.

For a standalone variance request, use the city's current ordinance, application instructions, cutoff calendar, and posted hearing record. Track whether the item is complete, noticed, heard, continued, or decided. A project team that labels every board matter simply as a "variance" can miss an appeal filing deadline or assume a decision deadline that does not apply.

Audit expiration and vesting dates before December

Approval status and approval life are different questions. Chapter 245 addresses permit applications, project vesting, expiration dates, and dormant projects. Section 245.002 permits an agency, under stated notice conditions, to let an incomplete application expire on or after the 45th day after filing when required documents are not supplied. Section 245.005 allows local rules to place expiration dates on dormant permits and projects within statutory limits, and it lists actions that count as progress toward completion.

A year-end audit should therefore ask which approval or application has an expiration date, what event extends or preserves it, and what evidence proves that event occurred. Check the actual permit, approval letter, ordinance, development agreement, and city correspondence. Do not rely on the date in a deal summary prepared months earlier.

Build the checklist from agendas and action records

Texas open-meeting law supplies two useful controls. Government Code Chapter 551 requires written notice stating the date, hour, place, and subject of a meeting. Section 551.043 generally requires at least three business days of public posting, and Section 551.102 requires final action on a matter discussed in closed session to occur in an open meeting that complies with the notice rules.

Use those records to run a weekly approval review for each active deal:

  • Match the case number, project address, applicant, and legal description across the agenda and internal file.
  • Record the posted meeting date, board or commission, agenda item number, and staff recommendation.
  • Mark the item as scheduled, withdrawn, continued, approved, conditionally approved, or denied. Do not treat agenda placement as a result.
  • Capture the motion, vote, stated conditions, and any direction to return at a later meeting.
  • Link the staff report, agenda, minutes or action record, approval letter, and final signed document when each becomes available.
  • Add effective dates, appeal windows, response deadlines, signature steps, recording status, and approval expiration dates.

Assign one owner to compare that ledger with the closing checklist every week through year-end. The owner should raise a mismatch while another meeting slot still exists, not after the closing team asks for the final approval.

AgendaWire monitors municipal agenda records and surfaces source-linked topic matches. If active deals depend on public approvals, start a free 14-day trial and build the year-end watchlist first.

AgendaWire provides source monitoring, not legal advice. Confirm current requirements with the city and your advisers before acting.

The useful output is a dated approval ledger that ties each deal assumption to a posted agenda, action record, or signed document.

Official sources

More agenda-monitoring guides

All articles