Task Too Long? Write a One-Page "Relay Note" for the AI Before Switching Sessions

Yesterday, I was tweaking my website’s navigation bar. By the 40th round of conversation, the AI started messing up—repeatedly bringing back color schemes I had already deleted. I had to copy-paste snippets from earlier exchanges just to say, "We already discussed this." After all that hassle, the whole day was gone.

This loss isn’t on the AI; it’s on me. I assumed, "It’s in the same chat, so it should remember." But the context window of a long session is like a pool with a leaky bottom: the further you go, the fuzzier the memory of what came before becomes.

So, I’ve been using a clumsy but effective trick: before switching sessions, I write a one-page "Relay Note." When starting fresh, I paste the note in, and we pick up right where we left off.

What Does a Relay Note Look Like?

A Relay Note is a short summary (under 200 words) intended for the "next runner" (a new session, your future self on a different computer, or a colleague taking over). It only needs to answer five questions:

1. What are we doing? (One sentence)

2. How far have we gotten? (List completed items)

3. What’s left? (List pending items)

4. What are the rules? (Constraints that must not be violated)

5. What have we tried and failed? (Pitfalls already encountered)

Here is a template:

[Relay] Site Navigation Bar Redesign
[Done] Changed nav background to dark; reduced logo size; removed bottom share icons
[Todo] Add copyright line; test display on 375px narrow screens
[Rules] No gradient colors; keep fonts unchanged
[Tried & Failed] Tried system font PingFang; rollback looked bad, so abandoned it

When pasting this to the AI, you only need one sentence: "Please continue the task based on this note." There’s no need to start from zero again.

When to Use It

**Scenarios where you should use it:**

- The conversation exceeds thirty rounds, or you notice the AI repeating previously discussed errors.

- You need to split the work into segments (e.g., pausing for the night to continue tomorrow, or closing your laptop).

- You are switching tools—moving work done in Tool A to continue in Tool B.

- You are handing off work to a colleague.

- You want to migrate the task to a more powerful model.

**Scenarios where you don’t need it:**

- Q&A tasks that are resolved immediately (ask and forget, no history to carry forward).

- The session is still short (under ten turns), and the context is intact.

- The task doesn’t require continuity—just finish it in the current session.

The rule of thumb: **Would you bet that you’ll come back to this tomorrow? If yes, write the note. If no, don’t bother.**

Checklist (5 Items, 30 Seconds)

Run through these points when writing:

- [ ] Can an outsider understand "what we are doing" from the title?

- [ ] Is every item in the "Done" list verifiable? (Not "optimized some things," but "changed nav background to dark.")

- [ ] Are the "Todo" items broken down into specific, actionable steps?

- [ ] Are the constraints clearly stated? This information is most easily overlooked and most critical.

- [ ] Did you record the pitfalls? The greatest value of a Relay Note is preventing the next runner from stepping into the same trap.

Three Common Pitfalls

1. **The note is longer than the conversation.** A Relay Note is a baton, not luggage. If it exceeds 200 words, start cutting.

2. **Recording only conclusions, not the process.** Saying "The layout looked bad, so it wasn’t used" tells the next person nothing useful. Instead, write: "Tried a three-column layout, but the main text width was too cramped." That’s actionable.

3. **Pasting the note in every single turn.** Paste it once when switching sessions. Subsequent context will build naturally. Pasting it repeatedly treats the new session like the old one, which actually clutters the new chat faster.

Trading a Mistake Log for Shackles

The Relay Note and yesterday’s concept of "Defining Done" are two sides of the same coin: "Defining Done" clarifies the finish line, while the Relay Note marks the intermediate milestones. One prevents drifting off course; the other prevents amnesia.

It also pairs well with the "Error Log Method": the Error Log records "where the pitfalls are in this project," while the Relay Note records "where I am right now." The former is the map; the latter is the coordinate. Writing both ensures the team doesn’t keep passing the baton into the same hole.

Practical tip: Save the template in your clipboard manager or as a custom input phrase (e.g., typing "relaynote" instantly pops up the template). The lower the barrier, the more likely you are to write it; the more you write it, the fewer crashes you’ll experience.

Final Thought

An AI session is a relay baton in a marathon. The Relay Note doesn’t need to be beautifully written, but it must be handed over promptly. Spending 30 seconds writing it can save you an entire afternoon.