Identify
Flag potential FOI and SAR requests against your configured categories and examples.
FOI and SAR identification
Spot information requests.
Route them for confirmation.
Identify potential freedom of information (FOI) and subject access requests (SARs) in correspondence. Send the request, summary and key facts into your handling process.
Workflow in action
Recognise the request within the message.
A request for personal information may arrive inside an account enquiry. Capture what is being asked and pass it into your information request process.
Summarise
Make the request clear and extract relevant facts for the receiving team.
Route for confirmation
Send the flag and context to the responsible team or system. Confirmation and fulfilment remain part of your information request process.
Adapters and APIs
Connect to the next step.
Connect a workflow
Use an adapter to connect the processing. Pass a potential request, its summary and relevant facts into your handling process.
Use the APIs
Send correspondence from new or existing systems and receive classifications, summaries and extracted information for the next step.
No-code configuration
Test the distinction using your examples.
Configure the workflow without writing code. Build from examples of requests and ordinary enquiries to assess how it distinguishes them.
Define the examples
Use representative correspondence and the results you expect.
Review the results
Test identification quality and refine the configuration before use.
Control publication
When requirements change, test a new version and choose when it is published.
Reusable data and control
Keep useful data. Keep control.
You own the structured, sovereign dataset created from the correspondence processed. Reuse identification results across reporting and wider processes.
Understand demand
Analyse the volume and types of potential requests identified.
Govern the workflow
Run in your Azure environment, with access controls, versions and audit records.
Evaluate at volume
Assess processing quality, speed and cost against the correspondence and volumes you expect.
Walk through your request process.
Explore the correspondence you receive, what the workflow identifies and where potential requests need to go.