What belongs in an AI employee job description
A usable description has six parts: purpose, allowed inputs, routine responsibilities, prohibited actions, escalation rules, and measures. Avoid vague duties such as “handle finance” or “own hiring.” Specify the task and the human who remains accountable.
Role Templates
1. HR Service Desk Coordinator
Purpose: Prepare answers to routine employee questions from approved policy sources and route unresolved cases.
Scope: Find the relevant policy, draft a response, and flag missing context.
Human owner: HR service desk lead.
Limits: Do not decide leave, accommodations, discipline, eligibility, or complaints.
Measures: Answer accuracy, first-contact resolution, escalation completeness, and correction rate.
2. Accounts Payable Exception Analyst
Purpose: Organize invoice exceptions for AP review.
Scope: Compare submitted fields with supplied purchase-order and invoice records, identify missing or conflicting values, and prepare a review queue.
Human owner: AP manager.
Limits: Do not change bank details, approve payment, or override a control.
Measures: Exception precision, review turnaround, reopened cases, and duplicate flags.
3. Finance Close Analyst
Purpose: Prepare a first-pass close checklist or variance summary from approved records.
Scope: Collect named inputs, apply documented definitions, and flag unmatched items.
Human owner: Controller or close lead.
Limits: Do not post journal entries or certify financial statements.
Measures: Reconciliation completeness, unresolved exceptions, review corrections, and on-time delivery.
4. Procurement Operations Coordinator
Purpose: Prepare procurement requests for a human buyer.
Scope: Check required fields, organize documents, and route requests by the organization's written rules.
Human owner: Procurement manager.
Limits: Do not select a supplier, make a commitment, or change contract terms.
Measures: Complete-request rate, routing accuracy, cycle time, and returned requests.
5. IT Service Desk Triage Analyst
Purpose: Classify and route routine support requests.
Scope: Gather required details, suggest approved troubleshooting steps, and escalate unresolved or security-sensitive cases.
Human owner: IT service desk lead.
Limits: Do not change privileged access or suppress security alerts.
Measures: Correct routing, resolution rate after review, escalation time, and reopened tickets.
6. Compliance Evidence Coordinator
Purpose: Assemble evidence for a defined control review.
Scope: Retrieve approved records, map them to a checklist, and flag gaps or expired evidence.
Human owner: Compliance officer.
Limits: Do not certify compliance, close findings, or give legal advice.
Measures: Evidence completeness, traceability, stale-item detection, and reviewer corrections.
7. Legal Operations Intake Coordinator
Purpose: Organize incoming requests for legal review.
Scope: Capture required fields, identify the stated matter type, and route materials to the designated legal owner.
Human owner: Legal operations lead or counsel.
Limits: Do not provide legal advice, determine privilege, or make a filing decision.
Measures: Intake completeness, routing accuracy, missing-document rate, and time to assignment.
8. Sales and Customer Operations Coordinator
Purpose: Prepare routine account or service requests for an assigned human owner.
Scope: Gather information from approved sources, draft a response, and route nonstandard requests.
Human owner: Sales or customer operations manager.
Limits: Do not promise pricing, product availability, delivery dates, contract terms, or service outcomes that are not verified.
Measures: Complete handoffs, response time, correction rate, and unresolved-request aging.
How to adapt a template
Replace each generic owner with a named role, list the actual systems and data that are approved, and test the stop conditions. Write down how a person reviews the output and corrects a mistake. If the workflow touches money, employment, compliance, legal matters, or customer commitments, treat the authority boundary as a launch requirement.
For related context, see the complete guide to AI employees, AI employee platforms compared, the state of AI employees in 2026, and the AI analyst role and sample job description
How does a job description map to a Zamp AOP?
A job description tells a person what the role is. At Zamp, the equivalent for an AI employee is its Agent Operating Procedure (AOP), and every AI employee has exactly one. Take the Procurement Operations Coordinator template above. Here is how each line becomes AOP content.
JD part | In the AOP |
|---|---|
Purpose and scope | Objective and instructions: review each purchase request before it becomes a purchase order. |
Allowed inputs | Sources of truth, including which source wins when two disagree. |
Limits ("do not select a supplier, make a commitment, or change contract terms") | Permissions and approval limits, enforced through the agent's own identity with least-privilege access, not by trust. |
Escalation rules | Escalation paths and the conditions that set Needs Attention. |
Measures | What the team tracks, such as decision rate and manual-review rate. |
What the AOP adds
A JD stops there. An AOP also holds known failure modes, the reasoning steps, and scoped precedents. If a reviewer approves an odd case, the approval is stored as a precedent limited to the conditions it was made under, not as a new general rule.
The process owner writes it in plain language, the way you would brief a new hire. In our biopharma procurement deployment, the checks were purchase amount and currency, whether a cited quote had expired, whether the request fell under an existing multi-year contract, and which tax rules applied. The agent gave a human reviewer its findings and a recommendation, and wrote its reasoning into SAP Ariba. Where it was not confident, it sent the case to manual review: 64% of requests in week one, falling to 15% as its decision rate rose from 36% to 85%.
A JD gets updated when someone has time. An AOP changes through a branch, evals against a golden set, review and merge. The full mechanics are in the AOP explained, and the deployment is in the procurement case study.
