The request was reasonable. The answer took four months.
Agencies, municipalities and public bodies. Transparency requests, procurement files and public records all have statutory clocks, and all of them are answered by people with three other jobs.
Requests, records and files answering to a statutory clock.
The record usually exists. It exists in a format nobody can search, held by a unit with no spare capacity, while a statutory clock runs regardless. Our core employees log every request against its deadline, find the unit that holds the file, and name the fields that need redacting — so the answer is a redacted document delivered in time rather than a refusal. Officials decide, classify and authorise, and every access is logged.
What arrives, and how
Citizen enquiries in either language, internal files, scanned records and procurement documents.
What we do with it
Log against the statutory clock, locate the holding unit, name what needs redaction, and hold it for a decision.
What never leaves your people
Deciding a request, classifying a document, authorising a payment.
The transparency request log · Q2, exactly as Sara filed it.
Every line carries the check that produced it, and anything held stays visible with its reason attached. Structure and logic from a live deployment; values changed.
ConsoleFileEditViewWindowTue 24 Jun 15:38«El expediente existe pero tiene datos personales de terceros, ¿lo mandamos completo o no mandamos nada?»
Neither. Sara flags the file as requiring redaction under the privacy framework, names which fields, and holds it for the transparency unit to decide — so the answer is a redacted document delivered inside the clock rather than a refusal.
Inside your case and document systems — not beside them.
Units keep working in the systems they already have. Data stays in the region you nominate, permissions are scoped per unit, and every access is logged — the deployment was reviewed by the entity’s own security team before go-live.
Connected on the systems you already run
Built against the rules you’re audited on
Your checklist is the source of truth, not ours. When a rule moves and the checklist doesn’t, your compliance lead gets told.
Four of our core employees, specialized on your entity.
Each one arrives generic and is taught your sites, your rules and your checklist over roughly three months. Scope and permissions are set per system, by you.
Logs and tracks every request against its statutory clock, locates the holding unit, flags what needs redaction and holds it for a decision.
Their page →
First response to citizens in either language — procedural questions answered, requests logged properly rather than lost.
Their page →
Budget execution and procurement payments reconciled against the file, with the discrepancy surfaced before the audit.
Their page →
Personnel records, mandatory training and declarations tracked to expiry across units.
Their page →Most of it happens against a statutory clock.
One Tuesday from a live deployment, reconstructed from the audit log. Times are local.
Sara reviews the request log and escalates one file with two days left on its clock.
Alex answers 26 citizen enquiries, 22 of them procedural, and logs four as formal requests.
Sara flags a file for third-party redaction and names the fields before release.
Memo reconciles Q1 budget execution and finds two payments without a matching file entry.
Maya flags 14 mandatory declarations outstanding across three units.
Alex answers a procedural question about a permit at the hour the citizen asked it.
An estimate you can check, not a quote.
Every assumption is written underneath. If one of them is wrong for your operation, the number is wrong — tell us and we’ll run it on your real volumes during the diagnostic.
How many requests and records does the entity process in a month?
Tell us where the
work piles up.
Send us the process that keeps your team late and we'll come back with a concrete read on what an AI employee would take off their hands — not a generic deck.
- A real person reads every message. No chatbot, no ticket queue.
- We reply within one business day, in Spanish or English.
- The first conversation is a 30-minute operational diagnosis. No commitment.
A government entity, under NDA.
Company name withheld under NDA. Numbers verified by their own internal audit six months after go-live.
Transparency requests were tracked on a spreadsheet and answered in an average of four months, sometimes past the statutory period. Procurement files were assembled when the audit asked for them.
Sara logs every request against its clock, locates the holding unit and flags what needs redaction; Alex answers the procedural questions that consumed most of the capacity. The entity cleared its external audit with no documentation findings.
Two weeks inside your unit, on your real request log.
Someone from our forward-deployment team works your transparency queue by hand, maps where the statutory clock is actually lost, and shows you exactly where this fits. Security review first, no commitment either way.