How to Organize a Research Project in WebSnips

What Research Project Organization Requires

A research project — whether it's a market analysis, a policy brief, a thesis chapter, or a competitive landscape report — has specific organizational requirements that differ from a general knowledge library:

• Defined scope: The project has a beginning and an end; not everything belongs in it
• Source tracking: You need to know what you've read, what you haven't, and what you're using
• Progress visibility: You need to see where the project is in its lifecycle — capture, analysis, drafting, review
• Synthesis output: The research needs to become something — a document, a report, a presentation
• Archival or handoff: When the project ends, the research needs to be closed out or shared

WebSnips' Collections, tags, Connections, and Creator Studio each serve specific functions in a research project workflow. This guide shows how to combine them into a system that handles a research project from kickoff through final output.

---

Setting Up a Research Project in WebSnips

Step 1: Create the project's Collections

Every research project needs a primary Collection and, for larger projects, secondary Collections for sub-topics or phases.

Primary Collection: Name it clearly: [Project Name] Research or Research: [Topic]

Examples:

• "Research: EV Battery Market Analysis"
• "Research: Remote Work Policy Review"
• "Research: Competitor Landscape Q4 2026"

Secondary Collections (for larger projects with 25+ sources):

Organize by sub-topic within the project:

For a market analysis:

• "EV Battery: Technology Landscape"
• "EV Battery: Competitor Analysis"
• "EV Battery: Customer Insights"
• "EV Battery: Regulatory Environment"
• "EV Battery: Supply Chain"

For a policy review:

• "Remote Work Policy: Research Evidence"
• "Remote Work Policy: Peer Company Benchmarks"
• "Remote Work Policy: Legal Considerations"

Sources can belong to multiple Collections: an article about a competitor's battery technology strategy belongs in both "Technology Landscape" and "Competitor Analysis."

Step 2: Define the project's tags

Create a tag taxonomy for the project before you start capturing. The three categories most useful for research projects:

Status tags (where is this source in the workflow):

• rp-to-read — captured, not yet read
• rp-reading — currently reading / partially read
• rp-annotated — fully read and annotated
• rp-to-cite — will be cited in the output
• rp-background — informative but not directly cited
• rp-excluded — captured but determined to be out of scope

Source type tags:

• primary-source — original data, first-hand accounts, official documents
• secondary-source — analysis, commentary, synthesis of primary sources
• company-data — reports, filings, announcements from the companies you're researching
• expert-opinion — interviews, quoted experts, commentary from practitioners
• quantitative — sources with data, statistics, market size numbers
• qualitative — case studies, interviews, descriptive accounts

Quality/confidence tags:

• high-confidence — vetted sources, authoritative data
• verify-needed — useful but needs cross-referencing
• single-source — claim appears in only one source; note the single-source risk

Step 3: Create Smart Collections for research status views

Create Smart Collections for each status layer so you always know where things stand:

• tag:rp-to-read AND collection:[Project Name] Research → Reading queue
• tag:rp-annotated AND collection:[Project Name] Research → Processed sources
• tag:rp-to-cite AND collection:[Project Name] Research → Sources being used in output
• tag:rp-annotated NOT tag:rp-to-cite NOT tag:rp-background AND collection:[Project Name] Research → Annotated but not yet allocated

These Smart Collections give you a live dashboard of the project's source state without maintaining a separate spreadsheet.

---

The Source Capture Workflow

What to capture

In a focused research project, resist capturing everything tangentially related. Ask before each capture: "Will this help me answer the project's core questions?" If you're unsure, use the rp-to-read tag and include a brief note about why it might be relevant — this lets you decide later without having lost the source.

Capture protocol

For each source:

1. Open the source in the browser
2. WebSnips extension → save popup
3. Select the primary project Collection (and sub-topic Collection if applicable)
4. Add status tag rp-to-read
5. Add source type tags (quantitative, primary-source, etc.)
6. Add a brief relevance note: "Why I captured this: [one sentence]"
7. Save

The relevance note is important even before you've read the full source — it documents your hypothesis about relevance, which you can evaluate after reading.

---

The Reading and Annotation Workflow

When to annotate

