Request overview tab — request status, key dates, scope, extensions, clock pauses, and timeline summary
Last updated: November 14, 2026 by Steve
Request Overview
The Details tab (once called Overview) is the main information screen when you open a request. It provides a summary of the request's current state, key dates, and scope.
The Request Header
The header shows the title and number, the status, the priority, the due date and a Discussion button. Point at the status to see the lifecycle stage it belongs to (for example Stage: In review), which helps when your organization named its statuses itself. The days figure reads Days remaining while the due date is ahead, Days overdue (in red, as a positive number) once it has passed, and Paused while the request is on hold. The … menu sits beside Help and Close and offers Add reminder, Place preservation hold… (see Preservation Holds on a Case) and, on a request still in Draft, Delete draft request (for people who may delete requests; an optional reason is recorded). Help opens the page for the tab you are on.

Editable Fields
The following fields can be updated on the Overview tab:
| Field | Description |
|---|---|
| Title | A descriptive title for the request. |
| Description | Summary of what information is being requested. |
| Scope | Date range and subject matter that define the boundaries of the request. |
| Keywords | Terms to help categorize and search for the request. |
| Information Categories | The types of information relevant to this request. |
| Priority | Low, Normal, High, or Urgent. |
| Complexity | Simple, Moderate, or Complex. |
| Status | The current lifecycle status of the request. |
AI Intake Triage
When AI Assist is enabled, an AI intake triage card appears on the Overview tab. It reads the intake text already on the request — the description and details captured when the request came in — and offers suggestions to help you set the request up:
- A suggested title, which you can apply with one click.
- A plain-language summary of what is being asked.
- Key topics, applied as keywords with one click.
- A Scope section — the records sought and any explicit exclusions, appendable to the request's scope in one click.
- A third-party callout flagging organizations or individuals whose interests may need consulting.
- Structured findings, each shown with the verbatim passage it was drawn from.
- Clarification questions worth putting to the requestor.
Everything the card produces is a suggestion — nothing is applied to the request until you click to accept it. The card deliberately does not suggest a request type: type changes recalculate deadlines, so that stays a human decision on the form.
AI intake triage is part of AI Assist, an optional capability. The card only appears when your organization has deployed AI Assist. AI Assist runs on an Azure OpenAI resource in your organization's own Azure subscription and region: request content never leaves your tenant, Microsoft does not train its models on it, and prompts and responses are not stored — only usage metadata is kept.

