01 / Public records tracker / Selected correspondence
What this tracker does—and does not—measure.
This is a public editorial chronology of five selected request files, reconstructed from the correspondence identified in the source register. It distinguishes requests, acknowledgments, referrals and denials. It is not a live connection to Gmail, a complete custodian log, or a certification that no response exists elsewhere.
Each file has a “last source event” date. The November 9 edition date says when this page was assembled; it does not make an old response new or imply a complete fresh search of every delivery channel. The most careful current status for an uncompleted file is “production not verified in the selected sources.”
No elapsed-day badge is labelled a legal violation. Receipt, jurisdiction, request sufficiency, working-day rules, clarifications and remedies require their own analysis. Read the access-route guide before applying a FOAA rule to a different kind of record.
02 / Public records tracker / Selected correspondence
The request files.
5 request files
Spending, eCourts contracts, lifecycle and service delivery
Production declined; procurement referral- Access route
- Judicial administrative records
- Request date
- 2026-09-20
- Last source event
- 2026-09-22
- Edition date
- 2026-11-09 — selected-source snapshot, not live monitoring
- · Request
Existing administrative records requested, with phased production and custodian routing. Source E01
- · Response
The legal-affairs director declined production on the stated FOAA ground and directed public contract/spending requests to Executive Branch procurement. Source E02
Unresolved question: Which requested categories are held by the Judicial Branch, which are held elsewhere, and what access route applies to each?
Limit: The response is documented. It is not a court judgment about the request or a showing that all responsive records were held by DAFS.
Download the public chronology
R48 / Public dollars & performance
Follow the contract all the way to the family-facing result.
R48 separates spending authority, invoices, payments, modeled capacity and actual outcomes—and connects the eCourts record to a reproducible contract-performance chain.
Tyler/eCourts procurement, agreements and payment records
Acknowledged; production not verified- Access route
- Executive-branch FOAA
- Request date
- 2026-09-22
- Last source event
- 2026-10-16
- Edition date
- 2026-11-09 — selected-source snapshot, not live monitoring
- · Request
Agreements, amendments, procurement and payment records requested. Source E03
- · Acknowledgment
DAFS acknowledged the request and described review before a time estimate. Source E04
- · Follow-up
Tracking, possible consolidation, estimates and rolling production requested. Source E09
- · Acknowledgment
DAFS acknowledged the follow-up. No production schedule is established by this message. Source E10
Unresolved question: What is the tracking reference, scope actually being searched, good-faith time/cost estimate and first available production?
Limit: No later production is verified in this selected source set. That does not establish the absence of every later email, portal delivery or paper response.
Tyler/BerryDunn agreements and payment exports — CT/RQS 20220428*2664
Acknowledged; consolidation not confirmed- Access route
- Executive-branch FOAA
- Request date
- 2026-10-13
- Last source event
- 2026-10-16
- Edition date
- 2026-11-09 — selected-source snapshot, not live monitoring
- · Request
Executed agreements, existing payment exports and identified oversight-amendment records requested. Source E05
- · Acknowledgment
DAFS acknowledged the narrowed request. Source E06
- · Follow-up
The requester asked whether this file and the September request would be consolidated. Source E09
- · Acknowledgment
DAFS acknowledged the follow-up without confirming consolidation in the reviewed response. Source E10
Unresolved question: Will the two related requests remain separate or be consolidated, and which existing contract/payment files can be supplied first?
Limit: RQ02 and RQ03 may overlap. Do not sum their requested categories as independent withheld records or treat the follow-up as another underlying procurement.
BerryDunn oversight, Tyler milestone acceptance and payment-approval records
Denied under JB-05-20 IV.B- Access route
- Judicial administrative records
- Request date
- 2026-10-13
- Last source event
- 2026-10-14
- Edition date
- 2026-11-09 — selected-source snapshot, not live monitoring
- · Request
Final oversight reports, acceptance decisions, agreements, invoices and independence records requested under section IV. Source E07
- · Denial
The State Court Administrator’s designee denied the request under JB-05-20 IV.B and again referred public-contract inquiries to procurement. Source E08
Unresolved question: Which specific categories were denied, what decision factors were applied, and what request or review route is available for final nonconfidential administrative records?
Limit: The policy citation is established. This tracker does not decide whether the denial was permissible or whether every requested item is exempt.
Public historical attendance and institutional-affiliation material
Research acknowledged; production not verified- Access route
- FOAA / public historical collections
- Request date
- 2026-09-20
- Last source event
- 2026-09-22
- Edition date
- 2026-11-09 — selected-source snapshot, not live monitoring
- · Request
A coordinated request sought existing public historical material to test specific archival leads. Source E11
- · Acknowledgment
The FOAA office said research and collection were underway, with timing, clarification and possible fee information to follow. Source E12
Unresolved question: What collections have been checked, what records are public and responsive, and what estimate or narrower scope would enable completion?
Limit: Shared educational or organizational connections do not establish friendship, bias or misconduct. No private student records are published here.
No request files match. Clear filters to see every file.
03 / Public records tracker / Selected correspondence
What would change a status?
| New evidence | Appropriate update | Avoid this shortcut |
|---|---|---|
| Records supplied | Record production date, actual files/categories and remaining gaps. | Do not call the whole request complete because one document arrived. |
| Search found no responsive records | Preserve the custodian’s wording, scope searched and date. | Do not equate “not located” with “proved never existed.” |
| Withholding or redaction notice | Record categories, cited basis and available review information. | Do not treat every blacked-out detail as concealment of wrongdoing. |
| Clarification or consolidation agreed | Record the agreed scope and effective date. | Do not assume a requester’s proposal was accepted. |
| Later correction or withdrawal | Preserve the change and reason while updating the current account. | Do not keep presenting a superseded status as current. |
04 / Public records tracker / Selected correspondence
Count the work, not the notification noise.
The October 16 follow-up is an event associated with two related DAFS requests. It is not automatically a third procurement investigation. Repeated acknowledgments are communications, not additional withheld contracts. A copied recipient is not another independent custodian action.
The public data file exposes the same fields used in the visible tracker: download JSON. It contains no private Gmail URLs or subscriber data. The fiscal report explains why counting messages as labor or waste would produce an unreliable model.
The proposed institutional standard is straightforward: identify the request, owner, scope, status, estimated next action and actual production. It should be possible to ask what remains without making a new request merely to locate the old one.
05 / Public records tracker / Selected correspondence
Add the missing record, not another unsupported conclusion.
A correction should identify the request-file ID and the specific dated event that is missing or misstated. Send only appropriate nonconfidential supporting material through the existing correction route. Do not submit private student, medical or family-court records for publication in a procurement tracker.
When a later response is verified, the current status should change and the history should remain. An acknowledgment should receive credit as an acknowledgment, a useful production as a production, and an effective correction as a correction. That is not indulgence. It is the method that makes stronger criticism possible.
Keep the context with the claim.
Share the page, not a cropped conclusion. This page is free without an account.