English

Response & fees tab — the next-step card, fees (how copies are priced, instalments per release), the response package with recordings, the response date from releases, closure with its completeness check, and the case audit export

Last updated: November 12, 2026 by Steve

Response & Fees

The Response & fees tab is where the request ends: send the response, settle the fees, record the outcome, and close. A next step card at the top reads the request's current state and says what typically comes next — activate a draft, wait on open assignments, send the response, record the outcome, or close — so you always know where the request stands.

Response & fees tab

Fees

The Fee panel manages the money side of the request end to end: assess a fee, itemize it against your fee schedule, waive it (fully or partially), record payments against it, and finalize it. When a fee is assessed and unpaid, the panel can suggest a fee-pending clock pause so the statutory clock reflects the wait.

Media review estimate. When the request holds video or audio records, the hours basis shows an Estimated media review line: the recordings' total duration multiplied by your tenant's multiplier — four reviewer-hours per recorded hour by default, which an administrator can tune. Suggest media review line opens the Add-line dialog pre-filled with the basis and, where the fee schedule bills review time, the amount; you confirm or edit it before it is added. Time actually spent is logged under the Media review hours category the Universal baseline pack ships.

The hours basis with the estimated media review line

How copies are priced. The estimate, the final fee and each release's instalment price pages the same way: electronic copies at the fee schedule's electronic rate (nothing, when the schedule makes them free), paper copies at its duplication rate, and inspection nothing per page. How the copies go is read from the request's Response method: Email and Portal are electronic copies, Mail paper copies, In person inspection; a request with no response method is priced as electronic copies. The fee panel's basis card says so (Copies: Paper copies · $0.10 per page — set by the request's response method).

A fee remembers how it was priced. An estimate or final fee stores the copy format it priced the pages with when it was generated, so once the estimate is issued the card keeps explaining that amount. When the request's response method has changed since, it says so and what applies now (The request's response method has changed since this estimate was generated. Now: Electronic copies (portal or email) · free under this fee schedule. Regenerate the estimate to apply it.). Regenerating the estimate, or recalculating the final fee, prices the pages the new way. A fee generated before 2.6.0 recorded no format, so its card shows the request's current one.

Free search hours can be part of an hour: the fee schedule gives them in quarter-hour steps (0.25, 0.5, 1.5 …), and the estimate and final fee subtract exactly that. Search time is charged in the unit the fee schedule sets — per hour, per 30 minutes, per 15 minutes or per minute — and part of a unit counts as a whole one: at $7.50 per 15 minutes, an hour and a half of search costs $45. When a fee schedule carries a fee change on a date, the estimate, the final fee and each instalment charge the amounts that applied on the request's received date (see Requestor Categories).

Instalments per release. A request answered in releases can ask for its fee in instalments, one per release, and a request type can hold releases until they are paid. See Instalments and hold until paid.

Currency. Every amount and rate is written in your interface language with the symbol and decimals of the currency of the request's own fee schedule, so a Canadian-dollar schedule and a pound schedule can sit side by side in the same organization. Amounts are never converted between currencies. A fee line's note reads, for example, 150 estimated pages at $0.20 per page, and a letter writes its amounts in the letter's language.

