Court, Municipal, and License Clerks
43-4031.00Median wage $48,700/yr179,750 employed (US)Rank #110 of 923 scored · top 12% by substitution
Perform clerical duties for courts of law, municipalities, or governmental licensing agencies and bureaus. May prepare docket of cases to be called; secure information for judges and court; prepare draft agendas or bylaws for town or city council; answer official correspondence; keep fiscal records and accounts; issue licenses or permits; and record data, administer tests, or collect fees.
Sub-scores
0–100 · band = confidence interval from rater disagreement
Substitution45
Exposure49
Augmentation67
Substitution — the headline: capability discounted by cost, barriers and adoption.
Exposure — technical capability alone, regardless of whether anyone deploys it.
Augmentation — how much AI assists without replacing. High here + moderate substitution = a changing job, not a disappearing one.
Tasks on the substitution scale
30 rated tasks, binned by substitution score.
Position among all scored occupations
Distribution of 923 occupation scores; the marker is this occupation.
Tasks with substitution ≥ 70
10%
Run 1.0.0-draft.1 · computed 2026-08-05 · rater panel: claude-sonnet-5, claude-haiku-4-5-20251001 · intervals span rater disagreement.
Why this score
The five weighted dimensions of the composite, averaged across this occupation's tasks (importance-weighted, panel mean). Exact weights and formulas: /api/v1/methodology.
Task automatabilityw 35%51
panel mean rating 3.0/5 → substitution pressure 51/100
Technical feasibility todayw 20%44
panel mean rating 2.8/5 → substitution pressure 44/100
Cost vs. human wagew 15%55
panel mean rating 3.2/5 → substitution pressure 55/100
Adoption barriersw 20%inverted — strong barriers lower the score40
panel mean rating 3.4/5 (barrier strength) → substitution pressure 40/100
Sector adoption velocityw 10%26
panel mean rating 2.1/5 → substitution pressure 26/100
Task breakdown (30 tasks)
Substitution pressure per task, weighted by O*NET importance in the composite. Expand a task for the full rater audit trail — every rating, every model, every rationale.
Code information on license applications for entry into computers.
84CI 81–87 · exposure 91 · augmentation 88 · importance 4.4/5 · click for rater detail
Code information on license applications for entry into computers.
84| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 4/5 | Government and municipal agencies have steadily adopted RPA and document-processing automation for license and permit applications over the past 5–10 years, with measurable displacement of clerical data-entry roles. Adoption is significant and accelerating in digitized public administration. |
| Sector adoption velocity | claude-sonnet-5 | 3/5 | Government and municipal offices adopt automation more slowly than private-sector finance/tech, though document digitization initiatives are increasingly common. |
| Augmentation potential | claude-haiku-4-5-20251001 | 4/5 | AI systems assist human clerks by pre-populating forms, flagging ambiguities, and catching common errors before database entry, substantially raising their throughput and accuracy. The human remains in the loop to resolve exceptions and validate batches, amplifying productivity. |
| Augmentation potential | claude-sonnet-5 | 5/5 | AI-assisted data extraction and validation tools significantly speed up clerks' review and entry work, letting them focus on exceptions and quality checks. |
| Task automatability | claude-haiku-4-5-20251001 | 5/5 | Coding structured information from license applications into computers is a core data-entry task highly amenable to automation. Current OCR and form-processing AI (including RPA and document-understanding models) can reliably extract and map application data to database fields with >50% time savings and high accuracy on standardized forms. |
| Task automatability | claude-sonnet-5 | 5/5 | Extracting structured fields from license applications and entering them into a database is a well-defined data entry/classification task that current OCR plus AI form-processing systems handle with high time savings. |
| Adoption barriers | claude-haiku-4-5-20251001 | 2/5 | Few hard regulatory or legal barriers prevent automation of routine data coding; no license is required to automate coding, and most jurisdictions do not mandate human review of the coding itself. Organizational inertia and customer preference for human oversight exist but are weak barriers compared to safety-critical tasks. |
| Adoption barriers | claude-sonnet-5 | 2/5 | No licensing requirement for who codes data, but government systems often have procurement, security, and legacy IT integration friction along with occasional need for human verification of accuracy. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 4/5 | AI-powered document processing and data entry automation costs a fraction of human clerk wages per application coded. Inference and integration overhead are modest for high-volume processing, making the cost ratio heavily favorable to AI automation. |
| Cost vs. human wage | claude-sonnet-5 | 5/5 | Automated document coding via OCR/AI is extremely cheap per transaction compared to a clerk's loaded wage for manual data entry. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 4/5 | Deployed products (document processing platforms, RPA tools, form-recognition APIs) perform this task reliably in production for structured license application data. Some edge cases and manual review oversight remain common, preventing a full 5, but many jurisdictions already use such systems operationally. |
| Technical feasibility today | claude-sonnet-5 | 4/5 | Intelligent document processing and data capture products (e.g., government forms automation, RPA with OCR/NLP) are deployed in production for permit and license processing, though some edge cases still require human review. |
Perform general office duties, such as taking or transcribing dictation, typing or proofreading correspondence, distributing or filing official forms, or scheduling appointments.
73CI 70–76 · exposure 75 · augmentation 88 · importance 4.2/5 · click for rater detail
Perform general office duties, such as taking or transcribing dictation, typing or proofreading correspondence, distributing or filing official forms, or scheduling appointments.
73| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 3/5 | Government and municipal offices typically lag private sector adoption due to legacy systems, budget constraints, and risk aversion. Pilots and small-scale implementations exist, but production-wide displacement of clerks remains patchy and slow across the sector. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Government and court administrative offices are typically slow adopters of AI due to procurement cycles, legacy systems, and compliance concerns, despite exceptions in general admin support tools. |
| Augmentation potential | claude-haiku-4-5-20251001 | 4/5 | AI substantially augments clerk productivity on each subtask: speech recognition and auto-transcription reduce manual typing burden, proofreading tools catch errors in real time, and automated scheduling handles routine appointment coordination. A human clerk using these tools can handle significantly higher volume. |
| Augmentation potential | claude-sonnet-5 | 5/5 | AI dictation, proofreading, and scheduling tools already substantially boost clerical productivity while humans retain oversight and handle judgment-based filing decisions. |
| Task automatability | claude-haiku-4-5-20251001 | 4/5 | Most of these subtasks—transcription, typing, proofreading, filing, and scheduling—can be substantially automated with current tools (speech-to-text, LLMs, document management systems, calendar APIs). End-to-end time savings of 50%+ are achievable with minimal manual oversight, though some quality assurance and exception handling may remain. |
| Task automatability | claude-sonnet-5 | 4/5 | Transcription, typing, proofreading, and scheduling are largely text/administrative tasks well within current AI capabilities, with speech-to-text and document tools offering major time savings, though filing physical forms and system-specific workflows still need human handling. |
| Adoption barriers | claude-haiku-4-5-20251001 | 2/5 | Court and municipal environments often have data sensitivity and archival requirements that slow adoption, and some jurisdictions require human sign-off on official filings. However, no hard legal barrier mandates a human clerk perform typing or transcription itself, and many organizations already use automated systems. |
| Adoption barriers | claude-sonnet-5 | 2/5 | Some official filings may require certified accuracy or specific clerical authorization within court systems, but most general office duties (drafting, scheduling) carry no licensing requirement. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 5/5 | The all-in cost of AI transcription, proofreading, and scheduling is orders of magnitude cheaper than the loaded hourly wage of a clerk ($25–40k/year salary + benefits), even accounting for oversight and error correction. |
| Cost vs. human wage | claude-sonnet-5 | 4/5 | AI transcription and drafting tools cost a small fraction of clerical wages per unit of output, though oversight and system integration keep this from being a 10x+ reduction. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 4/5 | Deployed products reliably handle transcription (Otter.ai, Google Docs Voice Typing), document drafting and proofreading (Grammarly, Claude, ChatGPT), and calendar management (Calendly, Gmail scheduling). These are production-ready in many organizations, though integration into legacy court systems may introduce friction. |
| Technical feasibility today | claude-sonnet-5 | 4/5 | Mature products (transcription services, Office/Google Suite AI features, scheduling assistants) are deployed at scale across offices today, though full integration into court-specific case management systems remains partial. |
Issue various permits and licenses, such as marriage, fishing, hunting, and dog licenses, and collect appropriate fees.
71CI 67–74 · exposure 75 · augmentation 75 · click for rater detail
Issue various permits and licenses, such as marriage, fishing, hunting, and dog licenses, and collect appropriate fees.
71| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 4/5 | Municipal government and local services have accelerated digital automation over the past decade, with online permitting and license portals now common in mid-to-large jurisdictions. Smaller municipalities lag, but the trend toward automation is clear and measurable in public systems. |
| Sector adoption velocity | claude-sonnet-5 | 3/5 | Government administrative offices are historically slower adopters of automation than private-sector professional services, though e-government and self-service kiosks have made meaningful inroads for permit issuance over the past decade. |
| Augmentation potential | claude-haiku-4-5-20251001 | 4/5 | AI-assisted systems can dramatically improve clerk productivity by auto-populating forms, flagging missing information, validating eligibility criteria, and routing complex cases for human review. This human-in-the-loop approach is already deployed in many permitting systems and enhances the clerk's efficiency without full replacement. |
| Augmentation potential | claude-sonnet-5 | 4/5 | AI-driven forms, chatbots, and automated payment/verification systems significantly speed up clerks' processing of applications and reduce manual data entry, even where a human remains involved for exceptions or approvals. |
| Task automatability | claude-haiku-4-5-20251001 | 4/5 | Most of this task—verification of applicant eligibility, fee calculation, form filling, and license generation—can be fully automated through existing systems. The primary remaining manual element is collecting fees, though this integrates with payment systems. A well-configured automation could achieve well over 50% time savings at equal quality. |
| Task automatability | claude-sonnet-5 | 4/5 | Issuing standardized permits/licenses and collecting fees is largely a data-entry, verification, and payment-processing workflow that online portals and automated systems already handle for most jurisdictions, though some edge cases require human judgment (e.g., verifying eligibility documents). |
| Adoption barriers | claude-haiku-4-5-20251001 | 3/5 | While there are no hard legal requirements that a licensed human must issue these permits, municipal governance, public accountability, and fee handling create moderate friction. Many jurisdictions are cautious about full automation without human oversight, and some fees still require human collection or verification of unique circumstances (e.g., objections, special waivers). |
| Adoption barriers | claude-sonnet-5 | 3/5 | While no license technically requires a human signature for most permits, government processes often mandate identity verification, legal recordkeeping, and in some cases in-person appearance (e.g., marriage licenses in some states), creating moderate regulatory and procedural friction. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 5/5 | Once initial software is deployed, marginal per-transaction costs are negligible (server time, minimal oversight). A single clerk might serve hundreds or thousands of transactions monthly, while an automated system serves them at near-zero variable cost. This represents at least an order of magnitude savings. |
| Cost vs. human wage | claude-sonnet-5 | 4/5 | Automated online portals and payment processing systems cost far less per transaction than a human clerk processing the same paperwork manually, though initial system setup and occasional human oversight add some cost. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 4/5 | Many municipalities already deploy automated permit and license issuance systems (online portals, kiosks, integrated management software). These systems reliably handle routine cases at scale, though some jurisdictions still rely on manual processing or hybrid approaches. Production deployment is common but not universal. |
| Technical feasibility today | claude-sonnet-5 | 4/5 | Many municipalities already deploy online licensing/permitting systems (e.g., DMV, fishing/hunting license portals, marriage license applications) that process routine issuance and fee collection reliably at scale, though full automation without any staff review is not universal. |
Prepare meeting agendas or packets of related information.
67CI 60–74 · exposure 70 · augmentation 75 · importance 4.5/5 · click for rater detail
Prepare meeting agendas or packets of related information.
67| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 2/5 | Court and municipal clerk offices are predominantly in the public sector with slower IT budgets, legacy systems, and organizational inertia. While some progressive jurisdictions pilot workflow automation, widespread production adoption remains limited and slow compared to private-sector information work. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Local government administrative offices are typically slow adopters of AI tools due to budget constraints, legacy software, and procurement processes, despite the task's straightforward nature. |
| Augmentation potential | claude-haiku-4-5-20251001 | 4/5 | AI can draft agendas, collate documents, flag missing items, and auto-format packets in real time, allowing clerks to focus on verification, legal compliance checks, and stakeholder coordination. This significantly raises clerk productivity while the human retains control over accuracy and authority. |
| Augmentation potential | claude-sonnet-5 | 4/5 | AI drafting tools can meaningfully speed up agenda writing, summarizing supporting documents, and organizing packets, while a human clerk still finalizes and verifies compliance. |
| Task automatability | claude-haiku-4-5-20251001 | 4/5 | AI can reliably extract agenda items, compile related documents, format packets, and generate agenda summaries with minimal human oversight. Current LLMs and document automation tools handle 80%+ of this task with little setup, achieving the ≥50% time-saving bar for routine, standardized packets. |
| Task automatability | claude-sonnet-5 | 4/5 | Compiling agendas and assembling related documents into packets is largely a formatting/organization task that current AI (drafting tools plus document assembly) can do with substantial time savings, though final verification of accuracy and completeness still requires a human check. |
| Adoption barriers | claude-haiku-4-5-20251001 | 3/5 | Some municipalities require human review and sign-off on official meeting materials for liability and accuracy, and public-sector procurement and IT governance can slow automation adoption. However, no strict legal mandate prevents AI from generating the underlying packet content if a human supervises. |
| Adoption barriers | claude-sonnet-5 | 2/5 | No licensing requirement to prepare agendas, but government transparency laws (open meetings acts) often require accurate compliance with specific procedural and notice requirements, creating moderate liability sensitivity around errors. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 5/5 | Once a template or workflow is configured, AI inference cost per packet is trivial (pennies), while clerk labor for assembly, formatting, and copying is measured in hours at typical loaded wages ($25–$50/hour). AI achieves 50–100x cost reduction per task. |
| Cost vs. human wage | claude-sonnet-5 | 4/5 | Once integrated with a records/agenda management system, AI-assisted drafting and packet assembly is much cheaper per unit output than clerical staff time spent formatting and compiling documents manually. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 4/5 | Mature products (document automation platforms, LLM-based workflow tools, and content management systems) already prepare agendas and information packets in production for many organizations. Some error rates exist in edge cases (complex legal references, multi-document cross-linking), but core functionality is deployable and demonstrated at scale. |
| Technical feasibility today | claude-sonnet-5 | 3/5 | Products exist (AI drafting assistants, document automation, agenda-generation templates integrated with meeting/records software) but are not universally deployed in municipal clerk offices, and current systems still require human review of legal notices and formatting compliance. |
Record and edit the minutes of meetings and distribute to appropriate officials or staff members.
66CI 65–67 · exposure 75 · augmentation 100 · importance 4.6/5 · click for rater detail
Record and edit the minutes of meetings and distribute to appropriate officials or staff members.
66| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 2/5 | Court and municipal clerk functions are traditionally conservative, risk-averse institutions with older IT infrastructure and strict compliance cultures. While some pilot adoption of transcription tools exists, deep production deployment in these sectors lags tech and finance. |
| Sector adoption velocity | claude-sonnet-5 | 3/5 | Government and municipal offices are historically slower adopters of AI tools than private-sector professional services, though transcription-assisted minutes are increasingly common in pilot and limited production use. |
| Augmentation potential | claude-haiku-4-5-20251001 | 5/5 | AI transcription and summarization dramatically accelerates a clerk's ability to produce accurate, complete minutes: real-time drafts, speaker identification, keyword extraction, and auto-distribution all enhance human productivity. The clerk remains the final authority on accuracy and compliance. |
| Augmentation potential | claude-sonnet-5 | 5/5 | AI transcription and drafting tools dramatically speed up minute preparation and editing while the clerk remains responsible for verification, formatting, and distribution. |
| Task automatability | claude-haiku-4-5-20251001 | 4/5 | Recording, transcribing, and distributing meeting minutes is substantially automatable with current AI: speech-to-text, meeting summarization, and auto-distribution workflows can handle the core work. However, editing for accuracy, legal compliance, and institutional conventions typically requires human review, preventing a clean 5. |
| Task automatability | claude-sonnet-5 | 4/5 | AI transcription plus LLM summarization/editing can turn recorded meetings into accurate, formatted minutes with substantial time savings, though final review for accuracy and formal compliance still needed. |
| Adoption barriers | claude-haiku-4-5-20251001 | 3/5 | No legal mandate requires a human to record minutes, but municipal and court contexts often have procedural rules around accuracy, authenticity, and record retention that create organizational friction. Some jurisdictions or institutions may require human sign-off on official minutes. |
| Adoption barriers | claude-sonnet-5 | 3/5 | Official meeting minutes often require certification by a designated clerk and may be subject to open-records/public-meeting laws, creating moderate procedural and legal friction against full automation. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 4/5 | AI transcription and distribution services cost pennies to dollars per meeting, while a clerk's loaded wage for the same task is typically $20–40+/hour. The all-in cost (inference + distribution + light oversight) is roughly one to two orders of magnitude cheaper than hiring a human for routine minutes. |
| Cost vs. human wage | claude-sonnet-5 | 4/5 | Subscription AI transcription/summarization tools cost a few dollars per meeting versus hours of clerical staff time, yielding roughly an order-of-magnitude cost reduction. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 4/5 | Deployed products (Otter.ai, Fireflies, Microsoft Teams transcription) reliably capture and distribute meeting transcripts at scale. Summarization and formatting are increasingly reliable, though accuracy on names, terminology, and legal specifics still benefits from human oversight in production. |
| Technical feasibility today | claude-sonnet-5 | 4/5 | Products like Otter.ai, Microsoft Teams/Zoom AI note-takers, and government-specific minute-taking tools are deployed in production and widely used by clerks and municipalities today. |
Perform record checks on past or current licensees, as required by investigations.
66CI 60–71 · exposure 70 · augmentation 75 · importance 4.3/5 · click for rater detail
Perform record checks on past or current licensees, as required by investigations.
66| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 3/5 | Government and licensing agencies are mid-stage in digitization and AI adoption; pilots are common in larger jurisdictions, but production deployment remains spotty and slower than private sector. Small municipal courts lag significantly. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Government administrative offices are generally slow adopters of AI due to legacy IT systems, procurement cycles, and public-sector risk aversion. |
| Augmentation potential | claude-haiku-4-5-20251001 | 4/5 | AI can rapidly surface relevant records, flag patterns, and organize historical data, allowing clerks to focus on interpretation and investigation direction rather than manual searching. The human investigator's judgment is sharpened and accelerated by AI-assisted retrieval. |
| Augmentation potential | claude-sonnet-5 | 4/5 | AI can quickly flag discrepancies, pull relevant historical records, and pre-populate investigation reports, substantially speeding up the clerk's review while the clerk verifies and finalizes. |
| Task automatability | claude-haiku-4-5-20251001 | 4/5 | AI can retrieve and cross-reference licensee records from databases, check regulatory histories, and flag discrepancies with high accuracy. The task requires pattern matching and data lookup—both routine for AI—though final judgment on investigation relevance may require human oversight, limiting full autonomy. |
| Task automatability | claude-sonnet-5 | 4/5 | Record checks against structured databases are largely a lookup/matching task that current AI and automation systems handle well, especially when integrated with existing government databases.4/5 reflects some residual need for judgment on ambiguous or incomplete records. |
| Adoption barriers | claude-haiku-4-5-20251001 | 3/5 | Licensing records are public, but access may require proper authorization and audit trails for regulatory compliance. Organizational friction around changing workflows and human verification of investigation findings exists, but no legal mandate requires a human to perform the lookup itself. |
| Adoption barriers | claude-sonnet-5 | 3/5 | No licensing requirement to perform the check itself, but government recordkeeping, data privacy rules, and chain-of-custody/audit requirements for investigations create moderate procedural friction. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 5/5 | Database queries and record retrieval via AI cost pennies to dollars per check, versus tens of dollars in loaded labor cost for a clerk to manually search and cross-reference records. The cost advantage is at least an order of magnitude. |
| Cost vs. human wage | claude-sonnet-5 | 4/5 | Automated database queries and matching are extremely cheap relative to clerk labor once integration is built, though initial setup and legacy system integration costs are nontrivial. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 4/5 | Document retrieval, record matching, and regulatory database queries are mature in production legal and compliance systems. Deployed e-discovery and compliance platforms routinely perform record checks; minor errors in edge cases remain, but core functionality is proven and reliable at scale. |
| Technical feasibility today | claude-sonnet-5 | 3/5 | Some jurisdictions use automated background/license check systems, but many rely on legacy, siloed databases requiring manual cross-referencing, so deployed reliable products vary widely in coverage. |
Question applicants to obtain required information, such as name, address, or age, and record data on prescribed forms.
61CI 51–71 · exposure 62 · augmentation 75 · importance 4.6/5 · click for rater detail
Question applicants to obtain required information, such as name, address, or age, and record data on prescribed forms.
61| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 3/5 | Government agencies and courts have adopted intake automation moderately, with pilots and legacy systems common but full replacement lagging due to regulatory caution and bureaucratic inertia; private licensing bodies have moved faster. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Government and municipal offices are typically slow adopters of AI due to legacy systems, procurement cycles, and compliance requirements, lagging behind private-sector information services. |
| Augmentation potential | claude-haiku-4-5-20251001 | 4/5 | AI can significantly assist clerks by auto-populating forms, flagging missing fields, and suggesting standardized responses, allowing humans to focus on complex cases and verification rather than routine data entry. |
| Augmentation potential | claude-sonnet-5 | 4/5 | AI-assisted form pre-fill, OCR for ID scanning, and chat-based intake significantly speed up data collection and reduce clerical errors while a human remains available for verification and edge cases. |
| Task automatability | claude-haiku-4-5-20251001 | 4/5 | Current AI can reliably extract and record structured personal information from applicants via conversational interfaces or form-filling agents, achieving significant time savings. However, edge cases (name ambiguities, address verification, age validation across different document types) still require occasional human review, preventing a perfect 5. |
| Task automatability | claude-sonnet-5 | 3/5 | Structured intake of standard fields (name, address, age) can largely be handled by chatbots or digital forms, but in-person verification, ID checking, and handling edge cases still require human judgment, capping full automation at present.5 |
| Adoption barriers | claude-haiku-4-5-20251001 | 3/5 | Government clerking roles face moderate barriers: some jurisdictions have identity-verification or legal-signing requirements that mandate human involvement, and organizational resistance to eliminating entry-level positions creates friction despite technical feasibility. |
| Adoption barriers | claude-sonnet-5 | 3/5 | Some jurisdictions require in-person verification or notarized/legally binding submissions, and government processes often have procedural and legal requirements slowing automation, though no strict licensure mandates a human for basic data intake. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 5/5 | AI-driven intake automation costs a fraction of human clerk wages per application processed, with minimal oversight overhead once systems are deployed and tuned, easily achieving an order-of-magnitude cost reduction. |
| Cost vs. human wage | claude-sonnet-5 | 4/5 | Automated form-filling and chatbot intake systems are markedly cheaper than staffing a clerk for simple data collection, though integration with legacy government systems and identity verification adds cost. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 4/5 | Deployed chatbots and intelligent form-filling systems already handle routine intake in many government and commercial settings, capturing name, address, age reliably at scale. Production systems exist but occasionally require human intervention for clarification or validation of uncommon cases. |
| Technical feasibility today | claude-sonnet-5 | 3/5 | Many government offices already use online forms and kiosks for intake, but fully autonomous conversational agents handling applicant Q&A with document verification are not yet standard in court/license clerk settings. |
Record case dispositions, court orders, or arrangements made for payment of court fees.
59CI 50–69 · exposure 66 · augmentation 75 · importance 4.6/5 · click for rater detail
Record case dispositions, court orders, or arrangements made for payment of court fees.
59| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 2/5 | Courts and government agencies are among the slowest adopters of automation due to legacy system lock-in, budgetary constraints, and organizational resistance. While pilot programs exist, production deployment at scale remains limited relative to private-sector clerical automation. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Government and judicial systems are historically slow technology adopters, with modernization of court record systems proceeding unevenly and often lagging private-sector AI adoption. |
| Augmentation potential | claude-haiku-4-5-20251001 | 4/5 | AI draft-completion and auto-population of forms significantly assist clerks in checking accuracy and handling high volumes, reducing manual transcription. The human remains essential for validating complex dispositions and exceptional cases, but productivity per clerk rises measurably. |
| Augmentation potential | claude-sonnet-5 | 4/5 | AI can meaningfully assist clerks by auto-populating fields, flagging inconsistencies, and drafting entries from court proceedings, significantly speeding up the underlying task while a human verifies accuracy. |
| Task automatability | claude-haiku-4-5-20251001 | 4/5 | AI can reliably extract and record case dispositions and court order information from structured court documents, transcripts, or input forms with high accuracy. The primary constraint is integration with legacy court management systems and validating against existing case records, which adds modest overhead but does not prevent substantial time savings. |
| Task automatability | claude-sonnet-5 | 4/5 | Recording structured case data (dispositions, orders, fee arrangements) into court systems is largely a data entry/transcription task that current AI (OCR, NLP extraction, structured data pipelines) can perform with substantial time savings, though final entries often require verification against legal records. |
| Adoption barriers | claude-haiku-4-5-20251001 | 3/5 | Court systems are quasi-public and subject to audit and record-keeping regulations, creating oversight and validation requirements that slow adoption. However, no license or mandatory human sign-off is legally required for this clerical task, only internal procedural controls. |
| Adoption barriers | claude-sonnet-5 | 4/5 | Court records are legal documents requiring accuracy and often statutory certification by authorized clerks, creating liability and procedural barriers to full automation without human sign-off. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 5/5 | Automated data extraction and record entry cost pennies per transaction in inference and integration, compared to a clerk's hourly wage. Even after overhead for oversight and system maintenance, AI is an order of magnitude cheaper. |
| Cost vs. human wage | claude-sonnet-5 | 4/5 | Automated data extraction and entry tools are inference-cheap compared to clerk wages, though integration with disparate legal case management systems adds some ongoing cost. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 4/5 | Deployed products (document processing, RPA, court management system integrations) perform this task in production at multiple jurisdictions; error rates are low on structured inputs. Some variance exists across jurisdictions' document formats, but mature systems handle the common patterns reliably. |
| Technical feasibility today | claude-sonnet-5 | 2/5 | Some court case management systems use automated docketing and e-filing integration, but fully autonomous recording of dispositions and fee arrangements into official court records is not yet a mature, widely deployed product across jurisdictions. |
Issue public notification of all official activities or meetings.
57CI 55–60 · exposure 66 · augmentation 63 · importance 4.6/5 · click for rater detail
Issue public notification of all official activities or meetings.
57| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 2/5 | Government and court systems are slow adopters of automation; legacy systems, bureaucratic procurement, and risk-aversion mean that notification automation remains rare in production even where technically feasible. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Government and municipal offices are generally slow adopters of AI due to procurement cycles, legal compliance concerns, and limited IT budgets, resulting in low observed deployment despite technical feasibility. |
| Augmentation potential | claude-haiku-4-5-20251001 | 3/5 | AI can assist by drafting notice templates, auto-populating meeting details, and suggesting publication channels, reducing clerk data-entry time. However, human verification of legal compliance and final approval remain necessary given the compliance risk. |
| Augmentation potential | claude-sonnet-5 | 4/5 | AI can significantly speed up drafting, formatting, and multi-channel distribution of notices, letting clerks focus on verification and compliance, providing strong augmentation even where full automation is not yet adopted. |
| Task automatability | claude-haiku-4-5-20251001 | 4/5 | Notification generation from meeting schedules/agenda data is straightforward document production; AI can draft and format notices at scale. The primary friction is ensuring legal compliance with jurisdiction-specific notice requirements and integrating with court/municipal systems, but the core text generation is highly automatable. |
| Task automatability | claude-sonnet-5 | 4/5 | Drafting and distributing standard public notices (meeting agendas, hearing notices) is templated, formulaic text generation well within current LLM and workflow-automation capabilities, though final posting/verification steps require some oversight. |
| Adoption barriers | claude-haiku-4-5-20251001 | 4/5 | Legal liability is material: incorrect or non-compliant public notice can void proceedings or expose the jurisdiction to litigation. Regulatory statutes often specify exact notice content, timing, and publication methods. A human clerk typically must review and sign off, creating a legal checkpoint. |
| Adoption barriers | claude-sonnet-5 | 3/5 | Many jurisdictions have statutory requirements about how and when public notices must be issued (e.g., open meetings laws), requiring an authorized clerk to certify or sign off, creating moderate legal/procedural barriers to full automation. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 4/5 | Once integrated, AI-driven notification systems have minimal per-notice marginal cost (inference + system maintenance), far cheaper than paying a clerk to manually format and distribute notices for dozens of meetings monthly. |
| Cost vs. human wage | claude-sonnet-5 | 4/5 | Generating and distributing standardized notices via AI/automation is very cheap compared to clerical staff time, though minor human review keeps it from being a full order-of-magnitude savings in all cases. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 3/5 | Document automation and email/publication systems exist and are used in some municipalities, but integration with legacy court management systems and legal oversight requirements mean production deployment remains partial and narrow-scoped. Most jurisdictions still rely on manual clerk processes. |
| Technical feasibility today | claude-sonnet-5 | 3/5 | Government CMS and notification software exist and some agencies use automated publishing tools, but most clerks still manually draft and post notices due to statutory formatting and verification requirements, so deployed end-to-end AI solutions are limited. |
Record and maintain all vital and fiscal records and accounts.
57CI 43–71 · exposure 62 · augmentation 75 · importance 4.6/5 · click for rater detail
Record and maintain all vital and fiscal records and accounts.
57| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 3/5 | Municipal and government sectors are slower to adopt automation than private information services, with many smaller jurisdictions still using manual or semi-manual record-keeping. Larger municipalities and states have deployed record-management automation, but broad, deep adoption remains uneven. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Government and municipal offices are historically slow adopters of new technology due to budget constraints, procurement cycles, and legacy systems, resulting in uneven and gradual automation. |
| Augmentation potential | claude-haiku-4-5-20251001 | 4/5 | AI-powered document capture, duplicate detection, and error flagging significantly enhance a clerk's ability to maintain accurate records at scale, allowing them to focus on exceptions, legal compliance, and quality assurance rather than manual data entry and filing. |
| Augmentation potential | claude-sonnet-5 | 4/5 | AI-assisted data entry, automated indexing, and error-flagging tools meaningfully speed up and improve accuracy of record maintenance while clerks retain oversight and final responsibility. |
| Task automatability | claude-haiku-4-5-20251001 | 4/5 | Current AI systems can reliably capture, classify, and file vital and fiscal records with high accuracy, and workflow automation tools can maintain accounts and flag discrepancies. While some judgment calls and exceptions require human oversight, the core recording and maintenance functions can achieve well over 50% time savings with existing RPA and document-processing systems. |
| Task automatability | claude-sonnet-5 | 3/5 | Structured data entry, indexing, and basic record maintenance can be largely automated with document processing and database tools, but variability in source documents and exception handling still require human oversight, so full end-to-end automation is only partial. |
| Adoption barriers | claude-haiku-4-5-20251001 | 3/5 | Municipal records often carry legal retention and audit requirements, and many jurisdictions mandate human sign-off on vital records for compliance reasons. However, AI can perform the bulk of recording and maintenance work, with human review as a final gate rather than a barrier to automation itself. |
| Adoption barriers | claude-sonnet-5 | 4/5 | Vital and fiscal records often carry legal recordkeeping requirements, chain-of-custody and audit standards, and jurisdiction-specific statutes that mandate authorized personnel handle or certify these records. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 5/5 | AI-driven document processing, storage, and account maintenance cost a small fraction of a full-time clerk's loaded wage, especially once integrated with existing systems; scaling cost per record approaches zero after initial setup. |
| Cost vs. human wage | claude-sonnet-5 | 3/5 | Software licensing, integration with legacy government IT systems, and required human review/audit narrow the cost advantage compared to fully manual clerking, though at scale it can still be somewhat cheaper. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 4/5 | Deployed products (document management systems, RPA platforms, and AI-powered OCR with classification) demonstrably handle vital and fiscal record capture and maintenance in government and municipal settings today, though integration with legacy municipal systems and occasional accuracy issues on poor-quality documents create modest friction. |
| Technical feasibility today | claude-sonnet-5 | 3/5 | Records management systems with OCR, workflow automation, and integrated databases are widely deployed in government offices, but accuracy on messy vital records and legacy paper systems still requires human verification. |
Evaluate information on applications to verify completeness and accuracy and to determine whether applicants are qualified to obtain desired licenses.
53CI 37–69 · exposure 58 · augmentation 75 · importance 4.7/5 · click for rater detail
Evaluate information on applications to verify completeness and accuracy and to determine whether applicants are qualified to obtain desired licenses.
53| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 2/5 | Court and municipal clerk roles are in smaller government offices with lower digitization rates and slower IT procurement cycles. While some progressive jurisdictions have modernized intake, adoption remains uneven and lags private-sector information work. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Public sector agencies, especially at municipal/court level, are historically slow adopters of AI due to procurement cycles, legacy IT, and regulatory caution. |
| Augmentation potential | claude-haiku-4-5-20251001 | 4/5 | AI can dramatically assist clerks by pre-populating summaries, flagging missing documents, highlighting discrepancies, and routing complex cases for human review. This accelerates the human's work and reduces errors, even in a human-in-the-loop model. |
| Augmentation potential | claude-sonnet-5 | 4/5 | AI can meaningfully speed up initial application review by flagging missing information, inconsistencies, or likely disqualifying factors for a human clerk to confirm. |
| Task automatability | claude-haiku-4-5-20251001 | 4/5 | The task of verifying completeness, checking accuracy against documents, and cross-referencing with qualification criteria is highly structured and rule-based. Current AI systems can extract information from forms, validate against explicit requirements, and flag discrepancies at scale, achieving substantial time savings. However, edge cases involving judgment calls or ambiguous qualification interpretations may still require human review. |
| Task automatability | claude-sonnet-5 | 3/5 | AI can check applications for completeness and cross-reference basic eligibility rules, but final qualification determinations often involve nuanced judgment, discretion, and legal accountability that current systems cannot fully replicate end-to-end. |
| Adoption barriers | claude-haiku-4-5-20251001 | 3/5 | Government agencies face some organizational friction and change-management resistance, and there may be nominal audit/sign-off requirements for license decisions. However, there is no legal mandate that a human clerk must personally perform the verification; automation is permissible with oversight. |
| Adoption barriers | claude-sonnet-5 | 4/5 | Licensing decisions are governmental functions often requiring statutory authority, accountability, and appeals processes, meaning a human typically must be the official decision-maker or signatory. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 5/5 | Once a document processing and rule-checking system is deployed, per-application cost is orders of magnitude lower than a full-time clerk. Inference is cheap, and integration overhead is amortized across thousands of applications annually, making the ratio highly favorable. |
| Cost vs. human wage | claude-sonnet-5 | 3/5 | Automated document verification and rule-checking can be cheap to run, but integration with legacy government systems and required human oversight narrows the cost advantage compared to a clerk's wage. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 4/5 | Production systems for document processing and form validation (OCR, rule-based verification, workflow automation) are deployed in government and licensing agencies today. Platforms like UiPath and Blue Prism handle similar intake workflows reliably. Some integration complexity exists around legacy systems, but the core task is routinely automated in mature organizations. |
| Technical feasibility today | claude-sonnet-5 | 2/5 | Some government workflow tools use rules engines and OCR/document extraction to flag missing fields, but few jurisdictions deploy AI to autonomously determine license eligibility in production at scale. |
Coordinate or maintain office tracking systems for correspondence or follow-up actions.
52CI 44–60 · exposure 58 · augmentation 75 · importance 4.0/5 · click for rater detail
Coordinate or maintain office tracking systems for correspondence or follow-up actions.
52| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 2/5 | Municipal government is among the slowest sectors to adopt AI and RPA, with most adoption still in pilots rather than production; budget constraints and legacy system lock-in slow widespread implementation despite technical feasibility. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Public sector and court administration are historically slow adopters of automation due to budget constraints, procurement cycles, and legacy systems, despite the task's technical automatability. |
| Augmentation potential | claude-haiku-4-5-20251001 | 4/5 | AI-driven workflow systems and intelligent routing can substantially raise clerk productivity by automating routine flagging, reminding, and routing of correspondence, allowing humans to focus on exceptions and judgment calls while maintaining full loop control. |
| Augmentation potential | claude-sonnet-5 | 4/5 | AI-powered tracking dashboards, automated reminders, and smart categorization can significantly boost clerk productivity while humans retain oversight of exceptions and judgment calls. |
| Task automatability | claude-haiku-4-5-20251001 | 3/5 | Coordinating and maintaining correspondence tracking systems involves repetitive record-keeping and data management tasks that can be partially automated (e.g., email sorting, filing, status updates), but the task requires judgment about priority, follow-up timing, and decision-making that current AI systems handle inconsistently without significant human oversight. |
| Task automatability | claude-sonnet-5 | 4/5 | Tracking correspondence and follow-up actions is largely structured data management and status monitoring, which AI-enabled workflow and case-management systems can automate with moderate setup and integration. |
| Adoption barriers | claude-haiku-4-5-20251001 | 3/5 | Municipal offices face regulatory requirements around records retention, accessibility standards, and legal compliance that impose configuration and oversight friction; however, there is no hard legal requirement that a licensed human must personally coordinate these systems. |
| Adoption barriers | claude-sonnet-5 | 3/5 | No licensing requirement for this administrative task, but government procurement rules, data security requirements, and legacy IT infrastructure create moderate organizational friction. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 2/5 | AI solutions (RPA, document management platforms) have meaningful setup, integration, and ongoing maintenance costs that often approach or exceed the salary of a clerk performing routine coordination work, especially for smaller municipal offices. |
| Cost vs. human wage | claude-sonnet-5 | 4/5 | Automated tracking software and AI-assisted scheduling tools cost far less per transaction than clerical labor once implemented, though initial integration with government systems adds cost. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 3/5 | Document management and workflow automation products exist in production (e.g., enterprise content management systems, RPA for routine filing), but they typically require substantial configuration and human oversight to handle the nuance of municipal correspondence rules and exceptions. |
| Technical feasibility today | claude-sonnet-5 | 3/5 | Workflow automation and CRM/case-tracking tools with reminders and status dashboards are widely deployed, but many court/municipal offices still rely on legacy systems requiring manual entry and oversight, limiting reliability at scale. |
Instruct parties about timing of court appearances.
51CI 25–76 · exposure 50 · augmentation 63 · importance 4.1/5 · click for rater detail
Instruct parties about timing of court appearances.
51| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 2/5 | Court systems are notoriously slow adopters of technology; most still rely on paper and phone calls, and initiatives to automate clerk functions remain pilots rather than widespread production deployments. |
| Sector adoption velocity | claude-sonnet-5 | 3/5 | Government/court administration is a slower-adopting public sector; some jurisdictions use automated reminders but many still rely on clerks and paper notices, so adoption is uneven and moderate. |
| Augmentation potential | claude-haiku-4-5-20251001 | 3/5 | AI could usefully draft standard instruction templates or check docket data for clerks, speeding up their work, but the human clerk remains necessary to navigate case-specific nuances, address party concerns, and ensure accuracy. |
| Augmentation potential | claude-sonnet-5 | 4/5 | AI-driven scheduling assistants and automated reminder systems significantly reduce clerk workload for routine notifications while clerks remain available to handle exceptions and answer questions. |
| Task automatability | claude-haiku-4-5-20251001 | 2/5 | While AI could generate standardized timing information, the task requires responsive interaction with parties who may ask follow-up questions, have complex scheduling conflicts, or need clarification—elements that demand human judgment and adaptability beyond simple information retrieval. |
| Task automatability | claude-sonnet-5 | 4/5 | Communicating scheduling information (dates, times, locations) is a highly structured, templated task that automated notification systems and chatbots can handle with minimal quality loss, though some edge cases need human clarification. |
| Adoption barriers | claude-haiku-4-5-20251001 | 4/5 | Courts are government entities with strict procedural rules, and instructions about court appearances carry legal weight—liability for a party missing a deadline due to AI error is high, and many jurisdictions require human accountability and verification of critical instructions. |
| Adoption barriers | claude-sonnet-5 | 2/5 | No strict licensing requirement to relay scheduling info, but courts have procedural rules about official notice and some liability concerns if automated notices are wrong or missed, creating moderate friction. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 2/5 | Building and maintaining a reliable court-integrated AI system costs significant capital and ongoing oversight; the clerk wage is modest enough that automation savings, if any, are offset by integration, error liability, and fallback staffing. |
| Cost vs. human wage | claude-sonnet-5 | 5/5 | Automated notification and scheduling systems cost a small fraction of a clerk's time per notification once built, offering large savings at scale. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 2/5 | Chatbots and IVR systems exist for basic court scheduling information, but they rarely handle the full complexity of instructing parties (different case types, docket variations, exceptions), and most courts still rely on human clerks for reliable, accurate delivery in production settings. |
| Technical feasibility today | claude-sonnet-5 | 4/5 | Automated court reminder systems (SMS, IVR, email notifications) are already deployed in many court systems and DMV/license offices to notify parties of appearance dates, though live-agent phone instruction still occurs for complex cases. |
Answer inquiries from the general public regarding judicial procedures, court appearances, trial dates, adjournments, outstanding warrants, summonses, subpoenas, witness fees, or payment of fines.
49CI 46–51 · exposure 50 · augmentation 75 · importance 4.5/5 · click for rater detail
Answer inquiries from the general public regarding judicial procedures, court appearances, trial dates, adjournments, outstanding warrants, summonses, subpoenas, witness fees, or payment of fines.
49| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 2/5 | Court systems are notoriously slow to adopt new technologies due to legacy IT infrastructure, budget constraints, and risk-averse organizational culture. While a few large urban courts pilot chatbots, widespread production deployment remains rare; this is a laggard sector. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Court systems are notoriously slow to modernize, often underfunded and reliant on legacy systems, resulting in patchy chatbot/IVR deployment despite some urban court pilots. |
| Augmentation potential | claude-haiku-4-5-20251001 | 4/5 | AI can substantially assist clerks by pre-drafting responses, retrieving relevant procedures and dates, checking databases, and flagging cases that need escalation, allowing human staff to focus on complex or sensitive inquiries and case exceptions. This augmentation model is highly deployable and raises productivity significantly. |
| Augmentation potential | claude-sonnet-5 | 4/5 | AI-powered knowledge bases, chat assistants, and automated case lookups can significantly speed up clerks' ability to answer routine questions while they remain available for complex or sensitive cases. |
| Task automatability | claude-haiku-4-5-20251001 | 3/5 | AI can automate significant portions of answering routine inquiries about court procedures, trial dates, and payments through chatbots or FAQ systems, but complex cases requiring interpretation of specific legal documents or warrant lookups may require human oversight. The task likely involves 30–50% of work that is repetitive and information-retrieval focused, meeting a partial automation threshold. |
| Task automatability | claude-sonnet-5 | 3/5 | Many routine inquiries (trial dates, fee schedules, general procedures) can be answered by chatbots/IVR systems, but complex or ambiguous cases involving warrants, subpoenas, or fines often require case-specific record lookups and judgment, limiting full end-to-end automation. |
| Adoption barriers | claude-haiku-4-5-20251001 | 4/5 | Courts are government entities with strict procedural requirements, liability concerns (incorrect warrant or fee information can cause harm), and regulatory oversight. Most courts require a human clerk sign-off or in-person verification for sensitive inquiries; public-facing automation faces institutional friction and legal risk mitigation mandates. |
| Adoption barriers | claude-sonnet-5 | 3/5 | No licensing requirement to answer these inquiries, but courts have due-process concerns, error liability (e.g., wrong warrant info), and public-facing government service expectations that slow full automation. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 4/5 | A modern chatbot or AI agent can handle inquiries at a fraction of the cost of a full-time clerk (labor cost ~$35–40k/year; AI inference and oversight per transaction is pennies). The ratio favors automation substantially, though integration and maintenance of accurate data systems add overhead. |
| Cost vs. human wage | claude-sonnet-5 | 4/5 | Automated phone/chat systems and self-service portals are dramatically cheaper per inquiry than staffing clerks for repetitive questions, though integration with case management systems adds some cost. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 3/5 | Deployed products (court-provided chatbots, AI-driven FAQ systems) exist and handle basic inquiries reliably, but material gaps remain in handling edge cases, accessing real-time court databases accurately, and explaining nuanced procedural rules. Production deployments are narrower in scope than full task coverage. |
| Technical feasibility today | claude-sonnet-5 | 3/5 | Court call centers and websites increasingly use chatbots and automated case-lookup portals, but accuracy on nuanced legal questions is inconsistent and many jurisdictions still route callers to human clerks for verification. |
Prepare dockets or calendars of cases to be called.
47CI 34–60 · exposure 53 · augmentation 63 · click for rater detail
Prepare dockets or calendars of cases to be called.
47| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 2/5 | Court systems are typically low-digitization, change-averse organizations with slow IT procurement cycles; while some jurisdictions pilot case management systems, production AI adoption for critical docket functions remains minimal. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Government and court systems are typically slow adopters of new technology due to budget constraints, legacy systems, and procurement processes, despite the task being technically automatable. |
| Augmentation potential | claude-haiku-4-5-20251001 | 3/5 | AI can usefully assist clerks by auto-generating initial docket drafts, flagging scheduling conflicts, and organizing cases by type or judge, meaningfully raising productivity while the clerk retains responsibility for final review and certification. |
| Augmentation potential | claude-sonnet-5 | 4/5 | AI and case management software already substantially assist clerks by auto-populating docket entries and flagging scheduling conflicts, significantly speeding up the human-led process. |
| Task automatability | claude-haiku-4-5-20251001 | 3/5 | Current AI systems can automatically extract case information, organize it chronologically, and generate formatted dockets with moderate setup, achieving partial time savings. However, tasks like resolving scheduling conflicts, handling last-minute changes, and ensuring legal compliance typically still require human oversight, preventing full end-to-end automation at production quality. |
| Task automatability | claude-sonnet-5 | 4/5 | Preparing dockets from case data is a structured data-organization task—scheduling, sorting, and formatting information—that off-the-shelf software plus AI scheduling tools can largely automate given access to case management systems. |
| Adoption barriers | claude-haiku-4-5-20251001 | 4/5 | Court systems are governed by strict procedural rules, case management system requirements, and liability concerns around docket accuracy; many jurisdictions require a licensed court officer or clerk to certify dockets, creating a hard procedural barrier to full automation. |
| Adoption barriers | claude-sonnet-5 | 3/5 | Court operations often require procedural accuracy and accountability, and some jurisdictions mandate clerk certification or sign-off, creating moderate institutional and legal friction to full automation. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 2/5 | Integration of AI for docket preparation requires custom setup for court systems, ongoing human oversight to catch errors, and compliance validation—costs that offset the relatively modest wage of court clerks performing this routine task. |
| Cost vs. human wage | claude-sonnet-5 | 4/5 | Automated docketing software is inexpensive to run at scale compared to clerical staff hours spent manually compiling and formatting case lists. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 2/5 | While document processing and scheduling tools exist, no mature production system reliably handles the full complexity of court docket preparation—which involves court-specific rules, precedent handling, and real-time coordination across multiple court systems. Most implementations remain narrow or require significant manual intervention. |
| Technical feasibility today | claude-sonnet-5 | 3/5 | Many court case management systems already auto-generate docket lists, but full integration across jurisdictions with varying rules and exceptions still requires human review, so reliability varies by system maturity. |
Perform administrative tasks, such as answering telephone calls, filing court documents, or maintaining office supplies or equipment.
46CI 39–52 · exposure 50 · augmentation 50 · importance 4.7/5 · click for rater detail
Perform administrative tasks, such as answering telephone calls, filing court documents, or maintaining office supplies or equipment.
46| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 2/5 | Court systems are notoriously slow adopters of technology, with many still using paper-based workflows and legacy systems; pilot projects are common but production AI automation remains rare in most jurisdictions. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Government and court offices are typically slow adopters of AI systems due to legacy IT, budget constraints, and procurement processes, placing this in a laggard-sector pattern. |
| Augmentation potential | claude-haiku-4-5-20251001 | 3/5 | Document management and search tools can meaningfully assist clerks in locating and organizing filings, and IVR can handle routine inquiries, freeing human time for complex cases and relationship maintenance. |
| Augmentation potential | claude-sonnet-5 | 3/5 | AI can meaningfully assist with call handling scripts, document search/filing suggestions, and inventory tracking reminders, improving clerk efficiency on parts of the task while humans still manage the mixed workflow. |
| Task automatability | claude-haiku-4-5-20251001 | 3/5 | Telephone answering and basic filing can be partially automated (IVR, document management systems), but the human judgment required to route inquiries, manage complex document workflows, and maintain organizational knowledge limits end-to-end automation to roughly half the effort with significant setup. |
| Task automatability | claude-sonnet-5 | 3/5 | Answering phones and filing can be substantially automated with call-routing bots and document-management systems, but maintaining supplies/equipment requires physical action that isn't automatable by software alone; overall roughly half the bundle meets the time-saving bar. |
| Adoption barriers | claude-haiku-4-5-20251001 | 4/5 | Court systems are heavily regulated and often require human attestation for document filing and records management; legal liability for misfiling or miscommunication creates high error costs, and organizational inertia in government IT adoption presents substantial friction. |
| Adoption barriers | claude-sonnet-5 | 2/5 | No strict licensing requirement blocks automating phone/filing tasks, though court administrative processes may have procedural rules and public-service expectations creating some friction. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 2/5 | Integration and ongoing oversight of automation systems for court administration require significant operational overhead; the cost advantage over a clerk's wage is modest when accounting for compliance, error correction, and the hybrid human-AI workflow still needed. |
| Cost vs. human wage | claude-sonnet-5 | 3/5 | Automated phone triage and digital filing systems are cheaper per interaction than a clerk, but integration, oversight, and the physical components of the task keep overall costs roughly comparable rather than dramatically lower. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 3/5 | Document management and IVR systems exist in production court systems, but error rates in routing and document classification remain material, and many courts still rely on manual processes due to legacy systems and regulatory constraints. |
| Technical feasibility today | claude-sonnet-5 | 3/5 | Deployed IVR/chatbot systems and e-filing/document indexing tools exist in many courts, but they handle narrow slices reliably while complex caller inquiries and physical inventory tasks still require humans. |
Answer questions or provide advice to the public regarding licensing policies, procedures, or regulations.
38CI 25–51 · exposure 38 · augmentation 63 · importance 4.5/5 · click for rater detail
Answer questions or provide advice to the public regarding licensing policies, procedures, or regulations.
38| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 2/5 | Government agencies adopt automation slowly due to budget constraints, change-management inertia, and legal caution; pilot chatbots for FAQs exist, but deep production displacement in municipal licensing remains minimal. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Public sector adoption of AI is generally slower than private sector due to budget constraints, procurement cycles, and risk aversion, though some municipalities have begun piloting chatbots. |
| Augmentation potential | claude-haiku-4-5-20251001 | 3/5 | AI can assist clerks by drafting answers to common questions, surfacing relevant regulations, and flagging policy gaps, improving human productivity in handling routine inquiries while the clerk retains responsibility for accuracy and edge cases. |
| Augmentation potential | claude-sonnet-5 | 4/5 | AI can significantly speed up clerks' ability to retrieve accurate policy information and draft responses, letting them handle more inquiries with human oversight for edge cases. |
| Task automatability | claude-haiku-4-5-20251001 | 2/5 | While AI can retrieve and summarize licensing information from structured documents, the task requires contextual judgment, clarification of ambiguous situations, and accurate application of regulations to specific cases—functions that current systems struggle with reliably at the 50% time-saving threshold without significant human oversight. |
| Task automatability | claude-sonnet-5 | 3/5 | AI chatbots can answer routine, well-documented licensing FAQs, but many inquiries require judgment on edge cases, exceptions, or verification against records that a system must be carefully configured to handle accurately. |
| Adoption barriers | claude-haiku-4-5-20251001 | 4/5 | Licensing advice often requires a human to be legally responsible for accuracy; municipalities typically retain human clerks to ensure compliance, and liability for incorrect guidance creates strong organizational and regulatory friction against full automation. |
| Adoption barriers | claude-sonnet-5 | 3/5 | No strict licensing requirement to answer procedural questions, but government liability concerns, accuracy requirements for legal/regulatory info, and public preference for human confirmation create moderate friction. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 2/5 | Integration costs, continuous updates for changing regulations, and oversight requirements to catch errors push the all-in cost close to or above that of entry-level clerical staff, especially accounting for reputational and legal risk. |
| Cost vs. human wage | claude-sonnet-5 | 4/5 | Once built and maintained, an AI system answering routine licensing questions costs far less per interaction than staff time, though initial setup, content curation, and oversight add cost. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 2/5 | Chatbots can answer simple FAQ-style licensing questions, but deployed products lack the reliability and legal accountability needed for real-world licensing advice; error rates remain material, and jurisdictions vary widely in regulations, limiting scalable products. |
| Technical feasibility today | claude-sonnet-5 | 3/5 | Government chatbots and virtual assistants are deployed in many jurisdictions for licensing/permit Q&A, but error rates and scope limitations mean staff routinely handle escalations and complex questions. |
Prepare documents recording the outcomes of court proceedings.
38CI 34–43 · exposure 45 · augmentation 75 · importance 4.4/5 · click for rater detail
Prepare documents recording the outcomes of court proceedings.
38| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 2/5 | Court systems are traditionally conservative, slow-moving, and fragmented across many jurisdictions with varying procedures. While some digital modernization is happening, production AI adoption for document preparation remains limited and experimental rather than widespread. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Government court systems are notoriously slow to adopt new technology due to procurement cycles, legacy infrastructure, and legal caution, placing this among laggard-sector adoption patterns. |
| Augmentation potential | claude-haiku-4-5-20251001 | 4/5 | AI can substantially assist clerks by drafting templates, auto-populating standard fields, and flagging inconsistencies in outcomes, meaningfully raising their productivity while the human remains responsible for accuracy and legal compliance. |
| Augmentation potential | claude-sonnet-5 | 4/5 | AI can meaningfully speed up drafting, formatting, and populating standard court outcome documents, letting clerks focus on verification and legal compliance rather than manual composition. |
| Task automatability | claude-haiku-4-5-20251001 | 3/5 | AI can assist with generating draft documents and transcribing court outcomes from audio or notes, potentially saving 30–50% of time on straightforward cases. However, complex proceedings, legal nuances, and jurisdiction-specific formatting requirements require human verification and judgment. |
| Task automatability | claude-sonnet-5 | 3/5 | AI can draft and populate standardized court outcome documents from structured inputs (dockets, judge notes) with significant time savings, but final entries require verification against legal accuracy and jurisdictional formatting rules, limiting full end-to-end automation today. |
| Adoption barriers | claude-haiku-4-5-20251001 | 4/5 | Court records have high regulatory requirements, audit trails, and legal standing; many jurisdictions mandate human clerks sign and certify records. Liability for errors in court documents is severe, and courts operate under strict procedural rules that limit algorithmic substitution. |
| Adoption barriers | claude-sonnet-5 | 4/5 | Court records are legally significant documents often requiring clerk certification, adherence to procedural rules, and accountability for accuracy, creating substantial regulatory and liability barriers to full automation. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 2/5 | While AI inference is cheap, the cost of integration into court management systems, oversight, and correcting errors for legal documents is substantial. The full all-in cost remains close to or slightly higher than a clerk's loaded wage for the critical quality assurance step. |
| Cost vs. human wage | claude-sonnet-5 | 3/5 | Where digital court records and structured data exist, AI-assisted drafting is cheaper than manual clerk work, but integration with legacy court IT systems and required human review narrows the cost advantage. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 3/5 | Products exist for document generation and court transcription (e.g., court reporting software with AI features), but they operate with meaningful error rates and typically require human review and correction before finalization. No fully autonomous end-to-end solution is reliably deployed at scale in most jurisdictions. |
| Technical feasibility today | claude-sonnet-5 | 2/5 | Some court case management systems include templated auto-generation features, but reliable production-grade AI drafting of outcome documents integrated with live proceedings is narrow and not widely deployed across most court systems. |
Respond to requests for information from the public, other municipalities, state officials, or state and federal legislative offices.
35CI 23–48 · exposure 38 · augmentation 63 · importance 4.1/5 · click for rater detail
Respond to requests for information from the public, other municipalities, state officials, or state and federal legislative offices.
35| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 1/5 | Municipal government is a laggard sector in AI adoption. Court and licensing clerks work in small organizations with legacy systems, and public agencies face regulatory and liability concerns that slow pilot-to-production transitions. Observed adoption remains minimal. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Local government is generally a slow-adopting sector for AI due to budget constraints, procurement processes, and legacy IT systems, despite some pilot chatbot programs. |
| Augmentation potential | claude-haiku-4-5-20251001 | 3/5 | AI can assist clerks by drafting responses to common queries, retrieving relevant records, and flagging missing information, thereby raising their productivity. However, the human must review, verify accuracy, and sign off on responses, so augmentation is partial rather than transformative. |
| Augmentation potential | claude-sonnet-5 | 4/5 | AI can draft responses, look up information, and triage inquiries, significantly speeding up clerks' work while they retain oversight for accuracy and sensitive matters. |
| Task automatability | claude-haiku-4-5-20251001 | 2/5 | While AI can draft responses to routine information requests, the diversity of inquiries (spanning municipal records, licensing status, legislative matters) and the need for accurate, jurisdiction-specific answers means significant human judgment and verification remain necessary. Current systems lack the reliability to handle this end-to-end without substantial oversight. |
| Task automatability | claude-sonnet-5 | 3/5 | Many routine informational requests (hours, procedures, form locations, status lookups) can be handled by AI chatbots or automated systems, but complex or legally sensitive inquiries still require human judgment and record access. |
| Adoption barriers | claude-haiku-4-5-20251001 | 4/5 | High barriers exist: responses to public inquiries and state officials carry legal accountability; incorrect information can expose municipalities to liability. Accuracy requirements, document authentication, and the need for a human-accountable record-keeper create significant friction against full automation. |
| Adoption barriers | claude-sonnet-5 | 3/5 | No strict licensing requirement for answering public inquiries, but public records rules, data privacy, liability for inaccurate government information, and preference for human contact create moderate friction. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 2/5 | AI inference is cheap, but integration into municipal record systems, compliance oversight, and error-checking by trained staff mean total cost remains close to or exceeds the wage of a clerk handling routine inquiries. The need for human verification limits cost advantage. |
| Cost vs. human wage | claude-sonnet-5 | 3/5 | Chatbot/AI systems are cheap per routine query, but integration with legacy government records systems, oversight, and handling escalations add costs that narrow the gap versus clerk wages. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 2/5 | No deployed product reliably handles the full scope of municipal information responses across all request types and jurisdictions. AI can assist with drafting, but production systems do not yet independently manage the accuracy and specificity required for official public information requests. |
| Technical feasibility today | claude-sonnet-5 | 3/5 | Government chatbots and virtual assistants are deployed in many municipalities for FAQs, but they handle only a subset of requests reliably and often escalate complex cases to humans. |
Research information in the municipal archives upon request of public officials or private citizens.
32CI 23–43 · exposure 33 · augmentation 63 · importance 3.8/5 · click for rater detail
Research information in the municipal archives upon request of public officials or private citizens.
32| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 1/5 | Municipal government and court systems are historically slow to digitize and automate; many archives remain paper-based or partially digitized. Adoption of AI for archive research is minimal in practice, with most jurisdictions still relying on clerks to navigate legacy systems and provide certified information. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Local government IT adoption is historically slow, underfunded, and heterogeneous across municipalities, resulting in limited and uneven AI deployment for archival research tasks. |
| Augmentation potential | claude-haiku-4-5-20251001 | 3/5 | AI-powered search and indexing tools can help clerks quickly locate candidate documents in digital collections and flag potentially relevant records, raising their productivity. However, the need for clerks to verify results and interpret context limits the transformative impact to a support role rather than full augmentation of the core task. |
| Augmentation potential | claude-sonnet-5 | 4/5 | AI search and document analysis tools can significantly speed up locating and summarizing relevant archival material, meaningfully boosting clerk productivity even without full automation. |
| Task automatability | claude-haiku-4-5-20251001 | 2/5 | While AI can search and retrieve text documents from digital archives, municipal research typically requires navigating non-standardized filing systems, interpreting ambiguous legal language, and applying contextual judgment about which historical records satisfy specific requests. Current AI systems cannot reliably handle the end-to-end task of understanding nuanced requests, locating appropriate materials in mixed-format archives, and validating findings without substantial human oversight. |
| Task automatability | claude-sonnet-5 | 3/5 | Retrieval and synthesis of archival records can be partially automated with search/RAG systems, but many municipal archives are unindexed, handwritten, or paper-only, requiring human verification and physical retrieval, limiting full automation. |
| Adoption barriers | claude-haiku-4-5-20251001 | 4/5 | Municipal clerks often hold official, licensed positions with statutory duties to maintain and provide accurate archival information to the public and government officials. The legal accountability for information accuracy, combined with public-trust requirements and the need for human certification of records, creates substantial barriers to full automation. |
| Adoption barriers | claude-sonnet-5 | 3/5 | No strict licensing requirement to search records, but data privacy, chain-of-custody, and accuracy/legal-reliance concerns create moderate institutional friction requiring human oversight. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 2/5 | AI document search and retrieval costs are modest, but the need for human oversight, correction of incomplete or incorrect results, and manual handling of non-digital records means total cost per successful task completion remains comparable to or higher than a clerk's labor, especially factoring integration overhead. |
| Cost vs. human wage | claude-sonnet-5 | 3/5 | Where records are digitized, AI-assisted search is much cheaper than a clerk's time, but overall cost is comparable once accounting for digitization, verification, and handling exceptions/physical archives. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 2/5 | No production systems reliably perform comprehensive municipal archive research autonomously. Document retrieval tools exist but require clean, digitized, well-indexed collections and struggle with paper records, microfiche, and non-standard metadata common in municipal archives. Deployed products work only in narrow, pre-structured scenarios with human validation still necessary. |
| Technical feasibility today | claude-sonnet-5 | 2/5 | Some digital government records systems allow keyword search and AI-assisted lookup, but most municipal archives are not fully digitized or standardized, so deployed products handle only a narrow slice reliably. |
Prepare and issue orders of the court, such as probation orders, release documentation, sentencing information, or summonses.
31CI 25–37 · exposure 33 · augmentation 63 · importance 4.4/5 · click for rater detail
Prepare and issue orders of the court, such as probation orders, release documentation, sentencing information, or summonses.
31| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 2/5 | Court systems are typically conservative, legacy-system-heavy organizations with slow digitization. While some jurisdictions pilot case management automation, actual automation of order preparation remains limited and heavily vetted. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Court systems are typically slow-moving, underfunded, and bound by legacy IT and procedural requirements, resulting in limited and uneven AI adoption compared to fast-moving private sectors. |
| Augmentation potential | claude-haiku-4-5-20251001 | 3/5 | AI can assist with template population, formatting, and flagging missing case information, meaningfully reducing clerk time on routine document preparation while maintaining human control over accuracy and legal compliance. |
| Augmentation potential | claude-sonnet-5 | 4/5 | AI-assisted templates and drafting tools can meaningfully speed up preparation of routine orders and documentation, letting clerks review and finalize rather than draft from scratch. |
| Task automatability | claude-haiku-4-5-20251001 | 2/5 | While document generation and formatting are automatable, orders require specific case details, judge signatures, official seals, and compliance with jurisdiction-specific legal templates. Current AI cannot reliably handle the full end-to-end task including verification against court records and legal compliance without substantial human oversight. |
| Task automatability | claude-sonnet-5 | 3/5 | Generating standardized court documents from templates and case data is largely mechanical, but requires accurate integration with case management systems and correct legal formatting that still needs verification. |
| Adoption barriers | claude-haiku-4-5-20251001 | 4/5 | Court orders must be issued by authorized court personnel and typically require judicial or clerk sign-off. There are strict legal requirements for authentication, jurisdictional rules, and liability for errors in court documents, creating substantial regulatory and authorization barriers. |
| Adoption barriers | claude-sonnet-5 | 4/5 | Court orders are legally binding documents often requiring clerk certification, judicial signature, or specific statutory procedures, creating significant procedural and liability barriers to full automation. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 2/5 | Current AI document systems require significant integration, legal compliance verification, and human oversight that approaches or exceeds the cost of a clerk preparing the document directly, especially given liability concerns. |
| Cost vs. human wage | claude-sonnet-5 | 3/5 | Document automation software can reduce clerical time significantly, but implementation, integration with court systems, and mandatory human oversight keep costs from being an order of magnitude lower. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 2/5 | Document generation tools exist, but no deployed product reliably handles the complete task of preparing legally compliant court orders with proper case-specific content, formatting, and authentication. Products are research-stage or require extensive customization and human review. |
| Technical feasibility today | claude-sonnet-5 | 2/5 | Some court systems use e-filing and document automation software, but fully autonomous generation and issuance of legal orders without clerk review is not a mature, widely deployed practice. |
Prepare ordinances, resolutions, or proclamations so that they can be executed, recorded, archived, or distributed.
30CI 23–37 · exposure 33 · augmentation 63 · importance 4.5/5 · click for rater detail
Prepare ordinances, resolutions, or proclamations so that they can be executed, recorded, archived, or distributed.
30| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 1/5 | Municipal government is a traditionally low-digitization sector with risk-averse procurement practices and limited IT infrastructure. Adoption of AI for ordinance preparation is minimal; most municipalities use established precedent files and templates managed by human clerks, with slow pilot activity. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Local government offices are traditionally slow adopters of AI due to budget constraints, legal caution, and low digitization compared to private sector professional services. |
| Augmentation potential | claude-haiku-4-5-20251001 | 3/5 | AI can assist by drafting initial text from templates, flagging formatting inconsistencies, or suggesting statutory cross-references, raising a clerk's productivity on routine portions. However, the need for substantive legal and jurisdictional review means augmentation is limited to clerical and organizational sub-tasks rather than transformative. |
| Augmentation potential | claude-sonnet-5 | 4/5 | AI can meaningfully speed up drafting, formatting, and proofreading of ordinances and resolutions, letting clerks focus on legal review, distribution, and archival steps. |
| Task automatability | claude-haiku-4-5-20251001 | 2/5 | Preparing ordinances requires understanding legal language, jurisdiction-specific formatting, and approval workflows. While AI can draft text and apply templates, the legal consequences of errors and the need for human review of each ordinance's substantive content mean current systems cannot achieve 50% time savings end-to-end without significant human oversight that negates the time savings. |
| Task automatability | claude-sonnet-5 | 3/5 | AI can draft, format, and structure ordinances/resolutions from templates and prior examples, but final preparation requires verifying legal accuracy, proper citations, and procedural compliance that still needs human review. |
| Adoption barriers | claude-haiku-4-5-20251001 | 4/5 | Municipal ordinances and proclamations typically require execution and certification by authorized officials (city clerk, mayor, or council); errors carry legal liability. Many jurisdictions have statutory requirements that a licensed clerk or attorney review and attest to proper form, creating hard barriers to full automation. |
| Adoption barriers | claude-sonnet-5 | 4/5 | Official government documents often require certified clerks to prepare, sign, or attest to accuracy, and there are legal recordkeeping and authentication requirements that create meaningful barriers to full automation. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 2/5 | AI-assisted document drafting tools have modest subscription costs, but the requirement for specialized legal review and iterative human refinement means the all-in cost (AI tool subscription plus expert human labor) remains comparable to or exceeds having a clerk prepare ordinances from templates and precedent without AI assistance. |
| Cost vs. human wage | claude-sonnet-5 | 3/5 | AI drafting assistance can reduce time spent on formatting and boilerplate language, but human legal/clerical review and certification remain necessary, keeping overall costs only moderately lower than fully manual work. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 2/5 | No deployed product reliably performs full ordinance preparation independently. Document assembly tools exist for simple forms, but municipal ordinances involve complex legal language, statutory cross-references, and jurisdiction-specific requirements that current AI systems handle inconsistently and typically require expert human revision. |
| Technical feasibility today | claude-sonnet-5 | 2/5 | Generic drafting tools and document automation exist, but no widely deployed product specifically handles municipal ordinance preparation end-to-end with the required legal formatting and jurisdiction-specific rules reliably. |
Perform budgeting duties, such as assisting in budget preparation, expenditure review, or budget administration.
28CI 25–30 · exposure 25 · augmentation 63 · importance 4.4/5 · click for rater detail
Perform budgeting duties, such as assisting in budget preparation, expenditure review, or budget administration.
28| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 2/5 | Municipal and court systems are historically slow adopters of automation due to budget constraints, legacy systems, and risk-aversion; while some larger cities have modernized financial systems, penetration of AI-driven budgeting remains limited and largely pilot-stage. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Municipal government is a traditionally slow-adopting sector for AI due to procurement cycles, budget constraints, and risk-aversion, resulting in limited production deployment for this specific task. |
| Augmentation potential | claude-haiku-4-5-20251001 | 3/5 | AI can usefully assist by automating data collection, generating preliminary variance reports, and surfacing budget anomalies, allowing clerks to focus on analysis and stakeholder coordination; however, the assistance is narrower than in purely analytical domains due to the compliance-heavy nature of the work. |
| Augmentation potential | claude-sonnet-5 | 4/5 | AI tools can meaningfully assist with data analysis, variance detection, drafting budget narratives, and forecasting, significantly speeding up parts of the budgeting workflow while humans retain final control. |
| Task automatability | claude-haiku-4-5-20251001 | 2/5 | Budgeting involves structured financial calculations and data entry that AI could partially automate (spreadsheet population, basic variance analysis), but requires human judgment on policy priorities, resource allocation trade-offs, and organizational constraints that current AI cannot reliably navigate end-to-end. |
| Task automatability | claude-sonnet-5 | 2/5 | Budget preparation and expenditure review require judgment, contextual knowledge of municipal priorities, and coordination with stakeholders that current AI cannot fully replicate end-to-end, though data compilation and calculation portions could be automated. |
| Adoption barriers | claude-haiku-4-5-20251001 | 4/5 | Municipal budgeting is governed by state and federal regulatory frameworks, audit requirements, and transparency laws that often mandate human sign-off and accountability; decision-making authority typically cannot be delegated to automated systems without explicit legal revision. |
| Adoption barriers | claude-sonnet-5 | 3/5 | Budget administration in government settings often requires accountability to elected officials, audit trails, and sometimes statutory sign-off, creating moderate organizational and procedural barriers to full automation. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 2/5 | AI-based budget tools and spreadsheet automation exist but still require significant human oversight, data validation, and judgment; the all-in cost (tool licensing, integration, clerical oversight) is likely comparable to or exceeds the cost of a clerk performing parts of these duties. |
| Cost vs. human wage | claude-sonnet-5 | 2/5 | While AI tools can cheaply generate reports or flag variances, the human review, judgment, and accountability required for budget administration keep overall costs comparable to human labor once oversight is factored in. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 2/5 | While AI can assist with data aggregation and routine report generation, no deployed product reliably handles the full cycle of budget preparation and administration in municipal contexts, which require domain expertise, regulatory compliance, and stakeholder engagement that products do not yet demonstrably achieve at scale. |
| Technical feasibility today | claude-sonnet-5 | 2/5 | Spreadsheet automation and financial software with AI-assisted forecasting exist, but no deployed product autonomously handles municipal budget administration reliably without significant human oversight. |
Train other workers or coordinate their work, as necessary.
28CI 25–30 · exposure 25 · augmentation 50 · importance 3.9/5 · click for rater detail
Train other workers or coordinate their work, as necessary.
28| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 2/5 | Adoption of AI in court and administrative clerk roles remains limited; training and coordination are among the least digitized functions in these sectors. Most organizations still rely on in-person or manual oversight of worker training. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Government clerical offices are generally slow adopters of AI, with limited deployment of AI-based training or coordination systems compared to private-sector professional services. |
| Augmentation potential | claude-haiku-4-5-20251001 | 3/5 | AI could assist by generating training outlines, flagging scheduling conflicts, tracking worker performance metrics, and drafting coordination messages, raising clerical productivity in training administration. However, human judgment and interpersonal presence remain central to effective training delivery. |
| Augmentation potential | claude-sonnet-5 | 3/5 | AI can help create training materials, answer procedural questions, and support scheduling, providing moderate assistance to a human trainer/coordinator. |
| Task automatability | claude-haiku-4-5-20251001 | 2/5 | Training and coordinating other workers requires dynamic judgment about individual performance, adaptive instruction, and real-time problem-solving. While AI could assist with scheduling or documentation, the interpersonal and contextual elements of effective training and coordination remain largely beyond current automation capabilities. |
| Task automatability | claude-sonnet-5 | 2/5 | Training and coordinating coworkers requires interpersonal leadership, contextual judgment, and adaptive communication that current AI cannot fully replicate end-to-end, though it can assist with materials and scheduling.' |
| Adoption barriers | claude-haiku-4-5-20251001 | 4/5 | Human judgment and direct interaction are deeply embedded in training and coordination roles; workers typically require personalized feedback and real-time guidance that stakeholders expect humans to provide. Organizational norms and employment law around supervision and training typically expect human responsibility. |
| Adoption barriers | claude-sonnet-5 | 3/5 | No strict licensing barrier for training/coordination itself, but organizational norms, supervisory responsibility, and interpersonal trust create moderate friction against full automation. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 2/5 | AI systems could assist with routine scheduling and documentation but cannot replace the human time invested in actual training and coordination. The cost of oversight and correction would likely exceed savings from partial automation. |
| Cost vs. human wage | claude-sonnet-5 | 2/5 | Effective training and coordination still require significant human oversight and interaction, so AI-assisted approaches only marginally reduce costs relative to the human doing the task directly. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 2/5 | No deployed AI products reliably perform end-to-end training and worker coordination in production. Conversational AI might draft training materials or send reminders, but assessing worker competence, adapting instruction, and resolving coordination conflicts requires human judgment that current systems cannot dependably provide. |
| Technical feasibility today | claude-sonnet-5 | 2/5 | AI tools exist for generating training content or scheduling but no deployed product autonomously trains or coordinates clerical staff in real government offices today. |
Search files and contact witnesses, attorneys, or litigants to obtain information for the court.
26CI 23–30 · exposure 25 · augmentation 50 · importance 4.2/5 · click for rater detail
Search files and contact witnesses, attorneys, or litigants to obtain information for the court.
26| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 1/5 | Court systems are notoriously slow to digitize and adopt emerging technology. Most courts still rely on paper files and manual contact processes; AI adoption remains minimal even in progressive jurisdictions. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Court systems are generally slow adopters of AI due to public-sector budget constraints, legal caution, and institutional inertia, with pilots more common than production deployment. |
| Augmentation potential | claude-haiku-4-5-20251001 | 3/5 | AI can assist by rapidly searching case files, surfacing relevant documents, and generating contact lists, moderately improving clerk efficiency. However, the judgment-heavy parts of outreach and information gathering limit transformative potential. |
| Augmentation potential | claude-sonnet-5 | 3/5 | AI can help clerks quickly search case files, draft outreach communications, and summarize case information, meaningfully speeding up parts of this task while humans still manage sensitive contacts. |
| Task automatability | claude-haiku-4-5-20251001 | 2/5 | Searching files can be partially automated through document retrieval systems, but contacting witnesses, attorneys, or litigants requires judgment about appropriateness, timing, and legal standing that current AI cannot reliably handle. The interpersonal coordination and legal nuance prevent end-to-end automation. |
| Task automatability | claude-sonnet-5 | 2/5 | Searching files can be partially automated, but the outbound contacting of witnesses, attorneys, or litigants requires judgment, negotiation, and adaptive communication that current AI cannot fully replace end-to-end. |
| Adoption barriers | claude-haiku-4-5-20251001 | 4/5 | Court operations are highly regulated; clerks are officers of the court with legal standing to contact parties and witnesses. Liability for improper contact, confidentiality rules, and the need for authorized human judgment create substantial barriers to automation. |
| Adoption barriers | claude-sonnet-5 | 3/5 | Court records and communications with parties often have procedural, confidentiality, and due-process requirements that create moderate friction, though clerks are not licensed professionals requiring sign-off like attorneys. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 2/5 | File search automation is cheap, but human oversight of contact outreach and information verification remains necessary, limiting cost savings. The per-task savings do not yet overcome the loaded wage of the clerk due to oversight requirements. |
| Cost vs. human wage | claude-sonnet-5 | 2/5 | AI can cheaply assist with file search, but the human-contact and verification components still require staff time, oversight, and liability management, keeping overall costs comparable to current clerk labor. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 2/5 | While AI can search digital files and generate contact lists, no deployed system reliably performs the full task of obtaining information from contacts while respecting legal constraints and case-specific context. Document retrieval is mature; outreach and judgment are not. |
| Technical feasibility today | claude-sonnet-5 | 2/5 | Document search/retrieval tools exist and are used in legal settings, but no deployed product reliably conducts the full contact-and-information-gathering workflow with litigants or witnesses in court operations today. |
Plan or direct the maintenance, filing, safekeeping, or computerization of all municipal documents.
25CI 25–25 · exposure 25 · augmentation 63 · click for rater detail
Plan or direct the maintenance, filing, safekeeping, or computerization of all municipal documents.
25| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 2/5 | Municipal government is a slow-adopting sector; many municipalities still rely on paper-based or legacy digital systems. While digitization projects occur, they are typically slow, fragmented, and driven by budgetary constraints rather than rapid AI adoption patterns. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Government and municipal offices are typically slow adopters of AI due to budget constraints, legacy systems, and compliance caution, resulting in limited production-level AI adoption. |
| Augmentation potential | claude-haiku-4-5-20251001 | 3/5 | AI can assist clerks by automating document scanning, OCR, and categorization, and by suggesting filing structures based on content. However, the human must retain responsibility for planning, policy decisions, and ensuring legal compliance, so augmentation is useful but partial. |
| Augmentation potential | claude-sonnet-5 | 4/5 | AI-powered document management, search, OCR, and workflow tools can meaningfully speed up filing, retrieval, and organization tasks even while a human clerk retains oversight and directs the process. |
| Task automatability | claude-haiku-4-5-20251001 | 2/5 | While document filing and basic computerization can be partially automated (scanning, OCR, indexing), the planning and direction of a comprehensive document management system requires judgment about retention policies, legal compliance, and organizational workflows. Current AI cannot reliably handle the full planning and oversight function end-to-end with 50% time savings at equal quality. |
| Task automatability | claude-sonnet-5 | 2/5 | Planning and directing document management involves judgment, policy decisions, and coordination across departments that current AI cannot fully replace, though components like digitization and indexing can be automated.' |
| Adoption barriers | claude-haiku-4-5-20251001 | 4/5 | Municipal document management is heavily regulated by record retention laws, public records statutes, and compliance requirements that mandate human authority and accountability. Legal liability for lost or mishandled records creates strong barriers to full automation without explicit human sign-off. |
| Adoption barriers | claude-sonnet-5 | 4/5 | Municipal records often have legal retention, public records law, and chain-of-custody requirements that mandate human accountability and sign-off, creating strong regulatory and liability barriers. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 2/5 | AI solutions for document management (scanning, OCR, storage) have upfront setup costs and ongoing infrastructure expenses that are comparable to or exceed the salary of a clerk handling routine filing, especially when accounting for integration and error correction oversight. |
| Cost vs. human wage | claude-sonnet-5 | 2/5 | While digitization tools are cheap, the managerial oversight, compliance decisions, and record-keeping accountability still require paid human staff time comparable to or exceeding AI tool costs. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 2/5 | Products exist for document scanning, OCR, and basic file management, but no deployed system reliably handles the complete task of planning and directing municipal document maintenance and safekeeping. Existing tools are narrow in scope and require significant human oversight and decision-making. |
| Technical feasibility today | claude-sonnet-5 | 2/5 | Document management software and OCR/digitization tools exist and are used, but the 'plan or direct' managerial aspect is not something deployed AI products handle autonomously in production. |
Perform contract administration duties, assisting with bid openings or the awarding of contracts.
25CI 25–25 · exposure 25 · augmentation 63 · importance 3.8/5 · click for rater detail
Perform contract administration duties, assisting with bid openings or the awarding of contracts.
25| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 2/5 | Municipal and government sectors are laggards in automation adoption due to budget constraints, legacy systems, and rigid procurement regulations. Pilot projects exist, but production deployment of AI-driven contract administration remains rare in local government. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Government and municipal offices are typically slow adopters of AI due to legacy systems, procurement rules, and compliance requirements, with pilots more common than deep deployment. |
| Augmentation potential | claude-haiku-4-5-20251001 | 3/5 | AI can meaningfully assist clerks by flagging compliance issues, summarizing bid documents, and organizing contract metadata, raising their review efficiency. However, the assistance is limited to parts of the workflow; final judgment and legal responsibility remain with human officials. |
| Augmentation potential | claude-sonnet-5 | 4/5 | AI can meaningfully assist by organizing bid documents, flagging compliance issues, summarizing proposals, and tracking deadlines, improving clerk efficiency substantially while humans retain final authority. |
| Task automatability | claude-haiku-4-5-20251001 | 2/5 | While AI can assist with document parsing, compliance checking, and data extraction from contracts and bids, the task requires human judgment on bid evaluation criteria, contract terms negotiation, and discretionary decisions that are rarely fully automatable. End-to-end automation without significant human oversight is not feasible under current conditions. |
| Task automatability | claude-sonnet-5 | 2/5 | The task blends procedural clerical work (document tracking, checklists) with situational judgment, coordination, and public accountability in bid openings, which AI can assist but not fully execute end-to-end today. |
| Adoption barriers | claude-haiku-4-5-20251001 | 4/5 | Contract administration and bid awarding in municipal settings face strong legal and regulatory barriers: authorized municipal officials or licensed professionals often must legally sign off on contracts and bid decisions, and liability for errors falls on the municipality. These hard compliance requirements significantly limit automation. |
| Adoption barriers | claude-sonnet-5 | 4/5 | Public contract awarding is governed by procurement law, transparency requirements, and often requires an authorized human official to open bids and formally award contracts, creating substantial legal/regulatory barriers. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 2/5 | Current AI contract review tools are moderately priced, but integration, customization for municipal procurement rules, and mandatory human oversight add significant costs. The all-in cost is comparable to or potentially higher than a skilled clerk's loaded wage for the nuanced work involved. |
| Cost vs. human wage | claude-sonnet-5 | 2/5 | While AI could cheaply handle data entry and document comparison, the overall task still requires human oversight, verification, and public presence, keeping all-in costs closer to human levels. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 2/5 | AI products exist for contract analysis and document review, but they are typically narrow in scope and require substantial human validation before bid awards or contract execution. No production system reliably performs full contract administration and bid opening without material human intervention and legal review. |
| Technical feasibility today | claude-sonnet-5 | 2/5 | Some procurement software automates parts of bid intake and compliance checking, but no deployed product independently conducts bid openings or awards contracts reliably in production. |
Verify the authenticity of documents, such as foreign identification or immigration documents.
24CI 23–25 · exposure 25 · augmentation 50 · importance 4.6/5 · click for rater detail
Verify the authenticity of documents, such as foreign identification or immigration documents.
24| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 1/5 | Court and municipal clerks work in highly regulated, conservative sectors with low digitization velocity and strict legal accountability. Adoption of autonomous document authentication is negligible; pilots are rare and serious liability concerns slow any movement toward automation. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Government and municipal offices are typically slow adopters of AI due to procurement cycles, regulatory constraints, and legacy systems, resulting in pilot-stage rather than widespread production use. |
| Augmentation potential | claude-haiku-4-5-20251001 | 3/5 | AI can usefully assist by extracting text, flagging inconsistencies, and highlighting security features for human review, reducing clerk effort on routine document comparison and flagging suspicious documents for escalation, but the final judgment remains with the human. |
| Augmentation potential | claude-sonnet-5 | 3/5 | AI-based document scanning and verification tools can assist clerks by flagging inconsistencies or matching against databases, improving speed and catching some fraud indicators, while final judgment remains human. |
| Task automatability | claude-haiku-4-5-20251001 | 2/5 | Document verification involves visual inspection, pattern recognition, and security feature assessment—skills where current AI excels—but authenticity determination requires cross-referencing against issuing authority records, detecting forged security features, and making liability-bearing judgments that AI systems cannot reliably perform end-to-end. Most practical workflows still require a human clerk to make the final authenticity decision. |
| Task automatability | claude-sonnet-5 | 2/5 | Verifying document authenticity, especially foreign IDs and immigration papers, requires physical document inspection, database cross-checks, and fraud-detection judgment that current AI can partially assist but not fully replace end-to-end at equal quality.assemble. |
| Adoption barriers | claude-haiku-4-5-20251001 | 4/5 | Legal and regulatory barriers are substantial: clerks often hold formal licensure or appointment, and courts/municipal authorities are legally liable for accepting forged documents. Liability asymmetry and regulatory requirement for human sign-off on document authenticity create strong adoption friction. |
| Adoption barriers | claude-sonnet-5 | 4/5 | Government clerks often have statutory authority and legal accountability for verifying official documents, and errors carry high liability (fraud, immigration consequences), creating strong institutional and regulatory barriers to full automation. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 2/5 | OCR and document analysis AI is cheap, but the overhead of integration, training on forgery patterns, maintaining live connections to issuing authorities, and human oversight for liability still leaves total cost comparable to or exceeding a clerk's wage for reliable output. |
| Cost vs. human wage | claude-sonnet-5 | 2/5 | Specialized document verification systems require licensing, integration, and human oversight for edge cases, keeping costs comparable to or only modestly below clerk wages once accuracy and liability are factored in. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 2/5 | AI products can assist with document reading, OCR, and flagging anomalies, but no deployed system reliably authenticates documents independently or handles the full range of foreign identification formats in production. Existing tools require substantial human review and currently lack legal defensibility for autonomous use. |
| Technical feasibility today | claude-sonnet-5 | 2/5 | Some AI-assisted document verification tools exist (e.g., ID scanning software) but they are narrow, error-prone with diverse foreign documents, and not deployed as standalone replacements for clerks in government settings. |
Examine legal documents submitted to courts for adherence to laws or court procedures.
24CI 23–25 · exposure 25 · augmentation 50 · importance 4.5/5 · click for rater detail
Examine legal documents submitted to courts for adherence to laws or court procedures.
24| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 1/5 | Court systems are among the slowest-digitizing public-sector institutions, with entrenched processes, conservative change management, and limited budget for experimental automation. Actual adoption of AI for legal compliance checking remains near zero. |
| Sector adoption velocity | claude-sonnet-5 | 2/5 | Court systems are notoriously slow to adopt new technology due to legal, budgetary, and procedural constraints, with AI pilots emerging but production use still rare. |
| Augmentation potential | claude-haiku-4-5-20251001 | 3/5 | AI can assist clerks by pre-flagging potential compliance issues, highlighting missing fields, or summarizing document structure, meaningfully speeding up their review process while the clerk retains final judgment and sign-off authority. |
| Augmentation potential | claude-sonnet-5 | 3/5 | AI can assist clerks by pre-screening documents, checking formatting, and flagging missing information, improving efficiency while the clerk retains final review responsibility. |
| Task automatability | claude-haiku-4-5-20251001 | 2/5 | While AI can extract and flag document metadata and obvious formatting issues, the task requires nuanced judgment about legal compliance with complex, context-dependent procedural rules that vary by jurisdiction and court. Current systems lack the reasoning depth to reliably determine adherence to procedural requirements without substantial human review. |
| Task automatability | claude-sonnet-5 | 2/5 | While AI can flag formatting or missing-field issues, comprehensive compliance review of legal documents against jurisdiction-specific laws and procedures requires nuanced judgment and accountability that current systems cannot fully replicate end-to-end.4o |
| Adoption barriers | claude-haiku-4-5-20251001 | 4/5 | Court systems are heavily regulated; many jurisdictions legally require a licensed clerk or judicial officer to certify document compliance and procedural acceptance. Liability and error costs (rejected filings, case dismissals) create strong organizational and legal barriers to full automation. |
| Adoption barriers | claude-sonnet-5 | 4/5 | Court filings often require certified clerks or officers of the court to verify compliance, and errors carry legal liability, creating strong procedural and regulatory barriers to full automation. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 2/5 | AI screening tools require significant infrastructure, customization per jurisdiction, and mandatory human review of flagged issues, making the total cost comparable to or exceeding the loaded wage of a clerk performing the task. |
| Cost vs. human wage | claude-sonnet-5 | 2/5 | AI tools could cheaply flag obvious errors, but the need for human oversight and legal accountability keeps effective all-in costs closer to the human baseline. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 2/5 | Document automation tools exist for simple checks (metadata, formatting), but no deployed system reliably examines complex legal documents for procedural compliance across varied court systems at production scale. Existing products are narrow and require high human oversight. |
| Technical feasibility today | claude-sonnet-5 | 2/5 | Some court systems use e-filing software with basic automated checklists, but no widely deployed product reliably performs substantive legal/procedural compliance review without human clerk verification. |
Participate in the administration of municipal elections, such as preparation or distribution of ballots, appointment or training of election officers, or tabulation or certification of results.
15CI 13–18 · exposure 20 · augmentation 50 · importance 4.5/5 · click for rater detail
Participate in the administration of municipal elections, such as preparation or distribution of ballots, appointment or training of election officers, or tabulation or certification of results.
15| Dimension | Model | Rating | Rationale |
|---|---|---|---|
| Sector adoption velocity | claude-haiku-4-5-20251001 | 1/5 | Election administration is a highly regulated, conservative sector with strong institutional and legal requirements for human authority; adoption of AI automation is minimal in production, limited mainly to isolated data-processing tasks in pilot programs rather than systematic automation. |
| Sector adoption velocity | claude-sonnet-5 | 1/5 | Government election administration is a slow-moving, highly regulated public sector function with minimal AI agent deployment in production due to security and legal concerns. |
| Augmentation potential | claude-haiku-4-5-20251001 | 3/5 | AI can usefully assist election clerks with data entry, preliminary tabulation, and reporting workflows, speeding up routine administrative steps, but the human must remain in the loop for certification, decision-making, and legal accountability in election results. |
| Augmentation potential | claude-sonnet-5 | 3/5 | AI can assist with drafting training materials, scheduling, ballot proofreading, and preliminary tabulation checks, improving efficiency while humans retain control and certification authority. |
| Task automatability | claude-haiku-4-5-20251001 | 2/5 | While some sub-tasks like ballot data entry and result tabulation could be partially automated, the task requires legal compliance, chain-of-custody oversight, and human judgment in election administration that current AI cannot reliably handle end-to-end. AI lacks the capability to independently manage the full workflow with the required security and legal accountability. |
| Task automatability | claude-sonnet-5 | 2/5 | Some sub-tasks like ballot formatting or tabulation aggregation could be AI-assisted, but the overall election administration involves legally mandated human oversight, physical logistics, and chain-of-custody procedures that resist end-to-end automation.' |
| Adoption barriers | claude-haiku-4-5-20251001 | 5/5 | Strong legal and regulatory barriers exist: election administration is governed by federal and state law requiring human officials to certify results and maintain ballot security; many jurisdictions mandate licensed or appointed human administrators to sign off on election integrity, creating hard barriers to full automation. |
| Adoption barriers | claude-sonnet-5 | 5/5 | Election administration is heavily regulated, requires sworn officials, chain-of-custody, certification, and legal authority; statutes typically mandate specific human officials perform or certify these functions. |
| Cost vs. human wage | claude-haiku-4-5-20251001 | 2/5 | Election administration demands high accuracy, security, and legal compliance; the cost of AI systems (including rigorous testing, validation, and integration with existing voting infrastructure) often exceeds the cost of human clerks performing these tasks, especially given low error tolerance. |
| Cost vs. human wage | claude-sonnet-5 | 2/5 | AI tools could reduce some administrative costs (e.g., drafting training materials), but the human staffing, certification, and legal sign-off requirements mean overall costs remain dominated by human labor and compliance overhead. |
| Technical feasibility today | claude-haiku-4-5-20251001 | 2/5 | Limited deployed products exist for election administration at scale; most systems in production handle narrow sub-functions (data entry, reporting) rather than the full suite of preparation, training, and certification. Election officials typically rely on specialized vendors and human oversight rather than general-purpose AI. |
| Technical feasibility today | claude-sonnet-5 | 1/5 | No deployed AI product manages municipal election administration end-to-end; existing election technology is narrow (tabulation machines, voter databases) and not autonomous AI systems performing this composite task. |
Related occupations — Office & Administrative Support
How to read this
A high substitution score does not mean this job disappears — it means a large share of its current tasks face replacement pressure, so the mix of tasks is likely to change. High augmentation alongside substitution typically means the occupation reorganizes around the protected tasks. Wide confidence intervals mean the rater panel disagreed: treat those scores as open questions, not verdicts.
What would change this score
New model capabilities (automatability, feasibility), falling inference costs (cost ratio), regulation and licensing shifts (barriers), and measured sector adoption (velocity) all re-enter at every index release. Each release is recomputed, versioned and kept queryable — scores are claims with a date on them, not permanent labels.