01 / Status model
Institutional follow-through has more than two states.
Sent
Transmission documented
Does not prove receipt by every address or attention by the intended decision-maker.
Acknowledged
Receipt or review acknowledged
Does not prove a substantive answer or production.
Substantive answer
The question was addressed
The answer may still be disputed, incomplete, denied, or referred.
Action initiated
An owner or process is assigned
Does not prove implementation or benefit.
Implemented
The change reached practice
Must still be measured for access, safety, cost, and unintended effects.
Measured result
Outcome evidence exists
The strongest status requires method, data coverage, limitations, and independent scrutiny.
02 / Selected tracker
Record the response that exists. Preserve the gap that remains.
Sent / period open
133rd Legislature fiscal-accountability submission
- Documented event
- The policy email and 21-page fiscal briefing were sent and published. A written response was requested within 14 days, expressly not as a statutory deadline.
- Next evidence
- Record a substantive referral, sponsor, committee assignment, or other official action when documented.
- Source
- Open source-linked record
- Limit
- Publication date is the same date as the submission; no conclusion about nonresponse is warranted.
Acknowledged
DAFS Tyler/BerryDunn FOAA follow-up
- Documented event
- DAFS acknowledged the follow-up and stated that it would provide a time estimate after review and identify reasons for withheld records.
- Next evidence
- Track an estimate, rolling production, fee notice, clarification, denial, or completed production.
- Source
- Open source-linked record
- Limit
- Acknowledgment is not production. The reviewed correspondence did not establish completed production.
Denied / referred
Judicial Branch BerryDunn oversight-record request
- Documented event
- The State Court Administrator’s designee denied the request under JB-05-20 IV.B and directed the requester toward Executive Branch procurement for public contracts.
- Next evidence
- Preserve the denial, distinguish internal performance records from procurement copies, and use the appropriate review or alternative-custodian route.
- Source
- Open source-linked record
- Limit
- The response does not establish that every requested internal project record was held by DAFS or publicly available there.
Substantive response / closed
Tyler support Ticket 1508385
- Documented event
- After the complaint about premature closure, support supplied statuses for three envelopes. The requester then authorized closure.
- Next evidence
- Use the sequence as a performance case study: closure before answer, later substantive answer, then authorized closure.
- Source
- Open source-linked record
- Limit
- The later answer must remain in the chronology. The record does not support describing the ticket as permanently unanswered.
Sent / status not entered
Governor-elect transition submission
- Documented event
- The site records the submission and requested operational action.
- Next evidence
- Enter an acknowledgment, meeting, referral, refusal, or substantive action only when documented.
- Source
- Open source-linked record
- Limit
- This tracker does not claim a response was absent; it states that no response status has been entered here.
03 / Rules
Do not manufacture silence.
- Search the complete relevant thread before stating that no response occurred.
- Distinguish an automated acknowledgment from a human substantive answer.
- Preserve a denial or referral even when the requester disagrees with it.
- Record a later correction, production, or substantive answer beside the original failure.
- Do not call a meeting, announcement, or pilot an implemented reform without delivery evidence.