The daily note: you write once, in the shape you already use.

One page per day

There are no documents to create and no folders to pick: there is a day, and today is already open. Days scroll straight back, and each one saves itself while you type.

There are other ways to write into today's note without opening the tab:

If the planner left the week's Crítico for that day, Opens the day shows up above the note with that task: it is what goes first. See Calendar and planning.

Bullets, outlines and indentation: the shape is the data

The editor is block-based, like the one in documents: bullets, numbered lists, checklists, headings and plain lines. For the analysis, the marker does not matter: what matters is what each line hangs from.

• A line with no bullet opens a topic. It is the heading: the client, the person or the project.
• A bullet is an item of that topic. With -, * or •, with or without a space after the dash.
• Indentation builds the tree: Tab pushes one level in, Shift+Tab pulls out. If you type fast, repeating the dash does the same — -- is two levels, --- is three.

A well-formed note looks like this:

Acme
- meeting with Ana about the renewal
-- we have to send her the proposal on Friday
-- legal reviews the contract
- we decided to bill per milestone, not per hour

Internal
- finished the database migration
- pending: pick the release date

If you already wrote it all in one go, the Organize by topic pill on the bar under the note rewrites it into that shape — one line per topic, with the items hanging off it — without changing the text of the lines that are already tasks, and as long as you do not keep typing, Undo organizing puts it back as it was. It shows up once the note has a few lines, on the web and desktop; on the Free plan, twice a day.

Inheritance: every line is read with its branch

When a line goes out to be analysed it does not go alone: it goes with the full chain of its parents as context. The deepest bullet in the example above arrives as "we have to send her the proposal on Friday", with "Acme" and "Ana" hanging off it.

Three behaviours follow from that, and they are worth knowing:

1. 1
   The parent's entities flow downThe person, organization or project sitting in the heading can be attached to the bullet's task, spelled exactly as it is written above. That is why the name goes in once, spelled right, instead of five times spelled wrong.
2. 2
   A parent with real children becomes context"Acme open items" or "Ana, finish this week" do not become tasks: the real item lives in the bullets underneath, and the line above only groups them. Without this rule, every heading would leave you a phantom task with no object.
3. 3
   Unless the children are parts, not items"Review the whole contract" with "section 3" and "section 4" underneath is still a task: the children are pieces of the same object, not independent assignments.

The criterion behind all of it: a task has to make sense without reading the bullets that follow it. If you need to look further down to know what to do, that line is context.

Predictive typing: your knowledge, as you write

From the third character on, what you are typing is matched against the names in your Atlas — people, projects, organizations and labels — and a small list appears next to the cursor. It matches aliases as well as the stored name, and it catches a word in the middle or a compound name: "Mari" offers you Mariana Falcón, "carlos cast" offers Carlos Castro. Enter or Tab inserts it, and on closed days it never appears.

