Get AI summaries of any video or article — Sign up free
How I use Logseq Daily - A Roam Research Alternative for Notes / PKM / To Do / Journal thumbnail

How I use Logseq Daily - A Roam Research Alternative for Notes / PKM / To Do / Journal

Ed Nico·
5 min read

Based on Ed Nico's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Use the Daily Journal page as the first step each morning to capture reflections, gratitude, and overnight thoughts before planning actions.

Briefing

Logseq Daily anchors a simple daily workflow that turns scattered thoughts into structured notes, actionable tasks, and trackable project context. Each morning starts with the Daily Journal page—an inbox for whatever is on the mind—then branches into reflections, gratitude, and overnight ideas before shifting into concrete goals for the day. That same page becomes the day’s command center: it holds “aims of today,” a practical to-do list, and quick reminders so key actions don’t get lost.

From there, the system stays lightweight but connected. Tasks are reviewed and broken down into what needs to be done (for example, calling someone or advancing a project). When a task requires context, the workflow links out to a dedicated project page rather than burying everything under the day’s entry. Project pages act as living summaries: they include key people, milestones, and status updates, and they keep call notes from turning the daily reminder into a long, messy document. When a meeting happens, a new page is created for that specific call (e.g., “Call with John…”) with next steps and takeaways, while the project page remains the stable reference point for what the project is and where it stands.

The approach also handles recurring “who/what” memory. For example, prior calls can be revisited by jumping to a date-specific page, and brief call summaries capture the essentials without reproducing the entire conversation. Logseq’s autocorrect and backlinking features reduce friction: autocorrect helps clean up quick entries, while backlinks automatically connect related notes so a user can trace thoughts back to the original date and context.

Outside daily planning, the workflow extends to reading and research. When consuming an article, the user creates a new page for the piece, then records key takeaways in their own words alongside the source link. This keeps ideas searchable and reusable later, and it supports revisiting “a moment in time” when the same topic resurfaces. Evening reflections close the loop: the Daily Journal page is used to review how the day went, what could improve, and what to prepare for next.

Overall, the core insight is that Logseq’s daily page works best when it functions as a hub—capturing thoughts, goals, and tasks—while deeper context lives in separate, purpose-built pages (projects, specific calls, and reading notes). The result is a system that stays organized without becoming cumbersome, making it easier to act during the day and review later with clear historical links.

Cornell Notes

Logseq Daily is used as a morning-to-evening hub for capturing thoughts, planning actions, and preserving context. Each day begins with the Daily Journal page for reflections and gratitude, then shifts into “aims of today” and a to-do list that turns intentions into concrete tasks. When tasks require background, the workflow links to dedicated project pages containing key people, milestones, and status updates, while individual meetings get their own dated pages with next steps and takeaways. Reading notes follow a similar pattern: create a page for an article, write key takeaways in one’s own words, and store the source link. Evening entries wrap up with reflection and preparation for tomorrow, supported by Logseq’s autocorrect and backlinking.

Why start with the Daily Journal page instead of jumping straight to tasks?

The Daily Journal page is treated as an “outbox” for anything on the mind—morning reflections, how someone slept, gratitude, and overnight ideas. That capture step prevents important thoughts from getting lost, and it also provides a place to branch into the day’s structure afterward. Once the mental clutter is written down, the same page becomes the launchpad for “aims of today” and the to-do list.

How does the workflow keep daily entries from becoming too long?

Daily reminders stay focused by linking out to separate pages for deeper context. Project details live on a dedicated project page (key people, milestones, and status updates). Specific meetings get their own dated pages with next steps and key takeaways. This avoids stuffing full call transcripts or extensive project history into the day’s entry, which would reduce the daily page’s usefulness as a quick reminder.

What’s the role of date-specific pages for calls?

Date-specific call pages act as lightweight memory anchors. Instead of recreating the whole conversation, they record who was involved and the key takeaways and next steps. Later, when it’s time to call someone again (like at lunch), the user can quickly find the relevant prior discussion and refresh context without searching through unrelated notes.

How are reading and research notes organized for later retrieval?

When reading an article, the user creates a new page for the piece and records key takeaways in their own words. They also copy and store the source link so the origin is preserved. This makes it easy to revisit the ideas as a specific “moment in time,” and it supports reuse when related topics come up again.

What features make the system feel low-friction?

Autocorrect helps clean up quick entries during capture. Backlinking connects related notes automatically, so thoughts can be traced back to their original date and context. Together, these features reduce manual organization work while keeping the note network navigable.

How does the evening routine complement the morning planning?

Evening reflections close the loop by reviewing how the day went, what could have improved, and what should be prepared for tomorrow. That reflection feeds forward into the next day’s Daily Journal capture, creating continuity between planning, execution, and adjustment.

Review Questions

  1. How does separating project pages from daily call notes improve the usefulness of the Daily Journal page?
  2. Describe the steps used to turn an article into a Logseq page that remains useful later.
  3. What information is stored on a call page, and how does that help when scheduling future calls?

Key Points

  1. 1

    Use the Daily Journal page as the first step each morning to capture reflections, gratitude, and overnight thoughts before planning actions.

  2. 2

    Write “aims of today” and convert them into a to-do list so goals become trackable tasks.

  3. 3

    Link tasks that need context to dedicated project pages rather than embedding full project history in daily entries.

  4. 4

    Create separate, dated pages for meetings that record participants, key takeaways, and next steps without reproducing the entire conversation.

  5. 5

    Store reading notes as article-specific pages with key takeaways written in your own words plus the source link.

  6. 6

    Use evening reflections to review performance, identify improvements, and set up preparation for the next day.

  7. 7

    Rely on Logseq’s autocorrect and backlinking to reduce manual cleanup and make related notes easy to trace.

Highlights

Daily Journal starts as a place to empty the mind, then quickly becomes a structured plan for the day’s aims and tasks.
Project pages stay clean by keeping milestones and status updates separate from day-by-day call notes.
Reading notes become reusable by pairing key takeaways with the original source link on an article page.
Backlinking makes it possible to revisit what was thought on a specific date without manual reorganization.

Topics