Planning Commission · Meeting · Nov 3, 2026

Tue, Nov 3, 2026

Reviews land-use requests, subdivision plats, and long-range growth plans for unincorporated areas of Hickman County.

Listen

Play the meeting audio here. Use the speed controls if you want to move through it faster.

Speed

This outline was generated by an LLM from a transcript and may contain errors or inaccuracies. Prefer the original recording when available.

Planning Commission members deferred action on adopting updated building and related codes after members said they lacked the actual resolution text in hand, despite staff warning the county is under a year-end deadline to stay within the state’s seven-year code window. The discussion laid out a significant package: adoption of the 2024 International Codes with local deletions and substitutions, especially using the 2009 Energy Code content inside the 2024 adoption framework to avoid stricter insulation and blower-door requirements and to stay aligned with expected Tennessee limits. The deferral passed 7–3, leaving timing pressure because county commission must read the measure twice.

The commission then unanimously approved a new permit-fee schedule, adding permitting for decks and pools, setting a $0.60 per square foot fee for new residential construction under roof, a $0.30 rate for remodels and similar work, a $75 reinspection fee after a failed follow-up, and doubled fees for work begun without permits. Members also unanimously approved a one-year moratorium on new data centers so the county can draft siting and operating rules before any project proceeds under current permissive zoning. Other notable threads included pool safety alarms and fencing, floodplain references tied to FEMA figures rather than ICC text, rollout of Cloudpermit, concerns about distributing resolutions with agendas, and a request that fire departments be notified earlier about subdivisions and major development so they can plan for water supply and response needs.

New Business / Agenda Items

Building and code adoption discussion

  • State code compliance discussion opened with staff explaining the county must stay within seven years of the most current code book, and that once the 2027 edition is released on February 1 the county’s current 2018 code set will be out of compliance under state law.
  • Staff said the state had not yet adopted its version of the new code package and likely would not until later in the spring, but that waiting for the state and then copying its action was no longer workable because the county still had to update on time.
  • Proposed code package described as adoption of the 2024 International Codes, including the International Residential Code, commercial building code, plumbing, mechanical, fuel gas, plus added adoption of the International Energy Code, Swimming Pool Code, Property Maintenance Code, and accessibility / usable buildings provisions tied to ADA requirements.
  • Energy code explanation was the most detailed and contentious policy point:
    • Staff said the residential and commercial books reference the International Energy Code, but the county has not formally adopted that code.
    • The proposal would adopt the 2024 energy code “cover” but replace its substantive provisions with the 2009 Energy Code language through deletions and insertions.
    • Justification was to preserve current insulation expectations—roughly wall insulation at 13 and ceiling insulation at 38—and avoid mandatory blower-door testing.
    • Staff said the county cannot be more stringent than the state, and the state is expected to keep the older 2009 energy provisions even if it adopts the 2024 framework.
  • A member asked whether the stricter 2024 energy rules would effectively force spray-foam insulation over batt insulation; staff confirmed the 2024 code is stricter and said that was why the proposal backed down to the 2009 energy provisions.
  • Staff also highlighted key local residential changes within the proposed 2024 IRC:
    • Floodplain construction would follow local FEMA figures rather than International Code Council values.
    • Section 309 on mandatory sprinkler systems in one- and two-family dwellings would be deleted in full.
    • If a sprinkler system is voluntarily installed, it must comply with NFPA standards.
  • Members clarified there was no intervening 2021 code edition being adopted here; the county is moving from 2018 to 2024, while 2027 is forthcoming but not yet available or approved.
  • Procedural problem emerged when members realized not everyone had the actual code resolution in front of them:
    • One member said the only resolution copy received concerned the data center item, not code adoption.
    • Another said the measure should be tabled or deferred so members could study the language.
    • Staff urged action because of the deadline and said the state fire marshal had already approved the text as written, but acknowledged county commission would still need two readings.
  • Motion made and seconded to defer consideration of the code adoption to the next meeting so all members could review the text.
  • Roll-call vote on deferral: 7 yes, 3 no, with one absence.
  • Outcome:
    • Code adoption deferred to the next meeting.
    • Delay creates timing risk because county commission would need two readings, making January the earliest possible final county action if planning commission waits until the next month.

