Scope Change Brief
Turn a requested scope change into a decision-ready brief.
Sample result
How it works
What Scope Change Brief does
Restates the request as a testable delta against the baseline, separates the need from the proposed solution, estimates effort with ranges, converts hours to cost and schedule through the critical path, lists knock-on effects on dependencies, risks, quality, and other commitments, offers at least three alternatives (accept, trade, defer, reduce), recommends one, and drafts the approval language with named approver, price, date, and what is unchanged.
Use it when
Someone asks to evaluate a change request, add a feature mid-project, price a scope addition, show the impact of a client or stakeholder ask, or write approval wording for a change order.
Use something else for
Scoring uncertain events, mapping handoffs, reforecasting spend after approval, or defining deliverables for a new engagement.
Inputs and results
What goes in, what comes back
- You give
A short brief describing what you need
Add a specialist method to the work.
- You get
Scope change brief, impact estimate, options table and approval language
The method guides the work with your files and context.
- You check
The sources and open questions
Review the output against your brief.
Questions and answers
Questions about Scope Change Brief
Updated Oct 20, 2026.
What does Scope Change Brief do?
Turn a requested scope change into a decision-ready brief. Restates the request as a testable delta against the baseline, separates the need from the proposed solution, estimates effort with ranges, converts hours to cost and schedule through the critical path, lists knock-on effects on dependencies, risks, quality, and other commitments, offers at least three alternatives (accept, trade, defer, reduce), recommends one, and drafts the approval language with named approver, price, date, and what is unchanged. Use when someone asks to evaluate a change request, add a feature mid-project, price a scope addition, show the impact of a client or stakeholder ask, or write approval wording for a change order. Do not use for scoring uncertain events (use risk-register), mapping handoffs (use dependency-map), reforecasting spend after approval (use budget-forecast), or defining deliverables for a new engagement (use match-engagement-deliverables).
Who is Scope Change Brief for?
It is designed for project managers, account leads, delivery leads, agency operators and sponsors.
What do I need to use it?
Nothing extra is needed. Sign in to Relay to run it with your own files and context.
What does Scope Change Brief produce?
Scope change brief, impact estimate, options table and approval language. Results come back with their sources and any open questions for you to check before anything is used.
How much does Scope Change Brief cost?
It is free to use. Paid model usage, if any, is shown before a run.
Can an AI agent use it?
Yes. Agents can read its public definition through the Relay API and run it with a person’s authorization. See the For Agents page for how to connect.
Details
Trust, access and technical details
Trust and access
- Visibility
- Public: anyone can view
- Status
- Published and maintained
- Pricing
- Free
- cmvgt9wsf00a1…
- Oct 20, 2026
- 0 signals
- Commit pinned
Security review is a static package assessment, not a guarantee of safety or a behavioral qualification.
Use it from code or an agent
Read the public definition, then check cost and inputs with a preflight before a run.
Open definitionPOST /api/v1/runs/preflight
How agents connect to Relay →Tags and source
- Repo
- rose-digital/relay
- License
- MIT
Connections
Where Scope Change Brief fits
Have a task this would help with?
Describe it. Relay plans the work, picks the right playbook and shows the cost before anything runs.