Time blocking fails when the calendar becomes a wish list. You plan a careful day, then a call runs long, a small task reveals three hidden tasks, and your afternoon blocks start looking like polite fiction. For ADHD brains, the gap between plan and day can feel especially loud.
A better daily plan starts from the notes that already know what's going on. Docapybara gives you a place to keep project pages, meeting transcripts, PDFs, loose tasks, and small inline databases, then ask Capy to help turn the current state into a realistic day. The point is not a perfect calendar. The point is fewer cold starts.
Plan from evidence, not from vibes
Before you block time, gather the sources. Open your inbox page, active project pages, meeting notes from yesterday, and any planning page you already use. Ask Capy to find open loops, due dates, waiting items, and tasks that have enough context to do next.
This is different from sitting with a blank planner and asking yourself what you should do. Blank planners reward whatever is loudest in your head. Your notes remember quieter things: the follow-up promised at the end of a call, the PDF you need to review, the decision you parked because you needed one more detail.
For the capture side of this, The Capture Habit pairs well. For the ADHD-specific note setup, see Note-Taking with ADHD.
Make a daily page that can get messy
Create one page per day or one rolling page for the week. Keep it simple: date, commitments, focus blocks, admin blocks, open loops, notes from the day. The page should be allowed to become messy because the day is messy.
A daily page is useful because it becomes both plan and record. In the morning, it holds what you intend to do. During the day, it catches interruptions and notes. In the evening or next morning, Capy can read it and help move unfinished items forward.
If you prefer a weekly shape, nest daily pages under a weekly parent. Page nesting lets you keep the current week easy to browse without designing a large planning architecture.
Use blocks as containers, not promises
A time block should answer "what kind of attention belongs here?" not "what exact future will occur?" Use broad labels: deep work, admin, errands, calls, recovery, planning. Then attach a short list of candidate tasks to each block.
For example, an admin block might contain three possible actions from your notes: send the invoice follow-up, book the vet appointment, and update the return status. If one task takes longer than expected, the block still did its job. It held admin energy.
This is where an energy column in an inline database can help. Use the :::database::: directive for active tasks with columns like task, context, status, due date, and energy. Then ask Capy: "From my active list, suggest low-energy admin tasks for a short block and deep-work tasks for a longer one."
Keep context attached to each task
A block that says "proposal" is not enough if the proposal context lives elsewhere. Put the task near the source page or link back to it. A daily page can say "Draft Rivera proposal" and link to the project page with the call transcript, requirements, pricing notes, and previous draft.
Capy can help assemble the context before the block begins: "Read the Rivera project page and give me a short brief for the proposal block." That gives you the relevant facts without reopening every source manually.
This same principle shows up in drafting emails and proposals inside your notes. The work gets easier when the task and the context live close together.
Re-plan without treating it as failure
The plan will break. Build a re-plan prompt into the daily page: "Given what changed today, what should move, what should drop, and what still needs attention?" Use it after lunch, after an interruption, or when the calendar starts to feel imaginary.
Capy can read the daily page and active notes, then suggest a revised plan. You still choose. The agent's job is to reduce the friction of seeing the new shape of the day.
This is especially useful for ADHD because the transition from "plan broke" to "new plan" is often where the day leaks away. A short re-plan makes the next step visible without requiring you to rebuild from scratch.
End the day by preserving the residue
Daily planning creates residue: tasks you didn't do, notes from calls, ideas that arrived during a block, and decisions you made while working. If that residue stays on the daily page forever, it becomes clutter. If you delete it, you lose context.
At the end of the day, ask Capy to sort the residue: "Move unfinished tasks to the active list, summarize decisions, and suggest which notes should become project updates." Review the changes before accepting them. Keep the daily page as a record, but move durable context to the pages where it belongs.
For people who keep restarting systems when daily pages pile up, How to stop starting over with productivity systems is the next guide to read.
Keep the plan humane
A useful day plan leaves room for being a person. Add buffer. Add recovery. Add a block whose job is catching up. Don't let the agent produce a heroic schedule just because the notes contain many tasks. Ask for a realistic plan with fewer commitments than the day could theoretically hold.
Docapybara helps most when the plan is grounded in your own vault: pages, transcripts, PDFs, and databases that reflect the real work. The setup notes are in the docs if you want to see how the workspace fits together.
Try Docapybara free at signup. Start with tomorrow's daily page, ask Capy to pull open loops from your current notes, and block only the work that actually has enough context to begin.