Reading the analysis of a request

What the analysis shows for each requested change, including the Included, Potentially additional or Unclear label, the evidence and what Needs review means.

Once a request is analysed, its page shows each change the client asked for, how it reads against the confirmed scope, and the exact agreement wording behind that reading. The analysis informs your decision. It never makes it.

Open a request

  1. Open the project and choose Requests.
  2. Select the request.

You can also open requests from the Inbox.

The page has two sides. On the left is the Client request: the text the client sent and Your team’s notes. On the right are the Requested changes and the Agreement evidence for the one you have selected.

While it is analysing

The evidence side shows “Queued” or “Analysing”, with the revision and scope version being checked. You can leave the page; the result appears when ready.

If the analysis fails, you see Assessment failed with the reason. A failed attempt does not count against your allowance. Owners and Delivery leads can select Retry, which uses one analysis.

Requested changes and their labels

A client message often asks for more than one thing. The analysis splits it into separate requested changes, and gives each one a label:

  • Included: the confirmed scope or an approved amendment appears to cover it.
  • Potentially additional: it appears to fall outside what was agreed, for example because the agreement excludes it.
  • Unclear: the agreement does not settle it. This is used when sources conflict, wording is vague, or approval evidence is missing.

These are labels, not verdicts. There is no confidence score. Above the list you will see counts such as “2 included”, “1 additional” and “1 unclear”.

Select a requested change to see its evidence. Use the arrow keys to move through the list.

Agreement evidence

For the selected change, the evidence side shows:

  • Quoted agreement wording, with the clause it comes from. Each quotation is marked Quotation matched to source text. The wording is taken from your stored agreement, not written by the AI, so what you read is what was signed.
  • Amendments, when an approved change request is relevant. These show the change request number, the approval date, and the added work, exclusions and assumptions. They are marked as approved by the client, not agreement wording.
  • Team interpretation, when your team recorded an interpretation of a scope item. It is marked “not agreement wording”.
  • Why: the analysis’s explanation.
  • Missing context: what would help settle it, when something is missing.
  • Suggested next step: what to do, when the analysis has a suggestion.

If no wording supports the label, you see No agreement wording cited.

Needs review

Some changes are marked Needs review. Check these against the agreement before relying on them. The reason is shown on the evidence side:

  • “The analysis cited scope that does not exist; that citation was removed.”
  • “No agreement wording or amendment supports this label.”

Any quotation that cannot be matched to your stored agreement is removed rather than shown.

Flagged for review

An analysis is Flagged for review when something it relied on changed after it finished, such as an amendment being reversed. The request list shows “Flagged: re-analyse”. Select Re-analyse on the request to check it against the scope as it is now. That uses one analysis.

About this assessment

Open About this assessment to see which scope version and agreement version were used, the model, when it finished, and how many context notes and amendments it read. A note marked “not used by this assessment” was added after the analysis ran.

If the request has been edited or re-analysed, buttons at the top let you switch between assessments and revisions. Earlier assessments are kept as history.

Similar past decisions

On the Business and Team plans, Similar past decisions shows up to five earlier decided changes from your workspace that are worded like this one. Each shows its decision, reason and a link. They are for reference only: nothing is suggested or filled in from them. Matching does not use your analysis allowance, and only projects you can see are included.

The AI never decides

Beside the decision you will see: “Labels are the AI’s reading of the confirmed scope. Check the agreement wording before you decide.” The label and your decision are kept separately. What to do about each change is up to you. See Recording a decision.

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