ScopeGuard
Scope creep becomes a decision, not a surprise.
ScopeGuard locks a versioned baseline of your sprint or release scope, then watches every change against it: added items, inflated estimates, silent descopes. Drift is scored, classified, and turned into a change request when it needs a conversation.
Baselines
A baseline is a snapshot of the agreed scope, versioned v1, v2, and so on. Create one manually when scope is agreed, then lock it. A locked baseline becomes the contract that drift is measured against. Unlocked baselines diff live instead.
Automatic baselines
ScopeGuard can create baselines for you when a Jira sprint starts or a GitHub milestone is created, so the contract exists from day one without anyone remembering to snapshot it.
Nightly snapshots and drift
Locked baselines are compared against reality every night. The diff is field-level: items added, items removed, and changed items including estimate deltas, each change weighted by how much delivery risk it carries.
Health score and trend
All drift rolls up into a 0–100 scope-health score with a trend over the recent snapshots. A slowly sinking score is the early warning that quiet additions are eating the deadline.
Change classification
AI classifies each detected change (new requirement, scope clarification, estimate correction) so you can see at a glance what kind of creep you are dealing with.
Change requests
When drift needs sign-off, ScopeGuard drafts the change request for you, including delivery-velocity context from your real throughput where available. It can be generated in multiple languages, and regenerated when it goes stale. Generation counts toward your monthly AI actions.
Decisions
Record the outcome (approved, rejected, deferred) against the baseline, building an audit trail of every scope conversation.
Impact in weeks, not just points
Where FlowLens velocity is available, ScopeGuard translates the drift it finds into a projected schedule impact in weeks: the concrete 'this pushes the date out by about this many weeks' that makes a scope conversation land.
Turning a change request into a decision
A generated change request can be emailed straight to stakeholders or downloaded as a branded PDF, and you can name the approvers whose sign-off it needs. Their names are added deterministically, never invented by the AI. Change requests can be generated in any of twelve languages and are marked stale automatically when the underlying scope moves on.