Daily Notes for PKM: Build an Inbox That Processes Itself

A daily notes practice is the capture layer of any effective PKM system.

Daily notes are where you dump everything:

• Quick thoughts
• Meeting snippets
• Ideas that pop up
• Things to remember
• Fragments you'll process later

Daily notes lower the friction to capture.

The key insight: daily notes are an inbox, not final storage.

You capture daily. You process weekly. You extract permanent notes monthly.

This guide covers designing a daily notes practice that actually works.

---

What Daily Notes Are For

Daily Notes Are For:

✅ Fleeting thoughts (capture before they disappear)

✅ Meeting notes (quick capture, process later)

✅ Temporary references (links, quotes, reminders)

✅ Day-specific info (who did I talk to, what happened)

✅ In-progress thinking (working through a problem)

✅ Low-friction inbox (everything goes here first)

Daily Notes Are NOT For:

❌ Permanent storage (that's permanent notes)

❌ Project documentation (that goes in project folder)

❌ Polished writing (that's final output)

❌ Permanent knowledge (that gets extracted later)

❌ Long-term reference (that belongs in permanent notes)

---

The Daily Notes Workflow

Phase 1: Capture (Throughout the Day)

As ideas, meetings, references, and thoughts happen:

Write them in today's daily note.

Format: Simple, fast, unpolished.

Thursday March 21

Standup

• Feature X is blocked on API response
• We'll retry after release Y
• Sarah will coordinate

Quick idea

• Maybe we should batch API calls instead of individual requests?
• Would save bandwidth

To Revisit

• That article on pagination [[link]]
• Process design from 2023 project

Decision from leadership

• Deprecating feature Z by Q3
• Why: no usage data, maintainability burden

**Key:** Speed and capture. Polish doesn't matter.

### Phase 2: End-of-Day Review (5 mins)

At end of day:

1. Scan today's note
2. Extract anything important for tomorrow: deadlines, decisions, action items
3. Note anything that needs follow-up

### Phase 3: Weekly Processing (30 mins)

Every Friday:

1. Scan all daily notes from the week
2. Extract 3–5 ideas worth keeping:
   - Meeting decisions that matter
   - Ideas that are interesting
   - Frameworks you'll reference
3. Create permanent notes or project entries for these items
4. Mark processed items done or move to archive

### Phase 4: Monthly Extraction (30 mins)

Every month:

1. Review weekly summaries and extracted items
2. Create high-level notes for recurring themes
3. Archive old daily notes
4. Identify patterns (what you're thinking about, what's recurring)

---

The Daily Note Template

Simple template structure:

[Date] [Day of Week]

Today's Focus

• [what you want to focus on]

Meetings

• Meeting name at HH:MM
  • Key point 1
  • Key point 2
  • Decision: ...

Ideas / Thinking

• Idea 1: description
• Idea 2: description

References

• [[Note or link]] — why you saved it

Decisions / Updates

• Decision X made
• Update: Status of project Y

To Do Today

• Task 1
• Task 2

Tomorrow

• Remember to ask about X
• Follow up on Y

Keep it minimal. The above is a template, not a requirement.

---

How Daily Notes Connect to Your Knowledge System

Extraction Flow

Daily notes → Weekly review → Extract important items → Permanent notes or project files

Example:

Daily note (capture):

### Idea
- API batching would reduce bandwidth by maybe 40%?
- Need to investigate actual impact

Weekly review:

• Idea seems good, extract for investigation

Create permanent note or project item:

• Add to "Performance Optimization" project
• Create task: "Investigate API batching impact"

Linking Back

When you create permanent notes from daily captures, link back to the original daily note:

"Source: [[March 21 Daily Note]]"

This creates a trail: capture → processing → permanent knowledge.

---

Preventing Daily Note Sprawl

Daily notes can become chaotic. Prevent this:

Rule 1: Archive Old Notes Monthly

After processing, move old daily notes to an Archive folder.

You can still search them if needed, but they're out of the active inbox.

Rule 2: Don't Over-Detail

Daily notes don't need perfect grammar or formatting.

"API batching 40% savings?" is fine.

"I was thinking about how batching API calls might save approximately 40% bandwidth, which would be excellent for our performance..." is too much.

Rule 3: Review Weekly

If you don't review weekly, they pile up and become unprocessable.

Set a calendar reminder for Friday 4 PM: "Daily note review."

Rule 4: Extract, Don't Copy

When you extract something to permanent notes, move it or reference it.

Don't duplicate.

---

The Psychology of Daily Notes

Daily notes work because they lower friction.

You don't need perfect organization. You just need to capture.

Organization happens later during weekly review.

This separation is powerful:

• Capture (unorganized, fast, daily)
• Process (organized, intentional, weekly)

Mixing them is where systems break down.

---

Examples

Example 1: Researcher

Monday's daily note:

### Paper Review
- Loaded "Attention Is All You Need" paper
- Key insight: attention mechanism replaces RNNs entirely
- Note: might connect to work on efficiency

### Ideas
- Could we apply attention to sequential data in our domain?
- Probably worth exploring

### Reference
- [[Paper link]]

Friday review:

• Extract: "Attention mechanism" idea is interesting
• Create permanent note: "Attention Mechanism Overview"
• Add to project: "Next quarter research"

Example 2: Manager

Tuesday's daily note:

### Team Standup
- Project X behind schedule (API work slower than expected)
- Decision: extend deadline by 2 weeks, communicate tomorrow
- Sarah will coordinate communication

### To Follow Up
- Check on API bottleneck progress Thursday
- Confirm extended deadline with stakeholders

Friday review:

• Extract: "API Bottleneck" as project issue
• Add to project management system
• Note: Decision log entry "Extend Project X deadline due to API complexity"

---

Daily Notes in Different Tools

Obsidian

Create a Daily Notes plugin:

• Automatic daily note creation
• Template support
• Automatic linking

Roam Research

Built-in daily notes:

• Each day gets a page
• Can embed and link

Notion

Create a "Daily" database:

• New entry per day
• Use template
• Filter by date

Google Docs / Markdown

Manual approach:

• Create one document per month
• Sections for each day
• Copy template each day

---

Starting Your Daily Notes Practice

Week 1: Setup

1. Choose a tool (recommend Obsidian or Notion)
2. Create a template (use the one above or simplify)
3. Create today's daily note
4. Capture throughout the day

Week 2: Add Review

1. Continue capturing daily notes
2. End of week: spend 30 mins reviewing
3. Extract 2–3 items to permanent notes

Week 3–4: Build the Habit

Continue the workflow:

• Daily capture (2 mins at end of day)
• Weekly review (30 mins Friday)
• Extract to permanent notes or projects

Month 2: Optimize

• Archive old daily notes
• Review patterns (what you're thinking about)
• Adjust template if needed

---

Conclusion

Daily notes are the inbox of your PKM system.

Workflow:

1. Capture daily — fleeting thoughts, meetings, ideas (minimal polish)
2. Review weekly — extract what matters
3. Extract monthly — create permanent notes from patterns

Key insight: Capture fast, process slow. Don't mix.

Start this week:

1. Create today's daily note
2. Capture throughout the day
3. Next Friday: review and extract

In a month, you'll have a low-friction capture system feeding your permanent knowledge base.

For more on Zettelkasten (which uses daily notes as input), see Zettelkasten Method Guide. For extracting to permanent notes, check Fleeting Notes to Permanent Notes.