ATIP coordinators
Work a request end to end
Open a live request, redact a record under the Act's own exemptions, and send the decision — guided step by step.
Work a request (opens the demo in a new tab)Solutions · By organization
Canada's Access to Information Act and Privacy Act on the federal 30-day clock with the Algorithmic Impact Assessments the TBS Directive makes mandatory; the United Kingdom's FOIA 2000 and EIR 2004 requests beside subject access under the UK GDPR — multilingual, audit-ready, and never leaving your Microsoft 365 environment.
For a national or central government department, AccessPoint runs the whole information-rights mandate in one place. In Canada, that means Access to Information Act and Privacy Act requests on the federal 30-day clock with section 9 extensions and the federal exemption catalogue, plus the Algorithmic Impact Assessments the Treasury Board Directive on Automated Decision-Making requires before an automated decision system goes into production. In the United Kingdom, it means Freedom of Information Act 2000 requests on the 20-working-day clock, Environmental Information Regulations 2004 requests routed under their own rules, and subject access requests under the UK GDPR and Data Protection Act 2018. Either way it deploys inside your department's own Microsoft 365 and Azure tenant, ships multilingual, and carries a flat published price billed through the Microsoft commercial marketplace.
The Canadian federal thread is the most developed, because the timing forced it: AccessPro Case Management was declared a Government of Canada legacy application effective June 2023, and departments migrating off it face a real decision — move to another vendor-cloud request tracker, or move the whole mandate into a system the department controls. The same ATIP office that answers requests also runs Privacy Act obligations, privacy breaches, Info Source descriptions of the department's holdings, and now AI governance; software that only logs requests leaves most of that in spreadsheets.
The UK story rhymes. A departmental information-rights team routinely holds FOIA 2000 requests, EIR 2004 requests, and subject access requests in the same queue, answering to the same Information Commissioner — and the three regimes diverge on almost everything that matters: 20 working days under section 10 against one calendar month under Article 12(3), a section 12 appropriate limit of £600 for central government against no cost limit at all under the EIR, absolute and qualified exemptions against a statutory presumption in favour of disclosure. Behind both threads sits the same structural bet: national government records should be processed where they already live. Responsive records sit in departmental SharePoint, Outlook, and Teams; AccessPoint collects them there instead of exporting them to a third-party cloud, custodians close their searches with legally-defensible digital attestations, and every action lands on a hash-chained audit ledger a commissioner can be shown without reconstruction.
Three realities every departmental access office is operating under.
Oversight doesn't just review files — it publishes league tables. The Information Commissioner's report cards grade deemed-refusal rates institution by institution, and the ICO names authorities under monitoring. A slow quarter across a few hundred files becomes coverage the deputy head answers for.
One file touches three other departments, and each consultation leaves your requester's clock running while another institution's queue decides your fate. The extension gets taken, the follow-ups multiply — and the deemed refusal, when it comes, lands on your statistics, not theirs.
Year-end arrives and the statistical report is assembled backwards — exemptions re-coded from closed files, timelines reconstructed from a tracker that never captured them, disposition categories argued over in a spreadsheet. Weeks of analyst time go to describing last year instead of working this one.
Whatever system your department selects — including if it isn't AccessPoint — these are the capabilities a central institution should insist on before signing.
Pre-configured by jurisdiction pack — Canada federal, the United Kingdom, and 70 more — and running entirely on your own Microsoft 365 and Azure footprint.
Two regimes, one configuration: the 30-day clock, section 9 extensions, the federal exemption and exclusion catalogue colour-coded for redaction, and a request flagged as overdue the day a deadline lapses. Records held in GCdocs are captured straight onto the request through the GCdocs connector.
The GCdocs connector →The 20-working-day FOIA section 10 clock with the Part II exemptions and the section 2 public-interest test; EIR requests routed separately on 20 working days extendable to 40, with regulation 12(2)'s presumption in favour of disclosure; the section 12 appropriate limit at £600 for central government; and subject access on the UK GDPR's one-calendar-month clock. Fee schedules arrive quoted in £, not converted from someone else's currency.
The work a national institution has that a municipality doesn't. Parliamentary questions run as a purpose-configured request type with their own intake, clocks, and reporting — the Canadian pack ships this as the Order Paper question type, and the equivalent can be configured for another parliament's process.
Run the AIA the TBS Directive requires — impact scoring and tiering, sections delegated to subject-matter experts, review sign-off, and a published, audit-trailed result — on the same engine as your PIAs.
Custodians certify their searches and production with legally-defensible digital attestations captured against the record and backed by the audit ledger — the evidence a commissioner review actually asks for.
Federal timeliness brackets and statutory statistical-report templates come preloaded, so annual reporting to TBS and Parliament is generated from the system of record — plus Report Studio for the operational reporting leadership asks for that the statute doesn't.
The interface ships natively in 11 languages, with English and French out of the box for Official Languages obligations, and is built to meet public-sector accessibility standards (WCAG). Case content can additionally be translated per record, with the original always one click away.
The AccessPro migration
AccessPro Case Management was declared a Government of Canada legacy application effective June 2023, and departments are selecting successors now. If you're outside Canada the designation won't apply to you — but the mechanism will, because leaving any legacy request tracker raises the same question. AccessPoint treats migration as a workbook exercise, not an ETL project, and it works in the other direction too, so you are never locked in.
Interactive demo
The real screens on a fictional caseload under the federal Access to Information Act and Privacy Act. No sign-up, nothing saved.
ATIP coordinators
Open a live request, redact a record under the Act's own exemptions, and send the decision — guided step by step.
Work a request (opens the demo in a new tab)Privacy assessments
Answer a section of your jurisdiction's own PIA template, draw the data flow, score a risk and send it for sign-off.
Start a PIA (opens the demo in a new tab)Records search
Send a records search to a program area. The custodian gets clear instructions and never sees who asked.
Send a records search (opens the demo in a new tab)Rather look around on your own? Open the full demo — requests, releases, assessments, breaches, complaints, risks, audits and reports, in 11 languages. Or book a live walkthrough on your own records.
Two editions, every price published. Hosted AccessPoint by the month or year, or one flat annual rate in your own Microsoft 365 tenant. Unlimited users either way, with no per-user fees.
Try AccessPoint free for 30 days, pre-configured for your national regime. No credit card required.
Prefer your own Microsoft 365 tenant? Deploy it there →