Ann Galpin v. University Shadows Homeowners Association, Inc.

Case Summary

Case ID 25F-H099-REL
Agency
Tribunal Office of Administrative Hearings, Arizona
Decision Date 2026-04-15
Administrative Law Judge NR
Outcome Petition Denied
Filing Fees Refunded
Civil Penalties

Parties & Counsel

Petitioner Ann Galpin Counsel Pro Se
Respondent University Shadows Homeowners Association, Inc. Counsel Mark Lines, Shaw & Lines, LLC

Alleged Violations

No violations listed

Video Overview

Audio Overview

Briefing Document: Galpin v. University Shadows Homeowners Association, Inc.

Executive Summary

This briefing document summarizes the administrative proceedings and final decision in the matter of Ann Galpin v. University Shadows Homeowners Association, Inc. (No. 25F-H099-REL). The case centered on a dispute regarding a homeowner's right to access specific financial records under Arizona Revised Statutes (A.R.S.) § 33-1258.

The Petitioner, Ann Galpin, alleged that the University Shadows Homeowners Association (the Association) failed to comply with her October 14, 2025, records request. While the Association provided over 1,000 pages of documents, Galpin contested the omission of multi-year, vendor-specific ledgers and transactional data requested in Excel or CSV formats. The Association maintained that it had produced all records kept in the ordinary course of business and was not legally obligated to create new reports or convert raw digital data into specific formats to satisfy a member's request.

On April 15, 2026, Administrative Law Judge (ALJ) Nicole Robinson issued a final decision denying the petition. The ruling affirmed that state law requires the disclosure of existing records but does not compel an association to generate new documents or reformat data into a requester's preferred digital medium.


Analysis of Key Themes

1. Statutory Interpretation: "Production" vs. "Creation"

