Client approvals, answered by link and kept on record.
AUVY sends a change request, a confirmation or a deliverable to your client as a link. The client approves, declines or answers without an account, and the answer is recorded in the project with the version it applies to. Someone on your team decides what goes out.
← Use casesFor: Project leads, account managers, and the clients who approve their work
Client approvals
How approvals go today.
- Approvals sit in reply-all threads, and the one that counts is hard to find later.
- A client approves version 3 on the phone, and the team delivers version 4.
- At the final invoice, nobody can show who approved the extra work, or when.
Use cases
What comes in, and what AUVY does with it.
- When
A change request needs the client's decision.
AUVYSends it as a link; the client approves or declines without an account.
You getThe decision recorded in the project, with the change request it applies to.
Reads Change request
- When
A date moved in a meeting.
AUVYDrafts a short confirmation for the client, with the minutes as the source.
You getThe new date confirmed in writing by the client.
Reads Minutes
- When
A deliverable is ready for sign-off.
AUVYSends that version for approval by link.
You getApproval tied to exactly that version.
Reads Deliverable version
- When
The client has a question before approving.
AUVYKeeps the question and your answer with the approval.
You getThe whole exchange in one place.
Reads The approval
- When
The client wants to see what was approved so far.
AUVYShares a read-only view of the approved changes by link; nothing else in the project is visible through it.
You getOne agreed list of what was approved, and when.
Reads The project's approvals
- When
The final invoice is due.
AUVYLists every approval with its date, version and evidence.
You getEvery approved change, provable line by line.
Reads The project's approvals
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.1 It is covered in the revised offer, section 4.2
2 of 3 sentences have a sourceNo source: “The workshop date is still open.”
- 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.
- 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 approvals come from.
Many approvals are given in a meeting. AUVY turns them into confirmations the client answers in writing.
How AUVY fits
How AUVY fits the way you have to work.
- No account for the client
- The client answers from a link; nothing else in your workspace is visible to them.
- Tied to the version
- Every approval records the version it applies to.
- A person sends it
- Nothing goes to the client until someone on your team accepts it.
- On record
- Every approval, question and answer stays in the project.
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 the client need an AUVY account to approve?
No. The client approves, declines or answers from a link.
What can a client approve?
A change request, a confirmation or a deliverable version. They can also answer a question.
Where are approvals stored?
In the project, with the version they apply to.
Does AUVY send approval requests on its own?
No. It drafts them, and a person on your team accepts before anything goes out.
Also read
Checked 29 September 2026 against what AUVY does today.