Permit fee schedule

  • The commission next took up proposed building permit fee changes for residential and commercial work.
  • Staff said the county’s current fee structure undervalues construction and is lower than nearby jurisdictions:
    • Current living-space valuation is based on $90 per square foot.
    • Staff said it is unrealistic to build at that figure now.
    • Example given: a house in Ritchie Farms was permitted for $637 based on a calculated valuation of $158,099, while the property assessor had already valued that same project at $441,762.
  • Main residential proposal:
    • Replace the current complex formula with a simpler square-foot method.
    • New home construction, manufactured homes, modular homes, and additions: $0.60 per square foot for anything under roof.
    • Remodels, unfinished basements, and accessory structures: $0.30 per square foot.
  • Staff justified the simplification partly as an administrative improvement:
    • Current process requires office staff to calculate separate values for living area, unfinished basement, garages, and covered porches, then apply a fee table.
    • Proposed system would be easier for office staff and better suited to the upcoming Cloudpermit software rollout.
  • A member questioned whether the adequate facilities tax line needed clarification because the draft could be read inconsistently with the “anything under roof” language used elsewhere.
  • Staff agreed the draft should more clearly distinguish that the adequate facilities tax applies to heated and cooled space.
  • Fee examples and concerns:
    • A member compared the proposal to a hypothetical $300,000 home and noted that a straight square-foot fee could produce different outcomes depending on project size and cost per square foot.
    • Staff replied that the proposal intentionally shifts from valuation-based calculations to square-foot calculations, so it is not a perfect apples-to-apples comparison.
    • For the Ritchie Farms example, current fee $637 would become about $1,288.20 under the proposal because porches under roof are included.
  • New fee items added to the county schedule:
    • Pools and decks would now require permits.
    • Single-wide mobile homes: current $250, proposed $500 one-time fee.
    • In-ground pools: proposed $250 fee, intended to cover about three inspections.
    • Reinspection fee: $75 for a second follow-up after failed corrections remain unaddressed.
    • Work started before permit issuance: permit fee doubled.
  • Pool permitting rationale:
    • Staff said state law requires a splash alarm for pools over 36 inches high.
    • Future adoption of the swimming pool code would also bring fence standards for in-ground pools: minimum 4-foot barrier and pickets less than 4 inches apart.
    • Above-ground pools can serve as their own barrier if they are a continuous 48 inches high; if partly banked into a slope and effectively lower than that, fencing would be required.
    • Staff framed this primarily as a life-safety issue to prevent drownings and to document county inspection efforts.
  • Deck permitting rationale:
    • Staff said recent field observations showed some decks were being attached improperly, including fastening into brick with Tapcons rather than using through-bolts or lag bolts into a ledger as required by code.
  • Reinspection discussion:
    • A member asked why the first reinspection after corrections would remain free when other inspection trades often charge on the next trip.
    • Staff said the goal was to allow one correction visit without charge because most homes will have some rough-framing correction items, but to deter repeated incomplete work by charging on the next return visit.
  • Commercial permit proposal:
    • Staff said the county’s current commercial valuation, around $48 per square foot, is no longer realistic.
    • Rather than forcing office staff to classify occupancy and mixed uses from incomplete information, the proposal would require applicants to submit an awarded contract bid or contractor letterhead showing project cost.
    • Commercial permit fees would then be based on that documented cost using the revised fee table.
  • Motion made and seconded to approve the proposed permit fee schedule.
  • Roll-call vote: 11 yes, 0 no.
  • Outcome: permit fee schedule approved unanimously.

Deck and swimming pool permitting follow-up

  • After the fee vote, members briefly revisited whether pool and deck permitting would affect existing installations.
  • Staff said the proposal would apply prospectively, beginning after county commission approval, potentially January 2 if the commission passes it in December.
  • Existing pools would not be forced to retrofit alarms or otherwise come into compliance under this proposal.
  • A member asked whether a homeowner with an existing house who later decides to install a pool would need a permit under the new system; staff said yes.
  • Enforcement limits were acknowledged:
    • Members noted it could be hard to enforce permits for homeowner-installed pools and decks.
    • Staff said the county cannot catch everything but needs to show the state fire marshal that it is trying, especially because permit practices are reviewed in a periodic audit.
    • Staff also emphasized that if an owner avoids the permit, responsibility falls on the owner rather than on the county for noncompliance.
  • Staff reiterated that the state fire marshal’s office had approved the proposed code-resolution language, even though the planning commission had just deferred acting on it.

