Confirming the scope
How to review the drafted scope beside the agreement, edit and add items, why quotations are checked word for word, and how to confirm the baseline.
The confirmed scope, or baseline, is what every client request is checked against. Agreeably drafts it from the agreement. You check each item, fix what is wrong and confirm it.
Owners and Delivery leads can edit and confirm scope. Viewers can read it.
Why the scope must be confirmed first
Requests are checked against scope your team has confirmed, not against a draft. Until there is a baseline, the project’s Requests and Change requests tabs are locked with “Confirm the scope to start checking requests”.
What the draft contains
Agreeably proposes five kinds of scope item:
- Deliverable
- Exclusion
- Quantity or revision limit
- Dependency or client responsibility
- Change procedure
Each item has a short summary and, where possible, a quotation from the agreement with its page or clause.
Quotations are checked word for word
Every drafted quotation is checked against the stored agreement text before it is shown. If the wording cannot be found exactly, the item is not shown as evidence. It is marked Needs review with the reason, for example “The drafted wording was not found in the agreement.”
Only direct quotations count as contract evidence. Your own reading of an item is kept apart and labelled Your interpretation · not contract wording.
Review the draft
When drafting finishes, the project’s Setup tab shows the draft beside the agreement. Select an item to jump to its quotation in the agreement, where it is highlighted. Use Hide the agreement or Show the agreement to change the layout.
Items are grouped:
- Needs a look: items flagged for review.
- Exact matches: items whose quotation was found word for word.
- Checked: items someone on your team has ticked.
Each item shows a tag: Quoted, Needs review, Edited or Not in the agreement. Items your team added are tagged Added by team.
To work through the draft:
- Read each item against the highlighted wording and tick Checked.
- Select Check all n exact matches to tick every exact match at once, once you have read them.
- Select Edit to correct an item, or Remove to drop it.
- Select Add item for anything the draft missed.
The bar at the bottom counts progress, for example “12 of 15 checked · 1 needs review”.
Edit or add an item
The Edit scope item and Add scope item forms have these fields:
- Kind: one of the five kinds above.
- Summary: a short description in your own words. It is not shown as agreement wording.
- Agreement wording: the exact wording, 20 to 1,500 characters. It is checked against the agreement before it is saved.
- Page: the agreement page the wording is on.
- Our interpretation (not agreement wording): your team’s reading. Required when there is no agreement wording.
An edited item keeps its earlier summary, shown as Was: with the old text struck through.
Confirm the baseline
- Resolve every item marked Needs review, by editing or removing it.
- Select Confirm as baseline.
- Read the message and select Confirm baseline.
Confirmation records who confirmed it, when, and which version. Agreeably then opens the project’s Requests.
Requests that arrived before the scope
Requests forwarded, pasted or sent from the browser extension before there was a confirmed scope wait as Awaiting assessment. When you confirm, Agreeably checks each of them automatically, oldest first, using one analysis each. Before you confirm, the page says how many are waiting and how many analyses they will use. If your analysis allowance runs out, the rest wait On hold and are checked when allowance is available.
Confirming a later version does not check again requests that were already analysed. Their analysis stays tied to the scope they were checked against.
Confirm as baseline stays unavailable, with the reason shown, while drafting is still running, while the draft has no items, while any item needs review, or when a newer agreement version has been added since the draft.
Confirmed scope cannot be edited. To change it, add a new agreement version, which drafts a new scope version. See Adding an agreement. For changes the client approved, use an amendment instead. See Amendments.
Discard a draft
Select Discard draft, then confirm. Its items are dropped. It still counts towards the three drafting attempts for that agreement version.
New scope versions
Once a project has a baseline, its first tab is Scope. It has these views:
- Baseline v1 (or the current number): the confirmed scope beside the agreement.
- Draft v2 vs baseline: when a new draft is open, a list of what was Added, Removed and Changed. Select Review side by side to check it item by item, and Confirm v2 to confirm it.
- History: every scope version with its status (Draft, Baseline, Superseded or Discarded) and when it was drafted, confirmed and superseded. Select Show to read one.
Confirming a new version replaces the current baseline. New requests are checked against it. Requests checked earlier keep the evidence they were checked with.
Common questions
Do I have to tick every item before confirming? No. Only items marked Needs review block confirmation. Ticking Checked is how your team tracks its review.
What if drafting failed? Choose Add items by hand and build the scope yourself, then confirm it.
Where do I check a request now? See Checking a request.
Checked against the app on . Something out of date or unclear? Email hello@agreeably.io.