THE BROADER RECORD · THROUGH SEPTEMBER 2026
Beyond the mandamus counts.
The court case is one part of the record. Later productions, separate requests and continuing complaints raise broader questions about how the City accounts for its records and responds when a delivery is challenged.
This guide is separate from the 13-count guide. Some later evidence bears on those counts; other entries concern separate requests. Earlier background is dated as such. These are selected documented questions, not additional pleaded counts or findings of misconduct.
Return to the 13-count guide ↗01 / OAG certification production
The records used to certify that records were supplied.
May 27 – July 2, 2026 · earlier forms included
What was said
On June 2, Webster sent a production link for Moring’s May 27 request for the City’s OAG submissions and marked the request closed. The request expressly included submitted certification forms.
What the records show
Moring’s June 3 reply identified the signed forms as missing from the City folder. OAG’s July 2 production then supplied complaint files containing seven distinct signed Webster forms: one dated October 22, 2025 and six dated April 27, 2026. Each selects the option that all existing responsive information was made available by email. The signature dates precede the May 27 request; the later OAG delivery allows those representations to be examined directly.
Official response / explanation
The City closed the request on June 2, and screenshots were later received. OAG’s July 2 transmittal also describes redactions, withheld ruling-review material and a further ruling request. It does not represent an unrestricted release of every OAG record.
What remains unresolved
Which City delivery, if any, included each requested certification and its submission record? Why were the forms not identifiable in the folder challenged on June 3? A signed completion statement and a later production discrepancy require reconciliation; they do not by themselves establish knowing falsity.
Check the evidence
Read the seven signed forms and their stated production dates
One entry per distinct signed form. The repeated October form is counted once. The seven-form set includes an older matter outside the May 27 request’s eight listed complaint numbers; it is not a one-for-one count of omissions from that request.
| Matter / form | Signed | Production date stated |
|---|---|---|
| Code, roof and complaint records ↗OR-25-034390-IC | October 22, 2025 | 8/13/25 |
| City communications ↗OR-25-055840-IC | April 27, 2026 | 12/2/25 |
| Ordinance 2025-24 ↗OR-25-057987-IC | April 27, 2026 | 11/26/25 |
| Request totals and tracking ↗OR-25-058955-IC | April 27, 2026 | 12/11/25 |
| Chief’s personal-phone records ↗OR-25-059503-IC | April 27, 2026 | 12/17/26 — as written; later than signature |
| January inspection visit ↗OR-26-004942-IC | April 27, 2026 | 1/21/26 |
| Keyword/name/OSHA email search ↗OR-26-006368-IC | April 27, 2026 | 2/2/26 |
These forms are City representations. The date written as “12/17/26” follows its April signature; the cause remains unresolved. Inclusion of a form does not release its entire underlying complaint file.
02 / Pretreatment and retained records
A department’s work should leave an explainable record.
April 13, 2026 · background for the wider pattern
What was said
Webster’s April 13 reply supplies thirteen red-font answers within the request: one “ATTACHED,” nine individual or grouped “NO CITY RECORDS EXIST” answers, and three references to information provided on September 15, 2025.
What the records show
The no-records answers cover annual pretreatment reports, TCEQ oversight and correspondence, program changes, inspection and enforcement records, industrial users and regulatory determinations. Item 3(e) is a privacy exclusion, yet it receives the same prior-production answer as records categories. That answer does not address the item’s wording.
Official response / explanation
The City said the ordinance was attached, several categories had no City records, and specified personnel information had already been provided. Moring disputed the September 15 reference and described a September 26 pickup. Repeated copies of his follow-up in the August 4 production preserve the reply; they are not additional City responses.
What remains unresolved
Who assumed the pretreatment responsibilities, what happened to the program files, and which prior delivered records answer each personnel and program-history item? Match the September delivery and the requested categories before concluding that records were destroyed or that the TCEQ material contradicts the City’s answer.
03 / Estimates and access
A charge should be traceable to the work requested.
May – July 2026 · separate requests
What was said
For the May 13 FY2025 audit-package request, the May 27 estimate sets a $72 total and requires a $72 bond. The June 1 version retains the total but removes that bond paragraph. Both describe more than four hours while itemizing exactly four.
What the records show
The two versions document a change in terms and a time-description mismatch. The June 1 correspondence offers June 2 or June 3 inspection times, conditioned on acceptance of the charges and payment before the records would be available for inspection. That condition belongs alongside the disputed terms.
Official response / explanation
The City revised the FY2025 letter and offered inspection subject to accepting the charges and paying before the records were available. For the other complaints, the receipt confirms submission and reproduces Moring’s description; it does not supply the City’s complete response or an OAG merits decision.
What remains unresolved
For each request, what work was performed, what was ultimately supplied or inspected, what was paid, and what did ORD decide? The receipt list preserves those open checks rather than declaring every challenged estimate unlawful.
Check the evidence
- FY2025 audit request · May 27 estimate · p. 1 ↗
- FY2025 audit request · May 27 estimate · p. 2 ↗
- FY2025 audit request · June 1 revised estimate · pp. 1–2 ↗
- June 1 inspection offer and payment condition · p. 1 ↗
- Estimate versions and inspection offer · reviewed chronology ↗
- Read the separate ORD complaint receipts below ↓
04 / Later files and completeness
A supplied file is not the same as an explained production.
July 23 – September 16, 2026
What was said
Webster’s September 16 compensation reply closes the request and marks four challenged categories “Already produced.” Moring asks for the exact files, worksheets or pages that answer them.
What the records show
The July 21 final compensation report names three interim reports on page 8 and a Combined Study Workbook in Appendix D, page 38. The September delivery listing shows seven files. Those references provide specific items to reconcile; filenames alone do not establish that the referenced material was omitted.
Official response / explanation
The City’s position is that the compensation categories were already produced. The SharePoint listing shows Webster in the Modified By column, but does not identify what changed. No earlier version or system log has been matched to show who removed a field, whether it existed before export, or whether the supplied file was altered substantively.
What remains unresolved
Which supplied file satisfies each named deliverable, and what retained native file or version history would explain the production? The documented field absences support a records-quality question without proving intentional sanitization or assigning the operation to one person.
05 / Notice and follow-through
An acknowledgment should be accounted for in the search.
April 28 – September 19, 2026
What was said
Vine’s April 28 reply acknowledges Moring’s OpenGov notice and says the City will investigate and work with partners. The May 14 request seeks existing receipt, acknowledgment, handling and investigation records. Webster’s May 27 certification identifies only Moring’s notice and says no responsive records were located for items 1–25.
What the records show
The original acknowledgment and the broad request create a specific search question: why was that City-generated reply not included or considered responsive? This is narrower and more verifiable than claiming that no investigation occurred.
Official response / explanation
The record contains Vine’s acknowledgment, Webster’s no-records certification and the later state-agency records response. A limited mailbox search did not locate a vendor reply to the September follow-up. It does not establish that no acknowledgment was ever sent.
What remains unresolved
What City records document the promised handling, which systems and custodians were searched, and did later recipients acknowledge or resolve the reported concerns? Raw exports, sensitive identifiers and held attachments are not reproduced here. The selected record does not establish a continuing live breach or a common technical cause.
CONTINUING ESCALATIONS · SELECTED TXOAG RECORDS
What was filed. What was decided.
ORD is the Texas Attorney General’s Open Records Division. Its confirmation records a submission and repeats the complainant’s description. That description is not an agency finding. Five selected receipts are shown here; this is not a total of every complaint filed.
June 12–13, 2026
The City’s OAG-submission records
OR-26-031655-IC
What Moring reported
Moring challenges the closed, paid production for missing certification forms or alternative submissions, converted emails and unresolved categories.
Verified procedural status
Submission confirmed. This matter also appears in the July 2 OAG attachment list; no merits decision is established by this receipt.
The email header displays June 12 at 9:24 p.m.; its Date Submitted field says June 13. Both are retained without assuming a time zone explanation.
Return to the related pattern ↑View the receipt excerpt · source page 1
Recipient email masked. Cropped before the personal-information section; the lower upload list and footer are omitted. The source original is preserved.
Open the excerpt at full size ↗
June 13, 2026
Microsoft 365 / IT estimates
OR-26-031660-CC
What Moring reported
Moring challenges a $54 estimate and related $720/$270 estimates, including labor and overhead for the requested inspection-first access.
Verified procedural status
Submission confirmed. The receipt warns that required cost-complaint documentation must be timely submitted; it does not decide whether the charges were proper.
Estimate amounts described in the complaint are not totals verified as paid.
Return to the related pattern ↑View the receipt excerpt · source page 1
Recipient email masked. Cropped before the personal-information section; the lower upload list and footer are omitted. The source original is preserved.
Open the excerpt at full size ↗
June 13, 2026
FY2019–FY2026 audit-record estimates
OR-26-031662-CC
What Moring reported
Moring challenges $192 and $126 estimates, alleging unsupported copy charges, unexplained labor, overhead errors and bond demands.
Verified procedural status
Submission confirmed; later disposition is not established by this receipt.
This is separate from the FY2025 audit-package request and its $72 estimate compared above.
Return to the related pattern ↑View the receipt excerpt · source page 1
Recipient email masked. Cropped before the personal-information section; the lower upload list and footer are omitted. The source original is preserved.
Open the excerpt at full size ↗
July 26, 2026
July Walmart inspection-record production
OR-26-040480-IC
What Moring reported
Moring reports that the City closed his July 9 request after two flattened PDFs and a $15 charge, with disputed source pages, complaint records and withholding notice.
Verified procedural status
Submission confirmed; the description is Moring’s allegation, not an OAG finding or a verified current omission total.
The file-property review above independently identifies specified missing metadata containers; it does not verify every allegation in the complaint.
Return to the related pattern ↑View the receipt excerpt · source page 1
Recipient email masked. Cropped before the personal-information section; the lower upload list and footer are omitted. The source original is preserved.
Open the excerpt at full size ↗
July 26, 2026
Telecom/vendor correspondence
OR-26-040481-IC
What Moring reported
Moring reports a $30 payment condition on his June 17 request and says no records, production date or further reply followed his objection as of the complaint.
Verified procedural status
Submission confirmed; the City’s subsequent delivery history and ORD disposition still need to be matched.
This is vendor correspondence, not another copy of the older City call-log format dispute or proof that no later response occurred.
Return to the related pattern ↑View the receipt excerpt · source page 1
Recipient email masked. Cropped before the personal-information section; the lower upload list and footer are omitted. The source original is preserved.
Open the excerpt at full size ↗
How to read these connections.
Compare the original request, the dated response, the actual delivery and any later correction. Repeated copies of one email are one event. A records complaint, a City certification, a production receipt and an agency decision establish different things. Recurrence supports asking for an explanation; it does not by itself establish intent or coordination.
This selection reuses the completed source and audio reviews and adds five visually checked ORD confirmations. Supporting complaint binders and every later disposition have not been re-audited. Held attachments and raw sensitive datasets remain excluded. Earlier scope qualifications remain in effect.