View all guides

Working notes

Turn rough meeting notes into a searchable .md file

During the meeting, capture the time, a decision candidate, and an owner. Afterward, separate what was decided from what remains open and add the next review date. You can find that structure later without keeping a transcript.

ResultOne searchable .md file per meeting, with decisions and actions separated
01

1. During the meeting, leave signposts instead of polished prose

Trying to rewrite each sentence while listening makes the next point easy to miss. Capture time, a decision candidate, an open question, and an owner. Rewrite after the meeting.

Rough notes14:08 pricing visibility needs decision14:21 Minji — verify data by Friday14:34 mobile first / reason: 62% of requests
02

2. Put the result above the chronology

Start with meeting name, date, participants, and a one-sentence outcome. Separate decisions from deferred items so a reader does not have to replay the discussion.

  • Decision and reason
  • Deferred item and missing evidence
  • Action with owner, done condition, and review date
  • Source link or recording timestamp
03

3. Write for search

Replace phrases such as ‘go with that option’ with the product, version, and exact choice. Pair a person with a role so the note still works after responsibilities change.

Before → afterGo with that option → Use TAB.REC 0.6.0 scheduled-stop revisionCheck by Friday → Store operations checks permission copy by August 14
04

4. Keep filenames boring

  • Start with YYYY-MM-DD for chronological sorting
  • Use the product or project name people actually search
  • Avoid final-final; put the updated date inside or use version control
Examples2026-08-08-packwink-adsense-review.md2026-08-12-tabrec-release-check.md
05

5. Spend two minutes on the export

Paste into MD.SAVE and check that there is one H1, heading levels are sequential, and links are not empty. Remove internal URLs and personal information before external sharing.