FOIA and Public Records
Axcess1 Colorado
FOIA and Public Records management, built around CORA
Built around your law — not around generic case management.
Audio and video redaction, by hand and with AI
Blur faces, plates, screens and text, mute or bleep what is said, and every copy checked before release. The officer decides.
Built around your law — not around generic case management
Many case-management products ask a public body to adapt its process to the software. Axcess1 is configured around the legislation, the procedures, the vocabulary and the reporting obligations of each jurisdiction. An organization chooses its Act once; every screen, deadline, letter and report then follows it.
Generic case management
The organization adapts to the software.
Axcess1
The software follows the legislation and the way government works.
Legislation supported
Colorado Open Records Act (C.R.S. § 24-72-200.1 et seq.)
| What the Act requires | As configured in Axcess1 |
|---|---|
| Who it applies to | "Public records" of the state, any agency, institution or political subdivision of the state (counties, cities, towns, school districts, special districts) and elected or appointed public officials (C.R.S. § 24-72-202(6)). |
| Time limit to respond | 3 working days (C.R.S. § 24-72-203(3)(b)). The due date is calculated when the request is entered, with the holidays of the jurisdiction. |
| Extensions | Up to 7 working days. The period may be extended by up to 7 working days if the custodian finds, and states in writing to the requester within the 3 days, that extenuating circumstances exist: a broadly stated request covering a large category of records, the agency's resources devoted to an impending deadline or peak demand, or the General Assembly in session. (C.R.S. § 24-72-203(3)(b)) |
| Third parties | The Act sets no formal notice; consultations are recorded and tracked on the request. |
| Transfer to another body | C.R.S. § 24-72-203(2)(b) (records not in the custodian's custody: the custodian says so in writing and, if known, who has them), within 3 days |
| Decision and reasons | The decision letter gives the reasons, the provision relied on and the right of review (C.R.S. § 24-72-204(4) (written statement of the grounds for denial on request)). |
| Fees | No application fee. Amounts in U.S. dollars (USD). Copies: not more than $0.25 per standard page, or actual cost for other formats; no fee for sending records by e-mail. Research and retrieval: no charge for the first hour; after that, up to the hourly rate set in § 24-72-205(6) (adjusted for inflation) if the custodian has published a written fee policy. A deposit for the estimated staff time may be required. |
| Review and complaints | the district court of the district where the record is found (order to show cause, C.R.S. § 24-72-204(5)) (C.R.S. § 24-72-204(5)) |
Loaded for this Act
- 35 provisions (exemptions, exceptions and exclusions) ready to cite on a redaction, each with its section number.
- Request types: Colorado Open Records Act request (C.R.S. § 24-72-203).
- Statutory steps on the timeline: Extenuating circumstances found and stated in writing within 3 working days, C.R.S. § 24-72-203(3)(b) (up to 7 additional working days); Deposit requested for the estimated research and retrieval time, C.R.S. § 24-72-205(6); Records not in the custodian's custody — requester told in writing and, if known, who holds them, C.R.S. § 24-72-203(2)(b); Written statement of the grounds for denial given on request, C.R.S. § 24-72-204(4); Requester's 14-day written notice of intent to apply to district court received; meeting or call to resolve the dispute, C.R.S. § 24-72-204(5)(a); Application to the district court for an order to show cause, C.R.S. § 24-72-204(5).
Checked against the published text on 2026-10-28. Colorado General Assembly, Office of Legislative Legal Services — Law Summary: Colorado Open Records Act (CORA), with the table of exceptions, exemptions and extensions · Colorado Revised Statutes 2024 — § 24-72-204, Allowance or denial of inspection (Justia copy of the official text) · Colorado Freedom of Information Coalition — Guide to Colorado's Open Records and Open Meetings Laws
Legislation-to-feature matrix
| Legislative requirement | Axcess1 support |
|---|---|
| Statutory deadline | 3 working days (C.R.S. § 24-72-203(3)(b)): calculated automatically for each request; overdue and upcoming requests on the dashboard. |
| Extensions and holds | Recorded as events that move the due date, each tied to its section of the Act. |
| Exemptions and exclusions | The provisions of CORA in the redaction editor, each with its section number. |
| Third parties and consultations | Notices, consultation packages and their due dates tracked on the request. |
| Fees | Fee notices and payments recorded on the request. |
| Reviews, appeals and complaints | Recorded on the request timeline with their dates and outcome. |
| Redaction | Done by the analyst in the built-in editor; optional AI suggestions that the analyst accepts or rejects. |
| Decision letters | Generated from templates for this Act, with the provisions cited. |
| Release | A release package built from the reviewed records; redactions are permanent in the released file. |
| Annual statistics | Annual access statistics for the period, with each figure traceable to its requests. |
| Audit trail | Every action on a request is recorded with the user and the time. |
From request to release
1Receive and validate
The request is entered with its type, requester and date received; a number is issued from your own numbering pattern.
2Calculate the deadline
The due date follows the Act: 3 working days (C.R.S. § 24-72-203(3)(b)). Holds and extensions move it and are recorded.
3Assign and search
The request is assigned to an officer; the units holding records are tasked and their answers tracked.
4Collect and review
Records are uploaded (PDF, Office files, scans with text recognition) and reviewed page by page.
5Apply the provisions and redact
The analyst marks a passage and picks the provision of this Act; the released copy shows the section relied on.
6Consult
Consultation packages are produced per party, with their due dates.
7Approve
The response goes to the approver's inbox for review and signature.
8Release
The release package and the decision letter are generated from the request.
9Report
Requests, processing times, decisions and provisions invoked are counted for the period you choose.
Agentic AI across the lifecycle
AI is switched off until your administrator turns it on, one capability at a time. AI assists. Authorized officials decide.
Intake agent
Proposes a new request from a message, the portal or a drop folder; an officer confirms it.
Document intelligence
Summarizes and classifies the records and finds the people and organizations named in them.
Responsiveness agent
Suggests which records answer the request.
Exemption assist
Proposes provisions of CORA with reasons; redaction candidates appear in the editor.
Consultation agent
Suggests who should be consulted and on which pages.
Quality assurance agent
Checks a package a second time before release.
Deadline watch
Lists the requests at risk of running late.
Copilot
Answers questions about a request, citing the records it used.
Audio and video, redacted and checked
Picture and sound together
Blur or black out part of the picture and mute or bleep what is said at the same moment, each redaction tied to the provision of your Act.
Faces, licence plates, screens and text
Found on the server that runs Axcess1 (yours, or ours in Canada), with no outside AI service, and followed as they move. An authorized official accepts or rejects every find.
Checked before release
Each redacted copy is compared with the original, box by box and passage by passage. A copy that fails is not released; the original is never changed.
Migration
Case history, requesters and documents are brought over from the system you use today, so you do not start from an empty database.
Deployment
Hosted by SoftSim in Canada, on your own private cloud or servers, or standalone on a PC or Mac.
Security
Each organization's records are separate, access is controlled by role and every action is recorded. Run on your own servers, your records never leave your premises.
See Axcess1 working with your own Act
A 30-minute demonstration, with your legislation and your workflow.
Jurisdictions
Find Axcess1 for your jurisdiction
Canada
United Kingdom
Ireland
France
Australia
New Zealand
Axcess1 supports configurable workflows designed around the applicable legislation. Government organizations remain responsible for legal interpretation and statutory decisions. Summaries of the legislation are paraphrases prepared from the published text; they are not legal advice.