A useful assistant should know the edges of the job.
When a new employee joins a small business, the owner does not usually say, “Help with everything,” and walk away. The person gets a role, a few priorities, examples of good work, and a clear understanding of which decisions still belong to the owner. An AI assistant needs the same kind of clarity.
Without it, a simple request can become too broad. “Handle the inbox” might mean sort messages, summarize them, draft replies, change appointments, quote prices, or promise a delivery date. Those are very different levels of responsibility. The first three can be useful preparation. The last three can create commitments the business never approved.
The practical fix is a one-page assistant job description. It is not a technical policy or a thick manual. It is a short agreement about the work the assistant may prepare, the information it may use, the person who reviews it, and the actions it must never take on its own.
Start with one sentence about the job.
Write the role in plain language: “Prepare the information I need for tomorrow’s service schedule,” or “Turn approved job notes into customer-update drafts for the owner to review.” If the sentence contains several unrelated jobs, make it smaller.
Then describe a good finished result. A scheduling brief might include the customer name, confirmed time window, service address, assigned team member, known materials, and anything that still needs an answer. A customer-update draft might include only facts from the approved job notes, with every unconfirmed detail marked as a question.
This matters because the assistant should be measured against a visible result, not a vague hope that it will “save time.” You can look at the brief, find what is missing, correct what is wrong, and improve the instructions after a real week of use.
Use three lanes: prepare, approve, and stop.
The prepare lane lists work the assistant can do before a person reviews it. That might include organizing notes, summarizing an email thread, finding an unanswered question, building a checklist, or drafting a message. Preparation should leave the business with something easy to inspect.
The approve lane names the decisions that belong to a person. Prices, discounts, refunds, schedule changes, customer promises, hiring decisions, payments, and final messages often belong here. Write the reviewer’s role, not just “someone.” For example: “The service manager confirms timing; the owner approves any price change.”
The stop lane is for missing facts, sensitive information, unusual requests, and anything the assistant cannot verify. A simple stop rule can say: “Do not guess. Mark the missing item, show where you looked, and ask the owner.” That one rule is often more useful than a long list of clever instructions.
Illustrative example one: the morning schedule brief.
This is an illustrative example, not a customer result. Imagine a four-person electrical company that begins each morning by checking the day’s jobs. The owner wants fewer surprises but does not want an assistant moving appointments or contacting customers without review.
The job description says the assistant may prepare a 6:30 a.m. brief from the approved calendar and yesterday’s job notes. It lists the address, arrival window, assigned electrician, known equipment, access notes, and open questions. It may flag a missing gate code or a job that appears to need a part that is not on the materials list.
The assistant may not reassign an electrician, change an arrival window, or tell a customer that a part is available. The dispatcher reviews the brief, resolves the questions, and decides whether any message or schedule change is needed. The assistant makes the gaps visible; the team makes the operational calls.
Illustrative example two: a cleaner weekly numbers review.
This example is also illustrative. Picture a small landscaping business whose owner reviews open invoices, scheduled work, and expected material purchases every Friday. The information already exists, but it lives in separate approved reports.
The assistant’s job is to prepare a one-page review from those specific reports. It can group open invoices by age, list next week’s scheduled jobs, and flag any job whose material note is blank. It must include the source and report date beside each section, and it must mark conflicting totals instead of choosing one.
The assistant cannot decide that an invoice is uncollectible, change a customer balance, order materials, or forecast cash as if uncertain work were guaranteed. The owner checks the source reports and makes those decisions. The weekly review becomes easier to start without turning judgment over to a generated summary.
Test the job description with five real examples.
Before making the role part of the daily routine, run five past examples through it. Use records you are allowed to use, remove unnecessary personal information, and choose examples with a few wrinkles: a missing note, a changed appointment, an unclear price, or two sources that disagree.
For each result, ask four questions. Did the assistant use only the allowed information? Did it separate facts from questions? Did it stop where the instructions said to stop? Could the reviewer understand the result quickly enough to make a decision? Update the job description when an answer is no.
Keep a version date and the name of the person who approved the instructions. Review the role whenever the process, software, team, or risk changes. The goal is not a perfect prompt. It is a small working agreement the business can inspect and improve.
The takeaway: clarity comes before automation.
Pick one repeatable job and write four lines: what the assistant prepares, which sources it may use, who approves the result, and when it must stop. Test those lines against five past examples before using them in live work.
This approach reflects practical guidance from the National Institute of Standards and Technology: define the task, clarify human roles and oversight, document the process, and verify generated information. For further reading, see the NIST AI Risk Management Framework Core and the NIST Generative AI Profile at nist.gov.
If you want help shaping that first, bounded job, you can try a PeakAgent assistant free for up to 30 days. Bring one recurring task and the way you handle it today. We will help turn it into a useful, reviewable role while you keep the decisions and control.