WeVote
Log In

Bill

Bill

SB 731

Terminating Design Build Board

2025 Regular Session Introduced by Patricia Rucker

SB 731 clarifies and expands county research/URSDs, enabling developer roles in governance and contracted services while requiring timely provision of district services.

To House Government Organization
#financeandadministration
0
WeVote Research Nonpartisan
Bill Summary · SB 731

SB 731 — County Service Districts / Research and URSD

Status: Passed 1st Reading (Senate) — introduced Feb 21, 2025
Primary sponsor: Sen. Murdock

Purpose / Intent

SB 731 makes targeted revisions to North Carolina law governing county research and production service districts and urban research service districts (URSDs). The bill clarifies permissible purposes for such districts, updates procedures for advisory committees and multi‑county districts, and authorizes certain roles and contracting authority for developers operating within these districts.

Key provisions — summary by topic and statute

The bill amends provisions in Chapter 153A (counties), including G.S. 153A‑311, 153A‑313, 153A‑314, 153A‑315, 153A‑316.1, and 153A‑316.2:

  • Purposes (G.S. 153A‑311)

    • Confirms a county may define a research and production service district to finance, provide, and maintain for the district any service, facility, or function that a county or city is authorized to provide in its jurisdiction — either in addition to, or to a greater extent than, countywide services.

  • Advisory committee composition & appointments (G.S. 153A‑313 & 153A‑316.2)

    • Requires an advisory committee of at least 10 members for research/URSDs, with terms set in the establishing resolution.
    • Requires the association of owners/tenants (per G.S. 153A‑312(a)) to submit at least two candidate names for each committee appointment; the board must appoint from that list except for certain additional board appointments.
    • Explicitly grants the developer of a research/production park the authority to appoint one representative to the advisory committee.
    • In single‑county districts the board may make up to two additional appointments; in multi‑county districts each county board may make one additional appointment.
    • Sets procedures for filling vacancies (board requests names from the association and appoints from the list, except for certain appointee slots).

  • Multi‑county district procedures (G.S. 153A‑314 & 153A‑316.1)

    • Clarifies that concurrent boards of counties may establish a multi‑county district even if any single county’s portion would not meet creation standards by itself.
    • When annexing territory that lies wholly within one county to a multi‑county district, only that county’s board need adopt the annexation resolution (subject to section requirements).

  • Service provision, developer as agent, and public‑purpose presumption (G.S. 153A‑315)

    • Requires counties to provide, maintain, or contract for required services within a reasonable time, not to exceed one year after district creation.
    • Permits the county to designate the park developer as an agent to contract (with county approval) for services, construction, and procurement for the district.
    • Authorizes a developer‑agent to own property necessary to provide services (e.g., streets, sidewalks, parks, schools, utilities, transit) and states that tax proceeds used to pay for or maintain such property are “presumptively expended for a public purpose.”

Who is affected

  • Counties and county boards of commissioners (authority and procedures for creating, annexing, and administering districts)
  • Multi‑county district partners (boards share appointment and creation responsibilities)
  • Developers of research and production parks (formal advisory role; potential contracting agent; ability to own infrastructure)
  • Associations of owners and tenants (required to submit candidate lists)
  • Residents, businesses, and taxpayers within districts (service delivery, tax levies, and infrastructure ownership arrangements)
  • Local planning and procurement processes (county oversight remains required for developer contracting)

Procedural / timeline notes

  • Introduced Feb 21, 2025; referred to Rules and Operations of the Senate (per bill header).
  • Passed first reading in the Senate on March 26, 2025 (per legislative actions provided).
  • Further committee review, floor action, or enactment dates are pending (check the legislature’s docket for updates).

Practical implications / considerations

  • The bill formalizes and expands the developer’s role in district governance and service delivery while preserving county approval authority for contracts.
  • The one‑year timeline for providing district services tightens expectations for implementation.
  • The presumption that district tax proceeds used for developer‑owned property serve a public purpose may reduce legal friction for public‑private infrastructure arrangements but could raise governance and oversight questions (e.g., accountability and procurement transparency) that counties and stakeholders will need to manage.

For the statutory details, SB 731 revises G.S. 153A‑311, 153A‑313, 153A‑314, 153A‑315, 153A‑316.1, and 153A‑316.2 (see bill text for exact language).

Compiled from official sources — confirm details with the bill’s official record.

Sign in to ask a question.