The real job is not organisation — it is trust
A useful personal organisation system does not need to be clever. It needs to be trustworthy enough that your brain stops rehearsing the same reminders. That trust comes from a simple promise: when something matters, it has one obvious place to go, and when you need it again, you know how to find it. Life, Sorted. works best when you treat it as a dependable home for open loops rather than a collection of features to fill in. The goal is not to build a perfect database of your life. The goal is to reduce the number of things you have to keep mentally active.
People often assume the answer to feeling disorganised is more structure. In practice, too much structure creates another job. If you need to decide between twelve categories, three levels of projects, seven kinds of tags and a complicated review ritual every time you remember something, the system becomes harder to use than your memory. A trusted system has enough structure to answer useful questions such as what is due, what am I waiting for, what matters today and where did I put that note. Anything beyond that should earn its place by making a real decision easier.
Start by judging the system on behaviour rather than appearance. Can you capture something in seconds? Can you find it later? Does a task stay attached to its subtasks and supporting link? Does an appointment remain one record when the time changes? Can you see overdue work without searching? Can you leave for a few days and return without rebuilding the whole thing? Those are signs of trust. A beautifully organised dashboard that you avoid opening is not a successful system.
Capture first, decide second
The first habit worth building is capture. When something appears in your head — book the dentist, ask someone about a refund, remember a birthday idea, buy a cable, write down a thought — get it out of working memory quickly. Quick Capture exists for exactly this reason. If the item is obvious, you can describe it naturally and let it become a task, event, note, errand or another suitable record. If you are not sure what it is yet, putting it in the Inbox is better than leaving it in your head while you debate the perfect category.
Capture should be deliberately low-friction. You are not writing the final version of the task or planning the whole outcome. A rough line such as “sort insurance renewal” is enough to preserve the thought. Later, when you have the attention to clarify it, you can add the due date, provider, link or notes. This separation matters because remembering something and organising something are different kinds of mental work. Forcing yourself to do both at once makes capture slower, and slow capture is the kind people stop using.
The Inbox is not a failure state. It is a buffer. A small amount of unsorted material is healthy because it lets you preserve information without interrupting whatever you were doing. The problem is not having an Inbox; the problem is never looking at it again. Use the Weekly Reset or a short sorting session to turn captured items into tasks, calendar events, notes, goals, waiting items or references. Delete things that no longer matter. The point is to make decisions when you have the capacity to make them, not the second an idea occurs.
Know the difference between a task and a calendar event
A task is something you need to do. A calendar event is something that happens at a particular time or on a particular date. That sounds obvious, but mixing the two is one of the fastest ways to make both lists unreliable. “Call the garage” is usually a task because you can choose when to do it. “Garage appointment at 10:30” is a calendar event because another person and a time are involved. A deadline may belong in the calendar for visibility while the work required to meet it belongs in Tasks.
Use dates on tasks when the date helps you make a decision. A due date should mean something more useful than “I would vaguely like to do this by then.” If everything is due Friday, nothing is genuinely due Friday. Keep undated tasks undated until a date becomes useful. Life, Sorted. can still surface tasks by duration, energy and status, and What now? can help you find something sensible without manufacturing deadlines. Reserve the calendar for commitments and the task due date for work that really becomes relevant or urgent around that day.
When an appointment changes, edit the existing event rather than creating a replacement. One record means Search, Calendar and Today all point to the same information. Add the location, useful link and preparation notes to that event so you are not looking through messages five minutes before leaving. If the event creates work — for example, fill in a form before the appointment — make that a task and give it enough context to act on. The event tells you when. The task tells you what you need to do.
Make tasks small enough to start
A task should describe an action you can recognise when you see it. “Sort finances” is not necessarily wrong, but it is broad enough to create hesitation. “Download last three bank statements” or “list subscriptions to cancel” gives you a clear beginning. If a task contains several separate actions, use subtasks. The parent can hold the overall outcome while the subtasks show the sequence or the smaller pieces. This is especially useful when you want the task to remain visible as one piece of work rather than becoming five unrelated entries.
Do not decompose everything. “Put bins out” does not need six subtasks. Break work down when the current wording causes friction, when several steps need tracking, or when different steps have different dates. The best level of detail is the level that makes starting easier. If you are adding structure because the app allows it rather than because it helps, stop. A system becomes useful by removing decisions, not by providing more boxes to fill.
Links and notes belong with the task when they reduce future searching. If a task is “renew breakdown cover”, attach the renewal page. If there is a reference number that is not highly sensitive, put it in the notes. If the task belongs to a larger goal, use the goal action system rather than inventing a second copy of the same work. When the supporting information travels with the action, the moment you decide to work on it is not immediately followed by ten minutes of hunting.
Use lists for collections, not commitments
Lists solve a different problem from Tasks. A shopping list is a collection. A packing list is a collection. Questions for an appointment are a collection. Places you might visit are a collection. Those items do not necessarily need their own due dates, energy levels or workflow statuses. Keeping them in Lists makes them easier to scan and keeps Tasks focused on actions that require a decision or completion.
Sections become useful when a list grows. Groceries might be split into fruit and veg, fridge, cupboard and household. A packing list might use clothes, toiletries, tech and before leaving. The section should help you move through the real situation more easily. If a list contains four items, sections probably add more ceremony than value. You can add a section later when the list earns it.
Favourite lists you repeatedly reopen so they appear in Saved. That is a shortcut, not a duplicate. The original list remains the source of truth. Rename items when they change, clear completed items when the history no longer matters, and archive lists you want to keep without seeing every day. This keeps the active list screen quiet while preserving useful templates and reference material. A good list is something you can reopen and use, not an archaeological record of every item you have ever ticked.
Separate notes from reference information
Notes are useful for working information: thoughts, meeting notes, ideas, instructions, appointment details or something you are developing. Reference is better for stable information you expect to look up again, such as model numbers, provider information, sizing, household details or repeat instructions. The distinction does not need to be perfect. It simply gives your future self a more obvious place to look.
Pin a note when it is temporarily important or repeatedly useful. Save a reference when you know you will return to it. Search remains the safety net. If you cannot remember whether you put something in Notes or Reference, search the words you remember. A good system should tolerate imperfect filing. You should not have to memorise the system in order to use the system.
Avoid storing passwords, banking credentials, security answers or highly sensitive identity information in ordinary notes or references. Those belong in tools designed to protect secrets. Life, Sorted. is for everyday organisation. Being able to put everything in one place does not mean every kind of information should be there. Trust also means knowing what the system is not for.
Treat Waiting On as a real workflow
A surprising amount of mental clutter comes from work you cannot currently do. You have emailed someone, submitted a form, asked for a quote or requested a refund, and now another person has the next move. If you leave that as a normal task, you keep seeing an action you cannot take. Move it to Waiting On. Record who owes the response, when you asked and, most importantly, when you want to follow up.
A follow-up date converts vague anxiety into a decision. Until that date, you have permission not to think about it. When the date arrives, the item becomes actionable again. You can chase it, change the date or mark it received. This is one of the clearest examples of a system reducing cognitive load: the app is not doing the follow-up for you, but it is holding the agreement you made with yourself about when to look again.
Use Life Admin for obligations such as renewals, policies, bills, memberships and documents where provider, due date, recurrence and status matter. Waiting On is about another person or organisation making the next move. Life Admin is about an obligation remaining visible over time. Keeping those flows separate makes each screen quieter and more meaningful.
Let Today be a filter, not another master list
Today should answer a narrow question: what needs my attention now? It should not be a copy of every task, every goal and every future intention. Calendar events, the three priorities you deliberately chose, due tasks, useful routines, overdue work and a small number of upcoming reminders are enough. Everything else can stay where it belongs until it becomes relevant.
Choosing Today’s Three is a constraint, not a productivity score. Some days you need one priority. Some days an appointment is the whole day. The value of the three slots is that they force a decision about what deserves protected attention. If you fill them with trivial work simply to have three, the feature loses its purpose. Keep the selection honest and change it when reality changes.
Use the daily note for loose ends that belong to the day but do not deserve a new task or permanent note. It can hold a phone number you need for a few hours, a sentence about how the day went or a reminder to mention something later. If it becomes important beyond today, move the useful part into a proper task, note or reference. Today should feel lighter when you close it, not become another archive.
Use What now? when planning has stopped helping
There are moments when a carefully prepared task list is still too much. You have fifteen minutes, low energy and access only to your phone. Instead of scanning forty items and repeatedly rejecting them, use What now? to filter by the constraints you actually have. This is not an algorithm deciding what your life should be. It is a way to reduce the search space so you can choose from a handful of realistic options.
Energy works best as a practical estimate, not a personality judgement. Low-energy tasks should be things you can do when concentration or motivation is limited. Moderate tasks need more attention. High-energy tasks need your better hours. If you have high energy, lower-energy tasks are still possible; if you have low energy, a demanding task may simply be a poor fit right now. The purpose is to help the plan adapt to the person who actually turned up.
Starting a suggested task should change its status so you can find it again, and completing it should close the loop. If the suggested task still feels too large, edit it or create a smaller subtask. Repeatedly rejecting the same task is useful information. It may need clarification, a different context, a smaller first step or a decision to remove it. A task system should reveal friction rather than hiding it behind more scheduling.
Review the system just enough to keep it believable
A system loses trust when old information accumulates. Overdue tasks that no longer matter, expired waiting items, abandoned routines and stale plans make every current item harder to believe. The Weekly Reset exists to clean those edges before they become noise. You do not need an elaborate ritual. Clear the Inbox, glance at what happened, check the calendar and important dates, choose a few priorities, decide what to do with overdue work, scan errands and life admin, then write a short note if it helps.
The important word is decide. Do not automatically carry every unfinished task into another week. Ask whether it still matters, whether it needs a new date, whether it should become smaller, whether someone else has the next move, or whether you can delete it. Rescheduling without thinking simply moves clutter forward. A review is valuable when it changes the information, not when it merely confirms that a long list still exists.
Longer-term reviews serve a different purpose. Weekly organisation asks what needs attention. Direction reviews ask whether the goals and priorities still belong in your life. A goal can be paused or released without being a failure. A plan can be rewritten when circumstances change. Trust grows when the system reflects reality rather than demanding that reality match an old plan.
Keep cross-device sync boring
Sync should be infrastructure, not a feature you have to think about all day. The same Life, Sorted. data store underpins the modules, and independent account sync will eventually be there to move that saved state between devices. Your normal workflow should remain simple: edit the real record, let the app save it, and expect the same record to be available when the account connection has synced. Saved items are shortcuts inside the app; sync is what preserves the underlying data. They solve different problems.
Avoid creating duplicates because another device appears briefly out of date. Reopen the app, allow the connection to settle and check Search before entering the same information again. If a genuine conflict is detected, choose the correct copy deliberately. Cross-device systems are most reliable when there is one source of truth for each task, event or note and when edits happen to that record rather than to copies scattered across modules.
The practical test is simple. Add a harmless test task, let it save, open the app on the other device, confirm it appears, edit it there, then confirm the change returns. Do the same with a note or appointment if you want confidence in the workflow. Once you have proved the round trip, stop testing and use the app. Infrastructure is doing its job when it becomes uninteresting.
What a healthy Life, Sorted. system looks like after a month
After a few weeks, the app should contain real information but still feel navigable. Tasks should mostly represent things you might actually do. Completed work should disappear from the active views. Calendar events should be accurate enough that you trust them. Lists should be reusable rather than duplicated. Waiting On and Life Admin should hold open loops that used to float around in your head. Search should rescue you when you forget where something lives.
Your system will not be perfectly clean. That is normal. There may be uncategorised tasks, an old note, a routine you should pause and a list you forgot to archive. The standard is not perfect maintenance; it is recoverability. Can you find the important thing? Can you see what needs attention? Can you clean up a small amount of drift during a review? If yes, the system is doing useful work.
The best sign is that you think less about organisation itself. You capture something, find it later, make a decision and move on. Planning becomes a short conversation with reality rather than a hobby. The app earns trust by helping you remember, choose and close loops while staying out of the way. That is the standard worth optimising for: not the most detailed system, but the one you continue to use because it reliably makes ordinary life easier.