[{"data":1,"prerenderedAt":91},["ShallowReactive",2],{"blog-tag-document-intelligence":3},[4,24,36,49,60,72,82],{"id":5,"slug":6,"body":7,"html":8,"title":9,"description":10,"category":11,"tags":12,"author":17,"date":18,"year":19,"month":20,"quarter":21,"status":22,"featured":23},"2026\u002F09\u002Findustry-applications\u002Fpermitting-and-inspections-for-the-built-environment","permitting-and-inspections-for-the-built-environment","\nBuilding permits and inspections sit where government and the construction industry meet, and both sides feel the friction. Applicants submit drawings and documents that bounce back for missing items. Reviewers work through large submissions against complex codes. Inspections are scheduled by phone. Comments live in PDFs and emails. Everyone wants to know the status, and nobody can easily say.\n\n## What the application does\n\nThe **permitting and inspection** family in the Atlas covers the lifecycle for authorities, developers and consultants:\n\n1. **Submission:** applicants submit forms, drawings and supporting documents through a portal.\n2. **Completeness check:** required documents and fields are verified before the application enters review.\n3. **Review routing:** disciplines (architectural, structural, fire, MEP, zoning) each review their part, in parallel where possible.\n4. **Comments and resubmission:** structured comments linked to the documents, with a response cycle and version history.\n5. **Decision:** approval with conditions, or rejection with reasons, by the authorized officer.\n6. **Inspections:** scheduling, mobile checklists, findings, photos and re-inspections.\n7. **Enforcement and closure:** violations, notices, occupancy certificates and archival.\n8. **Reporting:** cycle times, bottlenecks and workload by reviewer and discipline.\n\n## Where AI helps\n\n- **Document intelligence:** classify submitted documents, extract key data (areas, occupancy type, heights) and flag missing items.\n- **Pre-review checks:** highlight likely issues against configured code rules, for reviewers to confirm.\n- **Comment drafting:** suggest comments from a library of standard findings.\n- **Summaries:** a one-page summary of a large application for the approving officer.\n- **Inspection support:** suggested checklists by project type and stage, and extraction of findings from inspector notes.\n\nCode interpretation and approval stay with qualified reviewers and officers. The AI prepares the ground and records its suggestions.\n\n## Controls designed in\n\n- Role-based authority for approvals\n- Conflict-of-interest rules for reviewer assignment\n- A complete version history of submissions, comments and decisions\n- A public-facing status that doesn't expose internal deliberations\n\n## Integrations\n\nGovernment portals and national identity, GIS and land registry, payment gateways for fees, document management, and, on the developer side, common data environments and BIM platforms.\n\n## Who uses it\n\nPermit applicants and consultants, plan reviewers by discipline, inspectors, approving officers, and department leadership.\n\n## First scope\n\nOne permit type with high volume, such as minor works or fit-out permits, from submission to decision. Measure first-time completeness, review cycle time and resubmission count. Scope it in a [Solution Definition Sprint](\u002Fservices\u002Fsolution-definition-sprint).\n\nSee [AEC and built environment](\u002Findustries\u002Faec-built-environment) and [government](\u002Findustries\u002Fgovernment-public-sector), explore the [Atlas](\u002Fatlas), or [bring us your permit process](\u002Fcontact).\n","\u003Cp>Building permits and inspections sit where government and the construction industry meet, and both sides feel the friction. Applicants submit drawings and documents that bounce back for missing items. Reviewers work through large submissions against complex codes. Inspections are scheduled by phone. Comments live in PDFs and emails. Everyone wants to know the status, and nobody can easily say.\u003C\u002Fp>\n\u003Ch2>What the application does\u003C\u002Fh2>\n\u003Cp>The \u003Cstrong>permitting and inspection\u003C\u002Fstrong> family in the Atlas covers the lifecycle for authorities, developers and consultants:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Submission:\u003C\u002Fstrong> applicants submit forms, drawings and supporting documents through a portal.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Completeness check:\u003C\u002Fstrong> required documents and fields are verified before the application enters review.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Review routing:\u003C\u002Fstrong> disciplines (architectural, structural, fire, MEP, zoning) each review their part, in parallel where possible.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Comments and resubmission:\u003C\u002Fstrong> structured comments linked to the documents, with a response cycle and version history.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Decision:\u003C\u002Fstrong> approval with conditions, or rejection with reasons, by the authorized officer.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Inspections:\u003C\u002Fstrong> scheduling, mobile checklists, findings, photos and re-inspections.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Enforcement and closure:\u003C\u002Fstrong> violations, notices, occupancy certificates and archival.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Reporting:\u003C\u002Fstrong> cycle times, bottlenecks and workload by reviewer and discipline.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2>Where AI helps\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Document intelligence:\u003C\u002Fstrong> classify submitted documents, extract key data (areas, occupancy type, heights) and flag missing items.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Pre-review checks:\u003C\u002Fstrong> highlight likely issues against configured code rules, for reviewers to confirm.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Comment drafting:\u003C\u002Fstrong> suggest comments from a library of standard findings.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Summaries:\u003C\u002Fstrong> a one-page summary of a large application for the approving officer.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Inspection support:\u003C\u002Fstrong> suggested checklists by project type and stage, and extraction of findings from inspector notes.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Code interpretation and approval stay with qualified reviewers and officers. The AI prepares the ground and records its suggestions.\u003C\u002Fp>\n\u003Ch2>Controls designed in\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Role-based authority for approvals\u003C\u002Fli>\n\u003Cli>Conflict-of-interest rules for reviewer assignment\u003C\u002Fli>\n\u003Cli>A complete version history of submissions, comments and decisions\u003C\u002Fli>\n\u003Cli>A public-facing status that doesn't expose internal deliberations\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Integrations\u003C\u002Fh2>\n\u003Cp>Government portals and national identity, GIS and land registry, payment gateways for fees, document management, and, on the developer side, common data environments and BIM platforms.\u003C\u002Fp>\n\u003Ch2>Who uses it\u003C\u002Fh2>\n\u003Cp>Permit applicants and consultants, plan reviewers by discipline, inspectors, approving officers, and department leadership.\u003C\u002Fp>\n\u003Ch2>First scope\u003C\u002Fh2>\n\u003Cp>One permit type with high volume, such as minor works or fit-out permits, from submission to decision. Measure first-time completeness, review cycle time and resubmission count. Scope it in a \u003Ca href=\"\u002Fservices\u002Fsolution-definition-sprint\">Solution Definition Sprint\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>See \u003Ca href=\"\u002Findustries\u002Faec-built-environment\">AEC and built environment\u003C\u002Fa> and \u003Ca href=\"\u002Findustries\u002Fgovernment-public-sector\">government\u003C\u002Fa>, explore the \u003Ca href=\"\u002Fatlas\">Atlas\u003C\u002Fa>, or \u003Ca href=\"\u002Fcontact\">bring us your permit process\u003C\u002Fa>.\u003C\u002Fp>\n","Permitting and inspections: digitizing approvals for the built environment","Building permit and inspection applications for authorities and developers: submissions, reviews, comments, inspections and approvals with an audit trail.","industry-applications",[13,14,15,16],"aec","government","document-intelligence","case-management","fazezero-editorial","2026-09-15T00:00:00.000Z",2026,9,3,"published",false,{"id":25,"slug":26,"body":27,"html":28,"title":29,"description":30,"category":11,"tags":31,"author":17,"date":35,"year":19,"month":20,"quarter":21,"status":22,"featured":23},"2026\u002F09\u002Findustry-applications\u002Fquality-and-non-conformance-management","quality-and-non-conformance-management","\nEvery manufacturer has a quality system on paper. Many still run parts of it in spreadsheets and email: non-conformance reports typed up after the shift, CAPA actions tracked in a workbook, supplier issues buried in threads, audit evidence gathered before each certification visit.\n\nThe consequence isn't just inefficiency. When quality data is fragmented, recurring problems stay invisible until a customer finds them.\n\n## What the application does\n\nThe **quality management** family in the Atlas connects the core quality workflows:\n\n- **Non-conformance reporting:** captured at the point of detection, on the shop floor or at incoming inspection, with photos, measurements and lot or batch references.\n- **Containment:** holds on affected lots, quarantined stock and notifications to downstream processes.\n- **Disposition:** use-as-is, rework, scrap or return to supplier, approved by the right roles.\n- **Root cause and CAPA:** structured analysis (5 Whys, fishbone), corrective and preventive actions with owners, dates and effectiveness checks.\n- **Inspections:** plans, checklists and results tied to parts, processes and suppliers.\n- **Traceability:** links between lots, materials, equipment, operators and non-conformances.\n- **Audit readiness:** evidence of control operation for ISO and customer audits.\n\n## Where AI helps\n\n- **Classification:** suggest the defect code, affected process and severity from free-text reports and photos.\n- **Similar-issue retrieval:** “has this happened before?” answered with links to past non-conformances and their root causes.\n- **Root-cause support:** propose candidate causes from correlated data (the same machine, shift, supplier lot or tooling) for engineers to test.\n- **Document intelligence:** extract data from supplier certificates and inspection reports.\n- **Summaries:** quality review packs drafted from the record.\n\nA quality engineer decides the root cause and the disposition. The AI shortens the search, not the judgement.\n\n## Controls designed in\n\n- Mandatory containment steps before disposition\n- Role-based approval for use-as-is decisions\n- Effectiveness verification before a CAPA can close\n- Full lot-level traceability and an audit trail\n\n## Integrations\n\nMES and SCADA or historians for process data, ERP for materials and lots, LIMS for lab results, PLM for specifications, supplier portals, and the identity provider for shop-floor access.\n\n## Who uses it\n\nQuality engineers and inspectors, production supervisors, supplier quality teams, plant managers, and auditors.\n\n## First scope\n\nOne product line or plant, with non-conformance reporting and CAPA moved into the application. Measure time to containment, recurrence rate and CAPA on-time closure. Scope it in a [Solution Definition Sprint](\u002Fservices\u002Fsolution-definition-sprint).\n\nSee [industrial and manufacturing](\u002Findustries\u002Findustrial-manufacturing), explore the [Atlas](\u002Fatlas), or [bring us your NCR backlog](\u002Fcontact).\n","\u003Cp>Every manufacturer has a quality system on paper. Many still run parts of it in spreadsheets and email: non-conformance reports typed up after the shift, CAPA actions tracked in a workbook, supplier issues buried in threads, audit evidence gathered before each certification visit.\u003C\u002Fp>\n\u003Cp>The consequence isn't just inefficiency. When quality data is fragmented, recurring problems stay invisible until a customer finds them.\u003C\u002Fp>\n\u003Ch2>What the application does\u003C\u002Fh2>\n\u003Cp>The \u003Cstrong>quality management\u003C\u002Fstrong> family in the Atlas connects the core quality workflows:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Non-conformance reporting:\u003C\u002Fstrong> captured at the point of detection, on the shop floor or at incoming inspection, with photos, measurements and lot or batch references.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Containment:\u003C\u002Fstrong> holds on affected lots, quarantined stock and notifications to downstream processes.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Disposition:\u003C\u002Fstrong> use-as-is, rework, scrap or return to supplier, approved by the right roles.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Root cause and CAPA:\u003C\u002Fstrong> structured analysis (5 Whys, fishbone), corrective and preventive actions with owners, dates and effectiveness checks.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Inspections:\u003C\u002Fstrong> plans, checklists and results tied to parts, processes and suppliers.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Traceability:\u003C\u002Fstrong> links between lots, materials, equipment, operators and non-conformances.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Audit readiness:\u003C\u002Fstrong> evidence of control operation for ISO and customer audits.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Where AI helps\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Classification:\u003C\u002Fstrong> suggest the defect code, affected process and severity from free-text reports and photos.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Similar-issue retrieval:\u003C\u002Fstrong> “has this happened before?” answered with links to past non-conformances and their root causes.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Root-cause support:\u003C\u002Fstrong> propose candidate causes from correlated data (the same machine, shift, supplier lot or tooling) for engineers to test.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Document intelligence:\u003C\u002Fstrong> extract data from supplier certificates and inspection reports.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Summaries:\u003C\u002Fstrong> quality review packs drafted from the record.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>A quality engineer decides the root cause and the disposition. The AI shortens the search, not the judgement.\u003C\u002Fp>\n\u003Ch2>Controls designed in\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Mandatory containment steps before disposition\u003C\u002Fli>\n\u003Cli>Role-based approval for use-as-is decisions\u003C\u002Fli>\n\u003Cli>Effectiveness verification before a CAPA can close\u003C\u002Fli>\n\u003Cli>Full lot-level traceability and an audit trail\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Integrations\u003C\u002Fh2>\n\u003Cp>MES and SCADA or historians for process data, ERP for materials and lots, LIMS for lab results, PLM for specifications, supplier portals, and the identity provider for shop-floor access.\u003C\u002Fp>\n\u003Ch2>Who uses it\u003C\u002Fh2>\n\u003Cp>Quality engineers and inspectors, production supervisors, supplier quality teams, plant managers, and auditors.\u003C\u002Fp>\n\u003Ch2>First scope\u003C\u002Fh2>\n\u003Cp>One product line or plant, with non-conformance reporting and CAPA moved into the application. Measure time to containment, recurrence rate and CAPA on-time closure. Scope it in a \u003Ca href=\"\u002Fservices\u002Fsolution-definition-sprint\">Solution Definition Sprint\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>See \u003Ca href=\"\u002Findustries\u002Findustrial-manufacturing\">industrial and manufacturing\u003C\u002Fa>, explore the \u003Ca href=\"\u002Fatlas\">Atlas\u003C\u002Fa>, or \u003Ca href=\"\u002Fcontact\">bring us your NCR backlog\u003C\u002Fa>.\u003C\u002Fp>\n","Quality and non-conformance management with AI-assisted root cause","Manufacturing quality applications for non-conformances, CAPA, inspections and traceability, where AI helps engineers find patterns faster.",[32,33,15,34],"manufacturing","quality","evidence","2026-09-10T00:00:00.000Z",{"id":37,"slug":38,"body":39,"html":40,"title":41,"description":42,"category":11,"tags":43,"author":17,"date":47,"year":19,"month":48,"quarter":21,"status":22,"featured":23},"2026\u002F08\u002Findustry-applications\u002Fthird-party-and-supplier-risk-reviews","third-party-and-supplier-risk-reviews","\nMost organizations depend on hundreds or thousands of third parties: cloud providers, outsourcers, suppliers, data processors, agents, fintech partners. Regulators increasingly hold the organization accountable for those dependencies. Yet third-party risk management often runs on questionnaires sent by email, answers pasted into spreadsheets, and reviews that happen at onboarding and then never again.\n\n## What the application does\n\nThe **third-party risk** family in the Atlas manages the full supplier risk lifecycle:\n\n1. **Intake:** a business owner requests a new third party, with the service description, data access and criticality.\n2. **Tiering:** inherent risk is scored from the service, data, criticality and jurisdiction, which determines the depth of due diligence.\n3. **Due diligence:** questionnaires, document requests (certifications, audit reports, policies) and specialist reviews such as security, privacy, financial and legal.\n4. **Assessment:** reviewers record findings, and issues get remediation actions.\n5. **Approval:** a risk-based approval with conditions.\n6. **Contracting:** required clauses confirmed, then onboarding.\n7. **Ongoing monitoring:** periodic re-reviews, certificate expiry, incidents, performance and external signals.\n8. **Exit planning:** for critical services, as regulators now expect.\n\n## Where AI helps\n\n- **Document intelligence:** extract scope, dates, exceptions and qualified opinions from SOC reports, ISO certificates and policies. This is where reviewers spend most of their time.\n- **Questionnaire analysis:** flag answers that contradict the evidence or are incomplete.\n- **Tiering suggestions:** propose a tier from the intake description, for the risk owner to confirm.\n- **Monitoring summaries:** condense external news and incident signals about a supplier into a short brief, with sources.\n- **Report drafting:** assessment summaries and committee papers.\n\nRisk acceptance, approval and exit decisions stay with accountable owners.\n\n## Controls designed in\n\n- Mandatory due-diligence steps by tier\n- Segregation between the requesting business owner and the approving risk function\n- Evidence retained against each finding\n- Re-review triggers on expiry, incidents or changes in service scope\n\n## Integrations\n\nProcurement and contract management systems, ERP vendor master data, GRC tools, security rating or intelligence feeds where used, the identity provider, and email for supplier correspondence.\n\n## Who uses it\n\nProcurement managers, third-party risk teams, security and privacy reviewers, compliance officers, business owners of each relationship, and internal audit.\n\n## Where it applies\n\nFinancial services, where outsourcing and operational-resilience rules apply. Government entities managing contractors. Any enterprise with significant data processors or critical suppliers.\n\n## First scope\n\nCritical and high-tier suppliers first: move them into the application with evidence extracted from their latest reports, and switch on monitoring. Scope it in a [Solution Definition Sprint](\u002Fservices\u002Fsolution-definition-sprint).\n\nExplore the [Atlas](\u002Fatlas), or [bring us your supplier inventory](\u002Fcontact).\n","\u003Cp>Most organizations depend on hundreds or thousands of third parties: cloud providers, outsourcers, suppliers, data processors, agents, fintech partners. Regulators increasingly hold the organization accountable for those dependencies. Yet third-party risk management often runs on questionnaires sent by email, answers pasted into spreadsheets, and reviews that happen at onboarding and then never again.\u003C\u002Fp>\n\u003Ch2>What the application does\u003C\u002Fh2>\n\u003Cp>The \u003Cstrong>third-party risk\u003C\u002Fstrong> family in the Atlas manages the full supplier risk lifecycle:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Intake:\u003C\u002Fstrong> a business owner requests a new third party, with the service description, data access and criticality.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Tiering:\u003C\u002Fstrong> inherent risk is scored from the service, data, criticality and jurisdiction, which determines the depth of due diligence.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Due diligence:\u003C\u002Fstrong> questionnaires, document requests (certifications, audit reports, policies) and specialist reviews such as security, privacy, financial and legal.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Assessment:\u003C\u002Fstrong> reviewers record findings, and issues get remediation actions.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Approval:\u003C\u002Fstrong> a risk-based approval with conditions.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Contracting:\u003C\u002Fstrong> required clauses confirmed, then onboarding.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Ongoing monitoring:\u003C\u002Fstrong> periodic re-reviews, certificate expiry, incidents, performance and external signals.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Exit planning:\u003C\u002Fstrong> for critical services, as regulators now expect.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2>Where AI helps\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Document intelligence:\u003C\u002Fstrong> extract scope, dates, exceptions and qualified opinions from SOC reports, ISO certificates and policies. This is where reviewers spend most of their time.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Questionnaire analysis:\u003C\u002Fstrong> flag answers that contradict the evidence or are incomplete.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Tiering suggestions:\u003C\u002Fstrong> propose a tier from the intake description, for the risk owner to confirm.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Monitoring summaries:\u003C\u002Fstrong> condense external news and incident signals about a supplier into a short brief, with sources.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Report drafting:\u003C\u002Fstrong> assessment summaries and committee papers.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Risk acceptance, approval and exit decisions stay with accountable owners.\u003C\u002Fp>\n\u003Ch2>Controls designed in\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Mandatory due-diligence steps by tier\u003C\u002Fli>\n\u003Cli>Segregation between the requesting business owner and the approving risk function\u003C\u002Fli>\n\u003Cli>Evidence retained against each finding\u003C\u002Fli>\n\u003Cli>Re-review triggers on expiry, incidents or changes in service scope\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Integrations\u003C\u002Fh2>\n\u003Cp>Procurement and contract management systems, ERP vendor master data, GRC tools, security rating or intelligence feeds where used, the identity provider, and email for supplier correspondence.\u003C\u002Fp>\n\u003Ch2>Who uses it\u003C\u002Fh2>\n\u003Cp>Procurement managers, third-party risk teams, security and privacy reviewers, compliance officers, business owners of each relationship, and internal audit.\u003C\u002Fp>\n\u003Ch2>Where it applies\u003C\u002Fh2>\n\u003Cp>Financial services, where outsourcing and operational-resilience rules apply. Government entities managing contractors. Any enterprise with significant data processors or critical suppliers.\u003C\u002Fp>\n\u003Ch2>First scope\u003C\u002Fh2>\n\u003Cp>Critical and high-tier suppliers first: move them into the application with evidence extracted from their latest reports, and switch on monitoring. Scope it in a \u003Ca href=\"\u002Fservices\u002Fsolution-definition-sprint\">Solution Definition Sprint\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Explore the \u003Ca href=\"\u002Fatlas\">Atlas\u003C\u002Fa>, or \u003Ca href=\"\u002Fcontact\">bring us your supplier inventory\u003C\u002Fa>.\u003C\u002Fp>\n","Third-party and supplier risk reviews that keep up with the supplier base","Third-party risk applications that tier suppliers, run due diligence, extract evidence from documents and track issues, with reviewers deciding.",[44,45,46,15,34],"risk","enterprise-operations","financial-services","2026-08-18T00:00:00.000Z",8,{"id":50,"slug":51,"body":52,"html":53,"title":54,"description":55,"category":11,"tags":56,"author":17,"date":59,"year":19,"month":48,"quarter":21,"status":22,"featured":23},"2026\u002F08\u002Findustry-applications\u002Freferrals-and-care-coordination","referrals-and-care-coordination","\nClinicians spend a significant part of their day on work that isn't clinical: referral letters, pre-authorization requests, follow-up coordination, chasing results and scheduling across providers. Patients experience that work as waiting.\n\nThe **care coordination** family in the Atlas focuses on these administrative and coordination workflows. It doesn't touch clinical decision-making, and it's designed so it cannot drift into it.\n\n## Workflows covered\n\n- **Referral intake:** referrals arrive from primary care, other hospitals or payers, and are checked for completeness.\n- **Triage and routing:** referrals go to the right service and are prioritized according to clinical rules defined by the provider.\n- **Pre-authorization:** requests are assembled with the required documentation, submitted to payers and tracked.\n- **Scheduling coordination:** appointments are linked across departments and providers.\n- **Care pathway tasks:** follow-ups, results, patient communication and hand-offs, each with an owner and due date.\n- **Closure and feedback:** outcomes communicated back to the referring provider.\n- **Reporting:** waiting times, bottlenecks and service-level performance.\n\n## Where AI helps\n\n- **Document extraction:** pull structured data from referral letters and attachments.\n- **Completeness checks:** identify missing information before a referral reaches a coordinator.\n- **Summaries:** a concise case summary for coordinators, drawn from the documents.\n- **Drafting:** pre-authorization justifications and patient communications, for staff to review.\n- **Queue prioritization:** suggestions based on the provider's own rules, never the model's opinion of clinical urgency.\n\n## Where it must not\n\nAI output in this family never replaces clinical judgement. Clinical triage rules are configured by the provider and applied deterministically, and any AI suggestion that touches clinical content is shown to a qualified person before it has effect. Each AI output is labelled and its acceptance recorded.\n\n## Privacy and hosting\n\nHealth data demands strict handling:\n\n- in-country hosting where regulations require it\n- role-based access down to record level\n- full access logging\n- a data-minimization default for AI features: models see only what the task needs\n- a documented choice of AI provider, including private or self-hosted models where required\n\n## Integrations\n\nEHR and HIS systems (typically via HL7 or FHIR interfaces), payer portals and APIs, scheduling systems, patient messaging, and the identity provider.\n\n## Who uses it\n\nReferral coordinators, care coordinators, pre-authorization teams, department administrators, clinicians (for review and sign-off) and operations leadership.\n\n## First scope\n\nOne referral pathway with a visible waiting-time problem. Measure time from referral to first appointment and the share of referrals returned incomplete. Scope it in a [Solution Definition Sprint](\u002Fservices\u002Fsolution-definition-sprint).\n\nSee [healthcare](\u002Findustries\u002Fhealthcare), explore the [Atlas](\u002Fatlas), or [bring us your pathway](\u002Fcontact).\n","\u003Cp>Clinicians spend a significant part of their day on work that isn't clinical: referral letters, pre-authorization requests, follow-up coordination, chasing results and scheduling across providers. Patients experience that work as waiting.\u003C\u002Fp>\n\u003Cp>The \u003Cstrong>care coordination\u003C\u002Fstrong> family in the Atlas focuses on these administrative and coordination workflows. It doesn't touch clinical decision-making, and it's designed so it cannot drift into it.\u003C\u002Fp>\n\u003Ch2>Workflows covered\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Referral intake:\u003C\u002Fstrong> referrals arrive from primary care, other hospitals or payers, and are checked for completeness.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Triage and routing:\u003C\u002Fstrong> referrals go to the right service and are prioritized according to clinical rules defined by the provider.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Pre-authorization:\u003C\u002Fstrong> requests are assembled with the required documentation, submitted to payers and tracked.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Scheduling coordination:\u003C\u002Fstrong> appointments are linked across departments and providers.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Care pathway tasks:\u003C\u002Fstrong> follow-ups, results, patient communication and hand-offs, each with an owner and due date.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Closure and feedback:\u003C\u002Fstrong> outcomes communicated back to the referring provider.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Reporting:\u003C\u002Fstrong> waiting times, bottlenecks and service-level performance.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Where AI helps\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Document extraction:\u003C\u002Fstrong> pull structured data from referral letters and attachments.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Completeness checks:\u003C\u002Fstrong> identify missing information before a referral reaches a coordinator.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Summaries:\u003C\u002Fstrong> a concise case summary for coordinators, drawn from the documents.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Drafting:\u003C\u002Fstrong> pre-authorization justifications and patient communications, for staff to review.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Queue prioritization:\u003C\u002Fstrong> suggestions based on the provider's own rules, never the model's opinion of clinical urgency.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Where it must not\u003C\u002Fh2>\n\u003Cp>AI output in this family never replaces clinical judgement. Clinical triage rules are configured by the provider and applied deterministically, and any AI suggestion that touches clinical content is shown to a qualified person before it has effect. Each AI output is labelled and its acceptance recorded.\u003C\u002Fp>\n\u003Ch2>Privacy and hosting\u003C\u002Fh2>\n\u003Cp>Health data demands strict handling:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>in-country hosting where regulations require it\u003C\u002Fli>\n\u003Cli>role-based access down to record level\u003C\u002Fli>\n\u003Cli>full access logging\u003C\u002Fli>\n\u003Cli>a data-minimization default for AI features: models see only what the task needs\u003C\u002Fli>\n\u003Cli>a documented choice of AI provider, including private or self-hosted models where required\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Integrations\u003C\u002Fh2>\n\u003Cp>EHR and HIS systems (typically via HL7 or FHIR interfaces), payer portals and APIs, scheduling systems, patient messaging, and the identity provider.\u003C\u002Fp>\n\u003Ch2>Who uses it\u003C\u002Fh2>\n\u003Cp>Referral coordinators, care coordinators, pre-authorization teams, department administrators, clinicians (for review and sign-off) and operations leadership.\u003C\u002Fp>\n\u003Ch2>First scope\u003C\u002Fh2>\n\u003Cp>One referral pathway with a visible waiting-time problem. Measure time from referral to first appointment and the share of referrals returned incomplete. Scope it in a \u003Ca href=\"\u002Fservices\u002Fsolution-definition-sprint\">Solution Definition Sprint\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>See \u003Ca href=\"\u002Findustries\u002Fhealthcare\">healthcare\u003C\u002Fa>, explore the \u003Ca href=\"\u002Fatlas\">Atlas\u003C\u002Fa>, or \u003Ca href=\"\u002Fcontact\">bring us your pathway\u003C\u002Fa>.\u003C\u002Fp>\n","Referrals and care coordination: the administrative workflows around care","Healthcare operations applications for referrals, pre-authorization and care coordination, with AI on paperwork and humans on every clinical decision.",[57,15,16,58],"healthcare","human-in-the-loop","2026-08-13T00:00:00.000Z",{"id":61,"slug":62,"body":63,"html":64,"title":65,"description":66,"category":67,"tags":68,"author":17,"date":70,"year":19,"month":71,"quarter":21,"status":22,"featured":23},"2026\u002F07\u002Fai-in-production\u002Fdocument-intelligence-in-regulated-workflows","document-intelligence-in-regulated-workflows","\nRegulated workflows run on documents: identity documents, company registries, financial statements, invoices, contracts, permits, medical referrals, supplier certificates, audit reports. Extracting data from them is among the most valuable uses of AI, and among the easiest to get subtly wrong.\n\nA demo extracts ten fields from a clean PDF perfectly. Production brings scans, photos, handwriting, multiple languages, unusual layouts and documents that are simply the wrong document.\n\n## The production pattern\n\n**1. Classify first.** Before extracting anything, determine what the document is. A bank statement sent where a trade licence was expected should be caught at the door.\n\n**2. Extract to a schema.** Every document type has a defined schema of fields, types and formats. The model's output is validated against it, and anything that doesn't conform is rejected.\n\n**3. Validate against rules and sources.** Cross-check extracted values: totals that should add up, dates that should be in order, registration numbers that should exist in a registry, names that should match the application.\n\n**4. Carry confidence and provenance.** Every extracted field records where it came from on the page and how confident the extraction is. Reviewers see the source next to the value.\n\n**5. Route by confidence and risk.** High-confidence, low-risk fields flow straight through. Low-confidence or high-risk fields go to a human review queue. The thresholds are business decisions, not model defaults.\n\n**6. Learn from corrections.** Every human correction is recorded and becomes evaluation data for the next model or prompt change.\n\n## Where it appears across the Atlas\n\nDocument intelligence isn't a product on its own. It's a capability inside many application families:\n\n- **Onboarding and KYC\u002FKYB:** identity and company documents\n- **Case management:** evidence submitted by applicants ([AI-assisted case management](\u002Fblog\u002Fai-assisted-case-management))\n- **Referrals and pre-authorization** in healthcare ([care coordination](\u002Fblog\u002Freferrals-and-care-coordination))\n- **Permits** in the built environment ([permitting and inspections](\u002Fblog\u002Fpermitting-and-inspections-for-the-built-environment))\n- **Supplier assurance:** SOC reports and certificates ([third-party risk](\u002Fblog\u002Fthird-party-and-supplier-risk-reviews))\n- **Finance:** remittances and statements ([reconciliation](\u002Fblog\u002Freconciliation-and-exception-workbenches))\n\n## Controls designed in\n\n- Original documents retained, unaltered, with hashes\n- Extracted values linked to their source location\n- Every human override recorded, with the reviewer and reason\n- Access to sensitive documents restricted by role and logged\n- The model provider and hosting chosen to meet data-residency requirements\n\n## Measuring it honestly\n\nField-level accuracy on a held-out test set per document type, straight-through processing rate, review queue volume and correction rate. Agree the thresholds with the business and compliance owners before launch. See [evaluation and guardrails](\u002Fblog\u002Fevaluation-and-guardrails-before-production).\n\n## Arabic and bilingual documents\n\nIn the GCC, many documents are Arabic, English or both, and include stamps, signatures and handwriting. Test sets must reflect that mix from day one. Performance on English samples says little about performance on the documents you'll actually receive.\n\n[Bring us the document types](\u002Fcontact) that slow your workflow down.\n","\u003Cp>Regulated workflows run on documents: identity documents, company registries, financial statements, invoices, contracts, permits, medical referrals, supplier certificates, audit reports. Extracting data from them is among the most valuable uses of AI, and among the easiest to get subtly wrong.\u003C\u002Fp>\n\u003Cp>A demo extracts ten fields from a clean PDF perfectly. Production brings scans, photos, handwriting, multiple languages, unusual layouts and documents that are simply the wrong document.\u003C\u002Fp>\n\u003Ch2>The production pattern\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>1. Classify first.\u003C\u002Fstrong> Before extracting anything, determine what the document is. A bank statement sent where a trade licence was expected should be caught at the door.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>2. Extract to a schema.\u003C\u002Fstrong> Every document type has a defined schema of fields, types and formats. The model's output is validated against it, and anything that doesn't conform is rejected.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>3. Validate against rules and sources.\u003C\u002Fstrong> Cross-check extracted values: totals that should add up, dates that should be in order, registration numbers that should exist in a registry, names that should match the application.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>4. Carry confidence and provenance.\u003C\u002Fstrong> Every extracted field records where it came from on the page and how confident the extraction is. Reviewers see the source next to the value.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>5. Route by confidence and risk.\u003C\u002Fstrong> High-confidence, low-risk fields flow straight through. Low-confidence or high-risk fields go to a human review queue. The thresholds are business decisions, not model defaults.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>6. Learn from corrections.\u003C\u002Fstrong> Every human correction is recorded and becomes evaluation data for the next model or prompt change.\u003C\u002Fp>\n\u003Ch2>Where it appears across the Atlas\u003C\u002Fh2>\n\u003Cp>Document intelligence isn't a product on its own. It's a capability inside many application families:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Onboarding and KYC\u002FKYB:\u003C\u002Fstrong> identity and company documents\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Case management:\u003C\u002Fstrong> evidence submitted by applicants (\u003Ca href=\"\u002Fblog\u002Fai-assisted-case-management\">AI-assisted case management\u003C\u002Fa>)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Referrals and pre-authorization\u003C\u002Fstrong> in healthcare (\u003Ca href=\"\u002Fblog\u002Freferrals-and-care-coordination\">care coordination\u003C\u002Fa>)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Permits\u003C\u002Fstrong> in the built environment (\u003Ca href=\"\u002Fblog\u002Fpermitting-and-inspections-for-the-built-environment\">permitting and inspections\u003C\u002Fa>)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Supplier assurance:\u003C\u002Fstrong> SOC reports and certificates (\u003Ca href=\"\u002Fblog\u002Fthird-party-and-supplier-risk-reviews\">third-party risk\u003C\u002Fa>)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Finance:\u003C\u002Fstrong> remittances and statements (\u003Ca href=\"\u002Fblog\u002Freconciliation-and-exception-workbenches\">reconciliation\u003C\u002Fa>)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Controls designed in\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Original documents retained, unaltered, with hashes\u003C\u002Fli>\n\u003Cli>Extracted values linked to their source location\u003C\u002Fli>\n\u003Cli>Every human override recorded, with the reviewer and reason\u003C\u002Fli>\n\u003Cli>Access to sensitive documents restricted by role and logged\u003C\u002Fli>\n\u003Cli>The model provider and hosting chosen to meet data-residency requirements\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Measuring it honestly\u003C\u002Fh2>\n\u003Cp>Field-level accuracy on a held-out test set per document type, straight-through processing rate, review queue volume and correction rate. Agree the thresholds with the business and compliance owners before launch. See \u003Ca href=\"\u002Fblog\u002Fevaluation-and-guardrails-before-production\">evaluation and guardrails\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2>Arabic and bilingual documents\u003C\u002Fh2>\n\u003Cp>In the GCC, many documents are Arabic, English or both, and include stamps, signatures and handwriting. Test sets must reflect that mix from day one. Performance on English samples says little about performance on the documents you'll actually receive.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"\u002Fcontact\">Bring us the document types\u003C\u002Fa> that slow your workflow down.\u003C\u002Fp>\n","Document intelligence in regulated workflows: extraction with verification","Extracting data from documents with AI is easy to demo and hard to trust. How to build extraction with validation, confidence and human review.","ai-in-production",[15,58,34,69],"production","2026-07-23T00:00:00.000Z",7,{"id":73,"slug":74,"body":75,"html":76,"title":77,"description":78,"category":11,"tags":79,"author":17,"date":81,"year":19,"month":71,"quarter":21,"status":22,"featured":23},"2026\u002F07\u002Findustry-applications\u002Freconciliation-and-exception-workbenches","reconciliation-and-exception-workbenches","\nFew finance processes consume as much skilled time as reconciliation. Statements, ledgers, sub-ledgers, payment files and counterparty reports all have to agree, and when they don't, someone investigates. At month-end that “someone” is usually a team working in spreadsheets.\n\nIt is also one of the most practical places to apply AI, because the work is repetitive, the data is structured, the exceptions follow patterns and the outcome is verifiable.\n\n## What the application does\n\nThe **financial operations** family in the Atlas includes reconciliation workbench foundations built around five workflows:\n\n1. **Ingest.** Pull statements, ledger extracts and payment files through adapters, and normalize them into a common model.\n2. **Match.** Rule-based matching first (exact, tolerance, many-to-one), then suggested matches for what is left.\n3. **Investigate breaks.** Unmatched items become exceptions in a queue, with ageing, ownership and priority.\n4. **Resolve and approve.** Adjustments and write-offs go through maker\u002Fchecker approval, with the reason recorded.\n5. **Close and evidence.** Reconciliation sign-off with a full history, ready for audit.\n\n## Where AI helps, and where it doesn't\n\n**It helps with:**\n\n- suggesting matches for items that rules can't pair, with a confidence score and the reasoning shown\n- classifying breaks by likely cause (timing, fees, FX, duplicates, missing entries)\n- summarizing an exception's history for whoever picks it up\n- extracting data from unstructured remittance advice and statements\n- spotting anomalies such as unusual break volumes or recurring counterparty issues\n\n**It doesn't:**\n\n- post adjustments on its own\n- approve write-offs\n- change matching rules without review\n\nDeterministic rules stay in charge of the ledger. AI shortens the path to a human decision.\n\n## Who uses it\n\nFinance analysts and operations controllers do the daily work. Treasury managers need cash visibility. Controllers and CFO offices need the close. Internal audit needs the evidence.\n\n## Integrations\n\nERP general ledgers, banking APIs and statement formats (including ISO 20022 camt messages), payment hubs, card processors and, in digital-asset operations, custody and wallet balances. See [stablecoin settlement operations](\u002Fblog\u002Foperating-stablecoin-settlement).\n\n## Controls designed in\n\n- Segregation between preparer and approver\n- Thresholds that force a second approval on large adjustments\n- Immutable history of matches, unmatches and overrides\n- Ageing and escalation rules for unresolved breaks\n\n## Measuring success honestly\n\nThe metrics that matter are auto-match rate, exception ageing, time to close and the number of manual adjustments. We agree baselines during the [Solution Definition Sprint](\u002Fservices\u002Fsolution-definition-sprint), so success is measured against your numbers, not a vendor's brochure.\n\n## Where it applies\n\nBanks, payment companies, insurers, corporate treasury and shared-service centres, and digital-asset operators reconciling on-chain and off-chain records.\n\nSee [financial services](\u002Findustries\u002Ffinancial-services) or [bring us your reconciliation](\u002Fcontact).\n","\u003Cp>Few finance processes consume as much skilled time as reconciliation. Statements, ledgers, sub-ledgers, payment files and counterparty reports all have to agree, and when they don't, someone investigates. At month-end that “someone” is usually a team working in spreadsheets.\u003C\u002Fp>\n\u003Cp>It is also one of the most practical places to apply AI, because the work is repetitive, the data is structured, the exceptions follow patterns and the outcome is verifiable.\u003C\u002Fp>\n\u003Ch2>What the application does\u003C\u002Fh2>\n\u003Cp>The \u003Cstrong>financial operations\u003C\u002Fstrong> family in the Atlas includes reconciliation workbench foundations built around five workflows:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Ingest.\u003C\u002Fstrong> Pull statements, ledger extracts and payment files through adapters, and normalize them into a common model.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Match.\u003C\u002Fstrong> Rule-based matching first (exact, tolerance, many-to-one), then suggested matches for what is left.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Investigate breaks.\u003C\u002Fstrong> Unmatched items become exceptions in a queue, with ageing, ownership and priority.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Resolve and approve.\u003C\u002Fstrong> Adjustments and write-offs go through maker\u002Fchecker approval, with the reason recorded.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Close and evidence.\u003C\u002Fstrong> Reconciliation sign-off with a full history, ready for audit.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2>Where AI helps, and where it doesn't\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>It helps with:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>suggesting matches for items that rules can't pair, with a confidence score and the reasoning shown\u003C\u002Fli>\n\u003Cli>classifying breaks by likely cause (timing, fees, FX, duplicates, missing entries)\u003C\u002Fli>\n\u003Cli>summarizing an exception's history for whoever picks it up\u003C\u002Fli>\n\u003Cli>extracting data from unstructured remittance advice and statements\u003C\u002Fli>\n\u003Cli>spotting anomalies such as unusual break volumes or recurring counterparty issues\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>It doesn't:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>post adjustments on its own\u003C\u002Fli>\n\u003Cli>approve write-offs\u003C\u002Fli>\n\u003Cli>change matching rules without review\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Deterministic rules stay in charge of the ledger. AI shortens the path to a human decision.\u003C\u002Fp>\n\u003Ch2>Who uses it\u003C\u002Fh2>\n\u003Cp>Finance analysts and operations controllers do the daily work. Treasury managers need cash visibility. Controllers and CFO offices need the close. Internal audit needs the evidence.\u003C\u002Fp>\n\u003Ch2>Integrations\u003C\u002Fh2>\n\u003Cp>ERP general ledgers, banking APIs and statement formats (including ISO 20022 camt messages), payment hubs, card processors and, in digital-asset operations, custody and wallet balances. See \u003Ca href=\"\u002Fblog\u002Foperating-stablecoin-settlement\">stablecoin settlement operations\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2>Controls designed in\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Segregation between preparer and approver\u003C\u002Fli>\n\u003Cli>Thresholds that force a second approval on large adjustments\u003C\u002Fli>\n\u003Cli>Immutable history of matches, unmatches and overrides\u003C\u002Fli>\n\u003Cli>Ageing and escalation rules for unresolved breaks\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Measuring success honestly\u003C\u002Fh2>\n\u003Cp>The metrics that matter are auto-match rate, exception ageing, time to close and the number of manual adjustments. We agree baselines during the \u003Ca href=\"\u002Fservices\u002Fsolution-definition-sprint\">Solution Definition Sprint\u003C\u002Fa>, so success is measured against your numbers, not a vendor's brochure.\u003C\u002Fp>\n\u003Ch2>Where it applies\u003C\u002Fh2>\n\u003Cp>Banks, payment companies, insurers, corporate treasury and shared-service centres, and digital-asset operators reconciling on-chain and off-chain records.\u003C\u002Fp>\n\u003Cp>See \u003Ca href=\"\u002Findustries\u002Ffinancial-services\">financial services\u003C\u002Fa> or \u003Ca href=\"\u002Fcontact\">bring us your reconciliation\u003C\u002Fa>.\u003C\u002Fp>\n","Reconciliation and exception workbenches: where finance AI earns its keep","Why transaction and ledger reconciliation is one of the most practical AI applications in finance: matching, break investigation and evidence.",[80,46,45,15],"reconciliation","2026-07-21T00:00:00.000Z",{"id":83,"slug":84,"body":85,"html":86,"title":87,"description":88,"category":11,"tags":89,"author":17,"date":90,"year":19,"month":71,"quarter":21,"status":22,"featured":23},"2026\u002F07\u002Findustry-applications\u002Fai-assisted-case-management","ai-assisted-case-management","\nCase management is everywhere once you look for it: benefit applications, licensing requests, complaints, investigations, customer disputes, employee cases, service requests. The shape is the same each time. Something arrives, it's triaged, someone works it, a decision is made and it may be appealed. Backlogs grow when intake outpaces the people who decide.\n\nThat common shape is why case management is one of the most reusable application families in the Atlas, and one of the best places to apply AI safely.\n\n## The core workflow\n\n1. **Intake:** cases arrive through portals, email, APIs or other systems, with documents attached.\n2. **Triage:** each case is classified by type, urgency and complexity, and routed to the right queue.\n3. **Assignment:** workload-aware allocation to case workers, with skills and conflicts respected.\n4. **Work:** information requests, internal consultations, notes and deadlines.\n5. **Decision:** a structured decision with its rationale, approved where policy requires.\n6. **Communication:** notifications and letters to the applicant or customer.\n7. **Appeal or reopen:** a linked case with its full history.\n8. **Reporting:** backlog, ageing, service levels and outcomes.\n\n## Where AI helps\n\n- **Document intelligence:** extract fields from submitted documents and check completeness before a case reaches a person.\n- **Classification and routing:** suggest case type and priority, with the suggestion recorded.\n- **Case summaries:** a short, current summary at the top of every case, so a new case worker doesn't reread forty pages.\n- **Similar-case retrieval:** find precedents and relevant policy passages with citations.\n- **Drafting:** propose decision letters and information requests for the case worker to edit.\n\n## Where it must not\n\nAI never makes the decision in consequential cases. It doesn't deny, approve or close on its own. The workflow puts human checkpoints at every decision, records who decided, and keeps AI-generated text visibly marked until a person accepts it. In the public sector, this is about legitimacy as much as risk: citizens are entitled to an accountable decision-maker.\n\n## Controls designed in\n\n- Role-based access to sensitive case data\n- Conflict-of-interest checks on assignment\n- A complete audit history of every change, view and decision\n- Retention and disclosure rules configured per case type\n\n## Integrations\n\nCitizen or customer portals, national identity and SSO, document management, CRM or registry systems, payment systems for fees, and messaging services.\n\n## Where it applies\n\nGovernment and public services, financial services complaints and disputes, insurance claims triage, HR case management and enterprise service teams. The foundation is the same, and the domain vocabulary and policies are configured.\n\n## First scope\n\nOne case type with a real backlog. Measure time to first touch, time to decision and backlog ageing before and after. Scope it in a [Solution Definition Sprint](\u002Fservices\u002Fsolution-definition-sprint).\n\nSee [government and public sector](\u002Findustries\u002Fgovernment-public-sector), explore the [Atlas](\u002Fatlas), or [bring us your backlog](\u002Fcontact).\n","\u003Cp>Case management is everywhere once you look for it: benefit applications, licensing requests, complaints, investigations, customer disputes, employee cases, service requests. The shape is the same each time. Something arrives, it's triaged, someone works it, a decision is made and it may be appealed. Backlogs grow when intake outpaces the people who decide.\u003C\u002Fp>\n\u003Cp>That common shape is why case management is one of the most reusable application families in the Atlas, and one of the best places to apply AI safely.\u003C\u002Fp>\n\u003Ch2>The core workflow\u003C\u002Fh2>\n\u003Col>\n\u003Cli>\u003Cstrong>Intake:\u003C\u002Fstrong> cases arrive through portals, email, APIs or other systems, with documents attached.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Triage:\u003C\u002Fstrong> each case is classified by type, urgency and complexity, and routed to the right queue.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Assignment:\u003C\u002Fstrong> workload-aware allocation to case workers, with skills and conflicts respected.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Work:\u003C\u002Fstrong> information requests, internal consultations, notes and deadlines.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Decision:\u003C\u002Fstrong> a structured decision with its rationale, approved where policy requires.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Communication:\u003C\u002Fstrong> notifications and letters to the applicant or customer.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Appeal or reopen:\u003C\u002Fstrong> a linked case with its full history.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Reporting:\u003C\u002Fstrong> backlog, ageing, service levels and outcomes.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2>Where AI helps\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Document intelligence:\u003C\u002Fstrong> extract fields from submitted documents and check completeness before a case reaches a person.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Classification and routing:\u003C\u002Fstrong> suggest case type and priority, with the suggestion recorded.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Case summaries:\u003C\u002Fstrong> a short, current summary at the top of every case, so a new case worker doesn't reread forty pages.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Similar-case retrieval:\u003C\u002Fstrong> find precedents and relevant policy passages with citations.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Drafting:\u003C\u002Fstrong> propose decision letters and information requests for the case worker to edit.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Where it must not\u003C\u002Fh2>\n\u003Cp>AI never makes the decision in consequential cases. It doesn't deny, approve or close on its own. The workflow puts human checkpoints at every decision, records who decided, and keeps AI-generated text visibly marked until a person accepts it. In the public sector, this is about legitimacy as much as risk: citizens are entitled to an accountable decision-maker.\u003C\u002Fp>\n\u003Ch2>Controls designed in\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Role-based access to sensitive case data\u003C\u002Fli>\n\u003Cli>Conflict-of-interest checks on assignment\u003C\u002Fli>\n\u003Cli>A complete audit history of every change, view and decision\u003C\u002Fli>\n\u003Cli>Retention and disclosure rules configured per case type\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Integrations\u003C\u002Fh2>\n\u003Cp>Citizen or customer portals, national identity and SSO, document management, CRM or registry systems, payment systems for fees, and messaging services.\u003C\u002Fp>\n\u003Ch2>Where it applies\u003C\u002Fh2>\n\u003Cp>Government and public services, financial services complaints and disputes, insurance claims triage, HR case management and enterprise service teams. The foundation is the same, and the domain vocabulary and policies are configured.\u003C\u002Fp>\n\u003Ch2>First scope\u003C\u002Fh2>\n\u003Cp>One case type with a real backlog. Measure time to first touch, time to decision and backlog ageing before and after. Scope it in a \u003Ca href=\"\u002Fservices\u002Fsolution-definition-sprint\">Solution Definition Sprint\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>See \u003Ca href=\"\u002Findustries\u002Fgovernment-public-sector\">government and public sector\u003C\u002Fa>, explore the \u003Ca href=\"\u002Fatlas\">Atlas\u003C\u002Fa>, or \u003Ca href=\"\u002Fcontact\">bring us your backlog\u003C\u002Fa>.\u003C\u002Fp>\n","AI-assisted case management: summaries, triage and human decisions","Case management across government services and enterprise operations: intake, triage, assignment, decisions and appeals, with AI assisting.",[16,14,45,58,15],"2026-07-16T00:00:00.000Z",1790080513538]