Understand the brief
Start with the business context the audience, and the question to answer. Keep source findings separate from assumptions.
Autonomous Mode
Give your agent room to work. Set the boundaries.
Choose what Jalli can take forward and what needs your review. Autonomous mode connects business context with permitted work, budgets and channel limits, keeping responsibility clear.
Example
One brief. Three ways to work.
Example brief: understand Harborline's logistics handoffs before considering contact. Switch the control level to compare who does the work and where review belongs.
You choose and carry out each step.
Work directly with assistance from Jalli. You choose the source, inspect the account context and decide whether a draft belongs next. Each activity remains a decision you initiate.
Example delegation briefNorthstar / Manual
- Work
- You research the account and write the brief, with assistance.
- Owner
- Northstar's operator chooses and performs each activity.
- Review
- You check the source, relevance, and any proposed message.
- Stop
- No further activity without your next instruction; budget and channel access still need definition.
You direct each step.
A clear brief stays at the center.
Delegation starts with a shared objective and a defined permission boundary. Context, judgment, activity, and memory should remain connected as the work develops.
One goal. Defined boundaries.
Choose within scope
Consider the next useful activity against the agreed permissions available budget, and review points. A new objective needs a new decision.
Keep the reasoning
Carry forward the source, decision, and open question. The next reviewer should understand why the proposed path changed.
Work or pause
Permitted work can continue inside its limits. Missing context, an excluded channel, or a budget boundary calls for human review.
Keep permissions, budgets, review responsibilities, and channel requirements with the plan.
A brief with boundaries
Decide what you are handing over.
Give the work a specific objective and name the activities it includes. For Northstar, understanding Harborline's logistics handoffs is a research brief. Sending an opening message is a separate decision, with its own permission and review.
Explore the AI Growth AgentNorthstar Studio · delegation brief
Research has a purpose. Contact needs permission.
- Objective
- Understand Harborline's logistics handoffs.
- Included work
- Review permitted sources and prepare account notes.
- Outside scope
- Sending messages or publishing content.
- Owner
- Northstar's research reviewer.
Example
A limit changes the next step
Make the stopping point part of the plan.
A useful next step can still sit outside the brief. Before work reaches a new channel, a spending boundary, or an unresolved question, identify what needs review and who can decide. Expanding the scope should be an explicit choice.
Explore reviewable Workflowsexception · Requested outreach
An opening is proposed. Contact stays on hold.
- Proposed activity
- Write to the account about a handoff review.
- Permission boundary
- Research only; no outbound channel permitted.
- Budget condition
- Stop at the agreed research limit; do not expand it.
- Review decision
- Northstar's reviewer checks scope before contact.
Example
Context for the person reviewing
Keep the reason beside the proposed action.
Review is easier when the source and uncertainty stay beside the proposed action. Keep a record of the brief, the reason to pause, and the decision still needed. A teammate can revise the plan without reconstructing the account's story.
Explore relationship memoryHarborline Logistics · decision record
An open question belongs in the record.
- Source context
- Example account note describes freight operations.
- Uncertainty
- The person evaluating a handoff review needs research.
- Reason to pause
- Research scope does not permit outbound contact.
- Next decision
- Reviewer clarifies the role and any proposed permission change.
Example
Questions about control and delegation
How do Manual, Copilot, and Autonomous differ?
Manual keeps direct operation with you, with assistance available. Copilot prepares work for your review. Autonomous describes permitted planning and execution inside an agreed scope, budget, and channel restrictions.
What should I define before delegating work?
Name the objective, permitted activities, sources and channels, budget, review owner, and stopping conditions. Decide which actions need prior review and what happens when context is missing. Supported actions and the operational behavior of those limits must be verified before relying on them.
What happens when work reaches a limit?
Bring a permission question, spending boundary, or missing context to the responsible reviewer. Clarify, revise, or stop the path before continuing.
Which level should my team start with?
Start from the work and the decisions your team is ready to delegate. Manual suits direct operation; Copilot suits preparation with review. Consider Autonomous for clearly scoped activities only after establishing supported actions, permissions, budgets, channel restrictions, and review responsibilities.
Choose the work. Define the room to move.
Tell us what your team wants to hand over. Start with a clear objective, boundary, and review owner then discuss the level of control that fits.