The Sidebar: AI Assist, Follow-ups and Related
The sidebar answers where does this case stand, and who owns it: the Status/priority card, the Hours card, the Key dates card, the Assigned owners card, a Follow-ups card, one AI Assist card and one Related card (linked requests and reference links, folded until you open it, remembering your choice). An Expedited processing card appears only for a request type whose law provides it (US FOIA) or when the requestor has already asked for it. The requestor's format preferences are on the Requestor tab, and the programs the request concerns are on the Response & fees tab under Case audit export.
The Follow-ups card lists the open, upcoming (waiting periods, with their end date and the law) and recently finished follow-ups on the request, with Done, Skip, Snooze and Reassign; your own reminders are marked Only you. See Follow-ups on a Case.
The AI Assist card groups three parts, each shown only when it has something to say, and — once the request is closed — a prompt to capture what was learned:
- Suggested next action — a small card suggesting the single most useful next step, with a one-sentence rationale grounded in the request's own facts and a link to the tab where the step happens. Results are cached per request, so an unchanged request doesn't re-run the AI — use the refresh icon to regenerate. Advisory only; nothing is ever done for you.
- Case check — sits under Suggested next action and lists what a quality reviewer would flag: overdue actions, missing approvals, redactions citing no exemption, unreviewed suggestions, and the like. Its compliance-relevant findings come from deterministic rules that run on every tenant; when AI Assist is deployed, an AI pass may add consistency observations — as warnings and suggestions only, never blockers. The same rules feed the tenant-wide Case hygiene report.
- How similar cases went — shows its two headline figures and folds the rest away: computed outcome facts from similar closed requests (outcomes, extensions taken, exemptions cited). It works with or without the semantic index — matching by meaning when available, by text overlap otherwise — and matches are always security-trimmed to requests you can open. It reports what happened; it never recommends.
Suggested next action and How similar cases went are part of AI Assist, an optional capability, and only appear when your organization has deployed it. Case check's deterministic findings appear on every tenant regardless; its AI-assisted observations require AI Assist.
Request Lifecycle
Requests move through the following statuses:
Draft → Active → In Review → Closed
A request can also move between Active and On Hold as needed.
Status Transitions
| From | To | When |
|---|---|---|
| Draft | Active | The request is ready to begin processing. |
| Active | In Review | Documents have been collected and the request is ready for review. |
| Active | On Hold | Processing is paused, e.g., waiting for the requestor to clarify their request or pay fees. |
| On Hold | Active | The hold reason is resolved and processing resumes. |
| In Review | Closed | Review is complete and the response has been sent. |
| Closed | Active | The request is reopened — see Reopening a Closed Request. |
Closed Requests Are Read-Only
Once a request is closed, a banner appears above the tabs, on every tab, confirming the lock. Assignments, tasks, documents, and collaboration records can be viewed but not edited. Post-closure correspondence (acknowledgments, appeals, follow-up letters) remains available under the Requestor tab so you can continue to log legitimate activity without reopening.
Reopening a Closed Request
If you need to make substantive changes after closure — for example, an appeal has been filed, a clerical correction is required, or new responsive documents have surfaced — click Reopen in the closed-request banner. A dialog asks for a reason; the reason is recorded in the activity log alongside the state change, together with the original close date for reference. Reopening sets the status back to Active. Only Administrators and Subject Access Officers can reopen a request.
Due Dates and the Received Date
The due date is always calculated; nobody types it. AccessPoint works it out from the received date with the request type's rule (its period, counted in calendar days, business days or months on the type's calendar, with its holidays), then adds every extension in the rule's own unit and every resumed clock pause in real days, and moves a deadline that lands on a weekend or holiday to the next working day. It recalculates whenever something it depends on changes: when the request is activated, when an extension or clock pause is recorded, resumed or deleted, when a running request's type changes, and when the received date is corrected. The due date cannot be set by hand anywhere, in the web part or through the API.
A request type with no statutory period (a "reasonable time" law) has no due date: the Key dates card says so instead of showing one. Where your organization works to an internal target on such requests, give the request type a standard duration and it is calculated like any other. When your administrator has set an organization time zone, the due date is counted from the received day in that time zone, whoever triggers the calculation.
How This Date Was Calculated
On the Key dates card, hover over or tab to the due date for a one-line summary, for example 30 calendar days from 1 Sep 2026 + extension of 30 calendar days + 12 days paused. The How this date was calculated button expands every step in place: the received date (and, if it was corrected, the original date with the reason); the day the clock really started when an identity-verification or intake hold opened at receipt; the rule (period, counting, the provision that sets it and the calendar); for a law that changed its period, which rule applied because of the date the request arrived; the holidays not counted, by name; the statutory due date; each extension and clock pause; and the final due date. It works with a keyboard, touch and screen readers.
If the due date on record differs from what the calculation gives today, the explanation says so and shows both. That happens for a due date set by hand before 2.5.0 (the card labels it Set by hand before 2.5.0) or when something the rule depends on changed after the date was calculated. Nothing changes it silently: the next extension, clock pause, received-date correction or type change recalculates it normally. Like every calculated statutory figure, check it against your own records and the regulator's instructions.
Where the Request Came From
Under the received date, the Key dates card shows an Origin row for a request that arrived through the public portal: Arrived through the public portal with the submission reference. There is no separate Portal tab; the secure deliveries made to the requestor are on Response & fees.
Release dates
A request answered in releases shows three more dates on the Key dates card: First release sent, Final release sent and, when the request has a release schedule, Next release due. Sending releases writes the first two and the request's response date; a follow-up rule can open work on Next release due.
Recorded requests waiting for an allowance (Hosted AccessPoint)
In Hosted AccessPoint, a request received when the plan's requests are used up is still recorded — its number, received date and computed due date, its requestor and its documents — and the page says Recorded — waiting for a request from your allowance. Due . (on the Free plan, Recorded. The Free plan includes 5 requests a year; choose a plan to work on this one.). It can be closed or withdrawn and a note added, but its case work waits until an allowance covers it; the next one goes to the waiting request due first. See Waiting Requests.
Correcting the Received Date
Once a request is active, its received date anchors the statutory clock, so it is no longer an ordinary field. On a Draft you edit it in Description & scope; on an active request it changes only through Correct received date on the Key dates card. The action needs three things: your administrator has switched on Allow received-date corrections on active requests (Settings → Features; off by default), you hold Correct the received date, and you can modify the request. A closed request must be reopened first.
In the dialog choose the correct date (not in the future, and not after the response was sent), a reason (Data-entry error, Received earlier at another office (date-stamped), Transferred request — deemed receipt date, Misdirected request or Other) and write the required explanation. You can attach evidence, such as the date-stamped letter; it is filed on the request as an administrative document and never goes into a response package. Before you confirm, the dialog shows what changes: the received and due dates old → new, whether the request becomes late or on time, any intake or identity-verification hold that moves with the date, a warning if the current due date was set by hand before 2.5.0, and the calculation before and after.