Annotation happens during or immediately after reading each source. Update the status tag from rp-to-read to rp-annotated after completing annotation.

Research annotation protocol

For each source, write:

Research question answered: Which of the project's core questions does this source address? Be specific ("This answers: What is the current price per kWh for solid-state batteries at scale?").

Key finding: The one-sentence answer the source provides.

Supporting evidence: The specific data, quote, or argument. Include page numbers or section headings for precise reference later.

Source credibility assessment: Who published this? What's their methodology? Any potential bias or limitation?

Connections to other sources: Does this source agree with, contradict, or extend another source in the project? List by name.

Draft notes: If you can already see how this finding will appear in the output ("This will go in the Supply Chain section, as evidence for the cost reduction trend"), note it here.

Example annotation for a market research report:

Research question answered: What is the projected market size for solid-state 
batteries through 2030?

Key finding: Global solid-state battery market projected to reach $8.4B by 2030, 
CAGR 38.2% from 2024 baseline of $0.9B.

Supporting evidence: "The global solid-state battery market size was valued at 
USD 0.94 billion in 2024 and is projected to reach USD 8.44 billion by 2030, 
exhibiting a CAGR of 38.2% during the forecast period." (p.4)

Source credibility: MarketsandMarkets report. Methodology: primary interviews 
with industry executives + secondary analysis of company filings. Standard 
market research methodology — projections should be treated as directional, 
not precise.

Connections: Goldman Sachs analysis (separate clip) projects $6.1B by 2030 — 
more conservative. Toyota IR presentations align with the higher estimate.

Draft notes: Use the $0.94B → $8.4B CAGR figure in the Market Opportunity 
section opener. Note the Goldman/MarketsandMarkets divergence as a range.

---

Building the Connections Map

Connections in WebSnips are especially valuable in research projects because research has inherent structure: sources support each other, contradict each other, cite each other, and address the same question from different angles. Making these relationships explicit transforms a pile of sources into a structured body of evidence.

Creating connections between research sources:

After annotating each source, create connections to the sources mentioned in your "Connections" annotation field:

• A contradicting source: label "contradicts on [specific claim]"
• A supporting source: label "supports with different evidence"
• A methodological predecessor: label "provides data used by"
• A response paper: label "responds to"

The graph view for research projects:

Filter the Connections graph to the project Collection. The resulting graph reveals:

• Hub sources: foundational works or authoritative data sets that many other sources cite or respond to — these are your most important citations
• Evidence clusters: groups of sources that all address the same sub-question
• Isolated sources: sources with no connections yet — either because you haven't connected them or because they're genuinely independent (single-source risks)
• Controversy chains: sequences of contradicting sources on a disputed claim

For a research project, the graph view at the mid-point of the project is a useful audit: isolated sources should either be connected to others or flagged as single-source claims.

---

Tracking Research Coverage

A research project needs to know not just what you've read but what the coverage gaps are.

Research coverage audit (mid-project):

1. List the project's core research questions
2. For each question, filter the project Collection with the question's topic
3. Check: Is the question answered by at least 2 sources? Are contradicting claims represented? Are primary and secondary sources both present?

Questions answered by only one source → flag for additional research. Questions with no sources at all → either add to the capture list or explicitly note as out of scope.

Source balance audit:

Review the distribution of source types:

• Are you over-indexed on a single source type? (e.g., mostly analyst reports, no primary sources)
• Are you over-indexed on a single perspective? (e.g., technology optimists, no skeptic voices)

Tags make this audit fast: filter by tag:primary-source to see primary source coverage, tag:expert-opinion to see expert coverage, etc.

---

Synthesizing in Creator Studio

When the research is captured, annotated, and connected, synthesis happens in Creator Studio.

Opening the project for synthesis:

1. Open the primary project Collection (or "This Issue"-equivalent: the rp-to-cite Smart Collection)
2. Click Draft with Creator Studio
3. The Collection's clips load in the research panel

The synthesis workflow:

1. Generate an outline from the project Collection → review and edit to match the output's intended structure

2. For each section of the outline:

   • Filter the research panel to the relevant sub-topic tags or sub-Collection
   • Draft the section with the relevant sources visible
   • Pull specific data and quotations from the research panel
   • Generate citations for sources you're citing directly

