Create the Asana task
Create the task in Asana with the client, requested output, and enough detail for Jessie to choose a skill.
Consultant workflow
How To Use Jessie
How to create a task Jessie can work on, how to add useful context, and what to expect back in Asana.
Basic Flow
Assign it to Jessie
Set the task assignee to Jessie. The live hosted intake requires this before the task is agent-eligible.
Add it to Jessie Intake
Add the same task to the Jessie Intake project. Assignment alone is not enough for the hosted intake path.
Set timing if needed
Leave start date blank for execute-now work. Set an Asana start date when Jessie should wait until a later date.
Review before delivery
A human reviews the comment, attachment, caveats, and approval gates before sending anything to a client.
Asana Setup
For hosted Jessie work, the task must satisfy both Asana routing requirements.
| Asana field | What to do | Why it matters |
|---|---|---|
| Assignee | Assign the task to Jessie. | The live Worker is configured to require the Jessie assignee before it treats a task as agent-eligible. |
| Project | Add the task to the Jessie Intake project. | Jessie Intake is the watched execution trigger. A task outside this project will not run through the hosted intake path. |
| Task name | Use a short outcome-oriented title. | The title helps routing but should not carry all critical context. |
| Task description | Put the request, period, client, expected output, questions, consultant notes, and approval boundary in the description. | Jessie uses the task body as the work brief and review trail. |
A task added to Jessie Intake but not assigned to Jessie is recorded as ineligible. A task assigned to Jessie but not added to Jessie Intake is not on the hosted intake trigger.
Timing
Jessie uses Asana dates to decide whether eligible ready work should run now or wait.
| Timing setup | Jessie behavior |
|---|---|
| No start date | Default execute-now behavior. If the task is eligible and ready, Jessie queues it immediately after intake assessment. |
| Future start date | Jessie parks the task until the Asana start date. The start date is the earliest execution date. |
| Due date | The due date is the target completion date, not the execution trigger. Use it to show when the consultant needs the output. |
| Only due date and timing matters | Add a start date too. If only a due date exists and timing is ambiguous, Jessie may ask whether the due date is the target completion date or the date it should start. |
Use start date for "do this later". Use due date for "I need the output by this date". If neither is set, assume Jessie may do it immediately.
Copy-Paste Task Template
Jessie, please run [skill/output] for [client] for [period].
Audience: internal consultant review.
Expected output: [HTML report / planning checkpoint / audit package / short analysis].
Timing: [run now / start on YYYY-MM-DD / due by YYYY-MM-DD].
Questions to answer:
- [Question 1]
- [Question 2]
Consultant notes / extra instructions:
- [Known client decision, caveat, or recent event]
- [Any agreed tradeoff, such as scaling spend while accepting higher CPA]
- [Anything to check or avoid]
Approval boundary:
- Do not publish to the client.
- Do not change websites, tracking, ad accounts, budgets, or dashboards.
- Post the result back on this Asana task for review.Real Internal Client Example
This example uses a real client name so consultants can see the expected level of specificity. The consultant can add further information to the prompt when they know something Jessie may not know from approved context yet.
Jessie, please run a GA4 report for Plunkett Homes for April 2026.
Audience: internal consultant review.
Expected output: internal HTML report attached to this Asana task.
Timing: run now. If this is needed for a meeting, set the Asana due date to the meeting preparation deadline.
Questions to answer:
- What changed materially compared with March 2026?
- Which channels, landing pages, and conversion events need consultant attention?
- Are there data-quality caveats we should check before discussing performance?
Consultant notes / extra instructions:
- The client has been comfortable testing growth even if some CPAs rise temporarily.
- Be careful not to call a conversion decline good or bad until lead quality is checked.
- Highlight anything that needs follow-up in Google Ads or Meta rather than treating GA4 as the only source of truth.
Approval boundary:
- Do not publish to the client.
- Do not change tracking, dashboards, website content, or ad accounts.
- Post the review-ready output back on this task.How Jessie Interprets Consultant Notes
- Consultant notes are task-specific context. They guide the run being performed now.
- They can explain known client decisions, planned tradeoffs, caveats, campaign timing, recent conversations, or extra questions.
- They do not override approval gates or safety rules.
- They do not become permanent approved client context unless captured through the context management process.
- If notes conflict with approved context or data evidence, Jessie should surface the conflict instead of silently choosing one.
Approval Boundaries
Jessie writes today
- Asana comments.
- Asana attachments or artifact references.
- D1/R2 run state, evidence metadata, and generated artifacts through the hosted runtime.
Jessie does not write today
- Client emails or client portal releases.
- Website/CMS changes.
- GA4/GTM/tracking changes.
- Ad account budget, campaign, bid, keyword, creative, or conversion changes.
- Secrets or credential values.