A five-minute shutdown note that makes tomorrow easier to enter

Stopping is harder when the project has no saved state

You close the laptop knowing you made progress, but the next morning the project looks unfamiliar. You reread messages, reopen several files, and try to remember which version was current. The first work block becomes reconstruction instead of movement.

Adults with ADHD may experience difficulty with organization, planning, remembering daily tasks, and completing large projects. Similar restart friction can follow fatigue, interruption, unclear ownership, missing access, or a project that changes while you are away. One difficult restart does not identify ADHD.

A shutdown note is a low-risk external cue. This guide's exact four-line format and five-minute limit are editorial tools, not a clinically validated ADHD treatment. The useful test is whether the note reduces reconstruction without adding a burdensome evening routine.

Leave four lines, not a new plan

If there is no blocker, write none. If the next action is not visible because a decision is missing, the next action may be one clarification question. The note stays short by recording the doorway, not rewriting the project history.

Use the five-minute sequence

1. Minute 0–1: stop at a safe checkpoint. Save or close work using the required file, version, privacy, and security process.
2. Minute 1–2: write the last verified state and its source location. Separate confirmed from assumed.
3. Minute 2–3: write one next visible action with a concrete verb, object, and small ending.
4. Minute 3–4: place the restart cue in the environment where work will resume—calendar event, task home, folder, or approved workspace.
5. Minute 4–5: record the blocker or owner, then close. Do not begin solving a new branch inside the shutdown note.

Write for re-entry, not for memory

What research can and cannot support

Laboratory interruption studies describe a resumption lag: returning to an interrupted task takes time, and the interruption's duration and cognitive demand can affect that return. Other experiments have found that task-related cues can support resumption under specific laboratory conditions. These studies do not prove that this exact shutdown card improves real-world work for every person or specifically treats ADHD.

A separate series of experiments by Masicampo and Baumeister found that making specific plans for unfulfilled goals reduced several measured cognitive effects of unfinished goals in those study settings. That finding supports testing a specific return plan rather than carrying a vague intention. It does not mean every unfinished task should be planned at night, that a note guarantees mental detachment, or that more planning is always better.

Use the note as a reversible comparison. Try it on ordinary work for several sessions and observe reconstruction time, first stopping point, and whether the format itself becomes friction.

Choose the cue that will actually reappear

• Same file tomorrow: place the note in the approved project home and link to the exact current source rather than a local duplicate.
• Scheduled work block: attach the note to the calendar event or task entry without adding private details others can see.
• Physical task: place a privacy-safe cue beside the tool or container only when doing so is safe and does not obstruct shared space.
• Waiting on someone: put the request and follow-up date in the trusted system; do not rely on the other person's name sitting in an open note.
• Variable start time: use an event cue such as after the morning check-in rather than a precise time you cannot control.

The cue should retrieve the note, not expose confidential work. Follow current workplace, school, household, privacy, security, and records rules.

Repair common shutdown failures

• The note becomes a full daily review: cap it at one active project or the work you are actually suspending; use a separate scheduled review for the backlog.
• You keep writing continue: add the exact object and observable end, such as compare these two rows or draft the first paragraph.
• The state is uncertain: write unverified and name the source that must be checked before changing the work.
• Tomorrow begins somewhere else: move the cue to the real entry environment instead of copying the whole note across several systems.
• The same blocker repeats: send the clarification, identify the owner, or use the formal escalation route rather than rewriting the blocker each evening.
• Shutdown itself causes distress or lost sleep: shorten it, move it earlier, or stop the experiment. Persistent sleep, anxiety, mood, or functioning problems deserve appropriate qualified support.

Do not use a personal note where a real handoff is required

Medication, clinical care, machinery, driving, laboratory hazards, financial authorization, legal filings, cybersecurity, regulated records, dependent care, and other high-consequence work may require checklists, independent verification, logs, version control, incident procedures, or a direct handoff. Follow those controls even when they take longer than five minutes.

If another person must safely resume the work, use the required handoff and confirm receipt where the process requires it. A private note beside your laptop does not transfer ownership.

Test one note against one ordinary restart

1. Choose one ordinary, reversible project you expect to resume within a few days.
2. At the stopping point, write the verified state, next visible action, restart cue, and blocker or owner.
3. On return, read the note before scanning the whole project history.
4. Record only how long reconstruction took, where you first stopped, and whether any line was missing or wrong.
5. After three restarts, keep, shorten, relocate, or stop the format based on the pattern rather than one unusually easy or difficult day.

Tonight, do not build a shutdown system. Leave one four-line note for one ordinary project. The goal is not to finish the day perfectly; it is to preserve a truthful doorway into the next work session.