Keep a short written brief for the work, and update a separate note when you stop. Supply both when you resume. Then check what the AI understood before giving it the next assignment.
That is the approach I recommend when you find yourself explaining the same business, customer or project every time you open an AI tool.
You already know why the proposal changed. You remember which number the customer corrected. The person responsible for the next approval is obvious to you. Those are easy things to leave out of a prompt, because you've been carrying them around all week.
Put them somewhere you can inspect and reuse.
Separate the background from today's state
The background changes slowly: what the project is for, who it's for, what a good result looks like, and which rules apply.
Today's state changes whenever you work: what is finished, what was decided, what is waiting, and what happens next.
Keeping those separate makes it easier to update the piece that changed. You can use two plain-text notes or two labeled sections in one document. Use a format you can open and edit yourself.
AI tools handle saved instructions, files and conversation history differently. For this exercise, paste the text directly into the conversation. That lets you check the material you've supplied without relying on a particular memory feature or file connection.
If you later use attachments or a connected folder, verify that the tool can read the relevant contents. Naming a file or pasting its location doesn't establish that access.
Write a brief for one project
Start with one job. A workshop plan needs different context from your bookkeeping or a customer complaint.
Use this template:
PROJECT BRIEF
Updated: [date]
Job:
[What are we trying to finish?]
Reader or user:
[Who will use it, and what do they need?]
Finished means:
[What must the result contain or do?]
Source material:
[Name the material supplied with this brief.]
Rules and boundaries:
[Tone, format, constraints and permitted actions.]
Decisions already made:
[Confirmed choices, with their source or approver.]
Open questions:
[What is still unknown, and who can answer?]
Each field has a job. "Finished means" keeps the output useful. Source material gives you something to check against. Open questions make gaps visible before a fluent answer fills them in.
Include only material appropriate to the task and approved for the tool you're using. A useful brief might contain one agreed requirement and a short customer note. It doesn't need your entire company archive.
A fictional example with a changed decision
Imagine you're planning an internal workshop. All the details below are fictional. Copy this brief to practice:
PROJECT BRIEF
Updated: October 2, 2026
Job:
Prepare a run sheet for an internal customer-service
workshop. The next working session will draft it.
Reader:
Pat, who is running the workshop. Pat needs activities and timings.
Finished means:
A 45-minute run sheet for six participants, including
practice with fictional customer inquiries and a
discussion of when to ask a supervisor for help.
Source material:
The organizer's notes, supplied in full here:
October 1: proposed 60 minutes for ten participants.
October 2: revised to 45 minutes for six participants.
The organizer approved that revision on October 2.
No room has been booked.
Rules and boundaries:
Use fictional examples. Keep the session practical.
Draft material in this conversation for my review.
Treat the October 2 revision as the current scope.
Decisions already made:
45 minutes and six participants, approved October 2.
Open questions:
The organizer must confirm the room and equipment.
The older numbers are there on purpose. A useful continuation should carry forward the approved revision. If the AI gives you a sixty-minute session for ten people, you've found a context problem before spending time on the activities.
Notice that the room is still unknown. A confident room name would be an invention.
Save what changed when you stop
At the end of a working session, ask the AI to draft a handoff:
Write a handoff I can supply in a fresh conversation.
Include the current objective, completed work,
decisions and their sources, unresolved questions,
and the next concrete action.
Separate proposed ideas from approved decisions.
Identify any source material or finished output
I must supply alongside the handoff.
Keep it short enough for me to check against our work.
Read that note before saving it. An inaccurate summary can carry the same mistake into tomorrow.
For our fictional workshop, imagine you've stopped after choosing the practice topics. This is an example handoff you could save with the brief:
SESSION HANDOFF
Updated: October 2, 2026
Objective:
Prepare the 45-minute workshop for six participants.
Completed:
Practice topics selected. No run sheet drafted yet.
Approved decisions:
In this practice scenario, I approved two fictional
inquiry topics: a delayed order and an unclear return
request. Use these in the run sheet.
Proposed, still open:
Pat suggested working in pairs. This is a suggestion
to consider while drafting, not an approved format.
Waiting:
The organizer must confirm the room and equipment.
Next action:
Draft a timed run sheet for review that can be
delivered without a screen.
Supply with this handoff:
The current project brief and its organizer notes.
There is no previous run sheet to retrieve.
That last part matters. A summary saying "use the approved draft" is a dead end if the next conversation can't access the draft. Carry the needed output with the handoff, or supply a source the tool can actually read.
Test it in a fresh conversation
Start another conversation and supply the example brief and handoff above. Then paste:
Read the supplied project brief and session handoff.
Before drafting, state:
1. The current duration and participant count.
2. The approved practice topics.
3. Which format idea is still only proposed.
4. What remains unknown.
5. The next concrete action.
Use the supplied material for the answers.
Flag missing information or conflicting instructions.
Wait for my review before drafting the run sheet.
Check the reply. It should say 45 minutes, six participants, and name both practice topics. Pairs should remain a proposal. The room and equipment should remain unconfirmed. The next action is a timed run sheet that works without a screen.
Once those facts are right, ask it to draft. Add the timings yourself to check that they total 45 minutes. Confirm that the plan includes both inquiry topics and the supervisor discussion. A correct recap is useful; the finished work needs its own review too.
Keep the brief useful
When a decision changes, update the current brief and record where the change came from. Keep old material clearly labeled if you need the history. If two sources conflict and you haven't settled which applies, make that an open question.
At CrewTracks, part of my coaching work with Erin was separating work that had accumulated in one workspace into distinct projects. She left able to organize those projects herself. The practical lesson here is to give each job a clear home and the context it needs.
If you're still learning how to assign the work itself, start with the one-task AI exercise. If your team needs to agree on who owns the sources, decisions and review, use the questions in my coaching and fractional leadership guide.
And if the same task keeps falling apart between sessions, bring the brief and one failed handoff to an AI coaching discovery call. We can look at what the next conversation was missing.