Data center moratorium

  • The commission then considered a proposed resolution imposing a temporary moratorium on new data centers.
  • The resolution was described as a one-year temporary moratorium on construction of new data centers, with the data-center definition contained in the resolution text.
  • Purpose of the moratorium:
    • Give the planning commission time to study data centers and draft setbacks, standards, permit procedures, and other regulations.
    • Allow the county commission to later adopt those rules, at which point the moratorium could end earlier than one year.
  • Members said the issue had become politically prominent and often produces conflicting claims about water use, power use, noise, tax value, and employment.
  • One member supported the moratorium because current zoning would not let the county direct where a data center goes or impose special conditions if an applicant seeks one in agricultural zoning.
  • Another member, drawing on personal experience starting up power systems for large data centers, pushed back on what he called widespread misinformation:
    • He cited prior work on large facilities for companies like Microsoft and T-Mobile.
    • He said large centers can consume major power—examples included 50 megawatts, 100 megawatts, and a Gallatin “metadata center” at 300 megawatts—but argued internet claims often exaggerate local utility impacts.
    • He said he had spoken with Gallatin Public Utilities superintendent David Kellogg, who told him the Gallatin data center uses less than 2 percent of the utility’s water production and ranks about fourth in water use, roughly comparable to the jail.
    • He contrasted that with large financial benefits, referencing an Elon Musk-related project in Memphis said to bring in $14 billion annually in property taxes, while the Gallatin facility reportedly brings about $1.8 million for 20 years under a separate arrangement after utility-system upgrades.
  • Noise and generator issues were also discussed in detail:
    • Backup generators were identified as the main source of objectionable noise.
    • One speaker said a large center could have 100 locomotive-sized generators.
    • Sound attenuation is possible but expensive.
    • Without local noise controls, a facility could create severe off-site impacts.
    • An example from outside Austin, Texas, was cited where a facility allegedly produced 187 decibels continuously for 7 days and 12 hours, heard from 4 miles away.
  • Broad consensus emerged that the county was not necessarily deciding it never wants a data center, but that it needs rules before one arrives.
  • A member said the county should use the moratorium period to consult similarly sized counties and use CTAS planning resources as a starting point.
  • County attorney Dan Mecklenborg noted the resolution places the responsibility on the planning commission to develop recommendations, and if those are ready in about six months they can move to county commission before the full year runs.
  • Motion made and seconded to approve the moratorium resolution.
  • Roll-call vote: 11 yes, 0 no.
  • Outcome: one-year data center moratorium approved unanimously, subject to county commission action.

Meeting time discussion

  • Members discussed whether regular planning commission meetings should remain at 6:30 or move to 6:00.
  • Several members preferred keeping 6:30, citing travel difficulties, including getting in from Nashville.
  • Outcome: no change; the commission kept the 6:30 meeting time.

Announcements

Fire department notice request

  • A member reported that at a recent health and safety meeting, the president of the fire association asked for earlier notice when subdivisions, industrial buildings, commercial buildings, or other new development are being considered.
  • Rationale was to let the relevant fire department evaluate water supply and prepare for service demands before projects are approved or built.
  • The member asked whether, when new projects come before planning and zoning, he could contact the responsible fire department so its representatives could attend and be made aware.
  • No objection was recorded.

Resolution distribution concern

  • A member asked that resolutions be distributed at the same time as agendas rather than being handed out or introduced for same-night review and voting.
  • He said he agreed with the data-center moratorium but still wanted more time in future to study four-page resolutions before a vote.
  • Staff accepted the criticism, said the short turnaround was largely due to workload and catch-up conditions, and committed to doing better.
  • Staff added that if materials cannot be sent out ahead of time, they should not be brought up for action.
  • Staff again said the code resolution was unusually rushed because of the state fire marshal deadline.

Adjournment

  • Motion and second to adjourn were made at the close of business.

Key figures and statistics

