SB 2673: Counties; OPSD; Chief Data Officer; Building Permits; Civil Engineering Permits; Statewide Permitting Data Standard; Report
- Session Year: 2025-2026
- House: Senate
- Latest Version Date: 2026-05-01
Current Status:
Passed
(2026-06-05: Act 104, on 06/05/2026 (Gov. Msg. No. 1204).)
Introduced
In Committee
First Chamber
In Committee
Second Chamber
Final Decking
Enacted
What does this bill do?
The bill requires the Office of Planning and Sustainable Development and the state Chief Data Officer, working with county permitting agencies, to create a statewide permitting data standard and requires each county to publish monthly, machine-readable permit data for building and civil engineering permits. The public datasets must include a data dictionary and key fields (permit number, dates, current status, address and coordinates, project cost, housing units, contractor info, and standardized status/type codes with county-to-standard crosswalks), and the office must report its findings to the Legislature.
The summary is provided by generative AI which can make mistakes. For original language, please view the details in the table below.
Requires a statewide permitting data standard developed collaboratively by the Office of Planning and Sustainable Development, county permitting agencies, and the Chief Data Officer. Requires each county to publish monthly updates of building and civil engineering permit data in accordance with that standard. Requires a report to the Legislature. (CD1)
Requires a statewide permitting data standard developed collaboratively by the Office of Planning and Sustainable Development, county permitting agencies, and the Chief Data Officer. Requires each county to publish monthly updates of building and civil engineering permit data in accordance with that standard. Requires a report to the Legislature. Appropriates funds. Effective 7/1/3000. (HD1)
Requires a statewide permitting data standard developed collaboratively by the Office of Planning and Sustainable Development and the Chief Data Officer. Requires each county to publish monthly updates of building and civil engineering permit data in accordance with that standard. Requires a report to the Legislature. Appropriates funds. Effective 4/19/2042. (SD1)
Requires a statewide permitting data standard developed collaboratively by the Office of Planning and Sustainable Development and the Chief Data Officer. Requires each county to publish monthly updates of building and civil engineering permit data in accordance with that standard. Requires report.
|
THE SENATE |
S.B. NO. |
2673 |
|
THIRTY-THIRD LEGISLATURE, 2026 |
S.D. 1 |
|
|
STATE OF HAWAII |
H.D. 1 |
|
|
|
C.D. 1 |
|
|
|
||
|
|
||
A BILL FOR AN ACT
RELATING TO THE COUNTIES.
BE IT ENACTED BY THE LEGISLATURE OF THE STATE OF HAWAII:
The legislature further finds that the governor's emergency proclamation on housing and the subsequent findings of the simplifying permitting for enhanced economic development task force have highlighted significant challenges in tracking permitting performance. The task force's building permit permitted interaction group found that counties use incompatible data standards to represent permit status, key dates, valuations, and categories, which complicates meaningful comparisons and shared learning. The group further suggested that the counties and the State work toward common data standards and reporting templates for building permits, including more granular status categories that distinguish delays attributable to applicants from delays attributable to agencies.
The legislature finds that while some permit data is currently available, it is often difficult to access or is provided in formats that do not allow for routine aggregation, analysis, or cross-county comparison. Requiring counties to publish permit data in a standardized, machine-readable format will reduce the administrative burden of ad hoc information requests, support customer service improvements, and foster transparency and accountability.
Accordingly, the purpose of this Act is to:
(1) Establish a statewide permitting data standard in collaboration with the office of planning and sustainable development, county permitting agencies, and the chief data officer of the office of enterprise technology services;
(2) Require each county to publish monthly updates of building and civil engineering permit data in accordance with that standard; and
(3) Require a report to the legislature.
SECTION 2. Chapter 46, Hawaii Revised Statutes, is amended by adding a new section to part V to be appropriately designated and to read as follows:
"§46- Publicly accessible permit data; monthly updates; statewide standard. (a) Each county shall host and maintain on its website a publicly accessible dataset containing data on all building and civil engineering permit applications administered by the county.
(b) The dataset required by subsection (a) shall:
(1) Be updated at least monthly;
(2) Be published in a machine-readable format, such as comma-separated values (CSV) or javascript object notation (JSON); and
(3) Include a data dictionary that defines each field and the permitted values for any coded field.
(c) To ensure statewide comparability, each record in the dataset required by subsection (a) shall include, at a minimum, the following fields and defined field names, which shall be populated in accordance with the statewide permitting data standard established under subsection (f):
(1) The permit number ("PermitNum");
(2) A detailed description of work permitted ("Description");
(3) The date on which the permit application was submitted, in YYYY-MM-DD format ("AppliedDate");
(4) The date on which the permit was issued, if applicable, in YYYY-MM-DD format ("IssuedDate");
(5) The date on which the permit was completed or finalized, if applicable, in YYYY-MM-DD format ("CompletedDate");
(6) A raw value indicating the current status of the permit ("StatusCurrent");
(7) The original property street address line 1, as stored by the county ("OriginalAddress1");
(8) The original property street address line 2, as stored by the county, if applicable ("OriginalAddress2");
(9) The original property city, as stored by the county ("OriginalCity");
(10) The original property state, as stored by the county ("OriginalState");
(11) The original property zip code, as stored by the county ("OriginalZip");
(12) A unique identifier for the county publishing the record ("Jurisdiction");
(13) A raw value indicating whether the permit is for residential or non-residential property ("PermitClass");
(14) A standardized value for the permit class, as defined by the statewide permitting data standard ("PermitClassMapped");
(15) A standardized value for the current status, as defined by the statewide permitting data standard ("StatusCurrentMapped");
(16) A raw value indicating whether the permitted work is new construction or work on an existing structure ("WorkClass");
(17) A standardized value for the work class, as defined by the statewide permitting data standard ("WorkClassMapped");
(18) A raw value indicating the permit type in abbreviated or shorthand format ("PermitType");
(19) A standardized value for the permit type, as defined by the statewide permitting data standard ("PermitTypeMapped");
(20) A longer description of the permit type ("PermitTypeDesc");
(21) The date on which the permit record was last updated in the county's system of record, in YYYY-MM-DD format ("StatusDate");
(22) The total square footage relevant to the permit ("TotalSqFt");
(23) The uniform resource locator to the county's public web page for the permit, if applicable ("Link");
(24) The latitude of the property in decimal degrees ("Latitude");
(25) The longitude of the property in decimal degrees ("Longitude");
(26) The estimated value of the project, if known ("EstProjectCost");
(27) The number of housing units authorized or affected by the permit, if any ("HousingUnits");
(28) The parcel identifier used for tax assessment purposes, including the tax map key, if available ("PIN");
(29) The primary company name of the contractor, if applicable ("ContractorCompanyName");
(30) A raw value indicating the contractor's trade, if applicable ("ContractorTrade");
(31) A standardized value for the contractor's trade, as defined by the statewide permitting data standard, if applicable ("ContractorTradeMapped"); and
(32) The contractor license number, if applicable ("ContractorLicNum").
(d) In addition to the fields and field names provided in subsection (c), each record shall include the following fields and defined field names, if the county's system of record captures the underlying information, to support statewide measurement of permitting timelines and responsibility for any delays:
(1) The date on which the application was accepted for processing or deemed complete, in YYYY-MM-DD format ("AcceptedDate");
(2) The permitting agency or county department administering the permit, as stored by the county ("PermittingAgency");
(3) The final disposition of the application, limited to: approved, denied, withdrawn, expired, or voided ("FinalDisposition");
(4) The date of the final disposition, in YYYY-MM-DD format ("FinalDispositionDate"); and
(5) The date on which the permit was last placed on hold or otherwise paused, in YYYY-MM-DD format ("HoldDate").
(e) Each county shall cooperate with the other counties, the office of planning and sustainable development, and the chief data officer to ensure that the statewide permitting data standard established under subsection (f) uses common definitions, common field names, and common standardized values that allow for accurate cross-county comparison. Each county shall:
(1) Designate a permitting data liaison responsible for coordinating implementation of this section;
(2) Provide, upon request, the county's permitting data dictionary, code lists, and documentation needed to map county-specific values to standardized values; and
(3) Maintain and publish, alongside the dataset required by subsection (a), a crosswalk that maps each county‑specific coded value used in fields required by subsections (c) and (d) to the corresponding standardized value.
(f) The office of planning and sustainable development, in collaboration with the chief data officer, shall establish, publish, manage, and periodically update a statewide permitting data standard to implement this section. The statewide permitting data standard shall:
(1) Be designed for routine monthly publication and public use;
(2) Incorporate, at a minimum, the required and recommended fields described in subsections (c) and (d);
(3) Define each field required by subsections (c) and (d), including data types, required formats, and allowable values;
(4) Establish standardized value sets for the fields ending in "Mapped", including status categories that distinguish, at a minimum, between delays attributable to an applicant and delays attributable to an agency;
(5) Specify how a county shall represent missing or inapplicable values; and
(6) Include implementation guidance intended to minimize the administrative burden on the counties.
(g) The statewide permitting data standard required by subsection (f) shall be published no later than January 1, 2027. Each county shall comply with the statewide permitting data standard beginning no later than January 1, 2027."
SECTION 3. The office of planning and sustainable development, in collaboration with the chief data officer, shall submit a report of its findings and recommendations, including any proposed legislation, to the legislature no later than twenty days prior to the convening of the regular session of 2027. The report shall include:
(1) The statewide permitting data standard published pursuant to this Act;
(2) The consultation process used to develop the standard, including participation by the counties;
(3) Any barriers to county implementation, including technology constraints, staffing, or legal barriers; and
(4) Any proposed legislation or administrative actions needed to improve statewide permitting data quality and comparability.
SECTION 4. New statutory material is underscored.
SECTION 5. This Act shall take effect upon its approval.
Report Title:
Counties; OPSD; Chief Data Officer; Building Permits; Civil Engineering Permits; Statewide Permitting Data Standard; Report
Description:
Requires a statewide permitting data standard developed collaboratively by the Office of Planning and Sustainable Development, county permitting agencies, and the Chief Data Officer. Requires each county to publish monthly updates of building and civil engineering permit data in accordance with that standard. Requires a report to the Legislature. (CD1)
The summary description of legislation appearing on this page is for informational purposes only and is not legislation or evidence of legislative intent.
|
THE SENATE |
S.B. NO. |
2673 |
|
THIRTY-THIRD LEGISLATURE, 2026 |
S.D. 1 |
|
|
STATE OF HAWAII |
H.D. 1 |
|
|
|
|
|
|
|
||
|
|
||
A BILL FOR AN ACT
RELATING TO THE COUNTIES.
BE IT ENACTED BY THE LEGISLATURE OF THE STATE OF HAWAII:
The legislature further finds that the governor's emergency proclamation on housing and the subsequent findings of the simplifying permitting for enhanced economic development task force have highlighted significant challenges in tracking permitting performance. The task force's building permit permitted interaction group found that counties use incompatible data standards to represent permit status, key dates, valuations, and categories, which complicates meaningful comparisons and shared learning. The group further suggested that the counties and the State work toward common data standards and reporting templates for building permits, including more granular status categories that distinguish delays attributable to applicants from delays attributable to agencies.
The legislature finds that while some permit data is currently available, it is often difficult to access or is provided in formats that do not allow for routine aggregation, analysis, or cross-county comparison. Requiring counties to publish permit data in a standardized, machine-readable format will reduce the administrative burden of ad hoc information requests, support customer service improvements, and foster transparency and accountability.
Accordingly, the purpose of this Act is to:
(1) Establish a statewide permitting data standard in collaboration with the office of planning and sustainable development, county permitting agencies, and the chief data officer of the office of enterprise technology services;
(2) Require each county to publish monthly updates of building and civil engineering permit data in accordance with that standard;
(3) Require a report to the legislature; and
(4) Appropriate funds.
SECTION 2. Chapter 46, Hawaii Revised Statutes, is amended by adding a new section to part V to be appropriately designated and to read as follows:
"§46- Publicly accessible permit data; monthly updates; statewide standard. (a) Each county shall host and maintain on its website a publicly accessible dataset containing data on all building and civil engineering permit applications administered by the county.
(b) The dataset required by subsection (a) shall:
(1) Be updated at least monthly;
(2) Be published in a machine-readable format, such as comma-separated values (CSV) or javascript object notation (JSON); and
(3) Include a data dictionary that defines each field and the permitted values for any coded field.
(c) To ensure statewide comparability, each record in the dataset required by subsection (a) shall include, at a minimum, the following fields and defined field names, which shall be populated in accordance with the statewide permitting data standard established under subsection (f):
(1) The permit number ("PermitNum");
(2) A detailed description of work permitted ("Description");
(3) The date on which the permit application was submitted, in YYYY-MM-DD format ("AppliedDate");
(4) The date on which the permit was issued, if applicable, in YYYY-MM-DD format ("IssuedDate");
(5) The date on which the permit was completed or finalized, if applicable, in YYYY-MM-DD format ("CompletedDate");
(6) A raw value indicating the current status of the permit ("StatusCurrent");
(7) The original property street address line 1, as stored by the county ("OriginalAddress1");
(8) The original property street address line 2, as stored by the county, if applicable ("OriginalAddress2");
(9) The original property city, as stored by the county ("OriginalCity");
(10) The original property state, as stored by the county ("OriginalState");
(11) The original property zip code, as stored by the county ("OriginalZip");
(12) A unique identifier for the county publishing the record ("Jurisdiction");
(13) A raw value indicating whether the permit is for residential or non-residential property ("PermitClass");
(14) A standardized value for the permit class, as defined by the statewide permitting data standard ("PermitClassMapped");
(15) A standardized value for the current status, as defined by the statewide permitting data standard ("StatusCurrentMapped");
(16) A raw value indicating whether the permitted work is new construction or work on an existing structure ("WorkClass");
(17) A standardized value for the work class, as defined by the statewide permitting data standard ("WorkClassMapped");
(18) A raw value indicating the permit type in abbreviated or shorthand format ("PermitType");
(19) A standardized value for the permit type, as defined by the statewide permitting data standard ("PermitTypeMapped");
(20) A longer description of the permit type ("PermitTypeDesc");
(21) The date on which the permit record was last updated in the county's system of record, in YYYY-MM-DD format ("StatusDate");
(22) The total square footage relevant to the permit ("TotalSqFt");
(23) The uniform resource locator to the county's public web page for the permit, if applicable ("Link");
(24) The latitude of the property in decimal degrees ("Latitude");
(25) The longitude of the property in decimal degrees ("Longitude");
(26) The estimated value of the project, if known ("EstProjectCost");
(27) The number of housing units authorized or affected by the permit, if any ("HousingUnits");
(28) The parcel identifier used for tax assessment purposes, including the tax map key, if available ("PIN");
(29) The primary company name of the contractor, if applicable ("ContractorCompanyName");
(30) A raw value indicating the contractor's trade, if applicable ("ContractorTrade");
(31) A standardized value for the contractor's trade, as defined by the statewide permitting data standard, if applicable ("ContractorTradeMapped"); and
(32) The contractor license number, if applicable ("ContractorLicNum").
(d) In addition to the fields and field names provided in subsection (c), each record shall include the following fields and defined field names, if the county's system of record captures the underlying information, to support statewide measurement of permitting timelines and responsibility for any delays:
(1) The date on which the application was accepted for processing or deemed complete, in YYYY-MM-DD format ("AcceptedDate");
(2) The permitting agency or county department administering the permit, as stored by the county ("PermittingAgency");
(3) The final disposition of the application, limited to: approved, denied, withdrawn, expired, or voided ("FinalDisposition");
(4) The date of the final disposition, in YYYY-MM-DD format ("FinalDispositionDate"); and
(5) The date on which the permit was last placed on hold or otherwise paused, in YYYY-MM-DD format ("HoldDate").
(e) Each county shall cooperate with the other counties, the office of planning and sustainable development, and the chief data officer to ensure that the statewide permitting data standard established under subsection (f) uses common definitions, common field names, and common standardized values that allow for accurate cross-county comparison. Each county shall:
(1) Designate a permitting data liaison responsible for coordinating implementation of this section;
(2) Provide, upon request, the county's permitting data dictionary, code lists, and documentation needed to map county-specific values to standardized values; and
(3) Maintain and publish, alongside the dataset required by subsection (a), a crosswalk that maps each county‑specific coded value used in fields required by subsections (c) and (d) to the corresponding standardized value.
(f) The office of planning and sustainable development, in collaboration with the chief data officer, shall establish, publish, manage, and periodically update a statewide permitting data standard to implement this section. The statewide permitting data standard shall:
(1) Be designed for routine monthly publication and public use;
(2) Incorporate, at a minimum, the required and recommended fields described in subsections (c) and (d);
(3) Define each field required by subsections (c) and (d), including data types, required formats, and allowable values;
(4) Establish standardized value sets for the fields ending in "Mapped", including status categories that distinguish, at a minimum, between delays attributable to an applicant and delays attributable to an agency;
(5) Specify how a county shall represent missing or inapplicable values; and
(6) Include implementation guidance intended to minimize the administrative burden on the counties.
(g) The statewide permitting data standard required by subsection (f) shall be published no later than January 1, 2027. Each county shall comply with the statewide permitting data standard beginning no later than January 1, 2027."
SECTION 3. The office of planning and sustainable development, in collaboration with the chief data officer, shall submit a report of its findings and recommendations, including any proposed legislation, to the legislature no later than twenty days prior to the convening of the regular session of 2027. The report shall include:
(1) The statewide permitting data standard published pursuant to this Act;
(2) The consultation process used to develop the standard, including participation by the counties;
(3) Any barriers to county implementation, including technology constraints, staffing, or legal barriers; and
(4) Any proposed legislation or administrative actions needed to improve statewide permitting data quality and comparability.
SECTION 4. There is appropriated out of the general revenues of the State of Hawaii the sum of $ or so much thereof as may be necessary for fiscal year 2026-2027 for the counties to establish, publish, manage, and periodically update a statewide permitting data standard, to be allocated as follows:
(1) $ to the city and county of Honolulu;
(2) $ to the county of Hawaii;
(3) $ to the county of Kauai; and
(4) $ to the county of Maui.
The sum appropriated shall be expended by the counties for the purposes of this Act.
SECTION 5. New statutory material is underscored.
SECTION 6. This Act shall take effect on July 1, 3000.
Report Title:
Counties; OPSD; Chief Data Officer; Building Permits; Civil Engineering Permits; Statewide Permitting Data Standard; Report; Appropriation
Description:
Requires a statewide permitting data standard developed collaboratively by the Office of Planning and Sustainable Development, county permitting agencies, and the Chief Data Officer. Requires each county to publish monthly updates of building and civil engineering permit data in accordance with that standard. Requires a report to the Legislature. Appropriates funds. Effective 7/1/3000. (HD1)
The summary description of legislation appearing on this page is for informational purposes only and is not legislation or evidence of legislative intent.
|
THE SENATE |
S.B. NO. |
2673 |
|
THIRTY-THIRD LEGISLATURE, 2026 |
S.D. 1 |
|
|
STATE OF HAWAII |
|
|
|
|
|
|
|
|
||
|
|
||
A BILL FOR AN ACT
RELATING TO THE COUNTIES.
BE IT ENACTED BY THE LEGISLATURE OF THE STATE OF HAWAII:
The legislature further finds that the governor's emergency proclamation on housing and the subsequent findings of the simplifying permitting for enhanced economic development task force have highlighted significant challenges in tracking permitting performance. The task force's building permit permitted interaction group found that counties use incompatible data standards to represent permit status, key dates, valuations, and categories, which complicates meaningful comparisons and shared learning. The group further suggested that the counties and the State work toward common data standards and reporting templates for building permits, including more granular status categories that distinguish delays attributable to applicants from delays attributable to agencies.
The legislature finds that while some permit data is currently available, it is often difficult to access or is provided in formats that do not allow for routine aggregation, analysis, or cross-county comparison. Requiring counties to publish permit data in a standardized, machine-readable format will reduce the administrative burden of ad hoc information requests, support customer service improvements, and foster transparency and accountability.
Accordingly, the purpose of this Act is to:
(1) Establish a statewide permitting data standard developed collaboratively by the office of planning and sustainable development and the chief data officer in consultation with the counties;
(2) Require each county to publish monthly updates of building and civil engineering permit data in accordance with that standard;
(3) Require a report to the Legislature; and
(4) Appropriate funds.
SECTION 2. Chapter 46, Hawaii Revised Statutes, is amended by adding a new section to part V to be appropriately designated and to read as follows:
"§46- Publicly accessible permit data; monthly updates; statewide standard. (a) Each county shall host and maintain on its website a publicly accessible dataset containing data on all building and civil engineering permit applications administered by the county.
(b) The dataset required by subsection (a) shall:
(1) Be updated at least monthly;
(2) Be published in a machine-readable format, such as comma-separated values (CSV) or javascript object notation (JSON); and
(3) Include a data dictionary that defines each field and the permitted values for any coded field.
(c) To ensure statewide comparability, each record in the dataset required by subsection (a) shall include, at a minimum, the following fields and defined field names, which shall be populated in accordance with the statewide permitting data standard established under subsection (f):
(1) The permit number ("PermitNum");
(2) A detailed description of work permitted ("Description");
(3) The date on which the permit application was submitted, in YYYY-MM-DD format ("AppliedDate");
(4) The date on which the permit was issued, if applicable, in YYYY-MM-DD format ("IssuedDate");
(5) The date on which the permit was completed or finalized, if applicable, in YYYY-MM-DD format ("CompletedDate");
(6) A raw value indicating the current status of the permit ("StatusCurrent");
(7) The original property street address line 1, as stored by the county ("OriginalAddress1");
(8) The original property street address line 2, as stored by the county, if applicable ("OriginalAddress2");
(9) The original property city, as stored by the county ("OriginalCity");
(10) The original property state, as stored by the county ("OriginalState");
(11) The original property zip code, as stored by the county ("OriginalZip");
(12) A unique identifier for the county publishing the record ("Jurisdiction");
(13) A raw value indicating whether the permit is for residential or non-residential property ("PermitClass");
(14) A standardized value for the permit class, as defined by the statewide permitting data standard ("PermitClassMapped");
(15) A standardized value for the current status, as defined by the statewide permitting data standard ("StatusCurrentMapped");
(16) A raw value indicating whether the permitted work is new construction or work on an existing structure ("WorkClass");
(17) A standardized value for the work class, as defined by the statewide permitting data standard ("WorkClassMapped");
(18) A raw value indicating the permit type in abbreviated or shorthand format ("PermitType");
(19) A standardized value for the permit type, as defined by the statewide permitting data standard ("PermitTypeMapped");
(20) A longer description of the permit type ("PermitTypeDesc");
(21) The date the permit record was last updated in the county's system of record, in YYYY-MM-DD format ("StatusDate");
(22) The total square footage relevant to the permit ("TotalSqFt");
(23) The uniform resource locator to the county's public web page for the permit, if applicable ("Link");
(24) The latitude of the property in decimal degrees ("Latitude");
(25) The longitude of the property in decimal degrees ("Longitude");
(26) The estimated value of the project, if known ("EstProjectCost");
(27) The number of housing units authorized or affected by the permit, if any ("HousingUnits");
(28) The parcel identifier used for tax assessment purposes, including the tax map key, if available ("PIN");
(29) The primary company name of the contractor, if applicable ("ContractorCompanyName");
(30) A raw value indicating the contractor's trade, if applicable ("ContractorTrade");
(31) A standardized value for the contractor's trade, as defined by the statewide permitting data standard, if applicable ("ContractorTradeMapped"); and
(32) The contractor license number, if applicable ("ContractorLicNum").
(d) In addition to the fields and field names provided in subsection (c), each record shall include the following fields and defined field names, if the county's system of record captures the underlying information, to support statewide measurement of permitting timelines and responsibility for any delays:
(1) The date the application was accepted for processing or deemed complete, in YYYY-MM-DD format ("AcceptedDate");
(2) The permitting agency or county department administering the permit, as stored by the county ("PermittingAgency");
(3) The final disposition of the application, limited to: approved, denied, withdrawn, expired, or voided ("FinalDisposition");
(4) The date of the final disposition, in YYYY-MM-DD format ("FinalDispositionDate"); and
(5) The date the permit was last placed on hold or otherwise paused, in YYYY-MM-DD format ("HoldDate").
(e) Each county shall cooperate with the other counties, the office of planning and sustainable development, and the chief data officer to ensure that the statewide permitting data standard established under subsection (f) uses common definitions, common field names, and common standardized values that allow for accurate cross-county comparison. Each county shall:
(1) Designate a permitting data liaison responsible for coordinating implementation of this section;
(2) Provide, upon request, the county's permitting data dictionary, code lists, and documentation needed to map county-specific values to standardized values; and
(3) Maintain and publish, alongside the dataset required by subsection (a), a crosswalk that maps each county‑specific coded value used in fields required by subsections (c) and (d) to the corresponding standardized value.
(f) The office of planning and sustainable development, in collaboration with the chief data officer, shall establish, publish, manage, and periodically update a statewide permitting data standard to implement this section. The statewide permitting data standard shall:
(1) Be designed for routine monthly publication and public use;
(2) Incorporate, at a minimum, the required and recommended fields described in subsections (c) and (d);
(3) Define each field required by subsections (c) and (d), including data types, required formats, and allowable values;
(4) Establish standardized value sets for the fields ending in "Mapped", including status categories that distinguish, at a minimum, between delays attributable to an applicant and delays attributable to an agency;
(5) Specify how a county shall represent missing or inapplicable values; and
(6) Include implementation guidance intended to minimize the administrative burden on the counties.
(g) The statewide permitting data standard required by subsection (f) shall be published no later than January 1, 2027. Each county shall comply with the statewide permitting data standard beginning no later than January 1, 2027."
SECTION 3. The office of planning and sustainable development, in collaboration with the chief data officer, shall submit a report of its findings and recommendations, including any proposed legislation, to the legislature no later than twenty days prior to the convening of the regular session of 2027. The report shall include:
(1) The statewide permitting data standard published pursuant to this Act;
(2) The consultation process used to develop the standard, including participation by the counties;
(3) Any barriers to county implementation, including technology constraints, staffing, or legal barriers; and
(4) Any proposed legislation or administrative actions needed to improve statewide permitting data quality and comparability.
SECTION 4. There is appropriated out of the general revenues of the State of Hawaii the sum of $ or so much thereof as may be necessary for fiscal year 2026-2027 for the counties to establish, publish, manage, and periodically update a statewide permitting data standard, to be allocated as follows:
(1) $ to the city and county of Honolulu;
(2) $ to the county of Maui;
(3) $ to the county of Hawaii; and
(4) $ to the county of Kauai.
The sum appropriated shall be expended by the counties for the purposes of this Act.
SECTION 5. New statutory material is underscored.
SECTION 6. This Act shall take effect on April 19, 2042.
Report Title:
Counties; OPSD; Chief Data Officer; Building Permits; Civil Engineering Permits; Statewide Permitting Data Standard; Report; Appropriation
Description:
Requires a statewide permitting data standard developed collaboratively by the Office of Planning and Sustainable Development and the Chief Data Officer. Requires each county to publish monthly updates of building and civil engineering permit data in accordance with that standard. Requires a report to the Legislature. Appropriates funds. Effective 4/19/2042. (SD1)
The summary description of legislation appearing on this page is for informational purposes only and is not legislation or evidence of legislative intent.
|
THE SENATE |
S.B. NO. |
2673 |
|
THIRTY-THIRD LEGISLATURE, 2026 |
|
|
|
STATE OF HAWAII |
|
|
|
|
|
|
|
|
||
|
|
||
A BILL FOR AN ACT
RELATING TO THE COUNTIES.
BE IT ENACTED BY THE LEGISLATURE OF THE STATE OF HAWAII:
The legislature further finds that the governor's emergency proclamation on housing and the subsequent findings of the simplifying permitting for enhanced economic development task force have highlighted significant challenges in tracking permitting performance. The task force's building permit permitted interaction group found that counties use incompatible data standards to represent permit status, key dates, valuations, and categories, which complicates meaningful comparisons and shared learning. The group further suggested that the counties and the State work toward common data standards and reporting templates for building permits, including more granular status categories that distinguish delays attributable to applicants from delays attributable to agencies.
The legislature finds that while some permit data is currently available, it is often difficult to access or is provided in formats that do not allow for routine aggregation, analysis, or cross-county comparison. Requiring counties to publish permit data in a standardized, machine-readable format will reduce the administrative burden of ad hoc information requests, support customer service improvements, and foster transparency and accountability.
Accordingly, the purpose of this Act is to:
(1) Establish a statewide permitting data standard developed collaboratively by the office of planning and sustainable development and the chief data officer in consultation with the counties; and
(2) Require each county to publish monthly updates of building and civil engineering permit data in accordance with that standard.
SECTION 2. Chapter 46, Hawaii Revised Statutes, is amended by adding a new section to part V to be appropriately designated and to read as follows:
"§46- Publicly accessible permit data; monthly updates; statewide standard. (a) Each county shall host and maintain on its website a publicly accessible dataset containing data on all building and civil engineering permit applications administered by the county.
(b) The dataset required by subsection (a) shall:
(1) Be updated at least monthly;
(2) Be published in a machine-readable format, such as comma-separated values (CSV) or javascript object notation (JSON); and
(3) Include a data dictionary that defines each field and the permitted values for any coded field.
(c) To ensure statewide comparability, each record in the dataset required by subsection (a) shall include, at a minimum, the following fields and defined field names, which shall be populated in accordance with the statewide permitting data standard established under subsection (f):
(1) The permit number ("PermitNum");
(2) A detailed description of work permitted ("Description");
(3) The date on which the permit application was submitted, in YYYY-MM-DD format ("AppliedDate");
(4) The date on which the permit was issued, if applicable, in YYYY-MM-DD format ("IssuedDate");
(5) The date on which the permit was completed or finalized, if applicable, in YYYY-MM-DD format ("CompletedDate");
(6) A raw value indicating the current status of the permit ("StatusCurrent");
(7) The original property street address line 1, as stored by the county ("OriginalAddress1");
(8) The original property street address line 2, as stored by the county, if applicable ("OriginalAddress2");
(9) The original property city, as stored by the county ("OriginalCity");
(10) The original property state, as stored by the county ("OriginalState");
(11) The original property zip code, as stored by the county ("OriginalZip");
(12) A unique identifier for the county publishing the record ("Jurisdiction");
(13) A raw value indicating whether the permit is for residential or non-residential property ("PermitClass");
(14) A standardized value for the permit class, as defined by the statewide permitting data standard ("PermitClassMapped");
(15) A standardized value for the current status, as defined by the statewide permitting data standard ("StatusCurrentMapped");
(16) A raw value indicating whether the permitted work is new construction or work on an existing structure ("WorkClass");
(17) A standardized value for the work class, as defined by the statewide permitting data standard ("WorkClassMapped");
(18) A raw value indicating the permit type in abbreviated or shorthand format ("PermitType");
(19) A standardized value for the permit type, as defined by the statewide permitting data standard ("PermitTypeMapped");
(20) A longer description of the permit type ("PermitTypeDesc");
(21) The date the permit record was last updated in the county's system of record, in YYYY-MM-DD format ("StatusDate");
(22) The total square footage relevant to the permit ("TotalSqFt");
(23) The uniform resource locator to the county's public web page for the permit, if applicable ("Link");
(24) The latitude of the property in decimal degrees ("Latitude");
(25) The longitude of the property in decimal degrees ("Longitude");
(26) The estimated value of the project, if known ("EstProjectCost");
(27) The number of housing units authorized or affected by the permit, if any ("HousingUnits");
(28) The parcel identifier used for tax assessment purposes, including the tax map key, if available ("PIN");
(29) The primary company name of the contractor, if applicable ("ContractorCompanyName");
(30) A raw value indicating the contractor's trade, if applicable ("ContractorTrade");
(31) A standardized value for the contractor's trade, as defined by the statewide permitting data standard, if applicable ("ContractorTradeMapped");
(32) The contractor license number, if applicable ("ContractorLicNum");
(d) In addition to the fields and field names provided in subsection (c), each record shall include the following fields and defined field names, if the county's system of record captures the underlying information, to support statewide measurement of permitting timelines and responsibility for any delays:
(1) The date the application was accepted for processing or deemed complete, in YYYY-MM-DD format ("AcceptedDate");
(2) The permitting agency or county department administering the permit, as stored by the county ("PermittingAgency");
(3) The final disposition of the application, limited to: approved, denied, withdrawn, expired, or voided ("FinalDisposition");
(4) The date of the final disposition, in YYYY-MM-DD format ("FinalDispositionDate"); and
(5) The date the permit was last placed on hold or otherwise paused, in YYYY-MM-DD format ("HoldDate").
(e) Each county shall cooperate with the other counties, the office of planning and sustainable development, and the chief data officer to ensure that the statewide permitting data standard established under subsection (f) uses common definitions, common field names, and common standardized values that allow for accurate cross-county comparison. Each county shall:
(1) Designate a permitting data liaison responsible for coordinating implementation of this section;
(2) Provide, upon request, the county's permitting data dictionary, code lists, and documentation needed to map county-specific values to standardized values; and
(3) Maintain and publish, alongside the dataset required by subsection (a), a crosswalk that maps each county‑specific coded value used in fields required by subsection (c) and (d) to the corresponding standardized value.
(f) The office of planning and sustainable development, in collaboration with the chief data officer, shall establish, publish, manage, and periodically update a statewide permitting data standard to implement this section. The statewide permitting data standard shall:
(1) Be designed for routine monthly publication and public use;
(2) Incorporate, at a minimum, the required and recommended fields described in the Building and Land Development Specification core permit dataset requirements;
(3) Define each field required by subsections (c) and (d), including data types, required formats, and allowable values;
(4) Establish standardized value sets for the fields ending in "Mapped", including status categories that distinguish, at a minimum, between delays attributable to an applicant and delays attributable to an agency;
(5) Specify how a county shall represent missing or inapplicable values; and
(6) Include implementation guidance intended to minimize the administrative burden on the counties.
(g) The statewide permitting data standard required by subsection (f) shall be published no later than July 1, 2026. Each county shall comply with the statewide permitting data standard beginning no later than January 1, 2027."
SECTION 3. No later than twenty days prior to the convening of the regular session of 2027, the office of planning and sustainable development, in collaboration with the chief data officer, shall submit a report to the legislature describing:
(1) The statewide permitting data standard published pursuant to this Act;
(2) The consultation process used to develop the standard, including participation by the counties;
(3) Any barriers to county implementation, including technology constraints, staffing, or legal barriers; and
(4) Any proposed legislation or administrative actions needed to improve statewide permitting data quality and comparability.
SECTION 4. New statutory material is underscored.
SECTION 5. This Act shall take effect upon its approval.
|
INTRODUCED BY: |
_____________________________ |
|
|
|
Report Title:
Counties; OPSD; Chief Data Officer; Building Permits; Civil Engineering Permits; Statewide Permitting Data Standard; Report
Description:
Requires a statewide permitting data standard developed collaboratively by the Office of Planning and Sustainable Development and the Chief Data Officer. Requires each county to publish monthly updates of building and civil engineering permit data in accordance with that standard. Requires report.
The summary description of legislation appearing on this page is for informational purposes only and is not legislation or evidence of legislative intent.
|
Date
|
Status
|
|---|---|
| Jun 5, 2026 | Act 104, on 06/05/2026 (Gov. Msg. No. 1204). |
| Jun 5, 2026 | Act 104, 06/05/2026 (Gov. Msg. No. 1204). |
| May 8, 2026 | Enrolled to Governor. |
| May 8, 2026 | Received notice of passage on Final Reading in House (Hse. Com. No. 888). |
| May 6, 2026 | Received notice of Final Reading (Sen. Com. No. 816). |
| May 6, 2026 | Passed Final Reading as amended in CD 1 with none voting aye with reservations; none voting no (0) and none excused (0). |
| May 6, 2026 | Passed Final Reading, as amended (CD 1). Ayes, 25; Aye(s) with reservations: none . 0 No(es): none. 0 Excused: none. |
| May 1, 2026 | Forty-eight (48) hours notice Wednesday, 05-06-26. |
| May 1, 2026 | Reported from Conference Committee (Conf Com. Rep. No. 192-26) as amended in (CD 1). |
| May 1, 2026 | 48 Hrs. Notice (as amended CD 1) 05-06-26. |
| May 1, 2026 | Reported from Conference Committee as amended CD 1 (Conf. Com. Rep. No. 192-26). |
| May 1, 2026 | The Conference Committee recommends that the measure be Passed, with Amendments. The votes were as follows: 3 Ayes: Representative(s) Hashem, Morikawa, Shimizu; Ayes with reservations: none; 0 Noes: none; and 0 Excused: none. |
| May 1, 2026 | The Conference committee recommends that the measure be PASSED, WITH AMENDMENTS. The votes of the Senate Conference Managers were as follows: 4 Aye(s): Senator(s) Wakai, Lee, C., Hashimoto, Fevella; Aye(s) with reservations: none ; 0 No(es): none; and 0 Excused: none. |
| May 1, 2026 | Conference committee meeting to reconvene on 05-01-26 12:15 PM; Conference Room 325. |
| Apr 30, 2026 | Conference committee meeting to reconvene on 05-01-26 10:45AM; Conference Room 325. |
| Apr 29, 2026 | Conference committee meeting to reconvene on 04-30-26 10:50AM; Conference Room 325. |
| Apr 27, 2026 | Conference committee meeting scheduled for 04-29-26 10:50AM; Conference Room 325. |
| Apr 21, 2026 | Received notice of Senate conferees (Sen. Com. No. 718). |
| Apr 21, 2026 | Senate Conferees Appointed: Wakai Chair; Lee, C., Hashimoto Co-Chairs; Fevella. |
| Apr 21, 2026 | Received notice of appointment of House conferees (Hse. Com. No. 800). |
| Apr 21, 2026 | House Conferees Appointed: Hashem, Morikawa Co-Chairs; Shimizu. |
| Apr 16, 2026 | Received notice of disagreement (Sen. Com. No. 710). |
| Apr 16, 2026 | Senate disagrees with House amendments. |
| Apr 16, 2026 | Received from House (Hse. Com. No. 688). |
| Apr 14, 2026 | Passed Third Reading with Representative(s) Cochran, Shimizu voting aye with reservations; none voting no (0) and Representative(s) Quinlan excused (1). Transmitted to Senate. |
| Apr 10, 2026 | Deferred one day 04-14-26. |
| Apr 10, 2026 | Reported from FIN (Stand. Com. Rep. No. 2070-26), recommending passage on Third Reading. |
| Apr 7, 2026 | The committee on FIN recommend that the measure be PASSED, UNAMENDED. The votes were as follows: 15 Ayes: Representative(s) Todd, Takenouchi, Hartsfield, Hussey, Keohokapu-Lee Loy, Kitagawa, Kusch, Lee, M., Miyake, Perruso, Templo, Yamashita, Alcos, Gedeon, Reyes Oda; Ayes with reservations: none; 0 Noes: none; and 1 Excused: Representative(s) Morikawa. |
| Apr 2, 2026 | Bill scheduled for decision making on Tuesday, 04-07-26 10:10AM in conference room 308 VIA VIDEOCONFERENCE. |
| Apr 2, 2026 | The committee(s) on FIN recommend(s) that the measure be deferred until 04-07-26. |
| Mar 31, 2026 | Bill scheduled to be heard by FIN on Thursday, 04-02-26 2:00PM in House conference room 308 VIA VIDEOCONFERENCE. |
| Mar 19, 2026 | Passed Second Reading as amended in HD 1 and referred to the committee(s) on FIN with none voting aye with reservations; none voting no (0) and none excused (0). |
| Mar 19, 2026 | Reported from WAL (Stand. Com. Rep. No. 1239-26) as amended in HD 1, recommending passage on Second Reading and referral to FIN. |
| Mar 17, 2026 | The committee on WAL recommend that the measure be PASSED, WITH AMENDMENTS. The votes were as follows: 7 Ayes: Representative(s) Hashem, Morikawa, Ichiyama, Iwamoto, Poepoe, Shimizu, Souza; Ayes with reservations: none; Noes: none; and 2 Excused: Representative(s) Belatti, Woodson. |
| Mar 12, 2026 | Bill scheduled to be heard by WAL on Tuesday, 03-17-26 9:00AM in House conference room 411 VIA VIDEOCONFERENCE. |
| Mar 10, 2026 | Referred to WAL, FIN, referral sheet 16 |
| Mar 10, 2026 | Pass First Reading |
| Mar 6, 2026 | Received from Senate (Sen. Com. No. 74) in amended form (SD 1). |
| Mar 6, 2026 | Report Adopted; Passed Third Reading. Ayes, 24; Aye(s) with reservations: none. Noes, 0 (none). Excused, 1 (Senator(s) Ihara). Transmitted to House. |
| Mar 5, 2026 | One Day Notice 03-06-26. |
| Mar 5, 2026 | Reported from WAM (Stand. Com. Rep. No. 2855) with recommendation of passage on Third Reading. |
| Mar 3, 2026 | The committee(s) on WAM recommend(s) that the measure be PASSED, UNAMENDED. The votes in WAM were as follows: 12 Aye(s): Senator(s) Dela Cruz, Moriwaki, DeCoite, Elefante, Hashimoto, Inouye, Kanuha, Kidani, Kim, Lee, C., Richards, Wakai; Aye(s) with reservations: none ; 0 No(es): none; and 1 Excused: Senator(s) Fevella. |
| Feb 25, 2026 | The committee(s) on WAM deferred the measure until 03-03-26 10:15AM; Conference Room 211 & Videoconference. |
| Feb 23, 2026 | The committee(s) on WAM will hold a public decision making on 02-25-26 10:57AM; Conference Room 211 & Videoconference. |
| Feb 19, 2026 | Report adopted; Passed Second Reading, as amended (SD 1) and referred to WAM. |
| Feb 19, 2026 | Reported from EIG/WLA (Stand. Com. Rep. No. 2465) with recommendation of passage on Second Reading, as amended (SD 1) and referral to WAM. |
| Feb 17, 2026 | The committee(s) on WLA recommend(s) that the measure be PASSED, WITH AMENDMENTS. The votes in WLA were as follows: 4 Aye(s): Senator(s) Lee, C., Chang, Lamosao, DeCorte; Aye(s) with reservations: none ; 0 No(es): none; and 1 Excused: Senator(s) Inouye. |
| Feb 17, 2026 | The committee(s) on EIG recommend(s) that the measure be PASSED, WITH AMENDMENTS. The votes in EIG were as follows: 5 Aye(s): Senator(s) Wakai, Chang, DeCoite, Fevella; Aye(s) with reservations: Senator(s) Richards ; 0 No(es): none; and 0 Excused: none. |
| Feb 13, 2026 | The committee(s) on EIG/WLA has scheduled a public hearing on 02-17-26 3:03PM; Conference Room 224 & Videoconference. |
| Jan 28, 2026 | Referred to EIG/WLA, WAM. |
| Jan 26, 2026 | Passed First Reading. |
| Jan 23, 2026 | Introduced. |
|
Date
|
Description
|
Location
|
Votes
|
|
|---|---|---|---|---|
| May 6, 2026 | Final Reading | House Floor |
Passed |
|
| May 6, 2026 | Final Reading | Senate Floor |
Passed |
|
| Apr 14, 2026 | Third Reading | House Floor |
Passed |
|
| Apr 7, 2026 | The committee on FIN recommend that the measure be PASSED, UNAMENDED | House Standing Committee on Finance |
Passed |
|
| Mar 17, 2026 | The committee on WAL recommend that the measure be PASSED, WITH AMENDMENTS | House Standing Committee on Water & Land |
Passed |
|
| Mar 6, 2026 | Third Reading | Senate Floor |
Passed |
|
| Mar 3, 2026 | The committee(s) on WAM recommend(s) that the measure be PASSED, UNAMENDED | Senate Standing Committee on Ways and Means |
Passed |
|
| Feb 17, 2026 | The committee(s) on WLA recommend(s) that the measure be PASSED, WITH AMENDMENTS | Senate Standing Committee on Water, Land, Culture and the Arts |
Passed |
|
| Feb 17, 2026 | The committee(s) on EIG recommend(s) that the measure be PASSED, WITH AMENDMENTS | Senate Standing Committee on Energy and Intergovernmental Affairs |
Passed |
This list shows positions taken on this bill by organizations on the date displayed, which is linked to the original source.
Positions by individuals are not included.
|
Organization
|
Position
|
Date
|
|---|---|---|
| Maui Chamber of Commerce | *** Support | Apr 2, 2026 |
| Office of Enterprise Technology Services | ** Support | |
| Office of Enterprise Technology Services | *** Support | Feb 17, 2026 |
| Office of Planning and Sustainable Development | *** Support | Feb 25, 2026 |
STAND. COM. REP. NO. 2855
Honolulu, Hawaii
RE: S.B. No. 2673
S.D. 1
Honorable Ronald D. Kouchi
President of the Senate
Thirty-Third State Legislature
Regular Session of 2026
State of Hawaii
Sir:
Your Committee on Ways and Means, to which was referred S.B. No. 2673, S.D. 1, entitled:
"A BILL FOR AN ACT RELATING TO THE COUNTIES,"
begs leave to report as follows:
The purpose and intent of this measure is to establish statewide permitting data standards and to require counties to report on certain permit applications under those standards.
Specifically, this measure:
(1) Requires the Office of Planning and Sustainable Development and the Chief Data Officer to create a statewide permitting data standard to be used by the counties for reporting permitting data;
(2) Requires each county to use the statewide standards to publish on its website certain data on building and civil engineering permit applications administered by that county;
(3) Requires the Office of Planning and Sustainable Development and the Chief Data Officer to submit a report to the Legislature before the Regular Session of 2027; and
(4) Appropriates moneys to the counties to establish and administer data collection and data reporting process.
Your Committee received written comments on this measure from the Office of Enterprise Technology Services and Office of Planning and Sustainable Development.
Your Committee finds that maintaining consistent and comparable data across counties would enable the State to better identify gaps and address deficiencies in construction permitting processes. The standardized data required by this measure will help expedite permitting and advance the States broader affordable housing and infrastructure objectives.
As affirmed by the record of votes of the members of your Committee on Ways and Means that is attached to this report, your Committee is in accord with the intent and purpose of S.B. No. 2673, S.D. 1, and recommends that it pass Third Reading.
Respectfully submitted on behalf of the members of the Committee on Ways and Means,
|
|
|
________________________________ DONOVAN M. DELA CRUZ, Chair |
|
|
|
|
STAND. COM. REP. NO. 2465
Honolulu, Hawaii
RE: S.B. No. 2673
S.D. 1
Honorable Ronald D. Kouchi
President of the Senate
Thirty-Third State Legislature
Regular Session of 2026
State of Hawaii
Sir:
Your Committees on Energy and Intergovernmental Affairs and Water, Land, Culture and the Arts, to which was referred S.B. No. 2673 entitled:
"A BILL FOR AN ACT RELATING TO THE COUNTIES,"
beg leave to report as follows:
The purpose and intent of this measure is to require:
(1) A statewide permitting data standard developed collaboratively by the Office of Planning and Sustainable Development and the Chief Data Officer;
(2) Each county to publish monthly updates of building and civil engineering permit data in accordance with that standard; and
(3) A report to the Legislature.
Your Committees received testimony in support of this measure from the Office of Planning and Sustainable Development and Office of Enterprise Technology Services.
Your Committees received comments on this measure from the Department of the Attorney General.
Your Committees find that the expedient processing of building permits is critical to addressing the State's housing shortage, enabling renewable energy projects, and supporting economic development. Establishing uniform data sets is a significant step toward enabling accurate comparisons between jurisdictions and fostering evidence-based decision-making. By creating a transparent and consistent data environment, this measure seeks to effectively identify and address systemic bottlenecks in the permitting process, which is essential for meeting the State's broader housing and infrastructure goals.
Your Committees acknowledge the concerns raised in testimony by the Department of the Attorney General that the publishing deadline of July 1, 2026, for the statewide permitting data standard may present implementation challenges; that the absence of appropriations to the counties may constitute an unfunded mandate; and that this measure lacks clarity of references to the Building and Land Development Specification core permit dataset requirements. Your Committees further acknowledge the concerns raised in testimony by the Office of Planning and Sustainable Development that the Office may not be the appropriate agency to develop and manage statewide permitting data. Therefore, amendments to this measure are necessary to address these concerns.
Accordingly, your Committees have amended this measure by:
(1) Clarifying that the statewide permitting data standard shall incorporate certain fields and defined field names;
(2) Specifying that the statewide permitting data standard shall be published no later than January 1, 2027;
(3) Inserting a blank appropriation amount for the counties to establish, publish, manage, and periodically update a statewide permitting data standard;
(4) Amending section 1 to reflect its amended purpose;
(5) Inserting an effective date of April 19, 2042, to encourage further discussion; and
(6) Making technical, nonsubstantive amendments for the purposes of clarity and consistency.
As affirmed by the records of votes of the members of your Committees on Energy and Intergovernmental Affairs and Water, Land, Culture and the Arts that are attached to this report, your Committees are in accord with the intent and purpose of S.B. No. 2673, as amended herein, and recommend that it pass Second Reading in the form attached hereto as S.B. No. 2673, S.D. 1, and be referred to your Committee on Ways and Means.
Respectfully submitted on behalf of the members of the Committees on Energy and Intergovernmental Affairs and Water, Land, Culture and the Arts,
|
________________________________ CHRIS LEE, Chair |
|
________________________________ GLENN WAKAI, Chair |
|
|
|
|
|
Date
|
Testimony PDF
|
|---|---|
| Apr 2, 2026 | SB2673_HD1_TESTIMONY_FIN_04-02-26_.PDF |
| Mar 17, 2026 | SB2673_SD1_TESTIMONY_WAL_03-17-26_.PDF |
| Feb 25, 2026 | SB2673_SD1_TESTIMONY_WAM_02-25-26_.PDF |
| Feb 17, 2026 | SB2673_TESTIMONY_WLA-EIG_02-17-26_.PDF |
Discussed in Hearing
2MIN
Conference Committee
1MIN
Conference Committee
8MIN
Conference Committee
1MIN
Conference Committee
39SEC
House Standing Committee on Water & Land
2MIN
Senate Standing Committee on Energy and Intergovernmental Affairs
2MIN
Senate Standing Committee on Water, Land, Culture and the Arts
2MIN
Senate Standing Committee on Transportation
Bill Author
