Turn Vague AI Delegation Instructions Into Clear Decision Boundaries
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
“Handle routine requests” sounds like a delegation instruction. It is actually an unresolved decision: who decides what routine means? One employee may interpret it as answering published questions. Another may include changing bookings, offering credits, or making exceptions for an unhappy customer. An AI assistant faces the same ambiguity, without necessarily recognising which interpretation the business intended.
To define AI delegation boundaries, replace broad task labels with an operating agreement: identify the judgments the assistant may make, the evidence those judgments require, the decisions it must not make, and the person who receives exceptions. Add examples immediately inside and outside each boundary. Then specify what happens while a decision is waiting.
The goal is not to remove judgment. It is to make the permitted judgment visible enough that staff can explain, review, and correct it. The worksheet below shows how to do that without turning the exercise into prompt engineering, access-control design, or automation configuration.
1. Separate the task from the authority to decide
A task describes work. Authority describes which choices someone may make while doing it. “Manage appointment requests” names work, but leaves several decisions unresolved: interpreting a customer's intent, proposing an alternative, changing a confirmed appointment, waiving a fee, and promising availability.
Start by separating three kinds of responsibility:
- Prepare: Gather facts, summarise the request, or draft a proposed response.
- Recommend: Select a proposed action and explain why it fits the agreement, but wait for approval.
- Act within a standing delegation: Complete a specifically authorised action when all stated conditions are met.
These are different grants of authority. Permission to draft a booking change is not permission to confirm it. Permission to report a published policy is not permission to interpret an exception.
A useful delegation sentence therefore reads: “For this request type, the assistant may make this judgment, using these facts, and may take this action without further approval. Otherwise, it sends the decision to this owner.” If the sentence cannot be completed, the work is not yet ready for delegated action.
2. Replace subjective labels with decision conditions
Words such as “simple,” “low risk,” “reasonable,” and “standard” can remain shorthand after the agreement is established. They should not be its only boundaries.
For each broad instruction, ask four questions:
- What can the assistant choose? Name the actual judgment, such as matching a request to a published service description.
- What evidence must support that choice? Name the accepted information source and the facts that must be present.
- What makes the case ineligible? Identify exceptions, conflicting information, missing facts, and prohibited commitments.
- Where does the unresolved decision go? Name an accountable owner and a backup, not merely “a human.”
A spending threshold alone is rarely enough. A small concession can still change a commercial term. A reversible action can still disrupt another person's work. Boundaries should describe the kind of decision as well as any limit on its size.
Also distinguish uncertainty about intent from missing authority. The assistant may be allowed to ask a customer which service they mean. It should not ask the customer to approve an exception that only a manager can authorise.
3. Filled hypothetical delegation worksheet
Fictional worked example: The business, people, responsibilities, and situations in this worksheet are hypothetical. This is a recommended operating design, not a description of any product capability. The agreement assumes that any delegated action has been separately authorised and is supported by the business's chosen tools.
Purpose, scope, and ownership
- Business: Cedar Desk, a fictional provider of bookable workspace.
- Original instruction: “Handle routine booking enquiries and keep customers informed.”
- Intended outcome: Customers receive accurate information or a clear handoff without the assistant inventing availability, changing commercial terms, or making unsupported commitments.
- Covered work: General service questions, new booking enquiries, and requests to change an existing booking.
- Accepted information: The current manager-approved service guide, the designated booking record, and the customer's stated preferences. A customer's account of an earlier exception is context, not approval to repeat it.
- Agreement owner: Maya Chen, operations manager.
- Escalation destination: Maya in the booking-exceptions queue. Backup: Alex Rivera, duty supervisor, when Maya is unavailable.
- Authority level: Answer eligible general questions; clarify missing preferences; prepare booking recommendations. Booking creation, amendments, and commercial exceptions require human approval under this agreement.
Responsibility A: Answer general service questions
- Permitted judgment: Match a customer's question to an explicit statement in the current service guide and explain that statement in plain language.
- Required evidence: The guide directly covers the service and condition being asked about, with no conflicting current information.
- Permitted action: Answer the question without implying that a particular booking is available or confirmed.
- Excluded decision: Infer an unlisted service, settle conflicting information, or promise a special arrangement.
- Just inside: A customer asks whether the meeting-room service includes a display screen; the guide explicitly says it does.
- Just outside: A customer asks whether staff can install unfamiliar presentation software. The guide mentions a display screen but says nothing about software installation.
- Handoff: Send the unsupported requirement to Maya, with the relevant guide entry and the customer's question.
Responsibility B: Clarify a new booking enquiry
- Permitted judgment: Determine which stated preferences are missing and ask for the intended date, time, group size, and room type.
- Required evidence: The customer's request clearly concerns a new booking and does not contain a separate unresolved complaint or exception.
- Permitted action: Gather missing preferences and prepare a booking recommendation for review. Describe any proposed option as unconfirmed.
- Excluded decision: Confirm availability, reserve a room, choose a paid upgrade on the customer's behalf, or promise a final price.
- Just inside: A customer requests a meeting room but omits the group size. The assistant asks how many people will attend.
- Just outside: A customer says, “Book whichever room you think is best and charge the usual amount.” That wording does not expand the assistant's authority to commit the business.
- Handoff: Send the proposed booking and remaining uncertainties to Maya for approval.
Responsibility C: Prepare an existing-booking change
- Permitted judgment: Summarise the requested difference between the existing booking and the customer's preferred replacement.
- Required evidence: The designated booking record is available through the business's established verification process, and the requested change is clear.
- Permitted action: Prepare a change summary and identify any terms requiring a human decision.
- Excluded decision: Amend the booking, cancel it, waive a fee, or state that the replacement has been accepted.
- Just inside: A customer wants to move a booking to a later time. The assistant records the requested time and prepares the change for review.
- Just outside: A customer says a previous manager always waived change fees. The assistant cannot treat that statement as current authorisation.
- Handoff: Send Maya the existing arrangement, requested change, and any claimed prior promise.
Responsibility D: Manage ambiguity and waiting
- Permitted judgment: Distinguish a missing customer preference from a decision reserved for the business.
- Permitted action: Ask a focused clarification question when the customer can supply the missing fact. Otherwise, acknowledge that human review is needed.
- Excluded decision: Resolve contradictory records by choosing the more convenient version, invent a response deadline, or imply that silence means approval.
- Just inside: A customer says “next Friday,” and the intended date is unclear. The assistant asks for the date.
- Just outside: The service guide and booking record disagree about what is included. The assistant sends the conflict to Maya rather than selecting a version.
- While waiting: Keep the affected decision pending. Do not mark it confirmed or complete. If Maya is unavailable, route it to Alex; if neither is available, retain the pending state and tell the customer that confirmation is outstanding.
4. Make escalation a usable handoff
“Escalate when necessary” leaves two gaps: what qualifies, and what the recipient needs to decide. The worksheet closes the first gap with exclusions. Close the second with a short handoff structure:
- The customer's requested outcome.
- The facts already established and their sources.
- The exact boundary encountered.
- The decision needed from the owner.
- What the customer has already been told.
- Any customer-stated timing constraint, clearly distinguished from a promised response time.
In the hypothetical booking-change case, the handoff should not merely say “customer needs help.” It should identify the requested time change and the claimed fee waiver, then ask whether the change and waiver are approved. Those are separate decisions.
The owner must also return an explicit disposition: approved, declined, or more information needed. A human approval for one case should not silently become a standing exception for future cases.
5. Test the boundary, not just the easy cases
Before using the agreement, have the business owner and a frontline colleague classify a small set of hypothetical requests independently. For each request, ask what the assistant may decide, what it may do, and where it must stop.
Include an obvious eligible request, a near-boundary request, missing information, contradictory information, and a customer pressing for an exception. The useful result is not a reassuring average score. It is a list of disagreements that reveal unfinished policy.
For example, if one reviewer thinks the assistant may suggest an unlisted alternative while another thinks it may only explain listed options, add a boundary pair that resolves that difference. Do not rely on “use common sense” to bridge it.
Test compound requests too. A customer can ask a permitted service question and request a prohibited concession in the same message. The agreement should allow the supported part to proceed while holding the concession for review, unless the unresolved issue makes even that partial answer misleading.
6. Choose where discretion is worth the cost
A narrow delegation can create more review work. A broad one can produce commitments the business did not intend. The right boundary depends on the value of the assistant's judgment, the available evidence, and the consequences of being wrong.
The hypothetical worksheet deliberately allows information and preparation while reserving booking commitments for people. That is a conservative starting point, not a universal model. A business may later authorise a specific class of amendments if it can describe the eligibility conditions and exclusions clearly.
Do not broaden authority merely because the queue is busy. First examine why cases are escalating. Missing customer preferences may call for better clarification. Conflicting internal information calls for an owner to resolve the source. Repeated commercial exceptions may require a business policy decision. These problems do not all justify more assistant discretion.
Conversely, avoid requiring approval for every wording choice. If the assistant may explain an explicit service fact, let it choose clear phrasing within that responsibility. Otherwise, the agreement delegates typing rather than useful work.
7. Recover from boundary failures without rewriting everything
When the assistant exceeds its authority, first establish what actually happened. A prepared recommendation, an approved decision, and a completed action are different states. Do not report an action as reversed unless someone has verified the reversal.
The responsible person should review any customer-facing commitment, arrange an appropriate correction, and identify the narrow failure:
- Unclear boundary: Add the missing exclusion and a near-boundary example.
- Missing or contradictory evidence: Resolve the information source before resuming that responsibility.
- Ignored boundary: Pause the affected delegated responsibility while the cause is investigated.
- Failed handoff: Repair ownership or backup coverage rather than expanding authority by default.
Keep case approval separate from agreement revision. The owner may approve an unusual request without authorising the assistant to approve similar requests later. Record any standing change explicitly and review the affected examples again.
8. Use a small review to decide the next change
As a hypothetical first review, choose a sample of 20 requests from one delegated responsibility. Record how many had sufficient evidence, how many were escalated, how many handoffs lacked a clear decision request, and whether any commitments exceeded the agreement. Treat these as observations about the operating design, not as proof of general reliability.
Look at both unnecessary escalation and missed escalation. A low escalation count is not success if the assistant is crossing boundaries. A high count is not necessarily failure if the work contains genuine exceptions.
The next action is concrete: replace one vague instruction with a completed worksheet, have its named owner approve the decision rights, and classify the hypothetical boundary cases before delegating live work. Schedule a review of the first sample and change only the boundaries that the evidence shows are unclear or unnecessarily restrictive.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications