Email and portals
Applications, forms, uploads
Blueprint · Reference architecture
Document intelligence with a person in the loop
A reference design for AI that prepares decisions but never makes them alone. It underpins QAO solutions in banking, healthcare, government and logistics.
Architecture
How it fits together.
Sources
Scanned documents
IDs, statements, certificates
Core system data
Customer, account and case records
Intake
Intake and classification
Every document identified and routed
Extraction
OCR and document AI pull fields with page references
Intelligence
Policy rules engine
Business rules a person can read and change
Reasoning agent
Checks, compares and drafts, via the model gateway
Approved knowledge
Retrieval over policies and procedures only
Human in the loop
Review cockpit
Approve, edit or reject; every fact links to its source
Systems of record
Core platforms
Banking, policy admin, ERP
CRM
Customer and case history
Case management
Decisions and follow-ups
How data flows
Six steps, one accountable decision.
Step 1
Arrive
Documents and requests arrive from email, portals or uploads.
Step 2
Classify and extract
Each document is identified and its fields extracted, with the page each fact came from.
Step 3
Check
The rules engine and reasoning agent check facts against policy and flag gaps.
Step 4
Decide
A person reviews the prepared case in the cockpit and approves, edits or rejects.
Step 5
Record
The decision, evidence and full trail are written to the systems of record.
Step 6
Learn
Corrections feed back into rules and evaluation, never silently into the model.
Controls built in
Designed for regulated work.
A person decides
The system prepares; a named person approves every outcome.
Every fact is traceable
Each extracted value links back to its source page.
Rules stay readable
Policies live as rules business teams can review and change.
Provider-neutral AI
Models run through a gateway, so the client chooses the provider and hosting.
Deployment
Runs where the data must stay.
Private cloud
Inside the client's own cloud account and network.
On-premises
For data that must stay in the client's data centre.
Public cloud
Managed services with private networking and encryption.
Where it is used