A central conflict in the case was the distinction between producing an existing record and creating a new one. The Association, represented by attorney Mark Lines and witness Austin Haywood, argued that the requested multi-year ledgers (specifically items #3 and #5 of the request) did not exist as standalone documents in their management software, Caliber.

  • Petitioner’s View: Galpin argued that because the data exists within the software, "converting" that data into a readable Excel or CSV format is a statutory requirement of making records "available." She cited A.R.S. § 10-11601(D), asserting that corporations must convert digital records into written form upon request.
  • Respondent’s View: The Association contended that generating a multi-year report requires "extracting and converting" data in a way that creates a new record not maintained in the ordinary course of business.
  • Legal Conclusion: The ALJ ruled that A.R.S. § 33-1258 does not require an association to create new documents or generate data into a particular format.
2. The Scope of "All Financial Records"

The Petitioner relied on the broad language of A.R.S. § 33-1258(A), which states that "all financial and other records of the association shall be made reasonably available." Galpin interpreted this to include the "bits and bytes" or "ones and zeros" inside the computer, arguing that a summary monthly statement is "non-transparent" and hides potential errors or mis-postings.

The Association countered by providing:

  • Monthly financial statements (P&L, Balance Sheets).
  • Bank statements and reconciliation reports.
  • Check registers.
  • Specific invoices for vendors (when they existed).

The court found the Association's production of these materials—totaling over 1,000 pages across two requests—to be sufficient under the law.

3. Management Software and Technical Constraints

The testimony of Austin Haywood provided insight into the technical operations of HOA management:

  • Software: The Association uses Caliber for accounting and Strongroom for third-party accounts payable.
  • Workflow: Invoices are received as PDFs, approved by various personnel (up to 15 people involved in the process), and stored electronically.
  • Data Integrity: Haywood testified that while transactional data exists, the "records" maintained for the Association are the compiled monthly reports provided to the Board, not the raw data exports Galpin requested.
4. Record Retention Policies

A secondary dispute involved the duration of record-keeping. The Association's "HOA Records Retention Policy" (revised January 1, 2019) stipulates a 3-year retention period for most financial documents, including bank statements, budgets, and monthly financial statements. Galpin argued for a 7-to-10-year period based on tax and legal standards, but the ALJ noted that the Association is governed by its own policy and the specific requirements of Title 33.


Important Quotes

Regarding the Obligation to Create Records

"The statutory framework governing condominium records requests draws a clear line between an association’s obligation to disclose the records it maintains and the impermissible burden of requiring the creation of new ones." — Respondent’s Answer, December 8, 2025

Regarding Digital Records

"The digital records that reside inside the computer are the other half… If a person can't use the records, the state would not even create this [transparency act] and say you can look at everything." — Ann Galpin, Petitioner, Closing Statement

Regarding the Final Ruling

"Respondent successfully argued that Ariz. Rev. Stat. § 33-1258, does not require an Association to create new documents or generate data into a particular format." — ALJ Nicole Robinson, Final Decision


Summary of the October 14, 2025, Records Request

The following table outlines the five categories of records requested by Galpin and the eventual status of those requests according to the hearing evidence:

Item # Description Status / Resolution
1 October 2025 Board Election records (ballots, tally sheets). Provided by the Association.
2 Detailed Monthly Financials (April–Sept 2025). Provided by the Association.
3 Multi-year General Ledger (2018–2025) in Excel/CSV. Denied (Required creation of new reports).
4 Specific invoices for Splashaway, AZ Red Mountain, and G. Quintana. Provided by the Association.
5 Detailed Vendor Ledgers (2018–2025) for 11 specific vendors. Denied (Required creation of new reports).

Actionable Insights

  • Establish Clear Record Boundaries: Homeowners associations are not required to act as data analysts for members. While "all financial records" must be available, this is limited to records that actually exist in the format they are kept by the association.
  • Format Flexibility: Requesters may "prefer" Excel or CSV formats, but an association satisfies its legal burden by providing records in the format they are maintained (e.g., PDF or hard copy).
  • Custodian Credibility: The ALJ relied heavily on the "credible testimony" of the management company's Vice President. HOAs should ensure their custodians of records are intimately familiar with their software capabilities and retention policies.
  • Retention Policy Defense: Having a written, board-approved Records Retention Policy provides a legal defense against expansive requests for ancient data. In this case, the Association's 3-year policy was a significant factor in limiting the scope of required production.
  • Mootness of Resolved Items: By providing items #1, #2, and #4 quickly, the Association successfully narrowed the legal battle to the technical "creation" issue, which was ultimately easier to defend.

Study Guide: Galpin v. University Shadows Homeowners Association, Inc.

This study guide provides a comprehensive overview of the administrative hearing case Ann Galpin v. University Shadows Homeowners Association, Inc. (Case No. 25F-H099-REL). It covers the legal dispute regarding records requests under Arizona law, the arguments presented by both parties, and the final judicial determination.

Case Overview

The case involves a dispute between Ann Galpin (Petitioner), a member of the University Shadows Homeowners Association, and the Association (Respondent) regarding the disclosure of financial and vendor records. The central conflict involves whether a homeowners association (HOA) is required to generate new reports or convert digital data into specific formats (such as Excel or CSV) to satisfy a member’s records request under Arizona Revised Statutes (A.R.S.) § 33-1258.

Key Entities and Figures
Entity/Figure Role
Ann Galpin Petitioner; a 29-year member and resident of University Shadows.
University Shadows HOA Respondent; a condominium association located in Tempe, Arizona.
Nicole Robinson Administrative Law Judge (ALJ) at the Office of Administrative Hearings (OAH).
Heywood Community Management The management company and custodian of records for the Association.
Austin Heywood Vice President of Heywood Community Management; witness for the Respondent.
Mark Lines Attorney representing the University Shadows Homeowners Association.
Trevan Nuttle Managing agent for the Association; observer at the hearing.

Core Concepts and Legal Framework

1. Statutory Authority: A.R.S. § 33-1258

This is the primary statute governing the disclosure of records for condominium associations in Arizona.

  • General Rule: All financial and other records of the association must be made reasonably available for examination by any member or their designated representative.
  • Timeline: The association has ten business days to fulfill a request for examination or provide copies.
  • Exceptions (Subsection B): Records may be withheld if they relate to privileged attorney-client communication, pending litigation, certain closed-session meeting minutes, or personal/financial records of individual members or employees.
2. Records Retention Policy

The Association operates under a specific Records Retention Policy (revised January 1, 2019):

  • Permanent Records: Articles of Incorporation, Bylaws, CC&Rs, Meeting Minutes (Annual and Board), and Plat Maps.
  • Three-Year Retention: Assessment information, bank statements, budgets, contracts, general correspondence, financial reporting/documents, and tax returns.
3. The "Creation vs. Conversion" Debate
  • Petitioner's View: Argued that digital data (binary "ones and zeros") inside accounting software constitutes a record and must be converted into a written, usable form (like Excel) per A.R.S. § 10-11601(D).
  • Respondent's View: Argued that the law requires the disclosure of existing records kept in the ordinary course of business. Generating a new report (e.g., a seven-year vendor history) constitutes the creation of a new record, which is not required by statute.

Chronology of the Dispute

Date Event
April 22, 2025 Petitioner makes an initial request for various records.
May 31, 2025 Association provides approximately 1,000 pages of documents but limits financial history to three years.
October 14, 2025 Petitioner submits a new written request for five categories of records (#1 through #5).
October 31, 2025 Association provides 25 attachments covering categories #1, #2, and #4.
November 11, 2025 Petitioner files a petition with the Arizona Department of Real Estate alleging non-compliance regarding items #3 and #5.
February 13, 2026 Prehearing conference held to define the scope of the hearing.
March 26, 2026 Formal evidentiary hearing conducted at the Office of Administrative Hearings.
April 15, 2026 ALJ Nicole Robinson issues a decision denying the petition.

Summary of the Contested Records (Items #3 and #5)

The hearing focused specifically on two items from the October 14, 2025, request that the Petitioner claimed were unfulfilled:

Item #3: Multi-Year Ledgers (2018–2025)

Petitioner requested the following in Excel or CSV format for a seven-year period:

  • Detailed General Ledger.
  • Detailed Accounts Payable Ledger.
  • Detailed Accounts Receivable Ledger.
  • Check Registers for all accounts (open or closed).
Item #5: Vendor-Specific Records

Petitioner requested a "Detailed Vendor Ledger" (2018–2025) and all supporting documentation (agreements, change orders, invoices, walkthroughs) for 11 specific vendors, including Heywood Community Management, ASAP Restoration, and Atlas Companies.


Short-Answer Practice Questions

  1. What was the Respondent’s primary justification for not providing the records in Category #3?
  • Answer: The Respondent argued that the requested multi-year ledgers in Excel/CSV format did not exist as standalone records in the ordinary course of business and would require the creation of new reports by extracting and reorganizing data.
  1. **Which Arizona statute did the ALJ determine was not applicable to this condominium association dispute?**
  • Answer: A.R.S. § 10-11601 (which the Petitioner cited regarding the conversion of records).
  1. According to the Association's witness, what accounting software is used to manage University Shadows?
  • Answer: Caliber.
  1. What was the total number of documents provided to the Petitioner in response to her April 2025 request?
  • Answer: Approximately 1,000 pages (provided on two flash drives).
  1. How many business days does an association have to fulfill a records request under A.R.S. § 33-1258?
  • Answer: Ten business days.
  1. Why did the Association refuse to provide "Aged Owner Balance Reports"?
  • Answer: Because those reports contain personal financial information of individual members, which is protected from disclosure under A.R.S. § 33-1258(B)(4).
  1. What specific period of time did the Petitioner’s October request cover for the financial ledgers?
  • Answer: July 1, 2018, through September 30, 2025.

Essay Prompts for Deeper Exploration

  1. Transparency vs. Administrative Burden: Evaluate the balance between a member’s right to "transparency" and an association’s right to be free from "impermissible burdens." Use the arguments from both Ann Galpin and the Association's counsel to support your analysis.
  2. The Definition of a "Record": In the digital age, does "data" residing in a database constitute a "record" before it is printed or exported? Discuss how the ALJ’s decision in this case defines the boundaries of what constitutes an "existing record" under Arizona HOA law.
  3. Statutory Interpretation: Ann Galpin argued that the "intent" of A.R.S. § 33-1258 is disclosure and transparency, while the Association argued for a literal "letter of the law" approach. Discuss the implications of these two different styles of statutory interpretation on the final outcome of the case.

Glossary of Important Terms

  • A.R.S. § 33-1258: The Arizona Revised Statute governing the inspection of records for condominium associations.
  • Caliber: The specific accounting and management software utilized by Heywood Community Management to maintain Association data.
  • Cash Basis Accounting: An accounting method where receipts are recorded during the period they are received and expenses are recorded in the period they are actually paid.
  • CSV (Comma-Separated Values): A plain-text file format used to store tabular data, often used for exchanging data between different applications like Excel.
  • Detailed General Ledger: A comprehensive record of all financial transactions of a business or organization over its entire life or a specific period.
  • OAH (Office of Administrative Hearings): An independent Arizona state agency that conducts hearings for various state regulatory matters.
  • Preponderance of the Evidence: The burden of proof in civil and administrative cases, meaning that the existence of a fact is more probable than its nonexistence.
  • Strongroom: A third-party accounts payable (AP) software system used by the management company to store and process electronic invoices.
  • Subledger: A detailed subset of accounts (like Accounts Payable or Accounts Receivable) that rolls up into the General Ledger.

The Limits of Transparency: Lessons from Galpin v. University Shadows HOA

1. Introduction: The Battle for the Books

In the world of community associations, few issues ignite as much friction as the "battle for the books." When a homeowner suspects financial mismanagement—or simply demands total visibility—the tension between a member's right to inspect records and a Board’s operational reality often results in litigation. The case of Ann Galpin v. University Shadows Homeowners Association, Inc. (No. 25F-H099-REL) serves as a definitive case study for Arizona HOAs. It addresses a fundamental question of modern governance: Does an Association’s duty to provide access to records include an obligation to "data mine" its software to create new, customized reports or convert digital data into a specific format to satisfy a member’s request?

2. Case Background: Ownership History and the Scope of the Dispute

The petitioner, Ann Galpin, a 29-year owner in the Tempe-based University Shadows condominium, initiated a series of aggressive record requests starting in April 2025. In response to her initial inquiries, the Association was remarkably transparent, producing over 1,000 pages of documentation and two separate flash drives. Despite this, Galpin filed a subsequent request on October 14, 2025, which ultimately led to an administrative hearing.

The dispute centered on two specific categories (Categories #3 and #5) spanning from 2018 to 2025. Galpin’s demand was not for existing documents, but for the generation of specific, multi-year compilations including:

  • Detailed General Ledgers in Excel or CSV format.
  • Accounts Payable and Receivable Ledgers in Excel or CSV format.
  • Vendor-Specific Ledgers (spanning seven years) for 11 specific contractors: ASAP Restoration, Asphalt Restoration Services, Atlas Companies, 5 Guys, LG Painting, Great Western Landscaping, Great Western Tree, Great Western Pest, Green Keeper Landscaping, Green Keeper Tree, Swain Asphalt, and Heywood Community Management.
  • Supporting Materials: Change orders, communications, and "standing walkthrough notes" related to these vendors.

Crucially, the Association’s formal Records Retention Policy (Exhibit 10) mandates that "Financial Reporting and Documents" and "Bank Statements" are only maintained for 3 years. Galpin was demanding data four years beyond the Association's legal retention window.

3. The "Creation vs. Production" Conflict

During the hearing on March 26, 2026, the legal arguments hinged on the definition of a "record."

The Petitioner’s Stance: Galpin argued that the Association was withholding "digital records." She contended that because the Association uses accounting software, the data exists as "bits and binary data" that must be "converted" into a readable written form (like Excel) per ARS § 10-11601(D). She distinguished between "source documents" (invoices) and the underlying "digital records" stored within the software.

The Respondent’s Stance: Led by attorney Mark Lines and witness Austin Haywood, the HOA argued that they had already complied with the law. They maintained that the multi-year, vendor-specific reports Galpin sought did not exist in the ordinary course of business. To provide them, the HOA would have to generate a new report rather than simply produce an existing one.

The Disconnect: Petitioner Requests vs. Association Records

Petitioner Requested (Excel/CSV Ledgers) Association Maintained (Ordinary Course)
7-year continuous General Ledger in Excel Monthly reconciled financial reports (3-year retention)
Multi-year Vendor-Specific Ledgers Individual invoices and monthly check registers
Data "converted" into CSV format Reconciled bank statements (PDF or Paper)
"Standing Walkthrough Notes" Do Not Exist / Not Maintained as Official Records
4. Technical Insights: The HOA’s Accounting Workflow

The testimony of Austin Haywood provided a sophisticated look at the technical reality of HOA management. The Association utilizes Caliber for core accounting and Strongroom for managing third-party payables.

As a matter of internal control and financial integrity, the Association maintains a strict separation of duties:

  1. Entry: One individual enters bills and invoices into the system.
  2. Payment: A separate individual processes the payments.
  3. Reconciliation: A General Ledger (GL) accountant reconciles these disparate actions against bank statements to produce the monthly reports used by the Board.

Because of this workflow, the "General Ledger" is a compiled result of these separate duties. The HOA argued effectively that while the raw data exists within the software, a "Vendor Ledger" is a report that must be specifically generated. If the Board does not use or maintain such a report for its monthly business, it is not an "existing record."

5. The Legal Verdict: Interpreting ARS § 33-1258

On April 15, 2026, Administrative Law Judge Nicole Robinson issued her decision, denying Galpin’s petition. The ruling was a significant win for Associations on two fronts:

First, the Judge clarified the statutory authority. While Galpin relied on ARS § 10-11601 (Nonprofit Corporations), the Judge ruled that this statute does not govern condominiums in this context. Instead, the dispute was decided strictly under ARS § 33-1258.

Second, the Judge established a clear boundary regarding format and creation. The verdict explicitly stated: "The statute does not require an Association to create new documents or generate data into a particular format." The law compels the disclosure of existing records, not the performance of customized accounting services or data conversion for a member's convenience.

6. Key Takeaways for Homeowners and Boards

This ruling serves as a vital precedent for community associations and legal analysts:

  1. Format is Not a Mandate: While owners often prefer Excel or CSV files for their own analysis, an HOA is not legally required to "convert" its records if they are maintained as PDFs or paper files.
  2. Creation vs. Access: There is a sharp legal distinction between inspecting records and demanding the generation of custom reports. Transparency laws apply to what is in the file cabinet—physical or digital—not what could be produced via software.
  3. The Supremacy of Retention Policies: Boards must adhere to their retention schedules. As shown in Exhibit 10, because the HOA only retained financial records for 3 years, Galpin’s request for 2018 data was legally unenforceable.
  4. The Burden of Proof: In an administrative hearing, the burden lies with the petitioner. As the Judge noted, Petitioner had no proof that the Association actually possessed the requested records and refused to provide them; "presuming" a record exists is legally insufficient.
7. Conclusion: Moving Toward Clarity

The Galpin v. University Shadows decision reinforces that "transparency" is grounded in the production of existing business records, not the provision of customized "data mining." For boards, the lesson is to maintain a clear records retention policy and a consistent accounting workflow. For homeowners, the lesson is that while the right to inspect is broad, it is limited to the records the Association actually uses to conduct its business. Understanding this distinction is the only way for both parties to avoid the significant costs of administrative hearings.

Case Participants

Petitioner Side

  • Ann Galpin (Petitioner)
    University Shadows Homeowners Association, Inc.

Respondent Side

  • Mark Lines (Attorney)
    Shaw & Lines, LLC
  • Austin Haywood (Vice President / Managing Agent / Witness)
    Heywood Community Management
    Also spelled Austin Heywood in the final decision.
  • Trevan Nuttle (Manager / Client Representative)
    Heywood Community Management
    Also spelled Treven Nuttall in the final decision.
  • Carly (Assistant)
    Heywood Community Management
  • Larry Haywood (Manager)
    Heywood Community Management

Neutral Parties

  • Nicole Robinson (Administrative Law Judge)
    Office of Administrative Hearings
  • Susan Nicolson (Commissioner)
    Arizona Department of Real Estate

Other Participants

  • John Sullivan (Observer)
  • Gabrielle Quintana (Homeowner)
    Referenced in relation to an insurance claim/water loss analysis records request.