English

Jurisdiction packs — importing and re-applying jurisdiction-specific configuration from the Realizer platform: 145 packs plus the Universal Baseline and Universal Learning, coach notes, settings that change on a date and release fees

Last updated: November 12, 2026 by Steve

Jurisdiction Packs

Jurisdiction Packs (formerly "Configuration Packs") are pre-built bundles of settings tailored to specific jurisdictions. They let you quickly set up AccessPoint with the correct request types, extension reasons, choice fields, exemption codes, letters and translations for your regulatory environment.

AccessPoint ships two universal packs — the Universal Baseline and, since 2.6.0, Universal Learning — plus 145 jurisdiction packs spanning Canadian access and health/privacy regimes, US federal and state public-records laws, and access and data-protection regimes across Europe, the UK, the Crown Dependencies and Gibraltar, Asia-Pacific, Africa, and Latin America. A tenant has both universal packs and installs the pack(s) matching its mandate — a general access-to-information pack, and (for health authorities or private-sector bodies) a sector-specific privacy pack. Browse the live list under Settings > Jurisdiction packs, or see the Solutions hub for the jurisdiction pages. Every US pack — federal FOIA, Privacy Act, HIPAA and FERPA, all fifty states, DC and the territories — carries Spanish alongside English.

A starting point, not legal advice. Packs are built from public information about the legislation and regulator guidance and provided as is. Your legal counsel validates and adjusts the content for your organization. The Jurisdiction packs panel says so, and applying a pack asks you to confirm that your organization will check its content before relying on it.

Jurisdiction Packs

Importing a Jurisdiction Pack

The first time anyone signs in to a new AccessPoint, it imports the Universal Baseline and then Universal Learning by itself, in the background, while a banner reads Setting up your workspace…. Then:

  1. Go to Settings > Jurisdiction packs.
  2. Browse the list of available packs. Each pack shows the jurisdiction and a summary of what it includes.
  3. Select a pack, choose the item types to import and the import mode, and tick the acknowledgement that your organization will check the pack's content before relying on it. Applying a pack is refused without that acknowledgement.
  4. Click Import and wait for the import to complete. The system will create all included items in bulk.

In Hosted AccessPoint, the jurisdiction pack is chosen when the organization is created, with the same acknowledgement, and imported with the two universal packs.

A pack can be applied only in your production tenant: in Lab mode the configuration is read-only, and the training copy takes your production configuration, packs included, at its next refresh.

Re-Applying Packs After an Upgrade

Re-applying a pack adds what is new and refreshes the pack items you have not edited. It never overwrites an item you edited, and an optional value the pack leaves empty never clears one of yours. A pack with a newer version shows it in the panel, and each pack's change notes list what changed.

Upgrading to 2.6.0.

  • Universal Learning arrives by itself on the first start after the upgrade. It takes over the practice cases and training paths that the Universal Baseline carried before, with the same identities, so nothing is created twice and your assignments, progress, completion records and certificates are kept. Your own choices on those rows (a module taken off Browse, a coach note switched off) are kept too.
  • Re-apply your jurisdiction packs to get the content that needs 2.6.0: release letters for requests answered in releases, coach notes where your pack ships them, and settings that change on a date.

Coming from a version before 2.5.0. Every jurisdiction pack had a new version in 2.5.0, and until a pack is re-applied, what it carries is missing: the privacy program has no rules, the follow-up, validation, survey and training notices are not sent, Lab mode has no training content, and regulators are named from their office text. Re-apply the Universal Baseline first (Settings > Jurisdiction packs, then the pack, then Add and update unchanged), then each jurisdiction pack you have installed.

Things to know:

  • New follow-up rules and storage policies arrive switched off. Preview each follow-up rule and switch on the ones you want, and check each recommended policy under Storage and archiving against your records schedule before you adopt it. Re-applying never switches one on and never changes one that is switched on or that you edited.
  • Re-applying tidies unused questionnaires. A questionnaire no assessment uses loses the questions and sections the pack no longer ships, so a reorganized questionnaire never lists a question twice. Questionnaires in use, and anything you added or edited, are never touched.
  • A letter you edited keeps your edit. If you edited a third-party decision letter, set its type to Third-party decision yourself.
  • Overwrite all (including customizations) restores the pack's version of everything, including your edits. Use it only on purpose.
  • Two packs that ship the same item. Some items are shared by two packs — for example the PIA add-on of Ontario's provincial and municipal packs. The first pack you import keeps the item, and the second pack does not write it again. When the two are identical, nothing is said; when they differ, the import notes say which one was kept. An item your organization wrote itself is always kept and flagged.
  • Shared deployments. When one AccessPoint deployment serves several Microsoft 365 organizations, each organization imports and edits its own packs, statuses and types; one organization's edit never changes another's.

