Start with a role charter

A role charter should answer five questions:

1. What work is in scope?
2. Which sources may it use?
3. What can it change or send?
4. What must it stop for?
5. Who reviews the result?

Use specific tasks, such as preparing an exception queue, rather than broad instructions like “manage finance.”

Set permissions in layers: read approved sources; prepare drafts or recommendations; execute only low-risk, reversible actions that have explicit approval; and require human approval for money movement, employment decisions, legal conclusions, access changes, or external commitments. Do not infer a tool's capabilities from the title “AI employee.”

Choose KPIs that expose quality and risk

• Completion rate: Completed runs divided by eligible runs, with exclusions documented.
• First-pass acceptance: Outputs accepted without material correction divided by reviewed outputs.
• Exception precision: Escalations that a reviewer confirms needed human handling divided by all escalations.
• Rework rate: Outputs reopened or corrected after acceptance divided by completed outputs.
• Escalation completeness: Escalations containing required context and evidence divided by reviewed escalations.
• Cycle time: Elapsed time from eligible input to accepted result, compared with the existing process.
• Control failures: Unauthorised actions, missed stop conditions, or broken audit trails. Set tolerance with the risk owner; do not hide these inside an average.

Measure a baseline before setting targets. A higher completion rate is not progress if errors, reversals, or unresolved exceptions rise. Keep denominators and exclusions visible so a team can reproduce each metric.

Review cadence: A practical starting point

• Daily: Review the exception queue, failed runs, and any action that affected a person, payment, or external commitment. Pause first if a control failure is unexplained.
• Weekly: Sample accepted outputs, inspect corrections and overrides, and check whether escalations reached the right owner. Use findings to update instructions or process controls, then test the changed workflow.
• Monthly: Revisit the role charter, access list, risk assessment, performance baseline, and owner assignment. Review whether the workflow still has a business purpose and whether any process or policy changed.

This cadence is a starting recommendation, not a legal standard. Higher-risk workflows may need more frequent checks.

Set explicit escalation rules

Route a case to a person when required data is missing, sources conflict, the request falls outside the role, confidence is not supported by evidence, or the next step could affect a person's rights, money, access, or legal position. The handoff should include the input, unresolved question, source references, and action the workflow did not take. A term such as Needs Attention can label cases that need review, but the label must correspond to a documented queue and owner. A status tag without a response time or escalation path does not provide oversight.

Keep the audit trail useful

For each run, retain the request or permitted input reference, the sources used, the output, actions attempted, approvals, exceptions, and final disposition according to the organization's retention policy. Limit access to the records and avoid collecting data that the workflow does not need. The NIST AI Risk Management Framework is a voluntary resource with four core functions: Govern, Map, Measure, and Manage. Use it to organize risk questions, not as proof of compliance or a certification. For broader category context, see the complete guide to AI employees, AI employee platforms compared, the state of AI employees in 2026, and the related AI analyst guide