Checking a client request against the scope

How to paste a client's request into Check a request, choose the project, add context notes for the analysis, and what happens once it is added.

When a client asks for something, paste their words into Check a request. Agreeably adds it to the project as a request and analyses it against the confirmed scope and any approved amendments.

You can also forward the email to the project’s address (see Forwarding client emails) or send it from the browser extension. All three end up in the same place.

Before you start

  • The project needs a confirmed scope. Until then it is listed in the dialog but cannot be chosen, with the note Confirm the scope first. See Confirming the scope.
  • Owners and Delivery leads can check requests. Viewers cannot, and the button is not shown to them.
  • The workspace must not be read-only, and the project must be active rather than archived.
  • The sample project is closed to new requests. It shows in the list as Sample: closed to new requests.

Open Check a request

There are three ways in:

  • From anywhere in the app, select Check a request in the sidebar.
  • Press N on your keyboard, as long as you are not typing in a field and no other dialog is open.
  • From inside a project, select Check a request in the project header. The dialog then opens with that project already chosen.

Check a request step by step

  1. Open Check a request.
  2. Choose the project. Projects are listed as name and client. Type in Search projects or clients to narrow the list, and use Load more if yours is not shown.
  3. Paste what the client wrote into the text box. It holds up to 20,000 characters.
  4. Optionally fill in Received from (who sent it) and Received on (the date it arrived).
  5. Optionally add notes for the analysis (see below).
  6. Select Check against scope.

If you chose the wrong project, select Change project before you check it.

Add a note for the analysis

Sometimes the request only makes sense with something the client said on a call or in a meeting. Select Add a note for the analysis to give the analysis that context.

For each note:

  1. Choose Where it came from: Call notes, Meeting notes, Email thread, Chat message or Other.
  2. Optionally add a Source, for example “Call with Dana, 30 October”.
  3. Write the Note itself.

Select Add another note for more, up to 10 per request. Remove notes closes the section and drops what you wrote.

The analysis reads notes as context only. It never treats them as agreement wording, so a note cannot widen the scope.

What happens next

Checking a request uses one analysis from your plan’s allowance. Once it is added:

  1. The dialog closes and the new request opens, numbered within the project.
  2. The analysis is queued, then runs. The page shows its progress, and you can leave while it works.
  3. When it finishes, the request moves to Awaiting decision with each requested change listed. Reading the analysis explains what you see.

If your plan’s analyses for the period are used up, the request is not lost. It shows as Held for allowance and is analysed automatically, oldest first, when allowance is available.

Changing a request after it is added

On the request’s page you can:

  • Select Add context note to add another note. This does not start an analysis. The note is read the next time the request is analysed.
  • Select Edit request to change the text. Saving adds a new revision and analyses it, using one analysis. The earlier revision and its assessment stay as they were.
  • Select Re-analyse to run the analysis again on the current text, for example after adding a note. This also uses one analysis.

Common questions

Why can’t I choose my project? Its scope has not been confirmed yet, it is the sample project, or it is archived. Only active projects are listed.

Why is there no Check a request button? You may be a Viewer, or the workspace may be read-only.

Can I paste several changes in one message? Yes. The analysis splits a mixed message into separate requested changes, and you decide on each one.

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