Strategy to execution

When should a project scope change trigger a request?

A project scope change check compares the request with approved work, budget, and criteria, then records whether to revise the plan or hold the boundary.

7 min readStrategy to execution
On this page5

A project lead moving task cards across a planning boardA project lead moving task cards across a planning board

A project scope change should trigger a change request when it changes approved work, budget, dependencies, or acceptance criteria enough that the existing approval no longer covers the work. Compare the request with the approved baseline, then record whether to revise the plan or keep the boundary.

What you’ll learn

  • How to describe what the project scope change adds or removes
  • How to compare the request with approved work and criteria
  • How to assess budget and dependency impacts
  • How to record a decision to revise or hold the boundary

What changed in the approved work?

Start by describing the difference, not by arguing whether it is small. Name the deliverable that would be added, removed, or altered. Then say what the approved version promised and what the requester wants instead.

A clarification makes an existing promise easier to understand without changing the result, work, or test for acceptance. A scope change alters one of those things. The distinction matters because a clearer description may need no new approval, while a changed result can create work the original approval did not cover.

Record who requested the change and why. Name the work it affects, including any work that must happen first or could be delayed. Note dates that might move, but distinguish a possible shift from one that has been assessed.

Keep the description concrete. Replace a phrase such as improve the report with the requested fields, format, or behavior. That gives the team something to compare with the approved scope and makes disagreement visible. If the request is not yet specific enough to compare, record what is missing and ask for it before deciding.

How does the request compare with approval?

Put the approved work beside the proposed change. Do not rewrite the baseline to match the request. The original approval is the reference point; the comparison should show what stays covered and what would need a new decision.

Compare the deliverables, owners, dependencies, budget, and acceptance criteria. Mark each item as covered, changed, or not yet clear. For every item marked changed, state the difference. For an unclear item, name the evidence or answer needed to settle it.

Comparison itemApproved baselineProposed changeDecision evidence
DeliverableWhat was approvedWhat would be added, removed, or alteredScope description and review
OwnerWho owns the approved workAny owner change requestedConfirmed owner and capacity
DependencyWork or input the plan relies onAny new, removed, or shifted dependencyDependency owner and timing
BudgetApproved amount or limitExpected cost change, if assessedCost estimate or assessment
Acceptance criteriaHow the approved result is acceptedAny new or altered conditionAgreed test for acceptance

Tip: Keep the original approval visible beside the request so the comparison does not quietly replace the baseline.

A comparison is useful only if the evidence can be reviewed later. A mission can make approved work, owners, budgets, and acceptance criteria explicit; see how missions work. The business plan to mission graph explains how a plan can be expressed as connected work rather than left as a static document.

Do not treat every difference as an automatic rejection. The comparison identifies what the current approval covers and what needs a decision. The person with authority can then decide whether the change is worth its cost and consequences.

Two colleagues reviewing a long timeline drawn across a whiteboardTwo colleagues reviewing a long timeline drawn across a whiteboard

When do budget or criteria require a new decision?

A request needs a new decision when its impact moves beyond what the current approval covers. Added work may require more budget, change the order of work, or draw on an owner who is committed elsewhere. A revised acceptance condition may also change what counts as a complete result, even if the deliverable sounds similar.

Separate an impact to assess from one that has been confirmed. If no one has estimated the cost, the budget impact is unknown, not zero. If a dependency might shift, record that as a risk to check rather than claiming the schedule has already moved. Ask the relevant owner to assess the effect before the decision-maker weighs the request.

Then test the requested result against the existing acceptance criteria. If the current criteria already cover it, say how. If the request adds a new condition, describe the condition and how it could be checked. If no one can yet say what passing means, the request is not ready for approval.

Important: Do not treat an unpriced request as if it fits the approved budget; get the impact assessed before deciding.

Where Brainis is used, your own acceptance criteria become Verify checks, authored once, composed into libraries, and enforced per domain. The Verify page describes that approach. A check can make a stated criterion reviewable; it does not replace the decision about whether the criterion or scope should change.

What should the change decision record?

Record the request, the comparison with approved work, and the decision. State whether the plan changes or the existing boundary holds. Include the reason, the decision-maker, and any impact that remains uncertain. This leaves a clear basis for the next review instead of relying on meeting memory.

If the request is approved, update the work record to match the new agreement. That may mean changing the owner, budget, dependencies, or acceptance criteria. Keep the earlier approval visible so people can see what changed and why. If the request is declined or deferred, record what remains in scope and what would need to change for the question to come back.

For consequential actions in Brainis, an authority contract governs the action and makes it auditable. Authority can be scoped by action, domain, value, risk, reversibility, time, and owner. The memory page is relevant when you need the decision and its reason linked to the work record. Approved strategies in Brainis compile into dependency-aware missions with owners, budgets, and acceptance criteria.

Example: A fictional design studio has approved a customer portal with a searchable list of invoices. A stakeholder asks to add invoice downloads. The project lead records the new deliverable, checks the cost and the dependency on document storage, and asks how the downloaded file must be tested. The decision is to defer approval until those impacts and criteria are clear; the searchable list remains the approved scope.

A deliverable in Brainis arrives as a reviewable diff, with old versus new, inline threads, and Verify findings on exact lines, before it counts as done. That makes changes easier to inspect, but the project still needs a clear decision about whether the changed work is approved.

A team standing around a table covered with sticky notesA team standing around a table covered with sticky notes

What should you do with the next scope request?

Choose one active project and find its approved scope. If the baseline is missing or hard to locate, make that the first problem to solve. Without a stable reference, the team cannot tell whether a request clarifies the existing promise or changes it.

Write the request as a specific difference: what will be added, removed, or altered, and why. Compare it with the approved deliverables and acceptance criteria. Ask the owners to assess any budget or dependency impact that is not yet known. Then record who decides, whether the boundary changes, and what must be updated if the request is approved.

For the next request, keep the record close to the work it affects. When an owner starts the change, make sure the updated work and its test for completion match the decision. A guide to defining done for AI work can help you make acceptance criteria concrete.

The aim is not to make every adjustment a formal event. It is to notice when the approved promise no longer covers the work, and to make that difference explicit before people act on it. A clear comparison gives the decision-maker enough to revise the plan or hold the boundary without losing track of what was agreed.

Strategy to executionDecide

Brainis Team

Notes on running a company with Brainis, from the people building it and running on it.

Tell me about your company.

Start with an idea or the business you run. I’ll find your next move and get to work.

Free plan, no time limit · no card needed