Someone asks why a project deadline changed. You remember the discussion, but not which meeting contained it. A folder full of files called “weekly notes” does not give you much to search.
A searchable meeting knowledge base connects an answer to the meeting record that supports it. Start with consistent names, a short index, and links between summaries, decisions, and source material. You can build it in a shared system your team already uses.
Give each meeting a predictable home
Choose one maintained location for a recurring meeting series. It might be a shared drive, document workspace, or project area. Avoid keeping the only usable copy in one participant's personal folder.
A simple structure could be:
Project review/
Index
2026-09-13 — Atlas review/
Summary
Source notes or transcript
Recording, if retained
This is an example, not a required naming standard. Include the actual meeting date and a stable project name. Add a distinctive topic when “weekly review” would be too vague.
Do not create a separate file for every section just to match a folder diagram. A short meeting may need one document with a source link. Keep separately managed decisions and tasks linked rather than duplicating them.
Let a reader enter at the right level
Someone checking the current decision needs a short answer. Someone disputing that decision needs the supporting passage. Keep both routes available:
- Summary: the main outcome and unresolved questions.
- Decision record: what was chosen, why, and whether it still applies.
- Task link: confirmed work, its owner, and current status.
- Source: the relevant notes, transcript passage, or permitted recording moment.
Our decision-log guide covers the individual choice. The action-item guide covers the work that follows. This page is about finding those records later.
Create an index people can scan
At the top of the meeting-series folder, keep one index with the series name, its owner, links to recent records, and important current decisions. Describe links by their subject, not only by date.
“Atlas review — why the handover moved” tells a reader more than “September meeting.” Preserve the meeting date beside the descriptive link.
Add a short list of stable project names and abbreviations if the team uses several names for the same work. Use those names consistently in titles and summaries.
Search capabilities depend on the platform. Google Drive, for example, offers filters for file type, people, and modification date. Check the filters your own system supports before designing a large tagging scheme around it.
Example: find the reason without knowing the meeting date
This project example is fictional. The Atlas team postpones a handover until two missing diagrams are ready. A month later, a colleague asks why it moved.
A useful record gives them:
- An index entry named “Atlas handover — waiting for diagrams.”
- A linked decision explaining the condition and whether it has been resolved.
- A source passage showing what the team agreed.
- A link to the separately tracked diagram task.
The reader can begin with “Atlas” and “diagrams” rather than remembering a date. Test whether those words actually find the record in your system; naming alone does not guarantee a search result.
Keep the collection usable as decisions change
After a meeting, check the source files open, review the summary, and add its index link. Name someone responsible for that small cleanup. There is no universal time allowance; the meeting length and sensitivity determine the work.
During a periodic review, check for broken links, duplicate records, missing owners, and decisions that have been replaced. Mark a replaced decision as superseded and link to the current one. Do not rewrite the old rationale to match what the team knows now.
Use the team's existing access and retention rules. Not every recording belongs in a permanent shared archive, and a link does not grant permission to the underlying file.
Test it with a real question
Ask a colleague to find an answer from a recent meeting without telling them where it is. Note the words they search and where they get stuck.
If the record is hard to locate, improve its title or index entry. If it is easy to find but hard to trust, check the summary and its source links. The summary-review guide covers that second problem.
Start with one meeting series. Expand only after someone other than its usual note-taker can find a current answer and check where it came from.
Edited by Recolx Editorial. Updated September 17, 2026.
