Recording client approval and adding a change to scope

Record how a client approved or rejected a sent change request, use owner approval on Team, and add the approved change to the project's scope as an amendment.

Once a change request is sent, you record what the client said. An approval becomes part of the project’s scope only when you add it as an amendment. Until then, future requests are still checked against the scope without it.

Owners and delivery leads record approvals, rejections and amendments. Every plan includes this. On Team, owners can also require their own approval before a change request is sent.

Owner approval before sending (Team)

On Team, an owner can require an owner’s approval before any change request is marked sent. This is internal approval. It is never the client’s approval and never records an approved value.

Turn it on

  1. Open Settings and choose Approvals and review times. Only owners can change it.
  2. Under Approval before sending, switch on Require an owner’s approval before a change request is marked sent.
  3. Under Which change requests need approval, choose Every change request or Only at or above these amounts.

With Only at or above these amounts:

  • Select Add a currency and enter an amount for each currency. A change request at or above its currency’s amount needs approval.
  • Optionally fill in Or when the schedule impact is at least, in working days.
  • Select Save rules.

A change request always needs approval when its currency has no threshold or it has no amount. With a schedule rule, it also needs approval when its schedule is to be agreed or not given in working days. Changing the rules does not affect revisions already approved.

Approve a change request

When a finalised change request needs approval, its Owner approval panel shows Waiting for an owner’s approval and Mark as sent is disabled.

  1. An owner opens the change request and selects Approve.
  2. They can add a Note, which is kept in the history.
  3. They select Approve.

The panel then shows who approved it and when, and Mark as sent becomes available. If the change request is reopened and finalised again, the new revision needs approving again. Earlier approvals stay listed under Earlier approvals.

Record the client’s approval

If the client approved in the client approval portal, the approval is recorded for you. Skip to adding it to scope.

Otherwise, once the client has approved by email, in a meeting note or in a signed document:

  1. Open the sent change request and select Record client approval.
  2. Choose how you hold the evidence:
    • Paste text: paste the client’s message into Approval text, up to 20,000 characters.
    • Upload PDF: select Choose PDF and pick a PDF of up to 10 MB. It is kept as evidence and not read by Agreeably.
  3. Enter Approved on, the Client contact and, optionally, Their role.
  4. Fill in Where it came from, for example “Email from Dana, 3 Nov”. It is required for pasted text.
  5. Select Record approval.

The change request moves to Client approved (recorded by the team). The Approval evidence section lists each approval with its date, contact, revision, who recorded it and when.

This is approval recorded by your team, or through the portal. It is not a signature or verified identity.

Record a rejection

  1. Select Record rejection on the sent change request.
  2. Enter a Reason. It is kept in the history.
  3. Select Record rejection.

A rejected change request stays visible and never changes the scope.

Add the approved change to scope

  1. Open the client-approved change request and select Add to scope.
  2. Choose Effective from, or leave it empty for today. A future day is allowed.
  3. Select Add to scope.

The change becomes an amendment in the project’s effective scope, and the status shows Added to scope. Only analyses queued from then on use it. Earlier analyses, the agreement and the confirmed baseline are not changed. See Amendments for how amendments sit alongside the confirmed scope.

Fix a mistake

An approval or rejection was recorded in error. Select Correct, give a reason and select Correct. The change request goes back to sent, and what was recorded stays in the history.

The change is already in scope. You cannot correct the approval while its amendment is effective. In the Amendment section, select Reverse, give a reason and select Reverse amendment. The change is removed from effective scope for analyses queued from then on. Analyses that used it are flagged for review so they can be re-analysed. Nothing earlier is deleted. You can then correct the approval.

Common questions

Does a client approval change the scope on its own? No. Neither a recorded approval nor a portal approval changes the scope until someone selects Add to scope.

Does an owner’s approval count as the client’s? No. Owner approval only allows a change request to be marked sent.

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