Every change you catch is a change you can price.

Most change requests are written weeks late, from memory, without the mail that caused them. AUVY flags new scope, moved dates and changed requirements where they appear, checks them against your offer, contract or statement of work and drafts the change request with its sources. A person decides, and the client approves by link.

← Use casesFor: Owners, project leads, commercial and delivery managers

Change requests

How change requests go today.

The change arrives in a side sentence and is delivered before anyone writes it down. At the final invoice, the argument is about who remembers what.

Use cases

What comes in, and what AUVY does with it.

When
A client asks for something new in a mail.
AUVY
Marks the request and checks it against the offer or statement of work.
You get
A change request with the mail and the offer clause attached.
Reads Mail · Offer
When
A decision in a meeting changes the scope.
AUVY
Finds it in the minutes and names the milestone and deliverables it affects.
You get
A change request drafted before the work is done.
Reads Minutes · Plan
When
A new revision of a document replaces the old one.
AUVY
Names what changed for your scope between the versions.
You get
The change visible, and a change request if it's extra.
Reads Document versions
When
The project closes.
AUVY
Lists every change with its status and sources.
You get
A final account where every item shows where it came from.
Reads The project's changes

Sources

Every answer shows its work.

Before a partner puts an answer in front of a client, they want to know where it came from. In AUVY that takes one click.

What did we agree about the Munich site?

The client added Munich as a third site on 12 March.¹ It is covered in the revised offer, section 4.² The workshop date is still open.

2 of 3 sentences have a sourceNo source: “The workshop date is still open.”

Offer v3.docxSource 2 · section 4, lines 12 to 14

4 Scope, phase 2
4.1 Munich is added as a third site,
as requested by the client on 12 March.
4.2 One workshop and two site visits.
4.3 Dates follow the revised plan.

Example project, synthetic data.

Meetings

Most scope changes are agreed in a meeting or a call.

MeetingsBeforeAfter

Steering committeeChange requests waiting for a decision, with their sources.Decisions recorded and new change requests drafted.

Client callOpen changes and what each would do to the dates.Wishes from the call notes marked as changes and drafted.

Rules

How AUVY fits the way your trade works.

Source first: Every change request cites the mail, minutes or file the change came from, and the offer clause it goes beyond.
The client decides by link: The client approves or declines without an account, and the answer is recorded.
No legal advice: AUVY drafts, and your people check wording, deadlines and contract terms.

At a glance

Walkthrough: 40 minutes on one of your own projects, free.
Price: €59 per person a month, billed yearly, with every project, team and bot included.
Your data: Stored on our own servers in Helsinki, never used to train AI, and deleted within 30 days after the contract ends.
Contract: Every order includes the data processing agreement under Art. 28 GDPR, German text binding.
Checked: 30 September 2026

Questions

Does AUVY find every change?

No tool can promise that. AUVY marks relevant changes in the sources you connected and the files you gave it, and shows what each one affects.

Can the client approve a change request without an account?

Yes. The client approves or declines from a link, and the answer is recorded in the project.

What does AUVY compare a request against?

The offer, contract or statement of work you gave the project, and the plan.

See it on one of your own projects.

Book a walkthrough Sign in