My Daily Workflow with RemNote

A single “Today” page in RemNote can act as the hub for a full workday—capturing stand-up prep, project journaling, meeting notes, and even code learning—while still letting those notes be reorganized later without losing the day’s narrative flow. The core idea is to keep one stream of capture in the daily document, then use RemNote’s organization tools to move content into project- or topic-specific areas once the day ends.

The workflow starts with RemNote’s daily document, created by using the “Today’s document” option that generates a page titled with the current date. For an analytics engineer working in an agile environment, that page becomes the staging ground for daily stand-ups. Before the 15-minute stand-up meeting, the workflow uses a short planning routine: spend five to ten minutes answering three stand-up questions—what was done yesterday, what’s planned for today, and whether any challenges need escalation. Notes are written directly into the daily page, and additional items that come up during the meeting are appended as they arise.

To avoid rewriting the same three questions every day, the workflow uses RemNote templates. After enabling templates in RemNote settings (via editor options), a “daily stand-up questions” template is created where the parent bullet point is marked as an automatically add template. The three question bullets become “slots,” so typing a hashtag in the daily document instantly inserts the structured prompts. That turns stand-up prep into a repeatable, low-friction routine and keeps the daily page ready for quick updates.

For longer project work, the approach stays intentionally lightweight: instead of creating separate folders and pages upfront, notes are captured in the daily document under a project heading as the work unfolds. For example, when planning a “project to make budget,” the notes naturally become a checklist of tasks and facts—like accounting for expenses or gathering forecasts—while also recording context from conversations (e.g., what was said by a stakeholder). Once the day is done, a small admin step cleans things up by moving the day’s project notes into a dedicated “projects” folder.

Crucially, moving doesn’t break the daily record. RemNote “portals” keep a window back into the original daily document, so the day remains a coherent log of what was worked on and achieved, even as notes are reorganized elsewhere. The same pattern is applied to recurring meetings such as weekly “ten tens” and career conversations: capture in the daily document, then move into the appropriate folder.

Finally, the workflow extends to knowledge retention. As a programmer, the system is used to save code snippets, theories, and concepts for later reference, using a separate structure for code learning. The overall payoff is reduced context switching—staying on one page for capture—paired with later organization that preserves both knowledge and the day’s timeline.