The Big Picture
In Texas, property owners who believe their home or business has been over-assessed for tax purposes have a formal right to challenge that assessment. Most disputes are settled through informal hearings at the local Appraisal Review Board (ARB). But when a property owner isn't satisfied with that outcome — and the property value meets certain thresholds — they can escalate to Regular Binding Arbitration (RBA).
RBA is an alternative dispute resolution process administered by the Texas Comptroller's Property Tax Assistance Division (PTAD). Instead of going to district court, the property owner and the appraisal district agree to let a neutral, certified arbitrator decide the case. The arbitrator's ruling is binding on both parties — hence the name.
Why it matters
RBA gives property owners a faster, less expensive path to contest their appraisal than litigation. For arbitrators, it's a structured, fee-based practice governed by specific state rules and timelines.
Key Parties
Every RBA case involves three core parties, plus the Comptroller's office in an oversight role.
How a Case Moves Through the System
The RBA process follows a defined sequence from the moment a property owner files through the final ruling and payment. Understanding this flow is essential context for understanding what the software manages.
- 1ARB Hearing & Protest OrderThe property owner first protests their value at the local Appraisal Review Board. If unsatisfied with the result, they receive an Order Determining Protest — the prerequisite for arbitration.
- 2Filing the AP-219 with the ComptrollerThe property owner submits Form AP-219 (Request for Binding Arbitration) to PTAD along with the required arbitration deposit. Strict deadlines apply — typically 60 days from the ARB order.
- 3Arbitrator AssignmentPTAD selects a qualified, available arbitrator from the Comptroller's registry and notifies both parties. The arbitrator receives the case file and begins managing the timeline.
- 4Pre-Hearing & Evidence ExchangeThe arbitrator establishes the hearing date and manages communication between parties. Both sides prepare and exchange evidence — appraisal data, comparables, photos, and supporting documents.
- 5The HearingConducted in person or virtually. Both parties present their case to the arbitrator. The format is less formal than court but governed by specific procedural rules under the Texas Property Tax Code.
- 6Ruling & AwardThe arbitrator enters the decision directly into the PTAD Portal, setting the final appraised value. The ruling is binding. If the property owner prevails, the CAD is responsible for paying the arbitration costs and PTAD issues the deposit refund to the property owner. If the owner does not prevail, the deposit is forfeited.
- 7Payment to ArbitratorIf the property owner does not prevail, PTAD releases the arbitrator's fee from the deposit. If the property owner prevails, the CAD pays the arbitrator directly. Fee amounts are set by the Comptroller's schedule and vary by property type and value. All fee entries in the software are manual — no auto-calculation.
Key Terms & Acronyms
You'll encounter these terms throughout the codebase, documents, and case data. Learn them now.
What the Software Does
The RBA Case Management System is a custom-built workflow tool for John Gann's arbitration practice. It replaces a legacy Airtable setup and manages the full lifecycle of every RBA case — from intake through ruling and payment.
- Case intake — capturing all parties, property details, and AP-219 data at case opening
- File numbering — auto-assigned YYYY-### identifiers that reset each calendar year
- Status tracking — cases move through defined workflow stages from intake to closed
- Hearing management — dates, format (in-person vs. virtual), and outcome recording
- Ruling capture — verdict type, final value, and binding decision documentation
- Payment tracking — fee amounts and payment status, manually entered per Comptroller guidance
- Reporting — case history and outcome summaries for the arbitrator's practice records
The system is built on Duda (web hosting) with Google Firebase Realtime Database for data storage. Google Firebase includes enterprise-grade security with role-based access rules, meaning case data is protected at the database level — only authenticated users with the correct permissions can read or write records. All case data is private to the arbitrator's practice.
An optional AI-assisted intake feature — available on a higher-cost plan and never required for normal operation — allows document images to be read and parsed automatically using the Claude API. The AI feature can be turned on or off at any time from the system settings and has no effect on any other part of the workflow.
Your role as a tester
You're helping verify that this system works correctly before it goes into active use on real cases. Understanding the RBA process gives you the context to recognize when a component is behaving correctly, when data fields make sense, and when something looks wrong. The more you understand the workflow, the better your feedback will be.
