Skip to mandamus guide
AN INDEPENDENT CASE STUDY Mount Pleasant, Texas
MOUNT COMPLACENTTHE PAPER TRAIL

PUBLIC RECORDS · COURT CASE

The mandamus dispute.

Read the parties’ filings, then compare specific statements with the underlying records and later productions.

THE COURT CASE THAT FOLLOWED

The mandamus case: assertions and evidence.

The mandamus case followed earlier concerns, records requests and City responses. The issue guides trace that history and later developments. Kyle Moring asked the court to compel the City of Mount Pleasant to provide public records; the City asked for dismissal. The following comparisons examine documentary assertions in the related correspondence and exhibits; they do not decide the City’s legal defenses.

September 25 search update

City attorney Lea Ream wrote that the City had run the search agreed upon at the courthouse and identified approximately 11,000 responsive emails. She said the City was reviewing them, hoped to provide the documents the following week and had indicated there would be no charge for this search. The email reports a search result and anticipated delivery, not a completed production.

Read Ream’s email · PDF ↗

Why it matters: a claim that records were supplied, or that a search answered a request, should be traceable to the actual delivery or search. These examples let readers test those claims.

A plea to the jurisdiction challenges the court’s authority to hear the case. A party’s assertion or filed exhibit is not a judicial finding. The City’s legal arguments and the accuracy of its documentary representations are separate questions.

Follow the dispute, count by count.

A “count” is a separately pleaded part of the case. The questions below identify Moring’s records disputes and the later evidence that narrows them. Thirteen counts do not mean thirteen established violations. The linked comparisons distinguish documented conflicts from allegations and unanswered questions.

Page links use the prepared 40-page viewing copy, whose page numbers differ from the original filing. Count I’s sensitive pages are excluded. A petition describes a party’s claims; it is not a court finding or an independent verification of every allegation.

COUNT ICase-related City communications

Privacy boundary

The underlying count contains sensitive material omitted from the prepared viewing copy. This guide does not reproduce those allegations or source pages.

Later records and necessary context

Related questions about City search methods can be examined through Counts V and VI without restoring excluded personal information.

COUNT IIThe October 28 Walmart visit and inspection

The discrepancy to examine

How does the City’s response fit with its inspection identifiers, record history and the DSHS joint-inspection account?

Later records and necessary context

The City supplied an inspection report and five photographs, and a February production included an Ankrum-to-Walmart transmission. DSHS later supplied City–DSHS correspondence and related inspection material. Moring disputes whether the City’s own productions included the requested City–DSHS exchanges and accounted for the inspection’s coordination, delivery and handling history.

Read this count · viewing-copy p. 11 ↗Compare the inspection identifiers and City explanations ↗Follow the emails and internal replies in date order ↗
COUNT IIIThe Chief’s call and voicemail records

The discrepancy to examine

When were the two call-log screenshots sent to Moring, and how do the claimed delivery dates fit with Webster’s May 7 statement that he had not received them?

Later records and necessary context

Moring received both screenshots on June 2. The May 12 transmittal went to the Attorney General’s office and City counsel; it does not by itself establish delivery to Moring that day. The City’s later account of earlier deliveries and the request for any other maintained call or voicemail records remain distinct questions.

Read this count · viewing-copy p. 12 ↗Compare the conflicting delivery accounts ↗Follow the emails and internal replies in date order ↗
COUNT IVThe January 13 inspection records

The discrepancy to examine

Beyond the three reports supplied, what records document the January 13 inspection’s coordination, delivery and handling, and how did the City address each requested category?

Later records and necessary context

The City supplied three inspection reports. Its response did not separately address every requested category, including coordination and delivery records. Whether an additional email, photograph or recording was maintained remains unanswered by the reports alone.

Read this count · viewing-copy p. 13 ↗Compare the category-by-category response ↗Follow the emails and internal replies in date order ↗
COUNT VMoring and OSHA keyword records

The discrepancy to examine

Did the search cover the requested terms and sources, and which specific messages remained unaccounted for after comparing the productions?

Later records and necessary context

Later deliveries supplied some material previously counted as absent, and some message text appears within quoted email threads. The earlier figure of 88 missing messages no longer represents the present gap. The comparison identifies individual messages and distinguishes a missing original email from text retained inside another message.

Read this count · viewing-copy p. 14 ↗Compare the request and supplied search description ↗Follow the emails and internal replies in date order ↗
COUNT VIWalmart correspondence and keyword records

The discrepancy to examine

Did the City search both requested branches—Walmart-domain correspondence and, in addition, Walmart-related terms—or restrict one branch with an AND condition?