Payments. Below the waivers, the Payments section is the ledger of every payment, refund and adjustment on the request (kind, method, amount, reference, who recorded it and when, and the provider's transaction id for an electronic payment), together with the payment requests raised on it (a deposit or a balance, with its short reference, amount due, amount paid and status).

  • Record payment logs money received outside the system: its method (cash, cheque, counter, transfer, other), a reference such as a receipt or cheque number, the paid-on date and the payment request it applies to. The Paid and Balance figures are computed from the ledger, and when the payments cover an open payment request the fee-pending clock pause is lifted automatically.
  • Request deposit (on an issued estimate) and Request balance (after finalization) raise a payment request by hand. A deposit is raised automatically when an issued estimate's net reaches the requestor category's prepayment threshold, the balance is raised automatically on finalize, and a net fee below the category's waive-below amount is waived in full without anyone asking.
  • Send payment link e-mails the requestor a link to the portal's pay page, where they verify with a code, see the amount and any convenience fee, and are sent to the payment provider's hosted page; AccessPoint never sees card or bank details. Copy link puts the same URL on the clipboard for a letter.
  • A payment is booked only when the provider confirms it to the server. The requestor's return to the portal never marks anything paid, and a receipt is e-mailed to them automatically.
  • Refund on a payment row asks for the amount (partial where the provider allows it) and a mandatory reason; an offline refund records its own method and reference.

The Payments section with a card payment, the deposit request it settled and its payment attempt

A test mode banner shows while the electronic provider is registered in test mode. Online payment needs Settings → Features → Payments (off by default), a provider under Payment providers and the public portal; the offline Record payment works regardless. See also Online fee payments.

The Response Package with Recordings

The response package is built through a release on the Documents tab's Releases sub-tab (formerly Response package) — see Releases. When a package includes recordings, the pre-flight says so and generation runs in the background: Export history shows its progress and you are notified when it is ready. The package is a ZIP holding the PDFs, a Media/ folder with the rendered MP4 or MP3 files (marks burned in, with a record-label caption), a Files/ folder for native files released as-is, and a MANIFEST.sha256 listing every entry's hash — the office's proof of exactly what was released. Records that cannot be merged into a PDF are listed on the package's Other records page with their disposition. See Video & Audio Records.

The Accessibility Check and the Accessible Edition

Every response package is checked when it is built. Its row in Export History carries one accessibility chip that sums up the check and the accessible edition, coloured only when someone has to act:

  • Accessibility: checking… or Accessible edition: building… while the work runs;
  • Accessible (green) when the package passed, or Accessible edition ready (green) when its edition is ready and nothing holds the package back;
  • in amber, Accessible edition: n figure(s) to describe, Accessible format owed (the request's Accessible format requested is set and no edition is ready) or Accessibility: action needed (your organization requires a pass or an acknowledgement before any secure delivery or publication, and the package has neither);
  • Accessible edition failed in red;
  • otherwise a neutral Accessibility details, Accessibility: acknowledged or Accessibility: not checked.

When the requirement covers only the reading room, the chip never asks for action. A package that did not pass is not an error in itself: a scanned record often cannot keep its tags, which is what the accessible edition is for. A package that was never checked says so, with Check now in its report. The chip opens the package's report, which starts with the same summary and what to do about it:

  • What was found, failures first: a record that is not tagged for screen readers (a scan, or a record whose tags were removed when its redactions were burned in), a merged PDF that is untagged because some of its records are, redactions drawn without a label (a screen reader is not told that text was withheld), figures with no text alternative, and anything the checker reported. Recordings and other files released beside the package are listed as not checked.
  • The PDF/UA-1 check. When your organization deployed the accessibility checker, it checks the package in your own subscription and lists each file with the rules it fails and the pages concerned. Check again runs a fresh check at any time, even while one is still waiting; a package built before 2.5.0 has Check now. When the checker does not answer within three hours, the package reads No answer from the accessibility checker: AccessPoint's own checks still show, no PDF/UA-1 claim is made, and a release rule that requires a passing check holds the package as needing review until someone acknowledges it. Without the checker no package can pass, and AccessPoint never describes one as meeting PDF/UA-1.
  • Human checks. No machine can tell whether the reading order makes sense or whether a text alternative describes its image. Open the package with a screen reader, then select I checked the reading order and the text alternatives; the confirmation names you and the date, is written to the audit ledger, and can be withdrawn.
  • Release anyway. Someone holding Release packages that did not pass the accessibility check can record why a package may be released although it did not pass. The reason is kept in the audit ledger and the acknowledgement can be withdrawn.

A package passes only when the checker found nothing, the in-house checks found nothing and a person confirmed the human checks. Rebuilding a package clears its confirmation and acknowledgement. Settings → Redaction appearance → Accessibility check before release decides what the verdict does: Advisory (the default, never blocks), or a requirement of a pass or an acknowledgement before publishing to the reading room, or before any secure delivery or publication.

The accessible edition. A redacted, scanned or untagged record cannot keep the tags a screen reader needs, so AccessPoint can build an accessible edition beside a response package that holds one. It reads the redacted pages (never the originals) and rebuilds each record as a tagged PDF with its text, headings, tables and figures in reading order, and every redaction announced where it sits (for example [Withheld — s.19(1) Personal information]). The package itself is never changed. By default the edition is built only when it will be used: at once when the request's accessible format is set, when the package is delivered through the portal or proposed for the reading room, or when you choose Build accessible edition in the report. The HTML, plain-text and Word editions are built when the request asks for them. Without Azure AI Document Intelligence no edition can be built. Settings → Redaction appearance → Accessible edition of response packages chooses when editions are built: When it is needed (the default), For every response package that needs one, or Off.

Figures need a person. When AI Assist is deployed and Figure description drafts is on, each figure arrives with a draft description; choose Use this description (edit it first if needed), Decorative or Draft again. A figure nobody described is announced as Figure not described. Choose Rebuild with these descriptions after describing figures. Once the edition is built, the accessibility check reads the edition, since that is what a requestor using assistive technology reads.

Delivering Through the Portal

With the public portal deployed, licensed and switched on (Settings → Public portal), Send release… on the Documents tab's Releases sub-tab delivers a release through the secure portal, and a Ready export in Export History also offers Deliver via secure portal. Give the delivery a title the requestor will see, the days until it expires and an optional per-file download limit. AccessPoint copies the package, and the accessible edition when there is one, into a delivery area the portal can reach and, when Defender for Storage is deployed, waits for the copies to be scanned clean before the delivery is Available. The requestor opens the link, verifies with an e-mailed code, downloads each file and may confirm receipt; the portal also states what the accessibility check found and how to ask for another format.

The Secure deliveries made to the requestor (status, created and expiry dates, downloads so far and the per-file limit, whether the requestor confirmed receipt) appear on this tab under the response, only once a delivery exists, with Copy link and Revoke. Revoking, or expiry, deletes the copied files and ends every download link at once. There is no separate Portal tab on a request.

Statutory Waiting Periods

Releasing a response package, delivering it on the portal, transferring or closing a case while a statutory window is open (for example a third party's 20 days to seek review) shows the window, the law and its end date. You can proceed; your confirmation is recorded in the audit ledger. See Follow-ups on a Case.

Recording the Response

Set the response method (for example email, mail or in person). It also decides how the fee prices copies (above).

Since 2.6.0 the response is sent through releases. Send release… on the Documents tab's Releases sub-tab records how and when each release went, and sending releases writes the request's First release sent and Final release sent dates and its response date — the date the on-time statistics read: the day the final release is sent, or the day the first release is sent where the request type's legal authority says so. A corrected or supplemental release moves none of them. Once a request has a built or sent release, its response date on this tab is read-only. Pages disclosed is the sum of the pages released by sent releases, unless someone entered the figure by hand. See Releases and Mark Package as Sent.

On a correction request, two more dates sit under the response: Statement of disagreement attached (when a correction was refused and the individual's statement went on the record) and Correction notices sent (when notice of the correction or the statement went to those the information had been disclosed to). Annual statistics reports count both.

The Case audit export section also lists the programs the request concerns.

Reviews and Approvals

If your workflow requires approval before the response can be sent:

  1. Add reviewers by clicking Add Reviewer and selecting the appropriate users.
  2. Each reviewer receives a notification and can review the response package.
  3. Reviewers approve or reject the response, with comments if needed.
  4. All reviewer decisions must be obtained before the request can be closed.

Closing the Request

Complete the Closure section: pick a closure reason — disclosed, disclosed in part, refused, transferred, and so on — add closure notes, and close. Choosing Transferred request reveals the receiving-institution fields and enforces the transfer deadline: an ATIA s.8 transfer is done here, not as a separate button.

The Close dialog runs a completeness check first — missing attestation, extensions without a reason, consultations without an outcome, redactions citing no exemption, unreviewed proposed redactions — shown as advisory findings, never a hard stop. Resolve them, or knowingly proceed.

When the last release was the final one. If the request's releases include no final release, the Close request dialog offers Mark Release n as the final release (the last release sent): tick it, say why, and the release is marked before the request closes, so the on-time statistics get their response date.

A closed request becomes read-only; reopen it from the banner if you must make further changes.

Case Audit Export

When you finalize a request, you can generate a court-ready case audit export (formerly called the "evidence package") — an export drawn from the tamper-evident audit ledger that documents how the request was handled.

Completeness Pre-Flight

Generating a case audit export runs the same completeness pre-flight as the Close dialog. Before the export is produced, it flags anything that looks unfinished so you can resolve it — or knowingly proceed:

  • Missing attestation.
  • Extensions recorded without a reason.
  • Consultations without a recorded outcome.
  • Redactions that cite no exemption.
  • Proposed redactions that were never reviewed.

AI Involvement Disclosure

When AI Assist is enabled, the case audit export also includes an ai-involvement.json file. This disclosure records exactly which AI features touched the request, how much, and what a person decided — giving you a defensible account of where AI was used and where human judgment applied.

The disclosure is built from usage metadata only. 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 the actual prompt and response content is never retained anywhere. Every AI output along the way was a suggestion or an editable draft that a person reviewed and decided on.

Case audit export completeness pre-flight