AUVY
DEBook a walkthrough

Every revision starts in a mail. AUVY carries it into the plan and the offer.

For engineering and planning offices, AUVY holds every client wish against the services you were hired for. It reads client mail, coordination minutes and drawing lists, flags wishes outside the agreed services, finds the drawings they touch and drafts the change note with its evidence. The project engineer signs off.

← Use casesFor: Owners, project engineers, specialist planners, and the client's project managers

Engineering & planning offices

A week in a planning office.

  • The client asks for “a second ventilation zone” in a two-line mail, and the drawing list is due before design freeze.
  • A specialist planner sends revision D; nobody is sure which drawings still show revision C.
  • Extra services get drawn first and argued about at the final invoice, without evidence on either side.

Use cases

What comes in, and what AUVY does with it.

  1. When

    The client wants a second ventilation zone for the lab wing.

    AUVY

    Marks the request, checks it against the services agreed for each phase in the offer, and finds the drawings it affects.

    You get

    A change note listing the extra services, for the client to approve by link before anyone draws it.

    Reads Mail · Offer v2, §2.4 · Drawing list

  2. When

    The structural engineer uploads a new revision of the load plan.

    AUVY

    Compares it with the previous revision and names what changed and which of your drawings still rely on the old one.

    You get

    Tasks for the affected drawings, each with an owner and a date.

    Reads SharePoint · Revision C ↔ D

  3. When

    A contractor asks a question about a detail during tender.

    AUVY

    Answers from the specification and the drawings with the exact page and version it read, and shows what it can't back with a source.

    You get

    A reply drafted for the project engineer to check and send.

    Reads Specification · Drawings · Tender mails

  4. When

    The client moves the design freeze by two weeks in a meeting.

    AUVY

    Finds the date in the minutes, shows where the plan still says the old date and which deliveries depend on it.

    You get

    The plan corrected with the source attached, and a confirmation for the client to answer.

    Reads Minutes · Plan

  5. When

    A project moves from design to tender with new people on it.

    AUVY

    Answers from the project's record: which wishes were agreed, which were declined, which revision is valid.

    You get

    A clean handover to the next team.

    Reads The whole project

  6. When

    You want a drawing register that stays current.

    AUVY

    Builds it as a small tool in the project from your description; the team updates it together, every change versioned.

    You get

    One register the whole team keeps current.

    Reads Your request · Drawing list

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

  1. 4 Scope, phase 2
  2. 4.1 Munich is added as a third site,
  3. as requested by the client on 12 March.
  4. 4.2 One workshop and two site visits.
  5. 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

Coordination meetings, client meetings, design reviews.

Prepared from the project's mail and files; followed through from the minutes you add.

MeetingsBeforeAfter
Design coordination meetingOpen points from the last minutes, new revisions since, and questions from specialist planners, each with its source.Every agreement in the minutes becomes a task with an owner and a date; changed dates are checked against the plan.
Client meetingNew wishes since the last meeting, which of them are outside the agreed services, and the change notes still waiting.Wishes marked as changes with the line of the minutes they came from, and the change note drafted for review.
Design review before freezeWhich drawings changed since the last review and why, with the mail or minutes behind each change.Decisions and open issues logged, the follow-up to the team prepared.

How AUVY fits

How AUVY fits the way you have to work.

Agreed services as the baseline
Name your service phases in the project, for example the HOAI work stages, and AUVY checks each new wish against the services agreed for that phase in the offer you gave it.
Revision history
Every version is kept, so you can show which revision was valid when, and which mail or meeting replaced it.
Evidence for every change note
Each change note cites the mail or minutes the wish came from. The client approves it by link, and the answer is recorded.
Specialist planners in one project
Partner offices are invited into the project they work on, never into your workspace.

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 know the HOAI?

AUVY works from the offer and the services you gave the project. When your offer lists services by work stage, it checks new wishes against them. It doesn't give legal advice; the project engineer decides.

Can AUVY read drawings?

It reads the drawing lists, specifications, PDFs and mails you give the project, and compares versions of documents. The engineers keep working in their CAD tools.

How does AUVY help with extra services?

It marks a new wish where it arrives, checks it against the agreed services, and prepares a change note with the evidence, for the client to approve by link before the work starts.

Where is project data stored?

Workspace and account data is stored in the EU (Helsinki). AI runs through approved providers in EU regions. Customer data is not used for model training.

Also read

All use cases →

Checked 29 September 2026 against what AUVY does today.

See it on one of your own projects.

Book a walkthroughSign in