AI Employees by Tech Local
Writing an AI employee’s job description
A good AI job description explains the work, the result you expect and when a person needs to step in. Write it in the language your team already uses. Tech Local helps turn that description into working instructions and a service agreement before you pay.
Describe a role someone can recognise
Start with a title and one sentence about the purpose. For example: “Quote preparation assistant: help the estimator turn approved site notes into complete quote drafts and keep follow-ups organised.” That is easier to manage than a general instruction to increase productivity.
Name the person who supervises the role. They decide what useful work looks like and handle exceptions. If several colleagues send requests, explain whose instructions take priority and how the supervisor resolves a conflict.
Write down inputs, duties and outputs
An AI employee needs the same business context a new colleague would need for the task: where information comes from, which source is current, the format to use and examples of a good result. Specify what it should do when an important detail is missing.
For quote preparation, the input might be site notes and an approved rate card. The output is a draft in your template, with missing details highlighted. Final pricing remains with the estimator. A completed draft and an issued quote are different outcomes; the job description should say which one is expected.
Set the working boundaries
Agree the expected workload, working hours and turnaround. These describe the role you are buying; they should reflect your actual workflow. State when the AI should pause, ask for information or escalate a problem to the supervisor or Tech Local.
List the approved tools and information. Be clear about which actions may happen independently and which need approval. A higher-capacity package does not automatically grant permission to send messages, spend money, change important records or make customer commitments.
Use a simple role checklist
Use these headings for the first conversation. You do not need to know technical configuration terms; examples from your working day are enough to begin.
- Job title and purpose: which part of whose job needs support?
- Duties and outputs: what arrives, what gets done, and what does good look like?
- Workload and schedule: how much work, by when, and in which working hours?
- Tools and access: which accounts, folders and information are needed?
- Approvals: what can proceed, and what needs the supervisor’s decision?
- Checks and escalation: how do we spot a problem and who handles it?
Keep the description useful after onboarding
The monthly review is a chance to compare the role with the work that is actually arriving. Bring examples of unclear instructions, recurring mistakes and useful new tasks. Tech Local helps refine the role and remains accountable for the agreed service.
If the job grows, update the agreement deliberately. Changes affecting the price require agreement first. A clear description gives both sides a practical way to discuss performance and decide what to do next.