For Writers
Every source, every claim, in one model.
Scopic gives every entity in your research its own record — and every connection between them a citation you can open.
Join waitlistThe situation
You are working on a long piece. People, organisations, events, and claims accumulate over months. You keep a spreadsheet of sources and a separate mind map of narrative threads. The mind map has no connection to the spreadsheet. A person appears in both, but there is no link between the two instances.
When you discover that two organisations are connected through a third, you add it to the mind map. The source you used is in the spreadsheet, in a different row, unrelated to the arrow you drew. Six months in, retracing a claim to its source means scanning both documents by hand.
Every connection carries its source
In Scopic, the link between a politician and a company is a connection with a source field, a date, and a notes field. On the map it renders as a typed line. Open it and you see the citation. When you revisit the map six months later, every relationship says what it meant when you drew it.
Screenshot: open connection record with source citation, date, and verification status
Filter to what still needs checking
Every claim in the database has a verification status property. Filter to show only unverified claims and see exactly what is still outstanding. Filter by source type to see which parts of the story rest on a single document. The map shows the structure; the database is the editorial checklist.
Screenshot: database filtered to unverified claims with source and status columns
The structure of the story is visible
Actors, organisations, events — each a record with properties. The 'employs', 'funds', and 'owns' connections between them build a network that shows hidden relationships a timeline or list cannot. When a new source changes one connection, you update it once. The rest of the map does not need to change.
Screenshot: actor network with typed connections and properties visible
What people say
Nine months into an investigation. Every connection I've found is in Scopic with its source. When my editor asks where a claim came from I open the connection and there it is.
1 month ago
I used to keep my research in a spreadsheet and my narrative structure in a mind map. They described the same thing and never talked to each other. Scopic is one thing.
2 months ago
The verification status filter is the most useful thing I've found for deadline pressure. Filter to unverified claims and I have a working list for the final week of reporting.
3 weeks ago
Writing a book about a complex institution. Every actor, every decision, every document is in Scopic. The network map made three hidden relationships visible that I would never have found in a flat list.
6 weeks ago
Map the story your sources are telling.
Join waitlistFor Writers
Every source, every claim, in one model.
The situation
You are working on a long piece — an investigation, a book, a series. People, organisations, events, and claims accumulate over months. You keep a spreadsheet of sources and a separate mind map or whiteboard of narrative threads. The mind map has no connection to the spreadsheet. A person's name appears in both, but there is no link between the two instances.
When you discover that two organisations are connected through a third, you add it to the mind map. The source you used for that connection is in the spreadsheet, in a different row, unrelated to the arrow you drew. Six months into the project, retracing a claim to its source means scanning both documents by hand.
What changes
In Scopic, every entity in your research — person, organisation, event, document, claim — is an element in the database with properties you define: source, date, credibility assessment, verification status. The connection between a politician and a company is a 'linked to' relation with a source, a date, and a notes field. On the map it renders as a typed line. Open it and you see the citation.
You can filter the database to show only unverified claims, or only sources from a given date range, or only connections of a specific type. The map shows you the structure of the story. The database lets you interrogate it. They are the same model.
Maps you'd build
- Source and claim network
Sources (documents, interviews, datasets) and the claims they support, with 'supports', 'contradicts', and 'corroborates' relation types. Each source has a credibility and verification status. Filter by unverified claims to see what still needs checking.
- Actor network
Every person and organisation in the story, with typed relations (employs, funds, owns, is affiliated with) and properties (role, date active, public profile link). Useful for tracing conflicts of interest and hidden connections across a large cast.
- Event timeline with actors
Events as elements with a date property, connected to the actors involved by 'participated in', 'authorised', and 'was affected by' relations. The map shows causal and temporal structure; the database lets you filter by actor or date range to reconstruct sequences.
Map the story your sources are telling.
Join the waitlist to get early access or talk through your use case.
Join waitlist- Source and claim network
Claims connected to sources by type — supports, contradicts, corroborates. Filter to unverified to see what needs checking.
- Actor network
Every person and organisation in the story, connected by typed relationships. Hidden connections become visible.
- Verification tracking
Verification status as a property on every claim. The database is the editorial checklist.