AccessPoint vs. AMANDA FOI Module | Comparison & Migration Guide

The short answer

AMANDA (now sold by Granicus as Permitting, Compliance & Licensing) is a broad government case-management platform whose FOI capability arrived as one module in 2019, decades into the product's life. It's a reasonable answer when FOI is a side-workload on a platform you already run for permitting. It's the wrong shape when access and privacy is the mandate: AccessPoint is purpose-built for that work — statutory deadline math, exemption-tagged redaction, PIAs, breach response, complaints, and a court-ready audit ledger — and it runs inside your own Microsoft 365 tenant rather than as another enterprise platform to operate.

What is AMANDA (Granicus Permitting, Compliance & Licensing)?

AMANDA began life at CSDC Systems, a Canadian company founded in the late 1980s, and became one of the most widely deployed government regulatory platforms in North America — permitting, licensing, inspections, and compliance case management for state, provincial, and municipal governments. CSDC rebranded as Calytera in 2019 and was acquired by Granicus in 2020, which now markets the product as "Permitting, Compliance & Licensing (AMANDA)."

FOI is a comparatively recent addition: CSDC launched the "Amanda Freedom of Information Solution" in June 2019, and Granicus's product page today lists an Access to Information and Privacy (ATIP) / Freedom of Information (FOI) module covering request intake, document management, review and redaction, and legislated reports. Real FOI deployments exist — Nova Scotia ran a province-wide FOI case-management system built on AMANDA 7 from 2016, and the City of Toronto moved its FOI processing onto AMANDA when AccessPro support ended.

That history also carries a caution about running statutory FOI on a generalist platform: Nova Scotia's AMANDA-based public FOI portal suffered a widely reported breach in 2018 that exposed roughly 7,000 documents and took the portal offline for 152 days, and a 2016 provincial Auditor General report had earlier flagged configuration gaps against the province's IT security standards. That's dated history under a prior owner — but it's a fair prompt for the question every FOI office should ask of any platform: was this built, hardened, and audited for this exact work?

AMANDA fact sheet

Product: AMANDA — sold by Granicus as "Permitting, Compliance & Licensing"; FOI/ATIP is one module
Vendor lineage: CSDC Systems (~1989) → Calytera (2019) → Granicus (2020)
FOI module: Launched June 2019; intake, document management, review/redaction, legislated reports
Deployment: Vendor-hosted cloud or on-site installation
Market: State, provincial, and municipal regulatory agencies — primarily permitting and licensing
Status: Actively sold

Sources

AMANDA and AccessPoint, side by side

	AMANDA	AccessPoint
What it's built for	Permitting, licensing, and compliance — FOI is one module of ~50 functions	Purpose-built for public-sector access, privacy, and responsible AI
Privacy program (PIA, AIA, breach, complaints, risk)	Not the product's focus	Integrated — same platform, same audit ledger
Where your data lives	Vendor-hosted cloud or your own servers	Your own Microsoft 365 and Azure tenant
Records collection	Documents brought into the platform	Pulled straight from SharePoint, OneDrive, Outlook, and Teams
Statutory deadline engine	Configured per implementation	Computed from jurisdiction packs — business-day calendars, holds, extensions, deemed refusal
Redaction	Review and redaction within the FOI module	Browser-native studio with statutory exemption tagging, fall-backs, and AI-proposed redactions
Implementation shape	Enterprise platform implementation, typically with configuration services	Deploys into your existing tenant in an afternoon; jurisdiction pack seeds the rules
Pricing	Enterprise licensing; quotes	Flat annual, published on the site, no per-user fees

Competitor capabilities vary by product edition and configuration; this table reflects each product's public positioning as of August 2026.

Where AMANDA fits

A fair comparison cuts both ways — AMANDA is a reasonable choice when:

Your organization already runs AMANDA for permitting and licensing, the FOI workload is small, and one-vendor consolidation genuinely outweighs purpose-built capability.
FOI intake is handled by the same back-office team that lives in AMANDA all day, and your privacy program is managed elsewhere.
You need deep permitting/licensing case management first and FOI second — that's the problem AMANDA was actually built to solve.

Where AccessPoint differs

Purpose-built beats bolted-on Statutory deadline math, exemption-tagged redaction, requestor PII firewalls, digital attestations — the hard parts of access work are AccessPoint's core, not a module added to a permitting system.

