Stopping work in the middle of a task is often unavoidable. The difficulty comes the next morning, when you must remember which file was current, why a paragraph was unfinished, and what you intended to check next. A shutdown note preserves that context in a few useful fields.

This is not a full daily journal or a second task list. It is a restart aid. A good note lets you resume one piece of work without rereading every message and draft that led to it. Use it at the end of a workday, before a long interruption, or when handing a partially completed task to yourself later.

Record the current state precisely

Describe what is complete and what remains. “Worked on the article” is too broad to help tomorrow. “Sections one to three revised; example in section four still needs a result check” identifies a useful boundary.

Point to the current file or note using a stable title or location. If several versions exist, identify the one that should be resumed. Avoid relying on “the newest file” when copies may have similar names or different modification times. The note should remove a choice, not leave another puzzle.

Name the next physical action

Choose the first action you would take if you had another ten minutes. In a fictional writing task, that might be opening the sample export and checking whether its final sentence is present. “Finish the guide” is the outcome; it is not the restart action.

Include the material needed for that action. A link to the sample, a section heading, or an unanswered reviewer question may be enough. Do not copy an entire document into the shutdown note if a clear pointer will do. The useful context should remain easy to scan.

Keep uncertainty separate from a plan

A planned next step can be wrong if a missing condition changes overnight. Mark dependencies explicitly: “If the reviewer approves the shorter scope, revise the opening; otherwise wait for the revised brief.” This prevents a tidy action list from hiding an unresolved decision.

Record a question as a question. “Check whether the PDF preserves the list order” is different from “PDF loses list order.” The first preserves uncertainty; the second invents a result. A restart note should tell your future self what you know and what still needs investigation.

A worked fictional example

Task: Prepare the browser-note export guide.
Current draft: Export guide, revision 2, in the agreed project folder.
Complete: Introduction and format explanation reviewed.
Open: Sample export has not been opened after download.
Next action: Open the harmless sample and inspect the final sentence.
Decision needed: Reviewer to confirm whether an image is necessary.
Do not redo: The title and scope are already approved.
After the check: Update the example, then send the draft for review.

The “do not redo” line is useful when you tend to restart settled work. It should point to an actual decision, not forbid revisiting a choice when new evidence appears.

Close the practical loops

Before stopping, save changes in the application you are using and check that essential material is where you expect it. For a browser note, distinguish the local note from an independent exported file. A shutdown note is not itself a backup strategy.

If another person is waiting, put the necessary update in the team's agreed channel. Writing “tell reviewer tomorrow” in a private note does not notify the reviewer. Keep external commitments visible in your task or calendar system rather than relying on a restart note alone.

Make the note short enough to trust

Include details that would be expensive to reconstruct. Remove a long account of how the session felt unless it explains an important work constraint. A paragraph about being busy is less useful than the exact section where progress stopped.

You can keep a single rolling restart note or one note per project. Choose the arrangement that makes the current state unambiguous. If you use a rolling note, archive or replace outdated instructions visibly so yesterday's next action does not compete with today's.

Resume by checking the state

At the next session, read the shutdown note before opening a collection of unrelated tabs. Confirm that the referenced file and dependency still match reality. Then complete or update the first action. If a colleague has changed the draft, reconcile the state before following an obsolete instruction.

After resuming, mark the old restart point as used or superseded. Keeping a history can help explain a handover, but a stack of unlabelled old next actions creates confusion. The current instruction should be easy to identify.

Know when another record is needed

A shutdown note is not a substitute for an issue tracker, incident record, or formal handover. Use those systems when the work needs shared ownership, controlled access, or durable approval evidence. The personal note can link to them.

The method has worked when the next session starts with a meaningful action rather than a search for context. Judge the note by that result. You do not need a perfect end-of-day routine; you need enough accurate information to restart the task you actually intend to continue.

Use the BiNotePads online notepad to adapt this example. For a separate copy of important work, follow the browser-note backup guide.