Core concepts
A quick glossary of the objects and ideas you'll meet throughout Scopingly.
Organization
The top-level tenant. Every user, team, document, PRD, and plan belongs to exactly one organization, and data is strictly scoped to it — no organization can see another's content. The person who signs up is the org owner.
User & roles
People in an organization hold roles that decide what they can do. Scopingly distinguishes organization roles (owner, admin, member) from platform roles (app admin) and per-resource permissions (owner / editor / viewer on a specific document or PRD). See roles & permissions.
Team
An optional grouping of users within an organization, with its own team owner(s). Teams back capacity planning and PRD/document ownership. See teams.
PRD (requirement)
A product requirements document — the source of truth for a piece of work. PRDs are collaborative, versioned, and approvable, and can be authored in Scopingly or imported (from .docx or Notion). See PRDs.
Gap
A weakness in a PRD that makes the eventual estimate riskier — a missing success metric, no out-of-scope boundary, an unspecified non-functional, a dangling integration reference. Detection is a byproduct, never a gate. See gap detection.
Scope (scope document)
A structured breakdown of the work implied by a PRD: deliverables, effort, and assumptions, in the scope.v1 format. A scope is generated from a PRD and carries provenance back to the PRD version it came from. See scope generation.
Version
Both PRDs and scopes are versioned. An approved artifact is immutable — you don't edit it, you supersede it with a new version. This gives every estimate a real, unchanging baseline. See scope versioning and the PRD approval lifecycle.
Approval & sign-off
Reviewers sign off on a version (a verdict: signed-off or changes-requested); the owner approves it. These are deliberately different actions — a reviewer never "approves," and only the owner (or an org admin) transitions status.
Provenance & drift
When a scope is generated, Scopingly records which PRD version produced it. If that PRD version is later superseded by an approved change, every scope derived from it is flagged as drifted — a signal to regenerate. See drift.
Actuals & calibration
An actual is the real effort a delivered piece of work took. Fed back in, actuals let the calibration engine correct Scopingly's estimate bias for your team. An opt-in, anonymized cross-org prior improves cold-start estimates for new teams. See calibration.
Schedule projection & compression
A projection turns a scope into a forecast — when the work finishes given your team's capacity and calendar. The compression meter measures how a target date squeezes that forecast, and which deliverables would have to give. See schedule & compression.
Epics & user stories
A delivery breakdown generated from a PRD — epics and their user stories, which can be pushed to JIRA. See epics & user stories.
Plan & tier
Your organization's plan (Free, Pro, Business, Enterprise) sets quantitative limits (seats, documents, AI generations) and unlocks feature entitlements (SSO, custom domains, RBAC, and more). See pricing.