A request that became complete later is not a reason. If the request only became complete later (the fee paid, a clarification answered, identity confirmed), keep the received date and record a clock pause for the days it waited. The dialog says so and will not submit that choice. A clock pause or extension recorded by hand before the new date also blocks a later date until you adjust or delete it.
When a second person approves. Your administrator decides when a correction needs a second person (Settings → Features → Second approver for received-date corrections): Never, Only when the date moves later (the default) or Always. The approver must hold Act as senior official, must be able to see the request, and is never the person who asked. Until it is decided nothing changes: the Key dates card shows the pending correction, approvers get a My Day action and a notice, the approver can Approve or Reject (a reason is required), and the person who asked can Withdraw it. One correction can wait per request.

What a correction records. The new received date and the recalculated due date take effect together. The Activity tab shows Received date corrected with the old and new dates, the reason, who asked and who approved, and the due date it moved. If the due date changed, the card offers Send corrected acknowledgement, which opens the correspondence composer on the acknowledgement letter; nothing is sent automatically. The Received-date corrections report lists every correction (see Received-date corrections).
Extensions and Clock Pauses
The Extensions section allows you to adjust the statutory deadline when legislation permits.

Adding a Deadline Extension
To add an extension:
- Click Add Extension in the Extensions section.
- Select an extension reason from the configured list. Only the reasons the request's received date allows are offered, where your organization gives reasons a date window (see Extension Reasons).
- Enter the number of additional days, in the rule's own unit. The due date is recalculated, never typed.
- Save the extension.
Adding a Clock Pause
A clock pause temporarily stops the statutory deadline clock, for example during a fee negotiation or while waiting for the requestor to narrow their request.
- Click Add Clock Pause.
- Set the start date for the pause.
- When the pause reason is resolved, return and set the end date to resume the clock.
All extensions and clock pauses are recorded in the request's activity history, providing a complete audit trail.
Identity-Verification Hold
One clock pause can open on its own. On request types that require identity verification and opt into the stop-the-clock (Settings → Request Types → Legal), an identity-verification hold opens automatically the moment the request is created and is released the moment identity is marked verified — no one has to add or remove it by hand. The received date stays the statutory anchor: days spent waiting for proof of identity never burn the clock (this mirrors GDPR Art. 12(6) / ICO stop-the-clock guidance, and several jurisdiction packs pre-wire the hold with the right statutory citation). If verification is later cleared, the hold re-arms itself.
Deemed Refusal
A request past its statutory due date keeps its status and is shown as overdue — in the request list, in its key dates, in My Day (with a suggestion to send a delay notice and a letter on the right to complain — the delay notice alone once the request is in Deemed refusal, since the requestor has complained) and in the late counts of the reports. AccessPoint never moves a request into Deemed refusal by itself: a late response is treated as a deemed refusal once the requestor complains to the Commissioner (or your oversight body) about it. Set the request's status yourself at that point — jurisdiction packs ship the status, "Deemed refusal" in Canadian regimes or "Constructive denial" in US FOIA — and the change is written to the Activity feed like any status change.
Requests that an earlier version moved into Deemed refusal automatically stay there until you change them. An administrator can still give a request type an optional Overdue status of the organization's own (Settings → Request Types): requests of that type then move into it when the due date passes, and back out when an extension moves the deadline. AccessPoint never undoes a status a person picks, though: once someone has picked a status for an overdue request with the status picker (Deemed refusal or anything else), the request is left alone until its due date moves. Activating, resuming or reopening a request is not a pick, nor is a linked case's status change.
When AccessPoint 2.6.0 first runs, it clears the overdue status of every request type — one a jurisdiction pack set up or one of your own — whose overdue status is a deemed-refusal status that a jurisdiction pack shipped, renamed or not. No request's status changes, and an overdue status your organization created itself is kept. One case keeps moving: a pack's request type that was linked, when the pack was applied, to a status your organization had created by hand under the same code (for example DEEMED-REFUSAL) — clear its Overdue status in Settings → Request Types. A pack applied again later never sets a deemed-refusal status as an overdue status.
Abandonment
When a requestor stops responding, send the pack-shipped abandonment-notice letter from the correspondence composer — its template type drives the workflow, so there is no special button. Sending or generating it stamps a response deadline on the request (30 days by default, tenant-configurable). If the deadline passes unanswered, My Day raises a dismissible nudge and the Close dialog pre-selects the Abandoned outcome. Closing always remains a human decision.