Roam Research Daily Notes: Turn a Log Into Next Steps

Roam Research daily notes work best as a dated capture point followed by a short review. Write down what happened as you work, connect relevant entries to their projects, and end the day by separating completed work, open questions, and the next action.

A daily log preserves the day; a handoff tells someone where to start next. fenbs can hold the selected task status and Where we left off for connected AI assistants, after you manually transfer and check the useful parts of your Roam notes.

How do you begin a useful daily entry?

1. Start in today’s Daily Notes entry and name the project you expect to work on. Write one immediate next action in ordinary language.
2. Capture short observations as they occur. Include a source or artifact location when the note describes something you may need to verify.
3. Separate a suggestion from a choice. If a person made a decision, record what they chose and when; otherwise label the question as open.
4. Before stopping, review the entry and write a short continuation note: completed, checked, still uncertain, waiting on a person, and start here next.

Roam presents its approach↗ (opens in a new tab) as collecting and connecting related ideas. Keep the daily routine simple enough to use while work is happening. You can clarify a rough sentence during the review instead of interrupting every activity to produce polished notes.

For example, begin a design review with the project name and the question under discussion. During the review, capture the options and evidence. At the end, add the actual outcome. That gives the note a purpose beyond being a timestamped list of whatever you happened to type.

What belongs in the log and what belongs with a project?

Use the daily entry to preserve sequence: the prototype failed a check, you changed the copy, then someone asked for another review. Use the project record to explain the current state: the copy is revised, the failed check still needs repeating, and approval is pending.

Connect the daily entry to the relevant project so you can return to the background. Write the current project summary separately and update it when the state changes. Otherwise, a reader has to reconstruct today’s answer from a trail of old observations.

This is one way to organize a broader AI second brain: keep the evidence findable while keeping the working conclusion readable. You do not need to turn every daily observation into permanent project knowledge.

How do you keep follow-ups from disappearing tomorrow?

Review actions before you close the entry. Rewrite vague reminders as concrete steps: check whether the revised form sends a message, rather than fix form. Include who needs to act, what they need, and the result that will let you call the action complete.

Choose one current place to track that action. If it becomes a fenbs task, keep the daily note as the background record and use the task for its current status. Maintaining two separate lists without deciding which is current makes a completed item look unfinished somewhere else.

Carry forward unresolved work by reviewing the project summary, rather than copying yesterday’s entire entry. A task waiting on a client needs a clear waiting explanation; it does not need another identical paragraph each morning. Put a review date in your own routine if you need to remember when to revisit it.

For reading sources, use the Roam book-notes workflow; for developing lasting ideas beyond a daily log, see the Roam Zettelkasten guide.

What should you save for the next AI session?

Write the smallest record that lets another session continue accurately. Include the project goal, the work completed, what was actually checked, what remains uncertain, and the next action. Mention the decision that constrains that action and where to find any necessary artifact.

Say a designer revised a contact form but did not test delivery. The handoff should say exactly that. If it says the form is finished, the next assistant may draft a release announcement before anyone knows whether messages arrive. Save the limitation beside the progress.

Read a proposed AI summary against the daily entry before accepting it. Remove invented ownership, dates, or approvals. The AI handoff guide explains how fenbs keeps this continuation record available when the chat or assistant changes.

How do you review a week without rewriting every day?

Look for changes in the work rather than recounting the week. Which questions became decisions? Which tasks stalled for the same reason twice? Which source or artifact needs to be easier to find? Keep a useful lesson when the answer should change your approach next time.

Keep a separate preservation routine for notes that matter. The Library of Congress guidance on digital preservation↗ (opens in a new tab) starts with selecting and organizing what to save, then keeping copies on separate media. A polished weekly summary is useful context, but it is not a backup of the original record.

Test the summary by reading it without the daily entries open. If you cannot tell what to do next, add the missing fact. If a paragraph is merely a list of activities, shorten it. The goal is an accurate continuation point that can survive a weekend or a change of assistant.

How to do this with fenbs

1. Create a free account. Add one active project on your personal kanban board; starting alone is free with no credit card.
2. Manually transfer the actions that need tracking into tasks. Use the plan for the next steps and record the current state accurately.
3. Add relevant project context and record a person’s decisions in Decisions and rules. Keep private reflections in your Roam notebook.
4. Connect a supported assistant using Integrations. Ask it to read the project context before it starts and save task and project progress before it stops.

fenbs is not the right fit for a private diary or a notebook whose only reader is you. It does not import your Roam graph. Use it when the selected work state needs to stay available beyond your personal daily record.

Keep the morning habit small: read the continuation note and choose the next action. Keep the closing habit equally small: correct the status and save the remaining work. The AI brain guide and second-brain topic hub explain the wider approach.