← All posts

article

A digital employee's first day starts with a job description

Before an AI role touches real work, write down what it knows, what it may use, what it may do and who it answers to. A practical checklist for the first week.

Hiring a person starts with a job description: responsibilities, the knowledge they need, the systems they may use, the decisions they may make and the manager they report to. A digital employee needs the same document, and for the same reason. Without it, you do not have a role. You have a prompt with access to your records.

This is a practical checklist for putting an AI role to work inside a business. It is not a claim that any particular setup meets a legal or audit requirement.

Start with one responsibility

"Help the team with AI" is not a role. A role is one area of work with a nameable owner: preparing customer-service replies, chasing documents for outstanding jobs, or keeping website content current.

Pick work that already exists and already has a measure. Work you currently outsource is a good candidate, because the budget, the expected result and the definition of done already exist. Success becomes easy to see: did the work get done, at the same quality, with less of someone's week?

Start with work that does not involve contacting customers directly. Customer-facing responsibility can come later, after testing, with disclosure and clear escalation rules.

Give it knowledge, not just logins

A new employee reading raw inboxes from day one is not onboarded. They lack the map: which customers matter, what was promised, how this business describes its own work.

A digital employee needs the same context in a usable form: customer records, work history, documents and the relationships between them, retrieved when a task needs them rather than copied into every prompt. The test is simple. Ask a question a new hire would ask, such as "what should I know before speaking with this customer?", and check whether the answer reflects the business or just one inbox.

Knowledge also has boundaries. The role should see what its job requires, not everything the business holds.

Set authority in tiers, not as a switch

Access is not one decision. Reading a record, changing it, contacting someone outside the business and spending money are different actions with different risk, and they should be permitted separately.

A practical starting tier list:

  • Read: retrieve the records the role needs, within its scope.
  • Draft: prepare replies, documents and updates for a person to review.
  • Act: make defined changes inside connected systems, with approval recorded.
  • Spend and send: any external contact or any payment stays with a person until the role has earned otherwise.

Most digital employees should start at draft. Authority widens when results are reliable, and it can narrow again just as easily. The authority belongs to the business, not to the AI model and not to whichever staff member happens to ask.

Name a human owner

Every role needs a person who oversees it: a marketing lead for a digital presence role, an accountant for document chasing. That owner approves work, reviews exceptions and decides when the role is ready for more.

Escalation is part of the job description, not a failure mode. Write down which situations stop the role and hand the decision to a person: an unusual amount, an angry customer, anything outside the defined task. A digital employee that never escalates is not performing well. It is hiding the hard cases.

Decide how you will review the work

You would not let a new employee work unreviewed for a year. Agree up front what the review looks like: a record of what was done, what was approved, by whom, and what the result was. Sampling a few completed tasks each week is enough at the start.

The record matters most when something looks wrong. If you cannot reconstruct what the role did and why, you cannot fix it, and you cannot trust the next task either.

Widen authority as results come in

A sensible first month: the role observes and drafts, a person approves, and the results are measured against the definition of done you set at the start. Then expand one tier at a time.

The sequence matters more than the speed. Knowledge first, then access, then narrow authority with review, then broader authority as the record earns it. That is how you would treat a promising new hire, and it is the standard a digital employee should meet before it carries real responsibility.

Holiday builds the business environment digital employees work in: connected business knowledge, authority set by the business, and an audit record of what was done. Read more about digital employees.