Flexible tracking
Define the fields a response actually needs (asset, exposure, owner, decision, whatever fits) and adapt them as understanding changes. No runtime database migration to add a column.
Product
A workspace built around the Campaign.
KnownScope has one canonical work unit. A Campaign brings the response team, tracked items, adaptable fields, imports, notes, decisions, permissions, history, and status into a single governed workspace, so a response has a home instead of a scattered trail.
The work unit
What a Campaign holds
Most response work doesn't fit one-ticket-per-asset or a scanner's fixed schema. A Campaign is deliberately shaped for the messy middle: a bounded investigation you can define, populate, work, and close out with the evidence intact.
- The responders, with clear roles
- Tracked items and the fields that describe them
- Imported data, with mapping and provenance
- Working notes and recorded decisions
- Permissions, history, and current status
| Item | Owner | Status | Impact | Source |
|---|---|---|---|---|
| edge-gw-01.corp | A. Reyes | confirmed | exposed | asset-import |
| edge-gw-02.corp | A. Reyes | patched | internal | asset-import |
| vpn-eu-1.corp | J. Okafor | reviewing | exposed | csv |
| vpn-us-3.corp | unassigned | triage | unknown | clipboard |
| partner-portal | M. Singh | not-affected | n/a | manual |
Private-preview access is to the live board. The panel above is a drawing of its structure.
The response lifecycle
Shape, Load, Coordinate, Prove.
A simple arc that fits how urgent response actually unfolds, from an empty workspace to a defensible record.
- 01
Shape
Open a Campaign and define the fields that matter for this response. No database migration, no waiting on a schema change.
- 02
Load
Bring items in from CSV, clipboard, or a spreadsheet with mapping, validation, a collision policy, and recorded provenance.
- 03
Coordinate
Filter, sort, assign, and bulk-update as the picture changes. Owners, Workers, and Viewers each see the right surface.
- 04
Prove
Every field and decision carries who and when. Export the state and keep the history, so the response stays defensible.
Capabilities
Designed for speed you can defend.
Capabilities marked Planned describe product direction for private preview and beyond, not features shipped today.
Governed imports
Load items from CSV, clipboard, or a spreadsheet with column mapping, validation, a collision policy for existing rows, and provenance recorded so you know where every item came from.
Accountable updates
Filter, sort, and bulk-update at spreadsheet pace. Each change is attributed at the field level with who and when, so a fast edit never costs you the record of what happened.
Role-based collaboration
Owner, Worker, and Viewer roles let mixed technical and non-technical responders share one workspace. The Campaign lives in one place on the server, so everyone is working the same state and nobody spends Friday reconciling two spreadsheets that drifted apart.
Auditability
A durable, non-destructive history of how a Campaign changed. Export the event history with a timestamp and an actor on every change, so you can reconstruct how scope moved from unknown to known and hand a reviewer a record that holds up after the fact.
API-first design
The direction is parity between the first-party interface and the API, so scripts and integrations operate on the same Campaign model your team does, not a reduced or divergent one.
Private preview
See it against your response work.
KnownScope is in private preview. Tell us about the response work you are trying to make legible, and we will follow up about early access.