Amendments to the agreed scope

How a client-approved change request becomes an amendment to the effective scope, where amendments are listed, how analyses use them, and how to reverse one.

An amendment is a change the client approved that your team has added to the project’s scope. Once it is effective, new requests are checked against the confirmed baseline and the amendment together.

The signed agreement and the confirmed baseline are never changed by an amendment. It sits beside them, with its own history.

How a change becomes an amendment

An amendment always starts as a change request:

  1. Draft a change request, finalise it and mark it as sent. See Drafting and sending a change request.
  2. Record the client’s approval. Its status becomes Client approved (recorded by the team). See Recording approval.
  3. Add it to scope, as below.

A change request that is still a draft, sent, rejected or superseded never changes the scope. Approval on its own does not change it either. Your team decides when the change takes effect.

Add an approved change to scope

Owners and Delivery leads can add a change to scope, on an active project.

  1. Open the project and choose Change requests.
  2. Open the client-approved change request and select Add to scope.
  3. Enter the Effective from date. It can be in the future.
  4. Select Add to scope.

The change request’s page then lists the Amendment. From now on, analyses use it. Analyses that ran before it are not changed.

Where amendments are listed

Open the project and choose Scope. Below the scope, Amendments lists every change your team confirmed into scope. Each shows:

  • the change request number and title, for example “CR-3 · Extra reporting dashboard”
  • the revision of the change request that was approved
  • the date it is effective from, and who confirmed it
  • its status: Effective or Reversed

The project header shows the count beside the baseline, for example “Baseline v1 + 2 amendments”.

How analyses use amendments

An analysis queued after an amendment is confirmed checks the request against the baseline and every effective amendment. When it relies on an amendment, the evidence shows the amendment’s Added work, Exclusions and Assumptions from the change request, with the date the client approved it.

The evidence is labelled “Approved by the client and confirmed into scope by your team” with its effective date, and Not agreement wording. This keeps amendment text apart from the signed agreement.

Reverse an amendment

If an amendment was added in error, reverse it rather than deleting it. Owners and Delivery leads can do this on an active project.

  1. Open the project and choose Scope, or open the change request.
  2. Under Amendments, select Reverse beside the amendment.
  3. Enter the reason and select Reverse amendment.

The amendment is marked Reversed and drops out of the effective scope for analyses queued from then on. Analyses that used it are flagged for review, and show Flagged: re-analyse in the Inbox, so you can analyse them again. Nothing earlier is deleted.

Correct a recorded approval

While a change is in the effective scope, its recorded approval cannot be corrected. Reverse the amendment first. Then use Correct on the change request to send it back to sent. The earlier record stays in its history.

Amendments or a new agreement version?

Use an amendment for a change the client approved through a change request. Use a new agreement version when the signed agreement itself is replaced, for example a re-signed statement of work. A new version drafts a new scope for you to confirm. See Adding an agreement.

Common questions

Does a client approval in the portal add the change to scope? No. It is recorded as approval evidence. Someone on your team still selects Add to scope.

Can an amendment be edited? No. Reverse it. If the approval itself was recorded in error, use Correct on the change request afterwards.

Do earlier requests change when I add an amendment? No. Requests already checked keep the evidence they were checked with.

Checked against the app on . Something out of date or unclear? Email hello@agreeably.io.