Later records and necessary context

The City initially supplied 19 native messages and later supplied additional comparison records. A visible query joins terms with AND, raising a question about its scope; that screenshot alone does not show every search the City ran. The saved search statistics and the City’s explanations provide further context.

Read this count · viewing-copy p. 15 ↗Compare the request, query and recorded explanation ↗Follow the emails and internal replies in date order ↗
COUNT VIICity-attorney correspondence and legal expenses

The discrepancy to examine

What did the later attorney-email production resolve, and what requested legal-fee or payment information remained unaccounted for?

Later records and necessary context

The City supplied attorney emails on August 28. The number of files cannot be compared directly with a count of distinct messages. Moring’s question about billing and payment records is separate from whether the correspondence was supplied.

Read this count · viewing-copy p. 17 ↗Compare the correspondence-review explanations ↗Follow the emails and internal replies in date order ↗
COUNT VIIIThe January 9 fire-inspection follow-up

The discrepancy to examine

What existing record, if any, explains the report’s “Signature of: E-Mail” entry and the requested delivery or follow-up history?

Later records and necessary context

The City supplied records on March 3 and told the Attorney General’s office that it searched email. The City disputed that the report’s “Signature of: E-Mail” field proves a separate email existed. The field leaves a specific delivery-history question; it does not establish an undisclosed message on its own.

Read this count · viewing-copy p. 18 ↗Follow the emails and internal replies in date order ↗
COUNT IXRegulatory-agency correspondence

The discrepancy to examine

How do specific agency-produced messages addressed to City personnel compare with the City’s searches, rolling deliveries and explanations of remaining records?

Later records and necessary context

Later DSHS and TCEQ referrals, City meeting acceptances, restored access and an August USB delivery supplied additional material. Agency copies addressed to City personnel allow a specific comparison with the City’s responses, although an addressee alone does not establish that every recipient retained the same record.

Read this count · viewing-copy p. 19 ↗Follow the emails and internal replies in date order ↗
COUNT XAnkrum’s July 18 call records

The discrepancy to examine

How does the supplied call-history image identify or account for the specific call Moring recalls reporting roof debris?

Later records and necessary context

The City’s call-history screenshot does not display the telephone numbers associated with the listed calls. The question is whether the retained call evidence and line identification account for the particular July 18 call Moring described.

Read this count · viewing-copy p. 21 ↗Follow the emails and internal replies in date order ↗
COUNT XICity-managed phone lines and call details

The discrepancy to examine

Was the Chief’s office line included or otherwise accounted for within the clarified request’s specified dates and external numbers?

Later records and necessary context

The December and March productions include later-supplied line information. The City’s explanation of which lines were searched and how they map to the clarified request remains relevant; an unidentified entry alone does not establish that a particular call occurred.

Read this count · viewing-copy p. 22 ↗Follow the emails and internal replies in date order ↗
COUNT XIIJuly complaint submissions and code-compliance records

The discrepancy to examine

How do the two retained July portal confirmations fit with the City’s completeness position and the requested complaint, assignment and resolution history?

Later records and necessary context

A letter about the July 28 follow-up appeared as an attachment in the February 2 production. It documents part of the response but is separate from the original complaint entries and their handling history. A September confirmation concerns a later submission, not a third July complaint.

Read this count · viewing-copy p. 23 ↗Compare the received letter with the state inspection findings ↗
COUNT XIIIOrdinance 2025-24 development records

The discrepancy to examine

How does the initial no-records/ruling explanation fit with the later located ordinance, agenda report and internal correspondence?

Later records and necessary context

The agenda report was available through the public meeting website, and quoted portions of the email appeared in a received thread. The missing original email and the presence of its quoted text are different facts. The later located ordinance materials remain relevant to the City’s initial response.

Read this count · viewing-copy p. 24 ↗Compare the request, certification and later records ↗Follow the emails and internal replies in date order ↗

EXAMPLE 1 / August 27, 2026

Did the search match the request?

What the City said

Austin Beck · DTRG · August 27, 2026

The letter acknowledges the search builder’s “AND” condition: it would populate the phrases “if it had a Walmart e-mail associated with it.” It then treats the request as closed.

Read the cited page 3 · Item 3: AND acknowledgment and closure ↗

What the records show

The displayed AND query does not implement both independent requested branches. It narrows the keyword branch to records with a Walmart participant, excluding purely internal City discussions from that query.

Compare the source pages side by side ↗

Official response and later developments

