The DAYS Framework: A Repeatable Daily Planning Template

When planning is done by feel, results swing. Some days are sharp and some drift. A framework turns a good day into a repeatable one. This one has four steps, about four minutes in the morning and two in the evening, and it is taught in Lesson 6.1.

I call it DAYS: Dump, Aim, Yield, Sum up. The names are just memory aids. The steps are what matters.

Dump everything, Aim at one thing, Yield time on your calendar, then Sum up the day in two minutes. Repeat daily.

D: Dump

Write everything in your head as it comes, for one minute. Tasks, worries, replies you owe, things you avoid. Do not sort. The dump is for getting things out of your head so you can see them.

Include the calendar. Add a line for each event, with its time. Your plan has to fit around those.

A: Aim

Paste the dump into an AI tool and ask for the one thing that matters most.

Here is everything on my plate today: [paste tasks, calendar, messages you owe replies to]. I have [hours] free. Pick the one thing that matters most and say why in two lines. Then list at most two more things that fit around it, and what I should drop or push to tomorrow. Ask me one question if something is unclear. Do not write a long list.

Read the answer. If you disagree, say why and ask again. The point is that you leave this step with one named task.

Y: Yield

Yield means giving the task time. Create a calendar event for it, 45 minutes or more, in your best hours. Name the event after the task. In Google Calendar you click an empty time, add a title and click Save; check your own calendar's help page if you use another.

Then yield the other way: decide what you will drop or move. Write one line, "Not today: X." A plan that cannot say no is only a list.

S: Sum up

At the end of the day, spend two minutes. Three lines:

1. Did the one thing move? Yes, partly or no.
2. What got in the way?
3. What carries over?

Tomorrow you begin by reading this note, so Sum up feeds the next Dump.

The framework on one card

The first three steps happen in the morning and take about four minutes. Sum up takes two minutes in the evening.

Why four steps and not ten

Each step solves a different failure. Dump fixes a crowded head. Aim fixes the lack of a choice. Yield fixes tasks that never get time. Sum up fixes the lack of feedback. If you remove one step, that failure comes back.

Make it repeat

A framework only helps if it runs. Attach Dump to a trigger such as opening your laptop. Keep the prompt saved so you paste, not write. After seven days, count how often the one thing moved.

Adapting it

If you work in shifts, run it at the start of each shift. If you manage a team, Dump should include what others wait on you for. If your calendar is packed with meetings, Yield may mean moving a meeting. Try it in your own setting for a week and change one step at a time.

The lesson that teaches this in full is Lesson 6.1. Pair it with your weekly review to see how daily picks add up, and a clean inbox every morning to shorten the Dump.

A full run of the framework

Say you are a coach with client sessions at 10 and 2. At 8:30 you open your note.

Dump. Prepare session notes, reply to three enquiries, write the newsletter, book travel, fix the booking page, pay a supplier.

Aim. You paste it in with "three hours free" and ask for one thing. The answer picks the three enquiries, because leads go cold and the replies are quick, and puts the newsletter second. You agree.

Yield. You block 8:45 to 9:30 for the replies. You write "Not today: booking page and travel."

Sum up. At 5pm you write: replies done, newsletter half done, a call ran over. Carry the newsletter. Tomorrow's Dump starts with that line.

The example is made up to show the shape, not to claim a result.

Common ways the framework breaks

Dump turns into a long sort. Keep it to a minute and do not rank. Aim returns a list. Repeat the instruction to give one thing and two extras at most. Yield gets skipped because the block feels optional. Make it a calendar event with a name and treat moving it as a decision. Sum up gets dropped on busy days. Do the 30 second version: one word for yes, partly or no.

Weekly use

Once a week, read your seven Sum up notes together. Look for the same obstacle appearing twice, such as meetings, a vague task or late starts. That is where the next improvement is. Your weekly review shows how to do this with AI help, and the metrics post covers which numbers to track. If you want a blank version to copy, use the free template.

How the framework differs from a to do list

A to do list records what exists. The framework decides what happens. The list is an input to the Dump step and nothing more. This is why people who keep a list and still feel stuck often improve quickly: they were missing the choice and the time, not the list.

It also differs from a weekly planner, which sets direction. The daily framework is the last mile, turning a direction into a Tuesday morning. If you want the weekly layer, your weekly review is where it lives, and the lesson shows how the two fit together.

Teaching it to someone else

The framework is easy to hand on. Give a colleague the four step card and the prompt, and ask them to run it for three days. Because each step has a clear output, you can ask "what was your one thing?" and get a short, specific answer, which makes a quick daily check in with a team much lighter.

Questions people ask

Do I need to follow the names?

No. They help you remember. The four actions are what count.

Can I skip Sum up?

You can, but it is the step that makes tomorrow easier. It takes two minutes.

What if I have two equally big tasks?

Ask AI which one has the earlier consequence. Pick that one.

Go deeper with the lesson

This post gives you the framework. Lesson 6.1, Plan your day in five minutes takes you through it step by step, in plain words, so you can do it for your own business.