Clients decide in passing. AUVY makes sure the decision is on record.

For architecture firms, AUVY puts every client decision on record when it is made. It reads client mail, minutes, the brief and the consultants' files, links each decision to the mail or meeting it came from, checks it against the brief and the agreed services, and drafts the confirmation. The architect signs off.

← Use casesFor: Principals, project architects, and the consultants and clients around them

Architecture firms

A week in a studio.

The client mentions a larger kitchen on the phone and confirms it in half a sentence by mail.
The structural and building-services consultants each send new files; the plan set has to follow both.
Decisions pile up across mails and minutes, and in the dispute about fees nobody can show when a wish came in.

Use cases

What comes in, and what AUVY does with it.

When
The client writes “as discussed, let's go with the larger kitchen”.
AUVY
Marks the decision, links it to the meeting where it came up, and checks it against the brief and the agreed services.
You get
A short confirmation to the client, and a change note if it's outside the scope, both ready for review.
Reads Mail · Minutes · Brief
When
The building-services consultant moves a shaft.
AUVY
Compares the new file with the old one and names the plans and details that still show the shaft in its old place.
You get
Tasks for the affected sheets, each with an owner and a date.
Reads Consultant files · Plan list
When
The building authority asks for more documents.
AUVY
Finds the request in the correspondence, lists what is asked for and what already exists in the project, with the source for each.
You get
A checklist and a reply drafted for the project architect.
Reads Authority letters · Project files
When
The client asks why the cost estimate went up.
AUVY
Answers with the decisions behind each increase and the mail or meeting each one came from.
You get
An explanation the client can follow decision by decision.
Reads Cost estimates · Mails · Minutes
When
A new project architect joins in the middle of the design.
AUVY
Answers from the project's record: every client decision, what was declined, which consultant file is current.
You get
The client keeps dealing with someone who knows the history.
Reads The whole project
When
You need a decision log the client can see.
AUVY
Shares a read-only view of the decisions with the client by link; nothing else in the project is visible through it.
You get
One agreed record of who decided what, and when.
Reads The project's decisions

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

Client meetings, planning team meetings, site meetings.

AUVY prepares from the project's sources and follows up from the minutes you add.

MeetingsBeforeAfter

Client meetingDecisions still open, wishes since the last meeting, and what each would change in cost and schedule, with sources.Decisions confirmed in writing with the line of the minutes, change notes drafted, tasks set.

Planning team meetingNew consultant files since the last meeting and where they conflict with the current plans.Agreements become tasks with owners and dates across the consultants.

Site meetingOpen questions from the contractors and the answers already given.Site decisions logged with their source, the follow-up prepared for review.

How AUVY fits

How AUVY fits the way you have to work.

Client decisions in writing: Every decision is linked to the mail or minutes it came from, and the client can confirm by link, without an account.
Brief and services as the baseline: New wishes are checked against the brief and the services agreed in your contract, so fee conversations start with evidence.
Consultants in one project: Structural, building-services and other consultants are invited into the project they work on, not your workspace.
A person decides: Nothing goes to the client, a consultant or an authority until 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 replace our CAD or BIM tools?

No. AUVY reads the mails, minutes, briefs and files you give the project and keeps the picture current. You keep drawing where you draw.

Can the client see what AUVY prepares?

Only what you share: a read-only link to one view, or a confirmation the client answers by link. Nothing leaves until someone on your team accepts it.

How does AUVY help when the client disputes additional fees?

Every wish and decision is linked to the mail or meeting it came from and every version is kept, so you can show when a change came in and what was agreed.

Is our data used for AI training?

No. AUVY does not designate customer data for model training.

See it on one of your own projects.

Book a walkthrough Sign in

Clients decide in passing. AUVY makes sure the decision is on record.

A week in a studio.

What comes in, and what AUVY does with it.

The client writes “as discussed, let's go with the larger kitchen”.

The building-services consultant moves a shaft.

The building authority asks for more documents.

The client asks why the cost estimate went up.

A new project architect joins in the middle of the design.

You need a decision log the client can see.