Every change you catch is a change you can price.

AUVY flags new scope, moved dates and changed requirements in the mail, minutes or file where they appear, checks them against your offer, contract or statement of work, and drafts the change request with the evidence attached. 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.
The change request is written weeks later, from memory, without the mail that caused it.
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 draft 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
Compares the versions and names what changed for your scope.
You get
The change visible, and a change request if it's extra.
Reads Document versions
When
The client has to approve.
AUVY
Sends the change request by link; the client approves or declines without an account.
You get
The answer recorded in the project with the version it applies to.
Reads Change request
When
The project closes.
AUVY
Lists every change with its status and evidence.
You get
A final account you can support line by line.
Reads The project's changes
When
You want the same change process on every project.
AUVY
Turns your change process into a repeatable workflow the team runs with review.
You get
Every project handles changes the same way.
Reads Your procedure

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–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.

Numbered sources: Every statement in an answer carries a small number. The number points to the file, the version AUVY read and the lines it used.
One click to the passage: Click the number and the file opens beside the conversation, scrolled to the passage and marked in the text. A deck turns to the slide; a spreadsheet selects the cited cells.
It checks itself: AUVY shows how much of an answer is backed by a source and names the sentences that are not, so you know what to verify before it goes out.
Every version kept: Files change during a project. Every version stays, so you can see the text an answer was based on and what has changed since.

Meetings

Where change requests are born.

Most scope changes are agreed in a meeting or a call. AUVY reads the minutes and notes you add and catches them there.

MeetingsBeforeAfter

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

Client callOpen changes and what each would cost in dates.Wishes from the call notes marked as changes, drafts ready for review.

How AUVY fits

How AUVY fits the way you have to work.

Evidence 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; the answer is recorded.
No legal advice: AUVY drafts; your people check wording, deadlines and contract terms.
Nothing leaves unreviewed: A change request goes out only after someone accepts it.

For every project

The same ground rules, whatever you deliver.

Only what you give it: Each project reads only the sources you give it: a folder, a mail thread, the Outlook, Teams and SharePoint places you connect.
One project, one room: Project content stays in its project. Personal notes stay yours. An outside partner is invited into one project, never into the workspace, and a read-only link shows one view and nothing else.
A person decides: AUVY prepares; a person accepts, edits or rejects. Nothing leaves until someone accepts it. When a step needs a person, AUVY stops and asks them by name.
Everything on record: Every answer cites the document and the exact version it read, and shows the sentences that have no source. Every version is kept, and a client's answer by link is recorded in the project.
Data in the EU, no training: Workspace and account data is stored in the EU (Helsinki); AI runs through approved providers in EU regions. Customer data is never used or designated for model training. Every subprocessor is listed in the trust center.
No one is scored: AUVY senses the project, not the people: no per-person performance views, no employee scoring. The AVV under Art. 28 GDPR is part of every order.

Questions

Does AUVY find every change?

No tool can promise that. AUVY marks relevant changes in the sources you connected and the evidence 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.

Does AUVY send change requests automatically?

No. It drafts; a person accepts, edits or rejects.

See it on one of your own projects.

Book a walkthrough Sign in

Every change you catch is a change you can price.

How change requests go today.

What comes in, and what AUVY does with it.

A client asks for something new in a mail.

A decision in a meeting changes the scope.

A new revision of a document replaces the old one.

The client has to approve.

The project closes.

You want the same change process on every project.