At nine-oh-two exactly she opened the amendment committee portal.
Saebyeok had developed a habit of precision since August. Not urgency: precision. She checked the amendment committee portal at 9:02 AM every weekday, which meant she had checked it thirty-four times since filing INQ-2047-09-09-4491. The extra two minutes past nine was a deliberate buffer. The portal sometimes showed cached data if you opened it the moment the inquiry desk came online. She had learned this in the second week. She had adjusted. 9:02 was now automatic.
The status was unchanged. RECEIVED. INQUIRY_LOGGED. Orange.
She had known it would be unchanged. The five-business-day inquiry window had run from September 9 through today, September 16, and the committee amendment review desk processed inquiries in order of receipt. Her inquiry, filed at 3:43 PM on a Tuesday, would have been seventeenth in that week's queue. She had requested the queue position in week two and been told it was not a disclosable metric. She had inferred it from the response patterns of other filers in the ARCH-INQ public database. The timestamps of blue-status entries, which marked substantive responses, showed the committee was processing approximately twelve to fifteen inquiries per business-day window when fully staffed. Seventeen in queue over five business days was theoretically addressable. The committee had apparently not been fully staffed.
She wrote the timestamp in her notebook: 9:02:17 AM, September 16, 2047. INQ-2047-09-09-4491. Status: INQUIRY_LOGGED. Window expired. No substantive response. Escalation triggered.
The escalation form was a PDF from the Track B oversight office, downloaded September 9 at 4:11 PM, twenty-eight minutes after filing the inquiry. She had done this because the inquiry window would either succeed or fail, and if it failed, she would need the escalation form the same day the window expired, and the oversight office website was slow to load during peak municipal hours. Better to have it on disk. Better to have filled in everything fillable on September 9: her name, the case identifier (ARCH-INQ-CASE-2047-L-5501, the master case number linking all component filings), the property file ID (PROP-2043-LENT-7782), and the nature of the inquiry. Failure to apply amendment 22-B to a housing-transition assessment finalized under pre-amendment criteria, resulting in ongoing administrative barriers to services for which the resident was eligible under the amended standard.
What she had not been able to fill in on September 9 were the fields that required the inquiry to have already expired. The date of window expiry. The documentation of non-response. The harm continuation statement.
Now she filled them in.
Date of window expiry: September 16, 2047.
For documentation, she clicked the portal print-to-PDF function. It generated a timestamped screenshot of the INQUIRY_LOGGED status, including the session ID, the portal version number (ARCH-INQ-Portal 4.2), and the UTC timestamp of generation. She attached it.
Harm continuation: The affected unit has been operating under a housing-transition assessment that does not reflect the amendment 22-B criteria that should have applied at the time of finalization. The resident has experienced ongoing administrative barriers to services that would be available under the corrected assessment.
She had written this sentence three times now. The initial dispute filing in August. The September inquiry. Now the September escalation. She wrote it a fourth time. The system required her to say it again. She said it again.
The escalation form had a second section: the notification to the Housing Transition Division liaison. Track B required two parallel filings, one with the oversight office and one with the HTD liaison. The HTD form was structurally different: two-field summary instead of full narrative, checkboxes for the type of committee failure. She checked: inquiry window expiry without response. Ongoing harm to transition eligibility. She had the liaison contact form in a second browser tab. She filled it in.
By 11:14 AM both were submitted.
She had not expected the committee to respond during the form-filling. She had refreshed the portal twice during those two hours, not from hope but from prudence: if the committee responded at 10:47 and she submitted the escalation at 11:14 with documentation timestamped at 9:02, this would create a question the oversight office would need to address. There was no question. At 11:02 the portal showed INQUIRY_LOGGED. At 11:14 the portal showed INQUIRY_LOGGED.
She made coffee. The first cup, made at 8:55, had gone cold on the desk. She made a second and drank it.
Amendment 22-B had been passed in late 2044, part of the third housing-transition policy revision cycle. The amendment changed one thing in the assessment criteria: it expanded the definition of eligible support services to include continuity-of-care coordination, which had not been a recognized service category under the pre-2044 standard. The practical effect, for residents in housing-transition status, was access to a class of administrative support services previously categorized as case management and therefore excluded from the housing-transition service bundle. The services themselves had not changed. The categorization had changed.
PROP-2043-LENT-7782 had been finalized in March 2043, before the amendment. The assessment had applied the pre-amendment criteria: continuity-of-care coordination was not included in the service bundle. The resident had been trying to access these services since November 2044, when the amendment came into effect, specifically a coordination service for a medical case that intersected with a housing-stability documentation requirement. The housing authority position was that assessments finalized before the amendment were not automatically revised; revision required a formal amendment review. The amendment review queue, as of September 2047, was running approximately eighteen months.
This meant that even if PROP-2043-LENT-7782 were added to the standard amendment review queue today, the correction would not happen until March 2049. The amendment dispute process existed precisely because the standard review queue was too slow for cases involving ongoing harm. The amendment dispute process was, as of September 2047, also slow. The inquiry window was five business days. The Track B escalation period was ten business days. The oversight review and hearing preparation period was eight to twelve weeks. Faster than eighteen months. Not fast.
Saebyeok had entered the case in July 2047, when the housing advocate filed a referral through the amendment dispute program. She had reviewed the file and identified three things. The timeline error: the assessment was finalized before the amendment, but the resident had been continuously enrolled in housing-transition status through the amendment effective date, which meant the resident was eligible for a transition-date reassessment under amendment 22-B section 4, subsection 3. The service intersection: the medical coordination service was classified under a pre-amendment category that had been renamed, not substantively changed, by the amendment, making the eligibility determination partly a classification question. The documentation barrier: the housing-stability documentation the medical coordination service was supposed to support was also blocked by the classification gap, creating a circular barrier.
She had told the resident in July: the process is slow because it is designed to be slow. Slowness is neutral-appearing. Neutral-appearing slowness is easier to sustain than outright refusal because refusal creates a clear adversarial record and a legal trigger, while slowness creates a record describable as backlog, understaffing, competing priorities, administrative complexity. Each step in the amendment dispute process had a built-in window. The dispute period. The inquiry period. The escalation period. The oversight review period. The hearing preparation period. Each window was an opportunity for the problem to resolve itself. If the housing authority corrected the assessment during the dispute period, the inquiry was unnecessary. If the committee responded during the inquiry period, the escalation was unnecessary. The system assumed most problems resolved before the hearing. This was true. Whether it was true because the windows gave responsible parties time to act, or because the windows gave barriers time to become acceptable, depended on which cases you were looking at.
The resident had said: how long will this take?
Saebyeok had given her honest estimate. Three to six months for a best-case resolution through the amendment dispute pathway. Longer if they needed Track B.
The resident had said: I don't have twelve weeks.
Saebyeok had said: I know. That is why we filed in September rather than waiting for the October review cycle.
Six weeks earlier. That was the practical gain. Six weeks of inquiry window, six weeks of escalation period, running in September and October rather than October and November. The hearing, if they reached it, would begin in November rather than January. Resolution, if everything moved on schedule, by February or March 2048. The resident had been navigating the barrier since November 2044. She would navigate it for at least four more months.
At 11:20 AM Saebyeok opened a new document.
She wrote the informal update to the resident first: not the formal case update, which would go through the case management system with the proper acknowledgment protocol, but the message in plain language. We did what we said we would do on the date we said we would do it. The escalation is filed. The HTD liaison has been notified. Here is the oversight case number. Here is what happens next and when.
What happened next: the oversight office would contact the amendment committee within ten business days. The HTD liaison would flag PROP-2043-LENT-7782 for priority review, moving the file out of the standard amendment review backlog. Neither action would correct the assessment. Both would make the committee's failure to correct the assessment into a documented record in two external oversight systems. The committee's inaction was no longer describable as backlog. It was now documented, across two systems, as a failure to respond within the required window, with ongoing harm to an identified resident.
She did not know if this would change the pace of resolution.
She knew it was the next step.
She sent the informal message at 11:31 AM. She sent the formal case update through the case management system at 11:38 AM, with the Track B escalation confirmation number and the HTD liaison confirmation number attached.
At 2 PM she had a meeting about a second case: a categorization error in a 2045 assessment that the housing authority had already acknowledged as an error and committed to correcting in the next review cycle, February 2048. Simpler because there was no denial, only acknowledged delay. She found the distinction between acknowledged delay and unacknowledged delay less consoling as a practical matter than as a procedural one. The resident in the second case had adjusted his documentation around the acknowledged error and was managing. He had had to adjust. He had managed. This was a different kind of administrative barrier than PROP-2043-LENT-7782, but it was the same kind of drain.
After the meeting she added the oversight case number to her files: TRACK-B-2047-1142. She noted the contact window: the oversight office would contact the amendment committee no later than October 1. She put October 1 in her calendar.
At 12:04 PM she had refreshed the portal.
INQUIRY_LOGGED. Orange.
She closed the tab. She had learned, in thirty-four mornings of checking, that closing the tab was the relevant action after checking. Not refreshing again. Just noting the status, noting the timestamp, closing the tab.
The amendment committee portal still showed INQUIRY_LOGGED. She did not open it again until 9:02 AM the next morning.
The Track B oversight office case number arrived in her email at 11:52 AM, forty-eight minutes after submitting the escalation. The confirmation message: Your Track B escalation has been received. A case coordinator will contact the relevant committee within 10 business days. The case number was TRACK-B-2047-1142. She added it to the case files and put October 1 in her calendar as the latest possible contact date.
The HTD liaison acknowledgment arrived at 12:08 PM: Your priority review notification for PROP-2043-LENT-7782 has been logged. Priority review flags are typically processed within the current quarterly review cycle. This was less precise than she would have preferred. She noted it.
In the ARCH-INQ public database, her inquiry remained visible under the orange-status filter: INQ-2047-09-09-4491, filed September 9, last status change September 9, from RECEIVED to INQUIRY_LOGGED. The committee had not updated the entry. She expected it to remain unchanged until the oversight office contact on or before October 1, at which point the committee would be required to log a response in the inquiry system regardless of whether they had substantively responded. The requirement to log a response was not the same as the requirement to act on the response. She understood this. It was still better than the current state, in which the committee was not required to do either.
She had stopped expecting the portal to show blue on any given day around September 4, a week before the inquiry window opened. She had not stopped checking at 9:02 AM. The two were compatible: the check was not driven by expectation. It was driven by the requirement to know the status at the moment the window expired, which was now. She knew. She had noted it. She had filed the escalation.
The portal would show what it showed tomorrow morning. She would check at 9:02.