3. Complete the draft

4. Export the reference list (filtered to rp-to-cite clips)

The annotation note as draft material:

Your "Draft notes" field from each annotation is the pre-organized material for each section. Before writing a section, filter to the relevant sources and read through their "Draft notes" annotations — these are the sentences and data points you already identified as going into the output. Writing becomes assembly.

---

Closing Out a Research Project

When the output is complete, close the project in WebSnips:

Archive the project Collections:

Rename the project Collection: "COMPLETE: [Original Name] [Date]" — this signals it's closed without deleting the research.

Export a final source list:

Generate the project's citation list (all rp-to-cite clips) as a formatted reference list. Save it alongside the output document as the project's source record.

Tag cleanup:

Review clips tagged rp-background and rp-excluded — some of these may be worth retaining in your general library with different tags. Remove project-specific tags from clips you want to keep as general reference.

Handoff (if sharing):

If the project is being handed off to a colleague or client, WebSnips' Collection sharing features let you share the project Collection with all annotations intact. The recipient sees your full research and annotation work, not just the output document.

---

Worked Example: A Policy Analyst's Research Project

Setup: A policy analyst at a think tank is producing a 25-page brief on the evidence base for four-day work week policies. She needs to review academic research, survey data, employer case studies, and counterarguments. Output is due in 6 weeks.

Week 1-2 (Capture): She creates 5 Collections:

• "4DWW Research" (primary)
• "4DWW: Academic Evidence"
• "4DWW: Employer Case Studies"
• "4DWW: Survey Data"
• "4DWW: Counterarguments"

She captures 45 sources over two weeks — academic papers from PubMed and Google Scholar, employer case study write-ups, survey reports, and skeptical commentary from management researchers. Each capture gets her relevance note and status rp-to-read.

Week 3 (Annotation): She annotates 7-8 sources per day using the research annotation protocol. By end of week: 45 sources annotated. She updates all tags to rp-annotated.

Week 4 (Connections + Coverage Audit): She creates 55 connections between sources — academic studies that inform the employer case studies, survey data that contradicts the case study evidence, the meta-analysis that synthesizes 11 primary studies. The coverage audit reveals: the counterarguments Collection only has 5 sources vs. 40 supporting sources — she adds 8 more counterargument sources before drafting.

Week 5 (Synthesis in Creator Studio): Outline generated from the primary Collection. She drafts the brief section by section, using the rp-to-cite Smart Collection as her research panel. Her annotations' "Draft notes" fields provide the core claims for each section.

Week 6 (Review and Export): Review and edit the draft. Export citations (APA format) from the rp-to-cite clips. Archive the project Collection.

---

Key Takeaways

1. Collections define scope (primary) and structure (secondary sub-topic): the primary Collection is the project container; sub-topic Collections enable filtering by research area during synthesis.
2. The five-part annotation protocol (research question / key finding / evidence / credibility / connections / draft notes) converts reading into structured draft material: draft notes especially — writing "this goes in Section 3 as evidence for X" at annotation time makes the synthesis step assembly rather than starting over.
3. Smart Collections on status tags provide a live project dashboard: no separate spreadsheet needed to track which sources are read, annotated, or confirmed for citation.
4. The Connections graph at mid-project is a coverage and quality audit: isolated sources are single-source risks; imbalanced clusters reveal perspective gaps.
5. Closing a project cleanly (archive Collection, export references, tag cleanup) preserves the research for future use: a well-closed project becomes a reusable knowledge asset, not a pile of clips that loses its organization over time.

---

Conclusion

A research project in WebSnips is organized around the same structure as the project itself: a defined scope (project Collection), a source lifecycle (status tags + Smart Collections), an evidence network (Connections), and a synthesis environment (Creator Studio). The system is designed so that the organizational work done during capture and annotation — tagging, annotating with protocol, creating connections — directly accelerates the synthesis and drafting stages. The research project workflow described here converts what is often a chaotic, multi-tool, spreadsheet-dependent process into one integrated environment from first capture through final output.

Set up your next research project in WebSnips — create the project Collection, define your tag taxonomy, and start capturing with the annotation protocol that will make your synthesis stage straightforward.