On April 1, 2026, a revised Texas Statistical Plan for Residential Risks takes effect.[1] Driven by House Bill 2067, passed during the 89th Texas Legislature, the new plan introduces two entirely new reporting requirements that have never existed in the residential statistical plan before, revises the transmittal form, adds a new policy-level data field, and clarifies several long-standing rules that have been sources of confusion for Texas Insurers.[2][3][4]
For any carrier writing homeowners, dwelling fire, tenants, or condominium policies in Texas (which means virtually every admitted residential property insurer in the state), this change requires action now. The first new reports are due June 15, 2026, covering April 2026 experience. That window is short, and the data infrastructure requirements are non-trivial.
This briefing walks through every material change in the revised plan, explains the legislative intent behind the new requirements, sets out the compliance calendar, and provides a concrete readiness checklist for compliance, actuarial, underwriting, IT, and systems teams.
The April 1, 2026 effective date is firm. The original effective date of January 1, 2026 was extended to April 1 specifically to give carriers more time to update coding and programming systems. TDI has stated it will not extend the deadline again. Carriers that have not begun preparation are at risk of first-report non-compliance.
The Legislative Driver: Texas House Bill 2067
To understand why the April 2026 changes look the way they do, you need to start with House Bill 2067, passed during the 89th Texas Legislature in 2025.[4] The bill made a deceptively simple change to Texas Insurance Code: it eliminated the requirement that policyholders must request a written explanation when their coverage is declined, canceled, or not renewed, and replaced it with an automatic disclosure obligation. Carriers must now proactively provide written reasons to the policyholder and, where applicable, to their licensed property and casualty agent.[4]
But HB 2067 went further. It also requires carriers to submit written reports to TDI, at least once per quarter, summarizing their reasons for declinations, cancellations, and nonrenewals, categorized by ZIP code.[3] This ZIP-code-level granularity is not incidental: it is the mechanism by which TDI will monitor whether carriers are effectively withdrawing from specific geographic markets or concentrating underwriting restrictions in particular communities.[4]
TDI is implementing HB 2067 in phases
- Phase 1 covers residential property and private passenger automobile insurance.
- Phase 2 will address commercial lines.
- Phase 3 will investigate reporting for lines not currently covered by a TDI statistical plan.[3]
This means the data infrastructure you build now for residential reporting will likely be the template for future obligations.
The date shift from January 1 to April 1 was also a direct response to carrier concerns. Multiple commenters in the rulemaking process cited the difficulty of updating coding and programming systems in time for a January 1 effective date. TDI agreed the additional time was warranted and extended the deadline, explicitly stating it believed a 90-day extension would provide sufficient time for implementation. That extension is now exhausted.
TDI stated the rationale directly in its 2024 Biennial Report: it recommended to the Legislature that insurance companies be required to tell consumers why a policy was declined, canceled, or nonrenewed because the existing law only required disclosure when the consumer asked. HB 2067 implemented that recommendation.
What Will Change: A Full Overview
The revised plan is a comprehensive rewrite, not a targeted amendment. While the core premium and loss reporting framework remains intact, several areas have been substantively revised or added. The table below maps the major changes:
| Area | Status | What Changed |
| Cancellation / Nonrenewal / Declination Notices | NEW | Brand-new monthly report. Carriers must report the reasons they gave policyholders for each action, by ZIP code, using coded reason fields. Due date: 45 days after experience month. |
| Actual Cancellations / Nonrenewals / Declinations Count | NEW | Brand-new monthly report. Carriers report the count of actual actions taken (not just notices) by ZIP code. Must reconcile with NAIC MCAS data. Due date: 45 days after experience month. |
| Transmittal Form | REVISED | Four report categories now required (was two). New fields for Notified Policy Count and Actualized Policy Count by action type. |
| Roof Coverage Type | NEW FIELD | New data element on premium and loss records. Must report whether roof coverage is replacement cost or ACV (even when the same as the overall dwelling coverage). |
| Private Flood Reporting | CLARIFIED | Explicit instructions added for stand-alone primary flood policies (LOB code 35). Excess flood policies expressly excluded. Cause of loss code 32 added for flood. |
| TWIA Depopulation Reporting | REVISED | New Record Type codes 07, 08 added. Specific instructions for assumption reinsurance transactions with premium reporting on gross basis. |
| Claim Status Codes | CLARIFIED | Expanded rules for claim status 1–6, including explicit treatment of claims closed with vs. without indemnity payment and expense-only closures. |
| Submission Medium | REVISED | All records must be submitted to TICO electronically. ShareFile portal references updated in transmittal requirements. |
The remainder of this briefing addresses each of these changes in detail, with specific attention to the new reporting requirements that represent the most significant compliance burden.
The Two New Reports: What they are and What they Require
The most consequential changes in the April 2026 plan are the two entirely new monthly reports introduced in Sections E, F, and G of the revised plan. Neither of these existed before. Both require data that many carriers currently capture inconsistently, store in fragmented systems, or do not capture at all at the level of granularity the plan demands.
Report 1: Cancellation, Nonrenewal, and Declination Notices (Sections E and F)
This report requires carriers to summarize the reasons stated in cancellation, nonrenewal, and declination notices provided to policyholders, applicants, and their agents under Insurance Code Chapter 551.[1] For each notice, the carrier must report:
- Notification date (the date the notice was sent)
- Action type (cancellation, nonrenewal, or declination)
- Type of policy (homeowners, dwelling, tenants, etc.)
- Reason source indicator (whether the reason came from the carrier, agent, or both)
- 60-day indicator (whether the notice was issued at least 60 days before the effective date)
- ZIP code of the risk
- Action effective date (the date the cancellation, nonrenewal, or declination takes effect)
- Reason code list — a concatenated alphabetical string of applicable reason codes from the plan’s codeset[1]
- Notified policy count — the number of policies that received a notice with that exact combination of fields[1]
The Reason Code Framework
The plan defines a specific set of reason codes that carriers must use to classify the basis for each action.[1] When multiple reasons apply, the carrier concatenates them in alphabetical order. For example, if reasons D, R, and L apply, the filed reason code is “DLR.” This concatenation approach means a single record can capture multi-factor decisions without requiring separate records for each reason.
The current reason code framework defined in the plan includes the following:
| Code | Reason Description | Applies To |
| A | Aggressive or threatening behavior by applicant/insured | C, NR, D |
| B | Fraud or material misrepresentation in application | C, NR, D |
| C | Failure to pay premium | C |
| D | Underwriting — Physical condition of the property | C, NR, D |
| E | Underwriting — Geographic / territory restrictions | C, NR, D |
| F | Underwriting — Prior claims history | C, NR, D |
| G | Underwriting — Occupancy or use of property | C, NR, D |
| H | Underwriting — Inability to inspect property | C, NR, D |
| I | Underwriting — Risk exceeds capacity | C, NR, D |
| J | Underwriting — Insured value or replacement cost | C, NR, D |
| K | Underwriting — Roof condition | C, NR, D |
| L | Underwriting — All other underwriting reasons | C, NR, D |
| M | Policy no longer available in market | NR |
| N | Change in insurer’s appetite/market withdrawal | NR, D |
| O | Insured’s request | C |
| P | Company/agency relationship change | C, NR |
| Q | Insured obtained coverage elsewhere | C |
| R | Other | C, NR, D |
| X | Assumption Reinsurance (TWIA only) | C |
Note that the reason codes are not arbitrary: they correspond to the reasons that must appear in the notice sent to the policyholder or applicant under Insurance Code Chapter 551.[1] This creates a direct linkage between your policyholder-facing notices and your TICO statistical submissions, meaning discrepancies between the two will be detectable by TDI.
Carriers cannot file reason codes in their TICO submission that differ from what was stated in the notice to the policyholder. The plan requires that the reported codes reflect the reasons given in the notice — not the carrier’s internal underwriting rationale. Your notice language and your statistical coding must be aligned.
Scope and Applicability
This reporting is required for notices related to cancellations, nonrenewals, and declinations effective on or after April 1, 2026, with two important exceptions: (1) declinations of applications made before April 1, 2026, and (2) cancellations of policies that were delivered, issued for delivery, or renewed before April 1, 2026.[1]
There is also a critical transition provision for the first report: carriers must include in their April 2026 submission any nonrenewal notices made before April 1, 2026, for policies whose nonrenewal is effective on or after April 1, 2026.[1] This means your first filing will require retroactive data capture: nonrenewal notices that were sent before the effective date but for future-dated actions.
The first report due June 15, 2026 is not a clean start. It includes pre-April 1 nonrenewal notices for policies nonrenewing on or after April 1. Carriers must trace back through their notice logs to identify these records, which may require coordination between underwriting, policy admin, and compliance teams.
Report 2: Number of Actual Cancellations, Nonrenewals, and Declinations (Section G)
The second new report is distinct from the notices report. Where Sections E and F capture the reasons stated in notices, Section G captures the counts of actions that actually took effect, by ZIP code, in each experience month.[1]
This report requires carriers to summarize, for each ZIP code, the number of actual cancellations (entire policy only), nonrenewals, and declinations of completed and submitted applications that had an effective date within the experience month.[1]
- Cancellations: Report only when the entire policy is canceled. Partial cancellations (e.g., removing a coverage) are not counted. If a canceled policy is later reinstated, the cancellation must still be reported.[1]
- Nonrenewals: Report by effective date of the nonrenewal.[1]
- Declinations: Report declinations of completed and submitted applications only.[1]
- Exclusions: Do not report rescissions or policies voided under Insurance Code Chapter 705. Do not count intra-group policyholder transfers.[1]
Critically, the plan explicitly states that the actual cancellation and nonrenewal counts in this Section G report must reconcile with the data submitted to the NAIC for the Market Conduct Annual Statement (MCAS).[1] This creates a formal cross-referencing obligation: TDI will be able to compare your TICO filings against your MCAS submissions. Discrepancies between the two will be visible to regulators.
The TICO Section G counts must reconcile with your NAIC MCAS cancellation and nonrenewal data. If your MCAS and TICO submissions are compiled by different teams from different source systems, build a reconciliation step before either report leaves your organization.
Other Material Changes in the Revised Plan
New Data Element: Roof Coverage Type
The revised plan adds a new required field to both premium and loss records: Roof Coverage Type. Carriers must report whether the policy provides roof coverage on a replacement cost or actual cash value (ACV) basis, including the impact of any endorsements.[1]
The rule has three nuances that operators must understand:
- Endorsement override: If a policy normally provides replacement cost to the dwelling but has an ACV roof endorsement, report as ACV roof. The endorsement controls, not the base policy.[1]
- Same-as-dwelling reporting still required: Even if the roof coverage type is the same as the dwelling coverage type (e.g., both replacement cost), the field must still be populated. This is an explicit requirement in the plan.[1]
- Declining schedules = ACV: Policies that provide a declining schedule of payments based on the age of the home or roof (whether expressed as a percentage of replacement cost or otherwise) must be reported as ACV.[1]
For carriers with a large portfolio of policies that have ACV roof endorsements, mixed roof-and-dwelling coverage structures, or age-based depreciation schedules, this field will require careful configuration in your policy admin system.
Revised Private Flood Reporting
The revised plan provides explicit, detailed instructions for private flood coverage reporting that were absent or ambiguous in prior versions.[1]
- Embedded flood coverage in HO policies: Report private flood coverage indicator “1” if the policy provides flood or rising water coverage, whether as part of the base policy, a premium-bearing endorsement, or a nonpremium-bearing endorsement.[1]
- Stand-alone primary flood policies: These are now explicitly reportable under Line of Business code 35. “Primary” means any private residential flood policy other than an excess flood policy.[1]
- Excess flood policies excluded: A private residential flood policy is an excess policy, and is therefore excluded from reporting, if it has a deductible greater than 10% of the dwelling limit or greater than $100,000.[1]
- NFIP / Write Your Own policies: Explicitly excluded. Do not report federal flood policies written through the NFIP’s Write Your Own program.[1]
- Cause of loss code: All flood losses must use cause of loss code 32.[1]
TWIA Depopulation Reporting
The revised plan provides explicit Record Type codes for TWIA depopulation transactions via Assumption Reinsurance (AR).[1]
- TWIA uses Record Type 07 to report a policy cancellation due to assumption reinsurance, with Action Type 80 and Reason Code X.[1]
- The assuming voluntary insurer uses Record Type 08 to report assumption of a TWIA wind-only policy.[1]
- Both TWIA and the voluntary insurer must report the premium on a gross basis — no deduction for reinsurance commissions.[1]
- The effective date for both transactions is the date the voluntary take-out insurer assumes the policy at the end of the required opt-out period.[1]
Carriers participating in TWIA depopulation programs should confirm that their reporting systems can generate both transaction types correctly and that their premium reporting reflects the gross basis requirement.
Prior Claims History Coding Clarification
The revised plan adds explicit language clarifying what may and may not be counted as a chargeable claim for prior claims history reporting. Carriers that use prior claims history in rating or tiering must report a 0–5 code reflecting claims in the previous five years.[1] The plan now explicitly states that the following may never be counted as a chargeable claim:
- Claims resulting from losses caused by natural causes[1]
- Claims filed but not paid or payable under a residential property policy[1]
- Claims prohibited from use under Texas Insurance Code §544.353[1]
Claim Status, New Claim Count, and Reopened Claim Count Expanded Rules
The revised plan contains substantially expanded rules for claim reporting, including detailed guidance on claim status codes 1–6, the distinction between “never previously reported as closed” and “previously reported as closed” claims, and explicit treatment of expense-only closures.[1]
Key points for claims teams and actuarial staff:
- Use status codes 1–3 for claims never previously reported as closed; use 4–6 for claims previously reported as closed.[1]
- Closed with indemnity payment (codes 2 or 5) includes cases where the payment was subsequently recovered from a source other than the insured — except where all payments were recovered from the insured.[1]
- Expense-only closures use status code 3 or 6, not 2 or 5.[1]
- New claims must be reported in the month the claim was reported to the carrier, regardless of whether a payment was made or reserve established.[1]
The Compliance Calendar: TICO Deadlines and Key Dates
All TICO reports remain due within 45 days after the close of the experience month.[1] The new reports follow the same cadence. The table below sets out the key dates for the transition period and ongoing compliance:
| Report | Experience Period | Due Date | Notes |
| Cancellation / Nonrenewal / Declination Notices | April 2026 (first report) | June 15, 2026 | Include pre-4/1 notices for policies nonrenewing on/after 4/1 |
| Actual Cancellations / Nonrenewals / Declinations | April 2026 (first report) | June 15, 2026 | Count by ZIP of actions with effective date in April 2026 |
| Ongoing — both new reports | Each subsequent month | 45 days after close of experience month | E.g., May 2026 experience due July 15, 2026 |
| Premium & Loss Reports (existing) | Each month, unchanged | 45 days after close of experience month | No change to existing premium/loss submission cadence |
| Annual Reconciliation | Once per calendar year | Per TICO coordination | Required by Rule 21 — submit to TICO annually |
Note: Rule 21 of the revised plan also requires that carriers submit an annual reconciliation to TICO’s designated statistical agent once per year.[1] This reconciliation requirement is unchanged from the prior plan but is worth ensuring remains on your compliance calendar.
The June 15, 2026 first-report deadline for both new reports is not negotiable. The 45-day clock starts from the close of April 2026. Carriers must complete TICO electronic submission testing for the Section E and G record layouts before that date, which means the testing process should begin immediately.
The Revised Transmittal Form
Every data submission to TICO must be accompanied by a transmittal form. The revised plan updates the transmittal form to reflect the four report categories now required.[1] The form must now include:
- Company Name and NAIC Company Code (unchanged)
- Record Count for all four report types: (1) Dwelling/HO Premiums, (2) Dwelling/HO Losses, (3) Dwelling/HO Cancellation/Nonrenewal/Declination Notices, (4) Dwelling/HO Number of Actual Cancellations/Nonrenewals/Declinations
- Totals for Significant Fields: Written Premium, Paid Losses, Outstanding Losses
- Notified Policy Count for Cancellations, Nonrenewals, and Declinations separately[1]
- Actualized Policy Count for Cancellations, Nonrenewals, and Declinations separately[1]
- Type of Reporting Medium: all records must be submitted electronically; contact TICO for set-up instructions[1]
- Record and Format Information: Files must be Fixed ASCII: Standard Data Format (SDF)[1]
Carriers using internally developed or vendor-managed transmittal form templates must update those templates before the first June 15 submission. The prior form template that omits the new counts is no longer compliant.
How to Prepare: TICO Reporting Readiness Checklist
| 1 | Systems & Data | Confirm your policy admin and underwriting systems capture the reason for every cancellation, nonrenewal, and declination at the time the action is taken — not retroactively. |
| 2 | Systems & Data | Verify that reason data is stored at the policy/application level and includes the notification date, action effective date, action type, and ZIP code. |
| 3 | Systems & Data | Map your internal cancellation / nonrenewal / declination reason codes to the TICO plan’s reason codes (A through R and X). Document the mapping in writing. |
| 4 | Systems & Data | Confirm your system can output Fixed ASCII / SDF format for the new Sections E and G record layouts. |
| 5 | Systems & Data | Update the transmittal form template to include the four report categories and new Notified / Actualized Policy Count fields. |
| 6 | Compliance & Legal | Review notice language sent to policyholders under Insurance Code Chapter 551 to confirm that the stated reasons align with the reason codes you will report. |
| 7 | Compliance & Legal | Determine which actions taken before April 1, 2026, on policies nonrenewing on or after April 1, 2026, must be included in your first June 15 submission. |
| 8 | Compliance & Legal | Confirm your process for excluding rescissions and policies voided under Insurance Code Chapter 705 from cancellation counts. |
| 9 | Compliance & Legal | Confirm that intra-group policyholder transfers are excluded per Insurance Code §551.004. |
| 10 | Actuarial / Finance | Establish a reconciliation process between your TICO actual cancellation/nonrenewal counts and your NAIC MCAS submissions. |
| 11 | Actuarial / Finance | Verify that the roof coverage type field (replacement cost vs. ACV) is captured for all residential policies — including cases where roof coverage matches the dwelling coverage type. |
| 12 | IT / Vendor Coordination | Contact TICO at 512-444-9611 to initiate electronic submission testing for the new Sections E and G record layouts before the June 15 deadline. |
| 13 | IT / Vendor Coordination | If you use a policy administration vendor, confirm their timeline for delivering Section E and G extract capabilities and the roof coverage type data element. |
| 14 | IT / Vendor Coordination | Update your regulatory calendar to add the new monthly reporting deadlines and the June 15 first-report milestone. |
The Data Architecture Challenge for Texas Insurance Companies
The two new reports expose a structural weakness in how most carriers currently manage cancellation, nonrenewal, and declination data. In the legacy operating model, the reason for a policy action is documented in a notice letter, filed in a document management system, and occasionally tracked in a CRM or underwriting workbench. It is rarely structured data and it is almost never stored in a way that maps directly to a regulatory reporting code.
What the April 2026 plan requires is a fundamental shift: the reason for every cancellation, nonrenewal, and declination must be captured as structured, coded data at the time the action is taken. It must be associated with the notification date, the effective date, the action type, the ZIP code, and the applicable reason code list. And it must be available for extraction into a Fixed ASCII / SDF file within 45 days of the close of each experience month, every month, indefinitely.
Carriers that rely on document-based reason tracking face a rebuild of their cancellation/nonrenewal/declination workflow, not merely a new report. The data that feeds Section E and G does not exist yet in many organizations.
What Modern Policy Administration Systems Enable
A configurable P&C policy administration platform can solve this problem architecturally rather than procedurally. When cancellation, nonrenewal, and declination workflows are configured within the PAS, reason codes can be captured as required data elements at the point of action, meaning underwriters and service teams cannot complete a cancellation or nonrenewal without selecting a reason that maps to the plan’s codeset.
This design has several advantages that extend beyond TICO compliance:
- Consistency between notice and report: When the PAS drives the notice text from the same reason code captured in the system, the risk of misalignment between the policyholder notice and the statistical submission is structurally eliminated.
- Automated extract generation: With structured reason codes stored at the transaction level (including notification date, effective date, action type, and ZIP code) the Section E and G record layouts can be generated as a scheduled extract from the core system, not a custom data project.
- MCAS reconciliation support: If cancellation and nonrenewal counts flow from the same source system that feeds TICO reporting, reconciliation with NAIC MCAS becomes a comparison of two outputs from the same data, rather than a detective exercise across multiple platforms.
- Future-proofing for Phase 2: When TDI extends HB 2067 reporting to commercial lines (Phase 2), carriers with a configured PAS can replicate the residential workflow for commercial lines with substantially less effort.
Interim Solutions for Carriers Not Yet on Modern Platforms
- Step 1: Manual Reason Code Mapping. Develop a lookup table that maps every reason code or reason description currently in use in your notice workflow to the plan’s codeset. Document this in writing and circulate to all teams generating cancellation, nonrenewal, and declination notices.
- Step 2: Structured Data Capture Going Forward. Implement a manual logging process, at minimum a structured spreadsheet updated daily, that captures notification date, effective date, action type, ZIP code, and reason code for every relevant action taken from April 1 onward. This is a temporary bridge, not a sustainable solution.
- Step 3: TICO Manual Coding Engagement. Contact TICO at 512-444-9611 to discuss interim submission options. TICO’s coding service may be able to support classification of notice data during a transition period. However, carriers should not assume this will be available for the volume of records the new reports require.
Looking Ahead: What Comes Next
The April 2026 residential plan revision is Phase 1 of a three-phase implementation of HB 2067.[3] Phase 2, which will revise the Texas Commercial Lines Statistical Plan to add equivalent cancellation, nonrenewal, and declination reporting, is coming next. TDI has not announced an effective date for Phase 2, but the residential implementation will be the template.
Phase 3 will address lines of property and casualty insurance not currently covered by a TDI statistical plan. TDI has indicated it will investigate reporting options and issue additional guidance.[3]
Carriers writing both residential and commercial lines should treat the April 2026 implementation as an investment in infrastructure that will need to scale. The reason code framework, the ZIP-code-level reporting structure, the reconciliation requirements, and the transmittal form design established in Phase 1 will likely be replicated in Phase 2. Carriers that build their systems correctly now will find Phase 2 to be an extension, not a rebuild.
The data infrastructure required by the April 2026 changes is not a one-time compliance project. It is a permanent operational capability. Carriers that treat it as a project will rebuild it again for Phase 2. Carriers that treat it as infrastructure will extend it.
The Three Things Every Texas Insurer Must Do Now
The April 1, 2026 effective date is weeks away, and the first reports are due June 15. The following three actions are the minimum required to achieve compliant first submissions:
1. Contact TICO immediately. Initiate electronic submission testing for the Section E and G record layouts. TICO’s setup process is not instantaneous. Carriers who have not contacted TICO to begin testing for the new record formats risk being unable to file electronically by June 15. Contact the TICO switchboard at 512-444-9611.
2. Audit your notice-to-data pipeline. Trace how cancellation, nonrenewal, and declination reasons are currently captured from notice generation through to any system of record. Identify the gaps between what you capture today and what Sections E and G require. This audit drives every subsequent technical decision.
3. Assemble a cross-functional team with a June 1 internal deadline. Compliance, underwriting, IT, actuarial, and finance all have roles in this implementation. A June 1 internal deadline (two weeks before the TICO due date) creates necessary buffer for testing, reconciliation review, and transmittal form validation. Without it, the June 15 deadline is a risk.
The April 2026 TICO changes are the most significant revision to the Texas residential statistical reporting framework in decades. They create new compliance obligations, new data architecture requirements, and new regulatory visibility into carrier underwriting practices at the ZIP-code level. Carriers who prepare methodically will meet the deadline. Carriers who do not will be among the first subjects of TDI’s new market conduct monitoring capability.
Texas carriers looking to build a sustainable, scalable reporting infrastructure that handles TICO’s new requirements, and future phases of HB 2067, should evaluate whether their current policy administration platform can embed structured reason code capture into cancellation, nonrenewal, and declination workflows. WaterStreet’s configurable P&C platform and built-in Business Intelligence tools are designed to make statutory reporting a byproduct of clean operational data, not a separate compliance exercise.
About WaterStreet
WaterStreet Company is a trusted technology and service partner to property and casualty insurers, MGAs, and insurtechs. WaterStreet’s configurable P&C platform is purpose-built for exactly this kind of statutory reporting precision. Because product rules, territory definitions, and coverage codes are configured, compliance teams can adapt to plan changes without waiting on IT development cycles. And with built-in Business Intelligence tools surfacing premium and loss data in real time, TICO reporting becomes a scheduled output of normal operations rather than a periodic scramble.
Reach out to WaterStreet Company today to request a consultation and demo.
References:
All factual claims in this document are sourced from official TDI, TICO, and Texas Legislature publications. Citations are indicated inline.
| Ref | Source | URL / Citation |
| [1] | Texas Statistical Plan for Residential Risks, eff. April 1, 2026 | tdi.texas.gov/rules/2025/documents/2026resclean.pdf |
| [2] | TDI Adopted Rule — 28 TAC §5.9503 and §5.9504 (Subchapter O) | tdi.texas.gov/rules/2025/documents/20269741.pdf |
| [3] | TDI Bulletin B-0008-25 — HB 2067 Implementation Phases | tdi.texas.gov/bulletins/2025/b-0008-25.html |
| [4] | Texas House Bill 2067, 89th Legislature, 2025 | capitol.texas.gov |
| [5] | TDI Bulletin B-0012-25 — 89th Legislature Insurance Laws Summary | tdi.texas.gov/bulletins/2025/b-0012-25.html |
| [6] | TDI — Texas Statistical Plan for Residential Risks (prior plan) | tdi.texas.gov/company/data-collection/dcspres.html |
| [7] | TICO — Statistical Reporting FAQ | ticostat.com/TICOResidentialFAQ.action |