Figure Type Context / topic
7 years Time period State-law window for staying current with the most recent code book
2027 Year Next code book becoming current beginning February 1
February 1 Date Release timing for the 2027 code book
2018 Year County’s current adopted code edition
2024 Year Proposed code edition for adoption
2009 Year Energy code content proposed to be inserted into the 2024 framework
13 Standard Wall insulation level staff said would be preserved under the 2009 energy provisions
38 Standard Ceiling insulation level staff said would be preserved under the 2009 energy provisions
309 Code section Residential sprinkler section proposed for deletion
7–3 Vote Planning Commission vote to defer code adoption
2 Readings County Commission readings needed to pass the code resolution
$90 per square foot Valuation rate Current living-space valuation basis for permit calculations
$637 Fee Current permit charged on the example Ritchie Farms house
$158,099 Valuation Permit valuation assigned to the example Ritchie Farms house
$441,762 Valuation Assessor valuation already placed on the same example house
$250 Fee Current single-wide mobile home permit fee
$500 Fee Proposed single-wide mobile home permit fee
$0.60 per square foot Fee rate Approved residential rate for new construction, manufactured homes, modular homes, and additions under roof
$0.30 per square foot Fee rate Approved residential rate for remodels, unfinished basements, and accessory structures
36 inches Threshold Pool height triggering splash-alarm requirement under state law as described
$250 Fee Proposed in-ground pool permit fee
3 inspections Inspection count Approximate number of visits the in-ground pool fee was meant to cover
4 feet Height Minimum fence height described for in-ground pools under the swimming pool code
4 inches Spacing Maximum picket spacing described for pool fencing
48 inches Height Above-ground pool height that can serve as its own barrier if continuous
$75 Fee Reinspection charge for a second failed follow-up visit
2 months Time period Staff’s observation period for seeing code-compliance improvement in the field
7 inspections Inspection count Typical number of inspections on new construction
$48 per square foot Valuation rate Current commercial-building valuation staff said is outdated
$1,288.20 Fee Example permit fee for the Ritchie Farms house under the proposed method
11–0 Vote Planning Commission vote approving the permit fee proposal
January 2 Date Possible start date for new pool/deck permitting if county commission acts in December
3 years Time period State fire marshal audit cycle mentioned for the program
1 year Time period Length of approved data center moratorium
50 megawatts Capacity Example size of large data centers discussed
100 megawatts Capacity Example size of large data centers discussed
300 megawatts Capacity Size cited for a Gallatin data center
less than 2 percent Percentage Gallatin utility water production reportedly used by the data center
4th Ranking Water-use ranking reportedly held by the Gallatin data center
$14 billion Revenue claim Property-tax figure cited for an Elon Musk-related Memphis data center project
$1.8 million Revenue claim Gallatin data center tax/payment figure cited
20 years Time period Length of Gallatin arrangement mentioned
$150 million per year Utility cost Power bill figure cited for the Gallatin center
100 Equipment count Number of locomotive-sized backup generators cited for a large center
80 decibels Noise level Sound level one speaker said could be achieved with attenuation
187 decibels Noise level Noise level cited in the Texas example
7 days and 12 hours Time period Duration cited for the Texas generator-noise example
4 miles Distance Distance from which the Texas noise example was reportedly heard
6 months Time period Possible shorter timeline to bring data-center recommendations forward
90 days Time period Time one member said it realistically takes to move something through now
11–0 Vote Planning Commission vote approving the data center moratorium
6:30 Meeting time Existing meeting time retained by the commission
6:00 Meeting time Alternative meeting time discussed and not adopted
4 years Time period Length of time one member said he had been attending periodically before joining

External vendors, brands, and software

Name Type Context / topic
International Code Council Company Source organization for the international code books and tables referenced in the code-adoption discussion
FEMA Company Floodplain construction references would use local FEMA amounts rather than ICC values
NFPA Company Standard cited for voluntary residential sprinkler installations
Cloudpermit Software Permit software scheduled to go live in the office before public rollout
Watts Company Pool company staff said would be notified by email if pool-permit changes are adopted
Pool and Spa Depot Company Pool company staff said would be notified by email if pool-permit changes are adopted
Microsoft Company Example company used in discussion of large data center experience
T-Mobile Company Example company used in discussion of large data center experience
CTAS Company Planning resource mentioned as having model material or a starting point on data centers

Laws and policies

Citation / name Level Type Context / topic
seven-year rule State Law State-law requirement that local codes stay within seven years of the most current code book
2024 International Residential Code State Code Proposed residential code adoption with local deletions and insertions
2024 International Building Code State Code Proposed commercial building code adoption
International Plumbing Code State Code Included in the proposed code package
International Mechanical Code State Code Included in the proposed code package
International Fuel Gas Code State Code Included in the proposed code package
International Energy Code State Code Proposed for adoption in 2024 form, with 2009 content inserted locally
Swimming Pool Code State Code Proposed adoption to govern barriers and related pool safety items
Property Maintenance Code State Code Proposed addition to the county’s code package
ADA Federal Law Accessibility / usable buildings provisions described as ADA-related in the code package
2009 Energy Code State Code Older substantive energy requirements proposed to replace 2024 energy provisions locally
Section 309 State Code Residential sprinkler requirement section proposed for deletion from the adopted code
state law requiring pool splash alarms State Law Requirement described for pools over 36 inches high
state fire marshal approval / audit requirements State Regulation Staff said the fire marshal approved the code text and audits the local program every three years

Files

This document is a proposed building permit fee schedule from the Hickman County Planning and Zoning Office, dated November 3, 2026. It outlines various fees associated with residential, commercial, and industrial building permits, including specific costs based on total valuation and square footage for different types of structures. Additionally, it includes information on mobile home permit fees and the Adequate Facilities Tax, which must be paid before a building permit is issued. The document also references a resolution establishing a temporary moratorium on new data center development, indicating ongoing regulatory considerations in the county. This excerpt represents only the beginning of the file, and further details may be present in subsequent pages.