DocsUsing Kwilt
Using Kwilt

Organize To-dos

Kwilt's to-do list is meant to orient you before you configure anything. Priority order helps the next honest action rise, while still giving you simple controls when you need to scan a crowded list.

7 min readUpdated June 2026

Start with priority order

The normal To-dos view can use Kwilt priority to help you notice what is likely to matter now. It considers signals like schedule, priority, actionability, recency, tags, and context that already belongs to the Activity.

Priority is not a second inbox. It is an ordering layer over your real to-dos. If you filter, group, or choose another sort, Kwilt treats that as your explicit way of looking at the list.

  • Use priority order when you want the list to help you choose.
  • Use filters or grouping when you already know what slice you want to inspect.
  • If the priority order feels wrong, edit the to-do, its schedule, priority, tags, or goal connection.

Read priority indicators lightly

When you sort by priority, Kwilt can show small rank indicators such as #1, #2, or #3 on the highest-priority rows. They are there to help you scan, not to grade your life.

Priority can come from explicit priority, schedule timing, goal context, recent updates, or manual movement. If you drag a to-do or change its action state, Kwilt treats that as feedback.

Group when scanning helps

Grouping changes the visual shape of the list without changing what a to-do is. It is useful when you want to scan by Goal, schedule, or action state instead of reading one long pile.

Groups are presentation, not identity. A to-do can still belong to a Goal, carry tags, have a schedule, and show a priority state while appearing under one current grouping.

  • Group by Goal to see which outcomes are carrying work.
  • Group by Schedule to separate overdue, today, upcoming, and unscheduled work.
  • Group by Status to see active, needs review, waiting, and later work.

Use Areas for the part of life a to-do belongs to

Areas are managed from Settings and describe where different kinds of to-dos usually fit, such as Work, Family, Home, Health, or a custom area you add.

Use Areas when planning needs more context than a simple work/personal split. They help Kwilt understand where an Activity belongs without forcing every capture through a setup step.

Sort and filter with intent

Sorts and filters are best when they answer a specific question: what is due soon, what changed recently, what belongs to this Goal, what is waiting, or what has a certain tag.

Saved or custom views can remember useful combinations. If a view becomes too clever to maintain, simplify it back to the default list and let capture stay easy.

  • Use Last modified when you want to resume recently touched work.
  • Use schedule and due-date views for time-sensitive work.
  • Use tags for reusable labels like errands, school, calls, or groceries.

Open tag groups when retrieval matters

Tags can behave like quick retrieval groups. If you have several to-dos tagged groceries, school, calls, or errands, open the tag list to pull that subset forward without building a full custom view.

Tags work best when they stay short and reusable. You do not need a perfect taxonomy; one clear label that helps you find a set later is enough.

Use action states honestly

Not every to-do is ready for immediate action. Kwilt can represent work as active, waiting, later, or needing review so the list does not pretend everything deserves the same attention.

These states are meant to reduce noise. Moving something to later or waiting is not failure; it is a way to make the active list more truthful.

Promote steps when they become real work

Sometimes a step inside a larger activity grows into its own to-do. Kwilt can keep that relationship so the new Activity is not detached from the original plan.

Use this when the step needs its own schedule, notes, priority, or follow-through. Keep it as a step when it is only a small part of the parent activity.

Next step
Keep going while the context is fresh.
Use Focus Mode

Related docs