No new enterprise platform to run AMANDA is a serious implementation with its own operational footprint. AccessPoint deploys into the Microsoft 365 and Azure tenant you already operate, governed by the security tooling you already have.

The whole privacy mandate PIAs, AIAs, breach notification with a live statutory calculator, complaints, and an ISO 31000 risk register — the other half of the office's work that a permitting platform doesn't carry.

106 jurisdictions out of the box Jurisdiction packs preload deadlines, exemptions, calendars, letters, and statutory report templates — configuration that on a generalist platform becomes a services engagement.

Migrating from AMANDA to AccessPoint

Whether you're on AMANDA's FOI module or weighing a move before committing your FOI history to it, AccessPoint imports historical caseloads without an ETL project.

Export your FOI cases from AMANDA to Excel — any built-in report that reaches a spreadsheet is enough.
Download AccessPoint's import template from Settings → Data import & export; it carries your tenant's own request types, stages, and codes, and your AMANDA case numbers ride along as legacy references.
Upload and read the per-row validation report — created, skipped, errors — before anything imports; fix and re-upload safely as many times as needed.
Stage legacy documents in the migration-staging container in your own Azure storage and list them on the workbook's Documents tab, with optional hash verification.
Import in the background. Records arrive historical — no notifications, no recomputed deadlines, and full Imported provenance in the audit trail.

FOI is often only one AMANDA module in use — migrating it to AccessPoint doesn't disturb your permitting and licensing operations, which stay where they are.

Plan your migration → · Data Import & Export guide · Migration & onboarding services

Questions people ask about AMANDA and AccessPoint

Does AMANDA handle FOI requests?

Yes — Granicus's AMANDA platform includes an Access to Information and Privacy (ATIP) / Freedom of Information (FOI) module, launched in 2019, covering request intake, document management, review and redaction, and legislated reporting. The comparison question isn't whether it can log a request; it's whether a module on a permitting platform matches a system purpose-built for statutory access and privacy work.

We already run AMANDA for permitting. Why would we buy a separate FOI system?

For the same reason your finance team doesn't run payroll in the permitting system: the hard parts are domain-specific. Statutory business-day deadline math, exemption-tagged redaction that survives a commissioner's review, PII firewalls between custodians and requestor identity, privacy impact assessments, and breach-notification calculators are deep, legislated capabilities. AccessPoint adds no new infrastructure — it runs in the Microsoft 365 tenant you already have — so the integration cost of 'separate' is far smaller than it used to be.

Is AccessPoint harder to stand up than an AMANDA module?

It's usually far easier. Enabling new AMANDA capability is typically an enterprise implementation with configuration services. AccessPoint deploys from a Bicep template into your own tenant's Azure subscription and installs into SharePoint from AppSource — often within an afternoon — and a jurisdiction pack seeds your statute's deadlines, exemptions, and letters.

Can we migrate FOI history out of AMANDA into AccessPoint?

Yes. Export your cases to Excel from AMANDA's reporting, map them into AccessPoint's tenant-generated import template, and validate before anything imports. Old case numbers persist as legacy references, documents stage through your own Azure storage with optional hash verification, and imported records arrive with no notifications, no recomputed deadlines, and full audit provenance.

What happened with Nova Scotia's AMANDA-based FOI portal?

Nova Scotia launched a province-wide FOI case-management solution built on AMANDA 7 in 2016. In 2018, its public FOI portal suffered a widely reported breach that exposed roughly 7,000 documents and kept the portal offline for 152 days; a 2016 Auditor General report had earlier flagged configuration gaps against provincial IT security standards. That's dated history under a prior owner (CSDC), and today's product is Granicus's responsibility — but it's a fair reminder to ask any FOI vendor exactly where your data lives and who has hardened it. AccessPoint's answer is structural: everything stays in your own Microsoft 365 and Azure tenant, governed by your own security stack.

Competitor information on this page is drawn from public sources — vendor websites, government reports, and press coverage — and was last reviewed in August 2026. Products evolve, and a comparison is never the whole story: capabilities vary by edition and configuration. Spot something out of date? Tell us and we'll correct it.

AccessPoint vs. AMANDA's FOI module