Request types — categories, default durations, date conventions, deadline provision, earlier rules, expedited processing, identity reuse and retention
Last updated: November 10, 2026 by Steve
Request Types
Request Types define the categories of requests your organization handles. Each type carries its own processing rules, deadlines, and retention settings.

Common Request Types
Typical request types include:
- Personal information requests
- Access to information requests
- Correction requests
- Continuation of access requests
These are usually imported via jurisdiction packs and customized afterward.
Configuring a Request Type
For each request type, configure the following:
Processing Deadline
- Standard duration — The number of days allowed to process a request of this type.
- Date calculation method — Choose between business days (excludes weekends and holidays) or calendar days.
- Deadline provision — The section of the law that sets the period (for example ATIA s.7). It is named in How this date was calculated on the request.
- Earlier rule — For a law that changed its period. Set Current period applies from a date, and give the earlier period and how it counts. Requests received before that day are counted under the earlier rule. The Ontario packs ship the earlier 30 calendar days of Bill 97 for requests received before 1 July 2026.
- The law provides expedited processing — On for US FOIA, which shows the request's Expedited processing card.
The organization's time zone decides which calendar day a request counts as received when its due date is calculated. A coordinator can correct a received date on an active request when the feature is switched on; the corrected due date is recalculated under the same rules.
Retention Settings
- Retention period (months) — How long a closed request of this type is kept before it becomes eligible for disposition. Leave blank to keep requests of this type indefinitely (the default — nothing ages out until you set a period), or enter a value of 1 or greater. Values below 1 are rejected. A closed request becomes eligible for disposition when this period has passed.
- Retention start point — the event the period is measured from: the closed date, or the response-sent date.
The same period/start-point pair exists on assessment, incident, and complaint types (and, for standalone risks, on risk categories), and all five feed the one Retention Review panel where administrators dispose of aged-out cases.
Legal
- Governing legal authority — the legal authority requests of this type are processed under.
- Requires identity verification — when enabled, a request of this type cannot be activated until the requestor's identity is confirmed.
- Pause clock until identity verified — available once identity verification is required. Turn it on and AccessPoint opens an identity-verification hold automatically the moment a request of this type is created, then releases it the instant identity is marked verified — the received date stays the statutory anchor, so days spent waiting on proof of identity never burn the deadline. This is the GDPR Article 12(6) / ICO "stop the clock" allowance; several jurisdiction packs pre-wire this setting with the correct statutory citation for their regime already selected. Clearing a verification later re-arms the hold.
- Identity hold extension reason — the extension reason cited on the automatic hold. Leave it unset and AccessPoint falls back to the pack-shipped
IDENTITY-HOLDreason.
Releases
- Hold releases until paid — off by default. When it is on, a release of a request of this type that carries an open instalment of the fee cannot be sent until the payment is recorded; each release can be switched on, off or back to the type's setting. Only a payment the payment provider confirmed (or one recorded by hand) counts. Someone who holds Waive fees can waive the instalment, and someone who holds Act as senior official can allow sending before payment, with a reason. California's public-records types switch it on. See Instalments and hold until paid.
Which sent release sets the response date is decided by the type's legal authority (Response date counts from — see Legal Authorities).
Reusing a recent identity verification
Below the list, Reusing a recent identity verification applies to every request type that requires identity verification. Switch on Offer one-click reuse and set the reuse window (1 to 730 days; 180 is proposed). It is off until you switch it on, jurisdiction packs never set it, and a change is recorded in the audit log.
Adding a Request Type
- Click Add Request Type.
- Enter the name and, if applicable, translations for each enabled language.
- Configure the deadline, date calculation, and retention settings.
- Click Save.
Editing and Removing
Existing request types can be edited at any time. Changes apply to new requests going forward. Removing a request type does not affect existing requests that were created with that type.