Report
A plain-language summary of what changed in a Project across a chosen time range. Generated on demand and exportable as PDF — designed to forward to stakeholders without editing.
A Report is a Specsight-generated document covering a specific time window — the last sprint, the past month, since a customer's last review. It pulls together every release that landed in that window and summarises the changes in plain language: new features introduced, existing scenarios modified (with before-and-after), scenarios removed.
Reports exist because the changelog answers a different question. The changelog is per-Feature and continuous — useful for tracing the history of one specific behaviour. A Report is per-period and aggregated — useful when a stakeholder asks "what changed last quarter?" and the right answer is a tidy two-page summary, not a sprawling per-Feature audit trail.
The output is non-technical by design. PMs forward Reports as release notes; account managers attach them to client updates; customer success teams use them to brief themselves before a quarterly review. The cadence and audience are yours to set; Specsight just makes the assembly free.
Related terms
- SPEC
Changelog
A chronological record of what changed in a product, feature, or scenario over time. In Specsight, every Feature carries its own.
- OPERATION
Release Sync
The release-triggered update that keeps a Specsight spec in sync with the codebase. Fires automatically every time code lands on the tracked branch.
- SPEC
Scenario
A single plain-language description of how a product behaves in a specific situation. The atomic unit of a living product specification.