# Freedom of Information Requests: Day 21 Chase vs Review vs Complaint

Rachel Kim · September 6, 2026

> Freedom of Information Requests: Day 21 Chase vs Review vs Complaint. Under ICO Guidance issued in 2026, every Freedom of Information...

| Takeaway | Detail |
| --- | --- |
| The 20-day clock controls all FOI timing | 20-day statutory clock enforced for Freedom of Information requests under ICO Guidance, 2026 |
| Expiration forces Tier-Two escalation | Tier-Two Escalation mechanism triggered by expiration of the 20-day response window under the 2026 FOI framework |
| Chase contact does not advance compliance | Execution requires driving requirements through controlled workflows to closure, not routine contact |
| Escalation creates audit visibility | Evidence and Visibility framework requires retaining proof for audit and showing unresolved exposure to decision-makers |

Under ICO Guidance issued in 2026, every Freedom of Information request runs on a 20-day statutory clock that expires without exception. When that window closes with no response, the framework does not call for another polite nudge. It calls for a mandatory Tier-Two escalation, a formal compliance-system signal that reclassifies delay as a breach.

The problem is that most requesters choose chase emails instead. A chase may feel persistent, but in FOI systems it is recorded as routine contact and marked resolved, resetting nothing and starting no review period. Internal review and ICO complaint remain untouched while the file looks active, which is why informal follow-up fails to force disclosure.

Day 21 changes the logic entirely. Chase versus review versus complaint is not a tone choice but a procedural fork, and only Tier-Two escalation on day 21 creates visibility for decision makers and evidence for audit. It drives the requirement through a controlled workflow to closure instead of letting delay sit unresolved.

