AccessPoint vs. GovQA

The short answer

GovQA, acquired by Granicus in 2021 and now sold as Records Request Management within the Granicus Operations Cloud, is an established US state-and-local platform for handling public-records request volume in the vendor's cloud. If your need is a public request portal and queue management, it's a credible incumbent. AccessPoint's difference is architectural and scoped: your records never leave your own Microsoft 365 tenant, collection happens where documents already live, and the same platform runs privacy impact assessments, breach notification, complaints, and risk — with flat published pricing.

What is GovQA (Granicus Records Request Management)?

GovQA was founded in Illinois and became one of the most widely used public-records request platforms in US state and local government — around 800 government customers at the time Granicus acquired it in August 2021, positioned around the era's exponential growth in records-request volume.

Under Granicus, the product has been folded into the Operations Cloud and renamed "Records Request Management (GovQA)," with a companion "Legal Suite" edition. Its center of gravity remains the US public-records workflow: public request portals, deadline tracking, deflection of duplicate requests, payment collection, and routing across departments.

It's a request machine — and that's the comparison point. The offices running records requests increasingly own privacy work too, and the records under review are among the most sensitive a government holds. AccessPoint's position is that both of those facts should shape the architecture: one platform for the whole mandate, running inside your own tenant rather than a vendor's cloud.

GovQA fact sheet

Product: Records Request Management (GovQA), part of Granicus Operations Cloud; Legal Suite edition available
Vendor lineage: GovQA (Illinois) → acquired by Granicus, August 2021
Deployment: Vendor-hosted cloud SaaS
Market: US state and local government public-records offices (~800 government customers at acquisition)
Status: Actively sold

Sources

GovQA and AccessPoint, side by side

	GovQA	AccessPoint
Scope	Public-records request management	Records requests plus PIAs, AIAs, breach response, complaints, and a privacy risk register
Where your data lives	Vendor's cloud	Your own Microsoft 365 and Azure tenant
Records collection	Documents uploaded into the vendor system	Pulled straight from SharePoint, OneDrive, Outlook, and Teams
Jurisdiction rules	US public-records focus; configured per implementation	106 jurisdiction packs — US states, Canadian federal/provincial, EU, UK, and more
Redaction	Within the vendor platform	Browser-native studio with statutory exemption tagging, fall-backs, and AI-proposed redactions
Audit trail	Application logging	Hash-chained, append-only ledger with court-ready case audit exports
Pricing	Enterprise SaaS; 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 GovQA fits

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

You're a high-volume US records office whose primary need is a public-facing portal with payment collection and queue deflection, and vendor-cloud residency is acceptable to your security team.
Your organization is already standardized on the Granicus Operations Cloud and wants requests handled inside that suite.
Records requests are your only mandate — no PIAs, breach program, or complaints handling to consolidate.

Where AccessPoint differs

Your records stay yours Responsive records are collected and reviewed inside your own Microsoft 365 tenant — not exported to a vendor cloud for processing. Your existing security stack governs everything.

More than the request queue Privacy impact assessments, breach notification with a live statutory calculator, complaints, and an ISO 31000 risk register run on the same platform and audit ledger as your requests.

Collection without re-uploading Search SharePoint, OneDrive, and Outlook and attach records straight to the request — including Teams chats, OneNote, and Copilot interaction history — instead of downloading and re-uploading into a portal.

Flat, public pricing Every tier is published, billed through the Microsoft marketplace, no per-user fees — and a 30-day free trial that runs in your own tenant, not a sales-controlled sandbox.

Migrating from GovQA to AccessPoint

Moving off GovQA — or consolidating a records queue and a privacy program into one system? AccessPoint imports historical caseloads from any export that reaches Excel.

Export your request history from GovQA's reporting to Excel — request registers, requester lists, and dates are enough to start.
Download AccessPoint's import template from Settings → Data import & export; your existing request numbers persist as legacy references.
Upload and validate — a per-row created / skipped / errors report runs before anything imports, and corrected files can be re-run safely.
Stage documents in the migration-staging container in your own Azure storage, listed on the Documents tab with optional hash verification.
Import in the background; records arrive historical, with no notifications, no recomputed deadlines, and Imported audit provenance.

Rehearse against a test tenant first — the Export tab produces the same workbook the importer accepts, so a trial migration validates cleanly.

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

Questions people ask about GovQA and AccessPoint

What is GovQA called now?

Granicus, which acquired GovQA in August 2021, now sells it as "Records Request Management (GovQA)" within its Operations Cloud, alongside a "Records Request Management Legal Suite (GovQA Legal)" edition. Most practitioners still call it GovQA.

How is AccessPoint different from GovQA?

GovQA manages public-records requests in the vendor's cloud. AccessPoint manages records requests plus the privacy side of the same office — privacy impact assessments, breach notification, complaints, and a risk register — and it runs natively inside your own Microsoft 365 tenant, collecting responsive records straight from SharePoint, Outlook, and Teams rather than having staff upload them into a portal. Pricing is flat and published rather than quoted.

Does AccessPoint have a public request portal like GovQA?

A requestor self-service portal — public intake with jurisdiction-aware forms, secure status tracking, and direct delivery of released packages through Microsoft Entra External ID — is on AccessPoint's public roadmap. Today, intake is handled by your team, including a New-from-email flow that turns an intake-mailbox message into a fully formed request in one step. If a public portal is your single highest requirement right now, check the roadmap page for current status.

We're a US office — does AccessPoint cover our state's public-records law?

AccessPoint ships jurisdiction packs for the federal FOIA and a growing set of US states — California, Texas, New York, Florida, Washington, and many others, 27 US public-records packs among 106 total — each preloading response deadlines, exemption catalogues, business-day calendars, and letter templates for that statute. The solutions section lists every covered jurisdiction.

Can we import our GovQA history into AccessPoint?

Yes. Export your request history to Excel, map it into AccessPoint's tenant-generated import template, and validate before anything imports. Old request numbers persist as legacy references, requester contacts import alongside their requests, and documents stage through your own Azure storage with optional hash verification. Imported records arrive historical — no notifications, no recomputed deadlines, full audit provenance.

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.