GTD in GleanLog
The five GTD tags, how they map to boards, and what "done" means.
GleanLog treats GTD as part of the data model, not a convention. Every task carries at
most one GTD tag, stored in the tasks.gtd_tag column, and that tag decides which
board shows it.
The five tags
| Tag | Board | Use it when |
|---|---|---|
@gtd-inbox | Inbox | You captured it and have not decided yet. |
@gtd-next | Next | This is the next concrete action. |
@gtd-waiting | Waiting | Someone else owes you something, or a date is in the way. |
@gtd-someday | Someday | Maybe later; keep it out of the way. |
@gtd-archived | — | Finished and filed; restorable, off the boards. |
Completed tasks leave the open boards and appear on Completed. Deleting a task is the one decision that cannot be undone, so the app asks first.
Tag versus status
A task's list also gives it a status (to do, in progress, complete — or whatever that list defines). The tag and the status are different things:
- The tag says how the task shows up in your GTD workflow.
- The status says where the task is in its list's own workflow.
When you change one, GleanLog maps the other by meaning: filing a task to Next moves it to an open status, and completing it moves it to the list's done status. A board or tag name is never written into a status field.
This is why you never have to maintain a second set of folders to make the boards work. The structure says where a task lives; the tag says what it means.
The review loop
- Capture without deciding. Everything starts in the Inbox.
- Triage the Inbox: give each item a tag, a list, or delete it.
- Work from Next. Check Waiting when you are blocked; dip into Someday when you plan.
- Complete what is done, and archive what you want to keep but stop seeing.