A future work-session review is the documented proposal. No Unified Development Code amendment is documented as completed or adopted, and no vote is recorded in the March 2 minutes. It is therefore unknown whether commissioners will advance defined revisions, leave the code unchanged or take another course after the review.
Franklin County puts development-code review on future agenda, without adopting changes
Commissioners raised concerns about the Unified Development Code on March 2, but the meeting minutes do not identify proposed revisions or set a date for the promised work session.
The next public step would be a county work session or later board record that identifies proposed amendments and shows whether commissioners act on them. No date, process or final outcome is stated in the March 2 minutes, leaving residents without a timetable or a defined set of code changes to evaluate.
At a glance
What this means now
The story
Franklin County commissioners agreed March 2 to put a review of the Unified Development Code’s objectives and possible revisions on a future work-session agenda after board members discussed concerns about the county’s development rules. The meeting did not produce an adopted amendment, and the minutes do not give a date for the future session.
The discussion matters because the Unified Development Code is the county framework that governs development rules relied on by residents, landowners and others planning or evaluating projects. But the immediate stakes remain hard to measure: commissioners did not identify which provisions they may alter, what concerns prompted a change, or what development practices could be affected.
The March 2 regular meeting created a path for a later review rather than changing the code itself. Commissioners first discussed concerns about the Unified Development Code, then agreed to take up its objectives and potential revisions in a future work session; the record stops short of proposed language, a formal amendment or a vote on any revision.
Commissioners are the only participants whose positions are described in the minutes: several board members raised concerns, and the board agreed to schedule further discussion. The record does not name the provisions at issue or describe positions from residents, developers, landowners, planning staff or other interested groups, so it does not establish who supports or opposes any particular change.
A future work-session review is the documented proposal. No Unified Development Code amendment is documented as completed or adopted, and no vote is recorded in the March 2 minutes. It is therefore unknown whether commissioners will advance defined revisions, leave the code unchanged or take another course after the review.
The next public step would be a county work session or later board record that identifies proposed amendments and shows whether commissioners act on them. No date, process or final outcome is stated in the March 2 minutes, leaving residents without a timetable or a defined set of code changes to evaluate.
Arguments in the record
Positions presented publicly
Commissioners discussed concerns about the Unified Development Code and agreed to review its objectives and potential revisions at a future work session; the minutes do not identify specific revisions or a final action.
What happened
How this issue got here
Open any step for its supporting record. A proposal remains labeled as proposed until later evidence establishes an outcome.
DiscussedconfirmedCommissioners discussed potential development-code amendments
On March 2, 2026, commissioners discussed concerns about the Unified Development Code and agreed to place a review of its objectives and potential revisions on a future work-session agenda. No code amendment was adopted at that meeting.
+
Commissioners discussed potential development-code amendments
On March 2, 2026, commissioners discussed concerns about the Unified Development Code and agreed to place a review of its objectives and potential revisions on a future work-session agenda. No code amendment was adopted at that meeting.
Still unresolved
What is not yet known
These are evidence gaps, not assumptions. They remain open until a dependable source closes them.
- The March 2 minutes do not state a date for the future work session.
- The minutes do not document adoption of a Unified Development Code amendment.
Newsroom notes1 open check on the record
How the newsroom is still working this matter. These are process notes, not reported facts.
- openThe retained records do not establish the final outcomeLocate later official minutes, resolutions, contracts, payments, or implementation records that resolve the matter.
Research the record