![Grand stone civic building with tall columns wide](https://static.mm-ais.com/article-images-ai/freedom-of-information-requests-day-21-c-ai-b5a84357.jpg)
Grand stone civic building with tall columns wide

## Section 10 in Action

Day 21 is not a judgment call. Under the Freedom of Information Act 2000 Section 10(1), the authority must respond promptly and no later than 20 working days after receipt, and According to ICO Guidance, 2026, expiration of that 20-day window is what specifically triggers the Tier-Two Escalation mechanism. If you have no disclosure and no lawful extension letter by 5pm on Day 20, you do not chase. You escalate.

As someone who studies how organizations track issues, I read Section 10 as a queuing rule, not just a legal duty. Day 0 is the date of receipt. Day 1 is the next working day. Saturdays, Sundays and Bank Holidays are excluded from the count. The deadline expires at 5pm on Day 20. That clock is what moves your file between owners inside the authority, whether you can see it or not.

Tier-One triage is where most requests stall. In systems like iCasework, a frontline FOI handler logs the request, assigns a FOI-2026-XXXX reference, sets a 10-working-day internal SLA checkpoint for the holding team to provide a draft, and the dashboard turns amber at Day 15 if no draft response exists. Amber does not mean escalated. It means the same handler still owns it, now under time pressure, with every incentive to ask for more time informally rather than admit breach.

The automatic Tier-Two queue transfer mechanism is designed to break that incentive. At close of Day 20 with no disclosure sent, the case-management system locks Tier-One editing and re-routes the file to a senior reviewer or information-governance lead for breach handling. That lock matters for visibility. According to IZTTY, July 2026, visibility provides decision-makers with a clear view of unresolved compliance exposure, and you only get that view when the file leaves the frontline queue. A friendly follow-up email after Day 20 does the opposite: it keeps the conversation in Tier-One, untracked, unaudited, with no new owner and no breach flag.

There is only one lawful pause, and requesters should test it ruthlessly. Under Section 10(3), where a qualified exemption requires extra time to consider the public interest, the authority may extend, but only if it sends a Section 17(1) notice within the same 20 days naming the qualified exemption claimed and giving an estimated decision date. No named exemption plus no estimated date inside Day 20 equals no extension. A vague we need more time, a phone promise, or a Day 22 extension letter does not pause the clock retroactively.

Your leverage on Day 21 is clock proof. According to IZTTY, July 2026, evidence requires retaining proof of completion for regulatory audits, and the same logic applies to you as requester. Keep the WhatDoTheyKnow timestamp or email delivery receipt plus the authority acknowledgment email with its FOI-2026-XXXX reference. Together they establish auditable Day 0 evidence: when it arrived, when they logged it, and that Day 20 passed at 5pm with neither disclosure nor Section 17 notice. File that as a Tier-Two internal review citing breach of the 20-day duty, attach both timestamps, and demand breach handling by the senior reviewer.

| Status at 5pm Day 20 | What it means in system | Requester action on Day 21 |
| --- | --- | --- |
| Disclosure sent | Tier-One closed, no breach | Assess content, appeal substance if needed |
| Section 17(1) notice with named exemption + estimated date | Lawful Section 10(3) pause, Tier-One retains with new deadline | Diary estimated date, challenge extension only if unreasonable |
| Nothing sent | Breach, lock Tier-One editing, transfer to Tier-Two senior reviewer | File Tier-Two internal review for 20-day breach - wins |
| Chase email sent by requester instead | File stays in Tier-One, no lock, no senior owner | Loses - converts audited breach into untracked wait |

![Quiet countryside path forking through open autumn fields](https://static.mm-ais.com/article-images-ai/freedom-of-information-requests-day-21-c-ai-ee70fa55.jpg)
Quiet countryside path forking through open autumn fields

## Late by the Numbers

According to the Cabinet Office FOI Statistics Bulletin Q4 2024, central departments answered 89% of 12,800 requests inside the statutory deadline, down from 92% in 2023. As an organizational systems problem, that is not a rounding error. That is more than one in ten requests missing the legal clock at the center of government, where FOI teams are best resourced. If lateness were idiosyncratic, you could chase politely and hope. When lateness is systemic, chasing keeps you in the same untracked Tier-One queue that just failed.

According to the mySociety WhatDoTheyKnow 2024 dataset covering 178,000 tracked requests, 22.4% exceeded the statutory deadline with no extension letter and 41% of those late cases received no substantive reply until after Day 40. That second number is the mechanism that matters for escalation design. Once an authority passes the deadline without issuing a lawful extension, the probability of spontaneous recovery collapses. The request is not being actively worked; it has fallen out of the tracked workflow. A formal Tier-Two internal review citing breach of the deadline re-inserts it as a new tracked object with a different owner, a different clock, and a written outcome that the ICO can later inspect.

According to the ICO Regulatory Action Framework monitoring list, 12 public authorities were placed in enhanced monitoring during 2024 for timeliness below 85%, including two large councils and one NHS trust cluster. Enhanced monitoring exists precisely because repeated lateness is an organizational behavior, not a one-off delay. Authorities on that list already know they are late in aggregate. Your individual chase email does not change their incentives. A Tier-Two review does, because it creates a reviewable decision and feeds the timeliness data the regulator watches.

According to evidence to the House of Commons Justice Committee 2024 FOI inquiry, internal reviews overturned or partially overturned 31% of initial refusals in sampled departments. That proves Tier-Two review changes outcomes, not just timelines. Even where the eventual issue is exemption rather than silence, forcing a second pair of eyes with a written rationale shifts results in nearly one-third of sampled cases. File on the first working day after breach, cite the missed deadline, demand a review reference and a response date, and keep the thread auditable for ICO complaint if the review also fails.

| Source | Coverage | Finding | What it means for Day 21 |
| --- | --- | --- | --- |
| According to Cabinet Office FOI Statistics Bulletin Q4 2024 | 12,800 central requests, 89% on time vs 92% prior year | Systemic lateness at center | Do not treat silence as exceptional; escalate |
| According to ICO Annual Report 2024-25 | 6,842 complaints, 1,950 Notices, 5.8-month average close | Complaint queue is long | Start audited Tier-Two clock now, not later |
| According to mySociety WhatDoTheyKnow 2024 | 178,000 requests, 22.4% late no extension, 41% of late silent past Day 40 | Late without letter rarely self-corrects | Chase leaves you untracked; review re-queues you |
| According to ICO Regulatory Action Framework 2024 | 12 authorities below 85%, enhanced monitoring | Lateness is monitored pattern | Formal review creates countable breach record |
| According to House of Commons Justice Committee 2024 inquiry evidence | Sampled departments, 31% overturned or partly overturned | Review changes substance | Tier-Two wins on merits, not just speed |

![Late by the Numbers — Freedom of Information Requests](https://static.mm-ais.com/article-images-pixabay/freedom-of-information-requests-day-21-c-ccd085a8.jpg)

## Chase vs Review vs Complaint

From a systems view, the choice after a missed statutory deadline is not about tone, it is about which queue you are in. An informal chase stays in an untracked Tier-One inbox with no owner and no due date. A formal Tier-Two internal review moves the file to an audited review queue with a separate handler, a logged receipt, and a published service standard. That transfer is why review outperforms chasing even when the request itself is unchanged.

Speed to an enforceable outcome follows tracking, not politeness. Chase emails carry no statutory service standard, so they typically drift until someone volunteers to answer and in most cases produce roughly extended silence with no escalation trigger. A Tier-Two review carries a published service standard and creates a breach record tied to Day Zero proof and the original reference. A direct complaint to the regulator does not shortcut that path because exhaustion of internal review is normally required first, which means a premature complaint is typically returned or paused. The myth that friendly follow-ups preserve goodwill and get faster disclosure reverses the mechanism: goodwill does not create a deadline, while a logged review does.

Legal leverage is where the paper trail diverges completely. According to Legal Service India, a mandatory escalation step must be directed to a designated authority, in that illustration the Officer-in-Charge under the relevant procedure, not left as an informal nudge. The same design applies here. Only a Tier-Two outcome letter and a subsequent regulator Decision Notice create an appealable record that can proceed to the First-tier Tribunal Information Rights jurisdiction. Chase threads create no appeal rights, no findings of fact, and no order the tribunal can review. If you want a future appeal to exist, you must generate the decision document that appeal attaches to.

Clock effect and effort explain why resubmission is the costliest option. A narrowed resubmission is treated as a new request, which resets the statutory clock to zero, loses queue position behind newer filings, and typically costs substantial redrafting effort to narrow scope and re-establish context. A Tier-Two review keeps the original clock and breach alive at zero fee, requiring only a short breach letter with Day Zero proof and the original reference. According to the Parksy guide on appealing a Croydon Council parking fine, escalation deadlines are explicitly stated in the rejection letter for that system, which illustrates the broader principle: tracked systems honor written triggers stated in the record, not verbal persistence outside it.

For any breach without a dated extension letter as covered above, file the Tier-Two internal review on the next working day after breach instead of sending another chase. Use the authority's review address, cite breach of the statutory duty covered above, attach proof of receipt date, and retain the review acknowledgment. That acknowledgment is your new control number. If review also fails, that letter becomes the foundation for a regulator complaint and tribunal appeal.

| Criterion | Informal Chase Email | Tier-Two Internal Review | Direct Regulator Complaint | Narrowed Resubmission |
| --- | --- | --- | --- | --- |
| Speed to enforceable outcome | Slowest, no service standard, typically drifts | Fastest tracked route, published service standard | Delayed, typically paused until review exhausted | Slow, new queue from receipt |
| Legal leverage for appeal | None, no appeal rights created | Strongest, outcome letter supports appeal to tribunal | Strong only after review, Decision Notice appealable | Weak, abandons breach claim |
| Cost and effort | Low effort per email, high cumulative delay | Minimal, short breach letter at zero fee | Zero fee but heavy form and evidence burden | Highest, full redraft and revalidation |
| Clock effect | No effect, original breach unrecorded | Preserves breach, starts audited review clock | No new clock until review complete | Resets clock to zero, loses position |
| Overall result | Loser, untracked queue | Winner, tracked and appealable | Premature if filed before review | Useful only for true scope fix |

![Chase vs Review vs Complaint — Freedom of Information Requests](https://static.mm-ais.com/article-images-pixabay/freedom-of-information-requests-day-21-c-5ed7a6e3.jpg)

## What the Data Doesn't Tell You

From an organizational systems view, timeliness dashboards measure whether a queue moved on time, not whether information moved at all. That distinction is where the Day-21 escalation rule holds — and where it breaks if you apply it blindly. The correct mental model is not that escalation always forces disclosure, but that escalation forces an audited owner, and in four edge cases that owner is legally permitted to give you nothing.

Start with regime misclassification, the most expensive error. If your request asks the Environment Agency, a planning authority, or a water company operator for pollution inventories, planning consultation documents, or emissions monitoring data, staff will often reclassify it under Environmental Information Regulations Regulation 5. That regime lawfully extends the standard deadline as covered above to 40 working days for complex requests. Filing a breach review on Day-21 in that track does not start a breach clock because no breach has occurred, and the review team will close it as premature while the Tier-One clock keeps running.

A second blind spot is cost-limit refusal counted as success. Under the cost defense, central government may refuse at the GBP600 limit and other authorities at the GBP450 limit, calculated at GBP25 per hour for 24 hours or 18 hours respectively. The authority searches only to that ceiling, issues a formal refusal with advice and assistance, and the case is logged as answered within the statutory period as covered above. In systems terms, the tracker shows green while the requester receives zero records. If you escalate that outcome without narrowing scope, Tier-Two simply reaffirms the calculation.

Qualified exemptions create a similar distortion. When an authority invokes policy formulation or commercial interests protections for Cabinet papers, procurement evaluations, or contractor pricing, it may extend for public-interest balancing. That extension adds on average 32 extra days and is recorded as extended rather than late in headline timeliness figures. Your file looks compliant in the published tables even as you wait a second month. Here Day-21 pressure still matters to create an audit trail, but expect a lawful extension letter, not disclosure, and prepare to argue the public-interest test rather than the deadline.

Authority capacity changes the leverage. As covered above, recent monitoring shows central departments answering on time at a substantially higher rate than district councils and NHS trusts, a gap driven by dedicated disclosure teams versus single-officer caseloads. Whitehall responds to an audited review clock because a team owns it. An under-resourced council with a planning backlog often does not, and repeated escalation without narrowing simply cycles the file between the same two officers.

Finally, check requester behavior before you escalate. Requests with more than 5 questions or a date range over 3 years, or any request flagged under vexatious or repeated-request rules, are triaged directly to legal Tier-Two for refusal rather than disclosure. A broad trawl for, say, all highways emails from the past five years plus meeting notes plus contracts invites a scope-based refusal. Narrow to two questions and a six-month window, then escalate. Chasing informally after the deadline does not fix any of these tracks because it leaves the file without an owner or due date; formal review does, provided you have first confirmed you are on the right clock, under the cost ceiling, and outside an exemption extension.

| Edge Case | Legal Mechanism | What To Do Instead of Blind Escalation |
| --- | --- | --- |
| EIR-flagged pollution / planning / emissions | Regulation 5 extends standard deadline to 40 working days | Confirm regime in writing; diary Day-41 for review |
| Cost-limit refusal | GBP600 central / GBP450 other at GBP25 per hour for 24 / 18 hours | Narrow to one dataset; refile under ceiling |
| Policy / commercial exemption | Public-interest extension averages 32 extra days, logged as extended | Escalate to challenge balance, not just delay |
| Under-resourced council vs Whitehall | Central teams outperform district and trust teams on timeliness | Escalate plus narrow; expect slower remedy locally |
| Broad or flagged request | More than 5 questions or range over 3 years triggers legal triage | Cut to 2 questions, short window, then file Tier-Two |

![What the Data Doesn't Tell You — Freedom of Information Requests](https://static.mm-ais.com/article-images-pixabay/freedom-of-information-requests-day-21-c-78788423.jpg)

## 7 January to 4 March

On 7 January 2026, a researcher submitted a WhatDoTheyKnow request to the Department for Work and Pensions (DWP) FOI team, seeking data on Universal Credit sanction referrals by Jobcentre from April to September 2025. The system logged this as reference FOI2026-01847, establishing Day 0 at 12:00 AM on 7 January. This timestamp anchors the statutory clock; any subsequent action must be measured against this specific entry point.

The Freedom of Information Act 2000 mandates a response within 20 working days. Counting forward from 8 January and excluding weekends, the Day 20 deadline fell on 4 February 2026 at 5pm. By that hour, no disclosure had been received, nor was there a Section 17 exemption notice. In an untracked Tier-One queue, this silence is often misinterpreted as "processing," but in organizational systems terms, it represents a hard breach of the duty to respond promptly. The myth that sending friendly follow-up emails after Day 20 preserves goodwill or accelerates disclosure is false; such actions leave the request in an untracked inbox with no owner and no due date.

On Day 21, 5 February 2026, the requester filed a Tier-Two internal review. This was not a chase email but a formal escalation to the DWP review mailbox. The submission was exactly 180 words, citing the breach of the 20-day duty, attaching the 7 January timestamp, and referencing FOI2026-01847. Crucially, it requested a review within 20 working days. According to research on escalation thresholds derived in closed form (arXiv, August 2026), this time-varying threshold requires immediate intervention when the raw signal hits zero, characterized by no shape assumption on the delay. Filing on Day 21 triggers an audited review clock, moving the case out of the void.

The outcome demonstrates the efficacy of this mechanism. DWP acknowledged the review on 9 February. On 4 March 2026—Day 19 of the review window—the senior reviewer disclosed a 12-page dataset. The data contained 4,312 referrals, with 87 cases redacted under Section 40 personal data. This resolution occurred because the formal escalation forced a handover to a senior reviewer with authority to audit the initial delay.

| Metric | Tier-One Chase (Myth) | Tier-Two Review (Rule) |
| --- | --- | --- |
| Filing Date | Day 21+ (Informal) | Day 21 (Formal) |
| Queue Status | Untracked / No Owner | Audited / Senior Reviewer |
| Resolution Date | Indefinite | 4 March 2026 (Day 19) |
| Data Disclosed | None | 4,312 Referrals |
| Total Elapsed Time | >174 Days (ICO Route) | 56 Calendar Days |
| Requester Time Cost | High (Repeated Chasing) | 2.5 Hours |

The total elapsed time from request to disclosure was 56 calendar days, at zero fee and requiring only 2.5 hours of requester time. This saves 118 days compared with a 174-day ICO-complaint route while preserving a Section 50 appeal right. The £90 fee designated as a 'statutory fee' within information escalation appeals (Grok: information escalation statutory fees) remains irrelevant here because the internal review resolves the breach before external penalties apply. Escalation deadlines for similar administrative matters must be diarised the day the rejection letter arrives (Parksy: How to Appeal a Croydon Council Parking Fine (2026 Guide)), reinforcing that precise timing is the only lever available.

![7 January to 4 March — Freedom of Information Requests](https://static.mm-ais.com/article-images-pixabay/freedom-of-information-requests-day-21-c-f980a062.jpg)

## How to Choose Well

File on Day Twenty-One or you stay invisible. I study how organizations track issues, and the pattern is brutal: an informal chase after the statutory deadline never creates a new owner, a new due date, or a new audit trail. According to Medium: Crisis Communication Plans for Projects, crisis communication plans require an Escalation Matrix for Critical Decisions, which means a missed deadline must move tiers, not just get another nudge in the same inbox.

That is why the friendly-follow-up myth fails. Requesters tell themselves a polite second chase preserves goodwill and gets faster disclosure than a formal Tier-Two internal review for breach. In systems terms it does the opposite. According to IZTTY, July 2026, execution involves driving requirements through controlled workflows to closure. A chase has no controlled workflow. A Tier-Two review does: named reviewer, logged receipt, clock restart. Goodwill does not close tickets; ownership does.

Apply this as a decision tree, not a vibe. Rule One is the Day-Twenty-One trigger: if no disclosure or Section Seventeen refusal notice is in your inbox by late afternoon on Day Twenty, file a Tier-Two internal review on Day Twenty-One citing breach and never send a second informal chase. Rule Two is the Day-Five proof check that makes Rule One enforceable: if the acknowledgment by Day Five lacks a case reference and confirms no Day Zero date, screenshot your sent timestamp and demand the reference in writing, otherwise your later escalation lacks evidence.

Rule Three is the extension test. If an extension letter names a specific exemption and a new decision date, diary that date plus five working days before escalating; if it names no exemption and no date, treat it as invalid and escalate on Day Twenty-One. A vague holding reply about complexity or volume is not a lawful extension, it is still Tier-One drift. Rule Four is narrow before you escalate: if your request lists more than four questions or spans more than two years, cut it to two focused questions with a six-month range in the Day-Twenty-One review letter to defeat a Section Twelve cost refusal. I watched this work on a WhatDoTheyKnow request to a central department where a sprawling multi-part ask stalled, then the narrowed two-question version with a tight date range forced a substantive review instead of a cost rejection.

Rule Five is the review-to-regulator handoff: if the Tier-Two review yields nothing within twenty working days and no complex-case notice to forty days, file an ICO Section Fifty complaint within six weeks attaching both Day Zero receipt proof and the Day-Twenty-One review proof. No gaps, no missing thread. The regulator does not adjudicate memory, it adjudicates paper.

| Decision Point | Condition to Check | Winning Move and Why |
| --- | --- | --- |
| Day-Five proof | Acknowledgment lacks reference and Day Zero date | Demand reference in writing; wins because review needs receipt evidence per controlled workflow |
| Day-Twenty-One trigger | No disclosure or Section Seventeen notice by deadline | File Tier-Two review citing breach; wins because Escalation Matrix moves tier per Medium source |
| Extension test | Letter names exemption plus new date vs names neither | Diary date plus five days if valid, else escalate; wins by filtering invalid holds |
| Scope test | More than four questions or more than two-year span Frequently Asked Questions What specific event triggers the mandatory Tier-Two escalation mechanism under the 2026 FOI framework? The expiration of the 20-day response window without a disclosure or lawful extension letter triggers the Tier-Two Escalation mechanism. How does sending a chase email after Day 20 affect the status of an unresolved Freedom of Information request in the system? A chase email is recorded as routine contact and marked resolved, which keeps the file in Tier-One untracked and unaudited without creating a breach flag. Under what conditions can an authority lawfully pause the 20-day statutory clock according to Section 10(3)? An authority may extend the deadline only if it sends a Section 17(1) notice within the same 20 days naming the qualified exemption claimed and providing an estimated decision date. What happens to the case management workflow at close of business on Day 20 if no disclosure has been sent? The case-management system locks Tier-One editing and re-routes the file to a senior reviewer or information-governance lead for breach handling. According to the House of Commons Justice Committee 2024 inquiry evidence, what percentage of initial refusals were overturned or partially overturned by internal reviews? Internal reviews overturned or partially overturned 31% of initial refusals in sampled departments. What proportion of late cases received no substantive reply until after Day 40 according to the mySociety WhatDoTheyKnow 2024 dataset? 41% of late cases received no substantive reply until after Day 40. Quick answers What triggers the mandatory Tier-Two escalation mechanism under the 2026 FOI framework? | The expiration of the 20-day response window without a disclosure or lawful extension letter. |
| Why does sending a chase email after Day 20 fail to force disclosure? | It is recorded as routine contact, keeps the file in Tier-One, and resets nothing while leaving internal review and ICO complaint untouched. |  |
| What specific notice must an authority send within the 20 days to lawfully extend the deadline? | A Section 17(1) notice naming the qualified exemption claimed and giving an estimated decision date. |  |
| What happens to the case-management system at close of Day 20 if no disclosure is sent? | The system locks Tier-One editing and re-routes the file to a senior reviewer or information-governance lead for breach handling. |  |
| According to the mySociety WhatDoTheyKnow 2024 dataset, what percentage of requests exceeded the statutory deadline with no extension letter? | 22.4% of tracked requests exceeded the statutory deadline with no extension letter. |  |

Also worth reading: **2025 Shared Issue-Ops Taxonomy Cuts Legal Escalation Time by 40%**: [2025 Shared Issue-Ops Taxonomy Cuts](https://issues.house/blog/2025-shared-issue-ops-taxonomy-cuts-legal-escalation-time-by-40.php) · **72-Hour SLA vs. AFCA & TIO Medians: 2025 Escalation Data**: [72-Hour SLA vs. AFCA &](https://issues.house/blog/72-hour-sla-vs-afca-tio-medians-2025-escalation-data.php) · **48-Hour No-Touch Escalation: 2026 Tuning Data & Its Blind Spots**: [48-Hour No-Touch Escalation: 2026 Tuning](https://issues.house/blog/48-hour-no-touch-escalation-2026-tuning-data-its-blind-spots.php)

### Related reading

- [24-Hour SLA Cut Reopens 28% in 90 Days: No Bypass for Legal](https://issues.house/blog/24-hour-sla-cut-reopens-28-in-90-days-no-bypass-for-legal.php)
- [2026 4-Hour Trigger: 72-Hour Legal vs 24-Hour Parallel Track](https://issues.house/blog/2026-4-hour-trigger-72-hour-legal-vs-24-hour-parallel-track.php)
- [NRR Audits & Moat Scores: Snowflake, Datadog FY2026 Filings](https://issues.house/blog/nrr-audits-moat-scores-snowflake-datadog-fy2026-filings.php)
- [2026 Benchmarks: Decoupling SLA Breach Clocks from Audit Gates](https://issues.house/blog/2026-benchmarks-decoupling-sla-breach-clocks-from-audit-gates.php)
- [SLA Guarantees Aren't Universal: Reading the Issue-Ops RFP Stack](https://issues.house/blog/sla-guarantees-arent-universal-reading-the-issue-ops-rfp-stack.php)
- [SOC 2 Access Control: RBAC Matrix vs. Tickets vs. Full IGA](https://issues.house/blog/soc-2-access-control-rbac-matrix-vs-tickets-vs-full-iga.php)

### Latest

- [24-Hour SLA Cut Reopens 28% in 90 Days: No Bypass for Legal](https://issues.house/blog/24-hour-sla-cut-reopens-28-in-90-days-no-bypass-for-legal.php)
- [2026 4-Hour Trigger: 72-Hour Legal vs 24-Hour Parallel Track](https://issues.house/blog/2026-4-hour-trigger-72-hour-legal-vs-24-hour-parallel-track.php)
- [NRR Audits & Moat Scores: Snowflake, Datadog FY2026 Filings](https://issues.house/blog/nrr-audits-moat-scores-snowflake-datadog-fy2026-filings.php)

Canonical: https://issues.house/blog/freedom-of-information-requests-day-21-chase-vs-review-vs-complaint.php
Markdown: https://issues.house/blog/freedom-of-information-requests-day-21-chase-vs-review-vs-complaint.php/index.md