{
"rule": "FCRA 611(a)(1)(A)",
"window_days": 30,
"start_evidence": "DOC-88141",
"started_on": "2026-07-16",
"due_at": "2026-08-15T23:59:59-05:00",
"calendar": "tenant/northgate/tx",
"extensions": [],
"writable": ["extensions"]
}The queue is the product
An operator seat spends its day in two places: a queue ordered by the clock that is closest to expiring, and one case record open beside it. Everything else on this page exists to serve those two.
Figures on this page are from a demonstration tenant.
Queues are defined by rule, not by folder
A case is never dragged into a queue. It appears in one because a statutory condition became true, and it leaves when that condition stops being true. That is why the counts can be reconciled and why nobody has to remember to file anything.
- 31Expiring inside 5 daysFCRA 611(a)(1)Due
- 4Window expired, no resultFCRA 611(a)(1)Overdue
- 12Cancellation hold runningCROA 1679eDue
- 7Awaiting despatch evidenceFCRA 611(a)(1)Open
- 9Method of verification openFCRA 611(a)(7)Due
- 148Closed this monthFCRA 611(a)(5)Cleared
Correspondence, one row under the rule
Point at a row or tab to it. The rule locks to the row and its detail appears in the rail without a single pixel of the table moving.
| Message | Case | Channel | Sent | Due | Rule | State |
|---|---|---|---|---|---|---|
| CR-2026-04187 | Certified mail | 2026-07-16 | 2026-08-15 | FCRA 611(a)(1)(A) | Due in 4d | |
| CR-2026-04188 | Certified mail | 2026-06-29 | 2026-07-29 | FCRA 611(a)(1)(A) | Overdue 37d | |
| CR-2026-04156 | Secure upload | 2026-08-11 | 2026-08-18 | FCRA 611(a)(6) | Cleared | |
| CR-2026-04156 | Certified mail | 2026-08-12 | 2026-08-27 | FCRA 611(a)(7) | Due in 15d | |
| CR-2026-04203 | Portal | 2026-08-18 | 2026-08-18 | CROA 1679e | Cancelled | |
| CR-2026-04211 | Furnisher channel | 2026-08-20 | 2026-08-27 | FCRA 611(a)(2) | Open |
Anatomy of the clock field
The clock is not a reminder attached to a case. It is a field on the case with four parts, and three of them are read only to every seat in the tenant.
- rule
- The statutory reference that creates the window. Read only.
- start_evidence
- A pointer to the document that proves the window started. Read only, and a case without one is flagged rather than dated.
- due_at
- Derived from the rule, the start evidence and the tenant business calendar. Read only. Writing to it returns 403.
- extensions[]
- Append only. Each entry names the rule that permits the extension, so the trail shows an extension as an extension and never as an edit.
Item level outcomes
A dispute usually covers more than one item, and the results letter usually does not answer all of them the same way. Outcomes are recorded per item, so a partial result never reads as a full one and a reinsertion is attached to the item it reinserted.
| Item | Basis | Outcome | Recorded | Rule | State |
|---|---|---|---|---|---|
| ITM-1 | Date of last activity | Modified | 2026-08-11 | FCRA 611(a)(5)(A) | Cleared |
| ITM-2 | Reported balance | Verified as reported | 2026-08-11 | FCRA 611(a)(6) | Closed |
| ITM-2 | Method of verification requested | Awaiting description of procedure | 2026-08-12 | FCRA 611(a)(7) | Due in 15d |
| ITM-2 | Consumer statement offered | Consumer declined for now | 2026-08-13 | FCRA 611(b) | Open |
A verified outcome is a real outcome. The platform records it plainly and offers the consumer statement and the method of verification request as the next legitimate steps, rather than recycling the same dispute and calling it persistence.
Next: the controls that gate these transitions, orhow each of them is recorded. Reach a person at+1 (512) 402-7719.