Starts the clock on the request nobody recognised as one
Public bodies miss information-request deadlines for one reason far more often than any other: nobody recognised the request. It arrives worded as a complaint or buried in a longer letter, so it is never logged — and the statutory clock starts regardless. By the time someone finds it, the only options left are a late response or an appeal.
This agent reads incoming correspondence for requests, whatever they are called and however they are worded, and reports when each clock started and when it runs out. It separates the parts that can be answered from the parts that need a decision, and drafts the answerable ones from the material you hold.
What it will not do is decide to withhold anything. Applying an exemption is a challengeable decision that a named person must own, so the agent identifies which parts appear to engage one, names the exemption, and hands it over. It also flags personal data that would need removing before anything is released — the failure that turns a routine response into a breach.
The commonest cause of an upheld complaint.
Instead of waiting behind the one contested paragraph.
What was identified, when, and what was referred to whom.
A request worded as a complaint is still a request, and the clock starts whether anyone logged it or not.
When it started, when it expires, and which requests are closest — from your own policy's rules.
Most requests are partly routine. Those parts should not wait on the part that needs a decision.
Withholding is a challengeable decision a named person must own. It identifies and routes; it does not decide.
Third-party data in a response is how a routine answer becomes a breach.
It drafts and tracks. Responses go out under a person's name, by their hand.
Why Government & Public Sector in particular. The deadline is missed because the request was worded as a complaint and never recognised. The clock started anyway, and by the time it surfaces the only options left are a late response or an appeal.
Runs unattended
Started by you or by an event, and it finishes on its own. Nothing waits for someone to be at a desk.
The same standard every time
The two-hundredth item is held to the bar the first one was. Consistency is the part people cannot sustain.
It cannot act on its own
Records Request Agent has no path to sending, spending or committing. That limit is why its output is safe to act on.
This agent runs server-side through the PROMIVO runtime. Each run is logged step by step and every tool call is permission-checked before it executes.
Read-only by design. This agent has no path to sending, spending, publishing or committing anything. Where that limit is the product, removing it would remove the reason to trust the output.
Demo dataIllustrative sample output, abridged.
{
"asAtDate": "2026-09-02",
"correspondence": [],
"warningWindowDays": 5
}{
"overdue": [],
"escalate": true,
"requests": [
{
"dueOn": "2026-09-08",
"parts": [
{
"part": "Copies of inspection reports",
"draft": "…",
"status": "answerable"
},
{
"part": "Names of the individual inspectors",
"status": "needs-decision",
"possibleExemption": "Appears to engage the personal data exemption in your policy section 6.2. Named for a decision, not applied."
}
],
"reference": "COR-4471",
"wasLogged": false,
"calculation": "20 working days from receipt, per your policy section 3.1. Two public holidays excluded.",
"clockStarted": "2026-08-11",
"recognisedAs": "Titled 'Complaint about the depot works'. The third paragraph asks for copies of the contractor's inspection reports, which is a request for recorded information."
}
],
"disclaimer": "Identification and tracking against your own policy. No exemption has been applied, nothing has been redacted or withheld, and no response has been sent.",
"policyFound": true,
"escalationReason": "A request was never logged, its clock expires in six days, and one part engages an exemption that a person must decide.",
"personalDataFlags": [
"COR-4471 — the reports contain a resident's address on page 4. Would need removing before release."
]
}No integrations required.
Find requests before they become overdue.
Establish which clocks have already run out.
Check what would need redacting.
$229/month
Billed monthly through your PROMIVO subscription. Cancel at any time.
Runs consume your plan allowance for agent executions and tokens. See plan limits.
No. Applying an exemption is a decision that can be appealed and must be owned by a person. It identifies which parts appear to engage one and names it, so the decision is made faster and with the reasoning in front of you.
No. It flags personal and third-party data for a person to remove. Automated redaction that misses one line is worse than no redaction, because it is trusted.
Whatever you load — your own policy and the deadlines that apply to you. Access regimes differ by country and body, and an agent quoting a remembered one would be quoting the wrong one.
No reviews yet. Reviews open once customers have run this agent.
Tell us what to change and our team will scope a customised version for your business.
Customize this agent