The same box shows up in documents, where it also completes formula variables when you type {{. See Memory and documents.

What gets flagged as you write · Hobby

Detection runs on top of what you write without touching it: it lays flags over your text, it never rewrites it.

Every line with content falls into one of four classes, and the first three leave a numbered flag over the text:

Whatever you want to be a task, a milestone or a definition without depending on detection, you mark yourself: the / → Mark as menu has Task, Milestone and Definition (and Reminder, further down). That line carries its flag from the moment you write it, and detection does not change it.

On top of the T flags a second one can show up, in amber: the warning that this task, read on its own a week from now, will not be understood. How it is scored and what it is for, in the next section.

In parallel, the panel on the right builds the labels of the day: people, projects, organizations and free labels, each linked to its Atlas entry. When a name it does not recognize shows up, it asks — who is "Ana"? — and you resolve it by linking to someone who already exists or creating them right there.

Everything is reversible before you close:

• The crossed-out eye dismisses a task, a decision, a milestone or a label. It stops counting for the close, and your text stays intact: what was surplus was the flag, not the line.
• Whatever you dismissed collects under Skipped, and comes back with one click.
• What is already confirmed in the Atlas beats what detection guessed: if "Acme" is stored as an organization, it will not be treated as a person because one sentence made it look like a name.

The vagueness score: will it still make sense in a week

A task written in the note lives two lives. In the note it is surrounded by everything that explains it: the line above, the project it hangs off, whatever you were writing. On the board it is on its own, one line among eighty, three days later. "Finish it on Wednesday" makes perfect sense while you are writing it and none at all when you read it loose — and by then there is nobody left to ask.

So every line flagged as a T also gets a score for the clarity of the action, which answers one question: is it clear what to do and about what? It does not look at whether the task matters, whether it has a date or whether it has an owner — all of that gets assigned later, at any point, and nothing is lost by not having written it in the note. What had to be done is the one thing you cannot recover.

A date or a proper name do not raise the score on their own: "finish it on Wednesday" still does not say what, and neither does "the Acme thing, pending". What raises it is having written the object of the action.

That score is crossed with a second thing, the anchor: whether the line hangs off a person, a project or an organization — its own, or inherited from the parent line. If it does, you will have something to pull on to reconstruct the rest. It is not a requirement: it is a mitigating factor.

A clear task with no project and no person never carries a flag: that is half the tasks in any note, and flagging them would turn the warning into wallpaper. The flag goes amber — yellow for the mild one, burnt orange for the severe one — and never red, which on the task list already means "urgent": two different warnings, and one task can carry both.

Why this is part of the method and not an app detail: a vague goal performs like "do your best", which is the worst instruction of the lot. It is in Capture, in the framework.

How it reads time

Dates are read in plain words and resolved against the day of the note, not against today. That is what keeps reopening last Friday's note on a Tuesday from shifting every date: "Monday" in that note still means the Monday after that Friday.

A date sitting in a line flagged as a task becomes its due date. After that there are two ways to change it without rewriting the line: drag the provisional task onto the calendar — that date overrides the one in the text — or set it while closing the day, with the +1, +3 and +7 day shortcuts.

Two details that prevent surprises: time words ("Monday", "week", "yesterday") are never taken as entity names, and a task's urgency — overdue, today, this week — is worked out in your local time.

Reminders: a line that also pings you

A date makes a task due on a day. An hour does something else: it makes something reach you at that moment, whether the app is open or not.

There are two ways to write one, and both count the same:

• With the / → Reminder menu, which writes the shape already built, rounded to the next half hour: ⏰ 15:30 — llamar al contador. Change the time and the text and you are done.
• By hand, in Spanish: "recordame mañana a las 9 llamar al contador". It understands clock times and also en un minuto, en dos horas or dentro de 3 días.

With no time there is no reminder: that is a task with a date, and everything above already covers it. The hour is exactly what creates something to announce.

They can also be asked for over chat, without opening the note: see WhatsApp and Telegram.

From a flag to a labelled task

While the day is open, every line flagged T lives as a provisional task: it already shows up in Tasks, with the Provisional label and the days it has left, the labels it inherited from its branch and the date read from the text. What you can do with it there is in Tasks. If you already took care of it, tick it done from the panel or from Tasks, and closing the day creates it already closed.

Provisional tasks are saved to your account, so they survive a reload and look the same from your phone. They last seven days: if you have not closed the day by then, they drop on their own.

Closing the day is what makes them real, and it is a review screen, not a blind button:

• Everything in one list, with a chip per row saying whether it is a Task, a Definition or a Milestone: if it landed wrong you change it right there.
• Tasks and milestones get a date in one click, or stay undated. A task that is too big can be split into several with AI, and the ones that arrived flagged vague get rewritten here: it is the last moment when fixing them costs one line.
• Every task carries a question — And this one? — with four answers: Me (it will ask for a block of your week), Someone else (it reserves follow-up, not your time), Already done (it took two minutes and you dispatched it: it is born closed) and Drop it. That is what keeps the week from filling up with things nobody decided to do.
• If a similar task already exists, it shows up beside it with how similar it is — "87% Write the copy for the stamps" — so you do not duplicate it.
• Definitions and milestones need at least one label — person, project or organization — to be saved: with nobody to belong to they do not enter the Atlas.

On confirm, tasks are created with their labels and their date, definitions and milestones are recorded, new entities are registered in the Atlas and the day locks. You can reopen it whenever you want: the lock says the day is processed, it does not shut you in.

Today you close yourself. Past days left open close on their own, after midnight or the next time you open the app: it comes switched on, and you turn it off with Close the day automatically, in the workspace settings.

What happens to those tasks afterwards — how they group into deliverables, how they look by person or by project — is in Tasks and detection.

Seven rules for writing the note

• One item per line. Two commitments in one sentence come out as a single task.
• The proper name on top, once. Everything hanging off that line inherits it.
• Make the task stand alone. "Review the Acme contract" is a task; "review that" is a note to yourself for the next two hours. That is exactly what the vagueness score measures.
• Say the date in words. "on Friday", "next week", "November 15": they all resolve against the day of the note.
• Accept the suggestion with Enter. It is the difference between adding to an entry and creating a near-copy of it.
• Dismiss with the eye, not by deleting the line. What is surplus is the flag; the text is your record of the day.
• Close the day. It is what turns all of this into tasks, entries and reports: while the day is open, none of it exists yet.