Packs on an Older Version

Realizer serves one set of packs to every supported AccessPoint version, in the form each version can import. An organization still on 2.5 is not offered Universal Learning or AccessPoint Learning content, and receives the Universal Baseline with the practice cases and training paths 2.5 shipped with — with no release letter, Lab mode notice or scripted practice case it could not use.

If your organization on 2.5 took the earlier content — it started with no practice cases or training paths, or the release letters arrived with blanks — re-apply the Universal Baseline (Settings > Jurisdiction packs → Universal Baseline → Add and update unchanged) to get the practice cases and training paths, then switch off the four release letters — Interim release, Fee for a release, Corrected release and Supplemental release — under Settings > Correspondence templates (each template's Enabled switch). Upgrading to 2.6 needs none of this: Universal Learning takes the practice cases and paths over, and the letters fill in.

What Gets Imported

A jurisdiction pack typically includes:

  • Request types with standard processing deadlines and date calculation rules
  • Extension reasons with suggested durations
  • Closure reasons appropriate to the jurisdiction
  • Exemption and exclusion provisions linked to the applicable legislation
  • Legal authorities referenced by the exemptions, including which release sets a request's response date where the statute says (see Releases and Fees)
  • Business-day calendars with the jurisdiction's statutory holidays
  • Requestor fee categories with the jurisdiction's fees, including the rate for electronic copies
  • Complaint and appeal types with the regime's grounds, disposition, and allegation-finding vocabularies
  • Correspondence and notification templates carrying the statutory wording and citations, in the jurisdiction's languages — since 2.6.0 including the letters for interim, corrected and supplemental releases
  • Statutory annual/quarterly report templates where the statute mandates a defined return — 24 jurisdictions ship one (including the Canadian federal ATIA/Privacy Act returns, Ontario, Québec, B.C., Alberta, Saskatchewan and Newfoundland, US FOIA, Washington JLARC, UK FOI, Scotland, Ireland, Australia, New Zealand, and Switzerland); packs for jurisdictions with no mandated form deliberately ship none
  • Follow-up rules with the statutory windows of the law (a third party's review window, the requestor's appeal window), switched off until you preview and switch them on
  • Recommended storage policies for each request and complaint type, switched off, with the pack's reasoning
  • Breach-notification rules where the regime's privacy modules apply
  • Suggested-redaction detection rules — the personal-information detectors that feed the proposed-redaction pipeline, with the jurisdiction's exemption citations wired on (see below)
  • Training content — Lab mode practice cases and learning paths, and, where the jurisdiction has them, coach notes, glossary terms and training obligations for AccessPoint Learning (see Coach Notes and Learning Content)
  • Choice field values for dropdowns throughout the system
  • Translations for all imported items in the supported languages
  • AI grounding (optional) — a jurisdiction playbook of process guidance, and per-item AI guidance text (see below), used only when AI Assist is deployed

The Universal Baseline pack supplies the jurisdiction-neutral foundation underneath — including the Privacy Officer role, the privacy program's rules, the audit types and questionnaires, the follow-up content: kind-neutral workflow statuses, generic incident choice-field values (harm/cause vocab is not law-specific), saved-view presets, default numbering, template skeletons — including the direct-to-institution complaint lane (a generic direct-complaint type with acknowledgement/response clock policy and its acknowledgement, response, and recommendation-response letters in all 11 languages) — and the core personal-information detection rules described below.

The Universal Learning pack (2.6.0) carries AccessPoint Learning's jurisdiction-neutral content, in all eleven languages: learning modules and learning paths for every jurisdiction (among them the request basics and the PIA course), glossary terms and training obligations, jurisdiction-neutral coach notes, the Lab mode practice cases on assessments, incidents, complaints, risks and the privacy program, a team exercise, a finished PIA worked example, and the role paths for new staff. It always imports after the Universal Baseline, because its cases name the baseline's types and templates. Request practice cases ship in the jurisdiction packs. Jurisdiction packs layer the regime-specific vocabulary and statutory content on top of both universal packs.

Crown Dependencies and Gibraltar

Four packs (2.6.0) cover the information-rights regimes of the Crown Dependencies and Gibraltar, each in English:

Pack What it covers
Jersey — FOI & Data Protection (je-foi-dp) The Freedom of Information (Jersey) Law 2011 for scheduled public authorities and the Data Protection (Jersey) Law 2018 with the Data Protection Authority (Jersey) Law 2018: requests, exemptions, the fee limits, internal review and appeals, subject access, breach notification and DPIAs
Bailiwick of Guernsey — Data Protection & Freedom of Information Code (gg-dp-access) The Data Protection (Bailiwick of Guernsey) Law, 2017 — subject access, exemptions, breach notification, DPIAs and complaints to the Authority — and the States of Guernsey Freedom of Information Code, with its complaint and appeals route
Isle of Man — FOI & Data Protection (im-foi-dp) The Freedom of Information Act 2015 and the applied GDPR under the Data Protection Act 2018, all overseen by the Isle of Man Information Commissioner
Gibraltar — Data Protection & Access to Information (gi-dp-access) Gibraltar GDPR and the Data Protection Act 2004, the Freedom of Information Act 2018 and the environmental information regulations, under the Gibraltar Regulatory Authority as Information Commissioner

Each carries its statute spine, deadlines and calendars, exemptions, fee rules where the law sets them, and the follow-up rules for its review and appeal windows. As with every pack, your legal counsel validates and adjusts the content before you rely on it.

Coach Notes and Learning Content

AccessPoint Learning's How we decide coach sits beside the decisions people make on a case — the scope of a request, an extension, an exemption, a fee, a consultation, closing, and the key decisions on assessments, breaches and complaints. Packs can ship coach notes: the plain-language rule for a decision, shown when the case matches what the note is about (a request type, an extension reason or an exemption, for example), with a link to the module that teaches it.

  • Universal Learning ships jurisdiction-neutral notes for every jurisdiction. Some jurisdiction packs add their own — the Canada federal pack, for example, ships notes in English and French on its extension reasons, main exemptions, fees and consultation regimes, each linking to the Act's section.
  • Notes from packs are listed apart, under From your jurisdiction packs (read-only). Someone who manages training can switch a pack's note off and on, and re-applying the pack with Add and update unchanged keeps that choice. Your organization's own coach notes sit beside them.
  • Packs also bring learning paths, glossary terms and training obligations. Pack learning paths are read-only; you can assign them to a person or a team, or — with the AccessPoint Learning module — give them an audience rule. Writing your own modules, checks and certificates also needs that module.

Like the rest of a pack, coach notes are general information, not legal advice; review them before you switch them on for your staff. See Learning paths and Lab mode.

Settings That Change on a Date

When a law changes on a known day, a pack can carry the change ahead of time, and AccessPoint switches each setting by itself on that day — nothing needs re-applying then. Each setting is judged on a request's received date, in your organization's time zone, so a request received before the change stays under the former rules, as transition provisions usually require:

  • Exemptions can be Available from and Available until a date (Settings > Exemptions). A request is offered only the exemptions its received date allows; an exemption already applied never changes.
  • Extension reasons can be Available from and Available until a date (Settings > Extension reasons). An extension already taken never changes.
  • Fees can carry a Fee change on a date (Settings > Requestor fee categories): the day the amounts take effect, and the amounts that applied before it. The estimate, the final fee and each release's instalment charge the amounts of the request's received date.
  • Mandatory assessments — an assessment type can be Mandatory from a date (Settings > Assessment types).

Nova Scotia's new Act. Nova Scotia's 2025 Freedom of Information and Protection of Privacy Act replaces FOIPOP 1993 and Part XX of the Municipal Government Act on 1 April 2027. The Nova Scotia pack switches each of its changes on by itself that day, by the request's received date: business-day periods, the new exemptions, three free hours, mandatory privacy assessments and breach notification. The regulations under the Act (fee amounts and privacy-assessment requirements, among others) had not been published when the pack was written; watch the pack's change notes for the update once they are. Set your organization's time zone in Settings > Localization & formats — the Nova Scotia pack sets America/Halifax for you when no time zone was ever chosen and only Nova Scotia's packs are installed.

Releases and Fees

Since 2.6.0 a request can be answered in numbered releases, and packs set the release and fee rules their statutes call for. Each setting can be changed in Settings after import:

  • Fees for electronic copies (Settings > Requestor fee categories > Electronic copies) — Charged like paper copies (the default), Free or Their own rate per page. The request's estimate and final fee and each release's instalment read it; how the copies go comes from the request's response method (e-mail and portal are electronic copies, mail is paper, in person is inspection, which is never charged per page). California's pack makes electronic copies free.
  • Free search hours can be part of an hour (in quarter-hour steps) — for example Vermont's half hour and Utah's quarter hour.
  • Search fees in the statute's own unit — a statute that sets its search rate per 15 minutes, per half hour or per minute ships that unit and that rate, never an hourly equivalent, and part of a unit is charged as a whole one. Ontario MFIPPA's $7.50 per 15 minutes makes an hour and a half of search $45. Alberta, the Northwest Territories, Nunavut and Ontario's packs charge per 15 minutes; Manitoba, Nova Scotia, Saskatchewan and New Zealand's per half hour; Vermont's per minute; and Yukon's $30 per hour or part of an hour.
  • Holding a release until paid (Settings > Request types > Hold releases until paid) — off by default. A held release with an open fee instalment cannot be sent until the payment is recorded; a coordinator can waive the instalment, or a senior official can allow sending before payment with a reason. California's public-records types switch it on, because the statute conditions copies on the fee; other packs leave it off.
  • Which release is the response (Settings > Legal authorities > Response date counts from) — The final release (the default) or The first release, for the on-time statistics. California's pack counts from the first release.

Suggested-Redaction Citations

Importing a jurisdiction pack also wires up your suggested-redaction rules. AccessPoint ships a set of universal personal-information detection patterns (phone numbers, email addresses, SIN/SSN, payment cards, postal codes, and dates of birth) in the Universal Baseline pack. When you import your jurisdiction's pack after the Universal Baseline, those core patterns are automatically wired to that jurisdiction's personal-information exemption.

Jurisdiction packs also add detectors for their own region: the US packs carry nine US personal-information rules, and the Canadian, UK (including Scotland's), Australian and New Zealand packs add street-address and vehicle-plate rules, as do the US packs for plates. A rule several packs share exists once, however many of those packs you import. A plate is found two ways: after a label that names it, which is on, and by its shape alone, which is off except for the current GB format because it runs over documents too and could flag look-alike text.

The result: accepted suggested redactions arrive pre-tagged with the correct provision out of the box, with no manual mapping. A few notes:

  • The Universal Baseline is in place before you import your jurisdiction pack, so the wiring is applied when the jurisdiction pack is imported (if the order was ever reversed, it simply applies on re-import).
  • Any exemption citation an Administrator has set or changed on a rule is preserved; pack imports never overwrite your edits.
  • A few jurisdictions are intentionally left unwired where a single personal-information exemption doesn't map cleanly; you can set the citation manually under Settings > Redaction Appearance > Suggestion patterns. See Redaction Appearance.

AI Grounding Seeded by Packs (Optional)

When the optional AI Assist component is deployed, packs can also seed the model-facing text that keeps AI answers grounded in your regime. None of this is used unless AI Assist is enabled, and it is English-only.

  • Jurisdiction playbook — process guidance ("how do we handle a transfer," "who signs off on an extension") scoped to a legal authority. The case assistant reads these entries to answer how-to questions in your jurisdiction's terms. Edit or add your own under Settings > Jurisdiction playbook — a pack re-import never overwrites an entry you've changed. See Jurisdiction Playbook.
  • Per-item AI guidance — many pack items also carry an optional plain-language AI guidance field, separate from the human-facing description: exemption detection guidance (feeding redaction suggestions and automatic exemption tagging), "how this type is worked" notes on request/complaint/incident/assessment types, when-it-applies notes on extension reasons and consultation regimes, tag meanings for document auto-tagging, and eligibility/fee cues on requestor categories.

Because it is inert without AI Assist, importing packs is safe whether or not you use the AI features.

After Import

Review and customize the imported items to match your organization's specific needs. All imported settings can be edited, renamed, or removed through their respective settings screens.

Jurisdiction packs are a starting point built from public information about the legislation, not legal advice — your legal counsel validates and adjusts them, and your organization may need to add items or adjust defaults after import. Statistical reports and the privacy program section carry the same caution for the figures and statuses AccessPoint computes from pack rules.