Home / How It Works
How It Works: One Records Request, Start to Fulfilled
A public records request is government document work at its most visible — a defined ask, a trail of records, and a resident waiting on the other side. This page follows one request through the loop: submitted, located, reviewed, fulfilled, and recorded.
Intake: the request is logged the moment it lands
At 10:12 a.m., a resident submits a records request through the portal — a MaxxLaunch™ form — asking for correspondence and permits relating to a specific property over the past two years. Arrival is intake: the request is timestamped, given an identity, and queued. Nothing waits in an inbox, and the response clock is visible from the start.
Because the request arrived as structured data — requester, subject property, date range, record types — fulfillment starts from facts, not from a paragraph someone has to re-read and retype into a tracking sheet.
Located & classified: the record set assembles itself
Next, MaxxOwl™ SI works the Outcome Repository™ with the request's terms and classifies what it finds: correspondence, issued permits, inspection reports, attachments. Each candidate record is identified for what it is, and its data — sender, dates, parcel, document type — is extracted and lined up against the request's terms.
Records outside the ask — a different parcel, a different period — fall away here. What remains is a working set organised by type and relevance, ready for staff, instead of a pile of files someone gathered by hand.
Review & redaction support: people decide, on the record
Staff review the working set in Outcome Workspace™, document and data side by side. Where reviewers determine that material in a record has to be withheld or redacted, the platform supports that work as document handling: passages are marked on a working copy, and every mark is tracked — what was marked, where, and by whom. The preserved original in the repository is never altered.
What the law requires in any given case is a decision for the agency and its advisors. The platform's part is narrower and mechanical: the review happens on the record, each decision is logged, and no document leaves the set unreviewed by accident.
Fulfillment: the response is assembled from the reviewed set
The response is built from exactly what was reviewed: the responsive records, redactions as the reviewers marked them, and the agency's reply. Delivery is recorded against the request — what was provided, in what form, and when — so the ask and its answer stay permanently linked.
If part of a request needs a judgement call along the way — an ambiguous record, an unusually large set — it surfaces as an exception in the same workspace rather than in a side conversation, and that decision joins the record too.
Outcome: the finish is recorded, not assumed
When the response goes out, the loop closes. The outcome — what got done with it — is written to the record: the request as submitted, the records located, the review decisions, the response as delivered, and how long each stage took. A later question about the same request, from the requester, from leadership, or from an auditor, is answered from that record.
That is also what Outcome Analytics™ reports on across every request: volumes by type, stage-by-stage turnaround, exception rates. The pattern of the work becomes visible because the loop kept its own evidence.
The other arrivals: applications and filings
A records request is one arrival. Permit applications, license filings, inspection reports, and board packets enter through the same doors — MaxxLaunch™ portals for structured submissions, MaxxOwl™ SI for documents that arrive as documents — and run through the same stages: checked, routed, worked, and recorded. Documents and data, one loop.
Same loop, every public document
Every document type public work runs on can be walked through the same five stages. The rules, reviews, and retention change from process to process; the loop doesn't. That consistency is what makes the outcomes comparable — and what makes a platform different from a pile of point tools.
← Back to the overview: intelligent document automation for government work
Put public documents through the loop
The stages above run on MaxxLogix — Outcome Cloud™, MaxxLaunch™, MaxxOwl™ SI, Outcome Workspace™, and the Outcome Repository™, with capacity published in SI Units and no surprise overages. See the government practice at maxxlogix.com.
MaxxLogix for Government