How to Use Capacities: Set Up Your First Knowledge System
Summary
- Set up Capacities by defining a small set of “objects” (like People, Projects, and Topics) and capturing notes as linked items instead of loose pages.
- Start with one real workflow (meetings, reading notes, or project tracking) so your system stays usable as it grows.
- Use consistent capture templates, lightweight linking, and a weekly review to keep your knowledge system findable.
- Expect some version and platform differences; verify exact menus and names inside your Capacities app as you follow the steps.
- If you also reuse lots of text across tools, a clipboard workbench like CopyCharm can help you save, search, and reuse snippets alongside your Capacities system.
This guide walks you through setting up your first knowledge system in Capacities: what to create first, how to capture notes as objects, and how to keep everything easy to retrieve later.
What Capacities is trying to help you do (in plain terms)
Capacities is designed for building a personal knowledge system where information is stored as structured items (often called “objects”) that you can link together. Instead of writing everything as standalone documents, you capture notes as things like a person, a meeting, a book, a concept, or a project, then connect them.
If you are searching “how to use Capacities” or “Capacities app tutorial,” the fastest path is: pick a small set of objects, create a few templates, and start capturing one repeatable workflow. You can expand later without rebuilding from scratch.
Before you start: choose one “first system” (don’t try to model your whole life)
A first knowledge system works best when it has a clear boundary. Pick one of these as your starting scope:
- Meetings system: people + meetings + decisions + follow-ups
- Reading & learning system: sources (books/articles) + notes + concepts
- Project system: projects + tasks/next actions + reference notes
Choose the one you will use at least weekly. Your goal is not completeness; it is repeatable capture and retrieval.
Step 1: Create a minimal object model (3–6 objects max)
In Capacities, you will usually define a few object types that match how you think and work. Keep it small at first. Here are three starter models you can copy.
Option A: Meetings-first model (great for work)
- Person (coworkers, clients, stakeholders)
- Meeting (1:1s, project syncs, interviews)
- Project (initiatives, deliverables)
- Decision (what was decided, why, when)
- Action (next steps you need to do)
Option B: Learning-first model (great for students and self-study)
- Source (book, article, video, paper)
- Note (your takeaways, summaries)
- Concept (ideas you want to reuse)
- Person (authors, thinkers)
Option C: Creator/freelancer model (great for content + clients)
- Client
- Project
- Deliverable (draft, landing page, email sequence)
- Brief (requirements, constraints, voice)
- Asset (snippets, claims, quotes you can reuse)
Practical constraint: If you create too many object types early, you will spend time deciding where something “belongs” instead of capturing it. Start small and add only when you feel repeated friction.
Step 2: Define the properties you will actually use
Objects become useful when they have a few consistent properties you can filter or scan later. Keep properties lightweight and tied to retrieval.
Suggested properties by object
- Meeting: date, attendees (linked People), related project, agenda, notes, decisions, actions
- Project: status, owner, goal, key links, milestones (if you truly use them)
- Source: author, link/citation info, status (to read/reading/done), key concepts (linked)
- Concept: definition (your words), examples, related concepts, sources
Limitation to watch for: property names, available field types, and where you can add them can vary by app version. If you cannot find an exact option described in a tutorial, look for the closest equivalent (for example, a “relation/link” field vs a “reference” field).
Step 3: Create two capture templates (so you don’t start from a blank page)
Templates reduce friction and make your notes consistent. Start with just two templates tied to your chosen system.
Template 1: Meeting note
- Context: purpose of the meeting in one sentence
- Agenda: 3–5 bullets
- Notes: freeform
- Decisions: bullets with “why”
- Actions: each action starts with a verb and an owner
Template 2: Source note (article/book/video)
- Summary: 3–6 bullets in your own words
- Key concepts: link to Concept objects you create or reuse
- Quotes/snippets: only the lines you expect to reuse
- My take: what you agree/disagree with, and what you will do next
Tip: If you are not sure what to template, look at your last five notes. Template the repeated structure you already use.
Step 4: Capture your first week of information (the “10-object sprint”)
To get momentum, aim to create a small set of real objects in your first week. For example:
- 3 People you interact with regularly
- 2 Projects you are actively working on
- 3 Meetings (or 3 Sources if you are learning-focused)
- 2 Concepts you keep encountering
As you create each object, add at least one link to another object. The links are what turn a pile of notes into a system you can navigate.
Example: turning a meeting into connected knowledge
- Create a Meeting object for “Client kickoff”
- Link attendees to Person objects
- Link the meeting to a Project object
- Create one Decision object for a key choice (scope, timeline, positioning)
- Create 2–5 Action items you can execute
Later, when you open the Project, you can see the meetings, decisions, and actions connected to it (exact navigation depends on your Capacities setup and version).
Step 5: Retrieval habits that make Capacities feel “smart”
A knowledge system succeeds when you can reliably find what you need under time pressure. Build these habits early:
- Link as you write: when you mention a person, project, or concept, link it instead of leaving it as plain text.
- Write “future-you” summaries: add a short summary at the top of meeting and source notes so you can scan later.
- Use consistent naming: e.g., “Meeting - [Client] - [Topic]” or “Source - [Author] - [Title].”
- Weekly review (10 minutes): close open loops by turning loose notes into linked objects and extracting actions/decisions.
Common setup mistakes (and how to avoid them)
- Over-modeling: creating many object types and properties before you have real notes. Start with fewer objects and add only when you see repeated patterns.
- Capturing without linking: unlinked notes become hard to browse. Add at least one meaningful link per new item.
- Mixing tasks with knowledge without a rule: decide what “done” looks like. For example, actions live in Action objects, while meeting notes stay in Meeting objects.
- No review loop: even a great structure gets messy without a short weekly cleanup.
How CopyCharm can complement Capacities (when your system includes lots of reusable text)
If your knowledge system involves frequent copy/paste (meeting agendas, recurring checklists, client questions, research snippets, or AI prompts), you may want a separate place to store and retrieve reusable text quickly while still keeping your long-term knowledge in Capacities.
CopyCharm is a Windows desktop app and local-first context workbench for copied text. It saves copied text locally, lets you search past clips, favorite important clips, and separately save reusable prompts.
A concrete “save, find, reuse” workflow alongside Capacities
- Save: When you copy something you will reuse (a standard discovery questionnaire, a project kickoff checklist, a polished paragraph, or a prompt), save it in CopyCharm as either a Favorite Clip (important copied text) or a Saved Prompt (reusable prompt text).
- Find: Later, search your past clips in CopyCharm when you are drafting a new Capacities note, preparing for a meeting, or writing a project brief.
- Reuse: Copy the selected text from CopyCharm and paste it into Capacities (or into email/docs). This can help reduce repeated rewriting while keeping Capacities focused on your connected knowledge objects.
If you use ChatGPT: when a connector helps vs manual reuse
CopyCharm also has an authenticated ChatGPT connector backed by optional AI Access sync and a read-only MCP service. After you sign in with an eligible active CopyCharm purchase, authorize the CopyCharm Desktop connection, enable and complete AI Access sync, and authorize the ChatGPT connector, ChatGPT can search or list recent supported synced clips and saved prompts and retrieve a selected synced item’s full text. ChatGPT cannot search or retrieve unsynced local CopyCharm data.
For Claude, Gemini, Cursor, email, documents, and other applications, the workflow is manual: you search or retrieve content in CopyCharm and copy/paste it into the destination app.
Putting it all together: a simple first-week plan
- Day 1: Pick your starting scope (meetings, learning, or projects). Create 3–6 object types.
- Day 2: Add only the properties you will use for retrieval (date, status, related project/person).
- Day 3: Create two templates (Meeting + Source, or Meeting + Project, depending on your scope).
- Days 4–7: Do the “10-object sprint.” Link each new object to at least one other object.
- End of week: Do a 10-minute review: extract actions, add missing links, and write short summaries at the top of key notes.
Frequently Asked Questions
FAQ 1: What is the fastest way to start using Capacities without overcomplicating it?
Answer: Pick one use case (meetings, learning, or projects), create a small set of object types (3–6), and capture one week of real notes while linking items as you go. Add new object types only when you repeatedly need them.
Takeaway: Start with one workflow and a small object model, then expand based on real usage.
FAQ 2: What should my first object types be in Capacities?
Answer: Choose objects that match what you reference repeatedly. For many people, a practical starting set is Person, Project, and Meeting (or Source if you are learning-focused), plus one “output” object like Decision, Action, or Concept. Keep the list short so capture stays fast.
Takeaway: Start with the entities you mention constantly, not an idealized taxonomy.
FAQ 3: How do I take meeting notes in Capacities so they are easy to find later?
Answer: Use a consistent meeting template (context, agenda, notes, decisions, actions), link attendees to Person objects, and link the meeting to a Project. Add a short summary at the top so you can scan search results quickly.
Takeaway: Consistent structure plus links (People/Projects) makes meeting notes retrievable.
FAQ 4: How should I organize reading notes in Capacities?
Answer: Create a Source object for each book/article/video, write a short summary in your own words, and extract reusable ideas into Concept objects that link back to the Source. If you save quotes, keep only the ones you expect to reuse and add your interpretation next to them.
Takeaway: Separate “where it came from” (Source) from “what it means” (Concept).
FAQ 5: How many properties should I add to each object?
Answer: Add only the properties you will use to filter, sort, or scan later (date, status, related project/person). If a property does not change what you do next or how you find the item, skip it for now and revisit after a week or two of real notes.
Takeaway: Properties are for retrieval and decisions, not decoration.
FAQ 6: What is a good weekly maintenance routine for a Capacities knowledge system?
Answer: Set aside 10–20 minutes to (1) turn loose notes into linked objects, (2) extract actions and decisions from meetings, (3) add short summaries to key notes, and (4) connect repeated ideas to existing Concepts instead of creating duplicates.
Takeaway: A short weekly review keeps your system navigable without big reorganizations.
FAQ 7: What are common limitations when following a Capacities app tutorial?
Answer: Tutorials can differ from what you see because Capacities may change feature names, layouts, or availability by platform/account. If you cannot find an exact button or menu, look for the underlying concept (object types, properties, templates, links) and adapt the steps to your interface.
Takeaway: Follow the concepts, then map them to your version of the app.
FAQ 8: Can CopyCharm help alongside Capacities for reusable text and prompts?
Answer: If you frequently reuse snippets (checklists, standard questions, polished paragraphs, or prompts), CopyCharm can store copied text locally, let you search past clips, favorite important clips, and separately save reusable prompts. You can then copy/paste into Capacities. If you enable AI Access sync and authorize the connector, ChatGPT can search and retrieve only supported synced data (not unsynced local CopyCharm data).
Takeaway: Use Capacities for connected knowledge objects, and use CopyCharm when fast snippet reuse is a recurring need.