After reviewing the 19 Walmart-related emails and the separate Moring-related production, Moring’s February 4 email asked for the actual search scope, queries, date ranges, custodians and systems, and a supplemental search if needed. He raised search concerns again in the February 18 meeting and later Council submissions. DTRG’s August 27 letter acknowledges the displayed AND condition but maintains that the request is closed; its August 25 letter attributes a Walmart count to a January 13 search. Separate requests later brought the October 23 shared-link transmittal and Spark messages into view. August City deliveries also included July 2025 DSHS referrals and the October 27 EPA–TCEQ–City/MPPD thread. These identifiable records allow comparison with earlier deliveries, but do not reveal every search the City performed. On September 25, Ream reported approximately 11,000 results from an agreed new search; production was still pending.

Read Moring’s February 4 search objection · selected PDF ↗Trace the methodology requests and meetings ↗

What remains unresolved

Which searches, taken together, covered the two requested branches?

The displayed query does not cover the request’s separate keyword branch on its own. The known internal Vine email appeared in a different Moring-related production, so it is not currently missing. These records do not establish that no other search ran or that every later-produced item was absent from every earlier delivery. The 19 supplied files are not a raw search-result count.

EXAMPLE 2 / August 25, 2026

Does the supporting exhibit verify the stated search?

What the City said

DTRG · August 25 letter · August 25, 2026

Item 3 attributes 5,991 matches in 174 of 984 locations to a January 13 Walmart search and identifies F-2/F-3 as the supporting query/data screenshots.

Read the cited page 4 · Item 3 · Walmart result count and stated date ↗

What the records show

The supplied F-3 image does not substantiate the letter’s stated January 13 Walmart result. Its query and date identify the August Moring search; image matching confirms reuse in both packets.

Compare the source pages side by side ↗

Official response and later developments

Moring requested search details when accepting the January cost estimate, repeated the request on February 4 and raised the search questions at the February 18 meeting and in later Council submissions. He identified the cross-request statistics mismatch in his August 26 response. Beck’s August 27 letter acknowledged the Walmart AND condition and maintained closure, but F-3 still displays the Moring query rather than independently verifiable Walmart statistics. Beck separately corrected the January location count from 290 to 209.

Read the February 4 request for search details · selected PDF ↗Trace the methodology requests and meeting ↗

What remains unresolved

Which search produced the stated Walmart total, and where are its matching query and statistics?

This establishes a mismatch between the supporting screenshot and the represented search. It does not establish whether a separate Walmart run had the same total, identify omitted records, or establish intent. The original request and F-2 AND filter are a separate scope issue.

EXAMPLE 3 / August 27, 2026

Were the same screenshots supplied on the dates claimed?

What the City said

Austin Beck · DTRG · August 27, 2026

After listing October 23, November 2, February 2, June 2 and August 26 deliveries of C-2 texts, the letter says: “The same applies to Exhibit C-3,” identifying C-3 as the Chief’s personal-cell call logs.

Read the cited page 1 · Item 1: delivery dates and C-2/C-3 assertion ↗

What the records show

The August 27 letter attributes the call-history screenshots to several earlier delivery dates. Direct examination of the October 23 physical media found five Axon videos and its spreadsheet index, but no call-history screenshots. The retained November 3 production and both original February 2 ZIPs likewise do not contain the two images by filename or hash. Webster had also said on May 7 that Moring did not receive screenshots, and her May 12 transmittal sent the images to Richardson and Beck. June 2 is the earliest verified delivery of these two call-history images to Moring in the reviewed physical media, retained folders, and original ZIP packages.

Compare the source pages side by side ↗

Official response and later developments

The October 23 media contains five Axon videos and its spreadsheet index, with no still images. The November 3 media contains three text-message screenshots and five audio files. The February 2 Moring-related ZIP contains those same three text screenshots as native-message attachments, but neither February ZIP contains the two later call-history images. The two call-history screenshots appear in the June 2 production and again in the August enclosure material; their embedded file timestamps are May 11, 2026.

Read Nipp’s November 12 text-message timestamps · selected PDF ↗Inspect the retained delivery inventory · PDF ↗John Beasley call screenshot · readable file properties ↗Carrie Mahon call screenshot · readable file properties ↗

What remains unresolved

Which dated delivery contained each screenshot, and how does that reconcile with the May 7 non-delivery statement?

The physical-media inventory establishes the USB contents visible to the filesystem on September 25, 2026, and records SHA-256 hashes for every user-delivered file. It cannot establish what existed elsewhere in City systems. The later call-image files carry May 11, 2026 creation metadata; that timestamp concerns the screenshot files, not the dates of the October 2025 calls displayed within them.