Exemptions — configuring exemption and exclusion provisions for document redaction, the dates a request may cite each one, and settings that change on a date
Last updated: November 10, 2026 by Steve
Exemptions
Exemptions define the specific legislative provisions that can be applied to documents during review to justify redactions or withholding of information.

How Exemptions Work
Each exemption represents a specific section or subsection of legislation that authorizes withholding information. For example:
- s.13(1)(a) — Information obtained in confidence from a government of a foreign state (ATIA)
- s.19(1) — Personal information (ATIA)
- s.26 — Information to be published (PA)
Every exemption belongs to a Legal Authority, which identifies the legislation it comes from.
Managing Exemptions
- Add — Click Add Exemption, select the parent legal authority, enter the section reference and description (with translations), and save.
- Edit — Click on an existing exemption to modify it.
- Remove — Delete exemptions that are no longer needed.
An option can also carry the days a request may cite it — Available from and Available until, judged on the request's received date. The list shows For every request or the window. A mark that already cites an exemption keeps it. See Settings that change on a date below.
Code and Name
Every option in the list separates the Code from the Name. The code is the stable identifier that redactions, detection rules and jurisdiction packs refer to, so it can be edited only when you add the option and is read-only afterwards; renaming it would orphan everything that points at it. The name is the label people read and can be changed at any time, including in each language through the globe icon. Editing just the name and saving is enough; you do not need to open the language tabs.
Choosing from Long Lists
Exemptions carry a section reference and a long title, so wherever someone chooses one (the redaction panel, Redact…, Find & redact, grid review, filters, and the pickers in Settings) it opens as a wider, searchable list instead of a narrow drop-down.
- The field shows the code in bold and as much of the title as fits. Point at it, or tab to it, for the full text and explanation.
- Open the list with a click, Enter, Alt+Down, or just start typing; what you type goes into its search box.
- Search by section number (19, s19 and s. 19 all put s.19 first, then s.19(1)) or by any words of the title or explanation, in any order. Accents and capitals do not matter.
- Each option shows its code and full title, wrapped onto as many lines as it needs, with a short explanation under it. Up and Down move, Enter chooses, and Escape closes the list without changing anything.
- Pickers that apply an exemption list your three most recent exemptions under Recently used at the top, shared across the redaction panel (a media mark's card included), Redact…, Find & redact, parts and grid review.
- Where several can be chosen (alternate exemptions, exemption filters), Enter or a click adds or removes the highlighted option and the list stays open. Your choices appear as chips under the field, each with its own remove button.
On a phone or a narrow Teams pane the list fits the screen and wraps.
Jurisdiction Packs
Pre-configured libraries of exemptions are available for supported jurisdictions through jurisdiction packs. These include the exemption and exclusion provisions for the applicable legislation, ready to use immediately after import — a starting point built from public information about the legislation, not legal advice; your legal counsel validates and adjusts them.
Usage
During document review, reviewers select exemption codes to apply to specific pages or passages. The applied exemptions are tracked per document and summarized in reports, providing a complete record of the legal basis for all redactions.
Follow-up rules can also be limited to requests that cite particular exemptions, picked from these catalogues. An exemption deleted later matches nothing.
Settings That Change on a Date
When a law changes on a known day, the jurisdiction pack can carry the change ahead of time, and AccessPoint switches each setting by itself on that day — nothing needs re-applying then. Each one is judged on a request's received date, in your organization's time zone (Settings → Localization & formats; when none is set, the time zone the request was entered and its due date computed in). So everyone who opens a request sees the same rules for it, and a request received before the change stays under the former rules, as transition provisions usually require. Set your organization's time zone when a law in your jurisdiction changes on a date (see Localization & Formats).
| Setting | Where | What changes on the date |
|---|---|---|
| Exemptions | Settings → Exemptions → the catalogue → the option: Available from / Available until | A request is offered only the exemptions its received date allows — the former Act's for a request received before the change, the new Act's from that day — in the redaction workspace, Find & redact, bulk changes and the media mark card, and AI and pattern suggestions use the same list. An exemption already applied never changes: the mark keeps it, with its label and colour, and the filters still find it. If a received date is corrected across the change, the request keeps the exemptions it already cites; review them. |
| Extension reasons | Settings → Extension reasons → the reason: Available from / Available until | Add extension offers a request only the reasons its received date allows. An extension already taken never changes. |
| Fees | Settings → Requestor fee categories → the category → Fee change on a date | The day the amounts on the schedule take effect, and the amounts that applied before it (blank = the same as now). The estimate, the final fee and each release's instalment charge the amounts of the request's received date. |
| Mandatory assessments | Settings → Assessment types: Mandatory from | From that day, in your organization's time zone, the type is mandatory even when its Mandatory switch is off. |
Suggested redactions (Scan for suggestions) tag the exemption the request may cite: a suggestion pattern can name several exemption codes, and the first one the request is offered is used.
An example: Nova Scotia. The Nova Scotia pack (version 1.29) uses these settings for the Freedom of Information and Protection of Privacy Act (S.N.S. 2025, c. 13), in effect on 1 April 2027: the new Act's exemptions and extension grounds, three free search hours and a mandatory privacy impact assessment for requests and activities from that day, and the former Act's or MGA Part XX's rules for requests received before it. Applying the Nova Scotia pack in an organization that has never set a time zone and has only Nova Scotia packs sets the time zone to America/Halifax, so every due date, "today" and displayed due day follows Halifax days. As with every pack, this is a starting point built from public information about the legislation, not legal advice — your legal counsel validates and adjusts it.