The grid operator moves the connection date. AUVY shows what moves with it.

For energy and infrastructure project companies, AUVY reads the mail, minutes, permits and supplier confirmations of each project, flags changes to dates, scope and requirements, shows which milestones and deliveries depend on them, and drafts the reply, the tasks and the change request, each with its source. The project manager signs off.

← Use casesFor: Managing directors, project managers, engineering and procurement, and the client's asset team

Energy & infrastructure projects

A week on an energy project.

The grid operator writes that the connection will be three weeks later, in the fourth paragraph of a letter.
A module supplier confirms a new delivery week in a PDF, and nobody links it to the installation crews.
The client adds a storage option in a meeting, and it reaches the offer only at the final invoice.

Use cases

What comes in, and what AUVY does with it.

When
The grid operator moves the connection date.
AUVY
Finds the new date in the letter, shows the commissioning and handover milestones that depend on it, and names who needs to know.
You get
The plan updated with the letter as the source, and notes to the client and the crews drafted.
Reads Grid operator letter · Plan
When
A supplier confirms delivery two weeks late.
AUVY
Compares the confirmation with the order and shows which installation step moves.
You get
A task to re-plan and a reply to the supplier, ready for review.
Reads Supplier confirmation · Order · Plan
When
The client adds a battery storage option in a meeting.
AUVY
Flags the wish in the minutes and checks it against the contract scope.
You get
A change request with the evidence, for the client to approve by link.
Reads Minutes · Contract
When
The permit comes back with conditions.
AUVY
Lists each condition with the page it is on and what in the project it affects.
You get
Tasks per condition, each with an owner and a date.
Reads Permit · Project files
When
Acceptance with the client is next week.
AUVY
Lists every agreed change since the contract, its status and the evidence behind it.
You get
An acceptance where every deviation is explained.
Reads Change requests · Contract · Mails
When
You run twenty similar projects at once.
AUVY
Links them, so approved work from one becomes context for the next while each project's content stays in its own project.
You get
What you learned on the last site, available on the next one.
Reads Linked projects

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

Site meetings, supplier calls, client reviews.

Prepared from the project's sources; followed up from the minutes and notes you add.

MeetingsBeforeAfter

Site meetingOpen points by trade, changed dates and questions from subcontractors.Agreements as tasks with owners and dates; changed dates checked against the plan.

Supplier callConfirmed and changed delivery dates, with the installation steps behind them.New dates logged with their source; the tasks that follow from them set.

Client reviewProgress, open changes and decisions due, each with its source.Decisions on record, change requests drafted, the follow-up ready for review.

How AUVY fits

How AUVY fits the way you have to work.

The contract as the baseline: Wishes and changes are checked against the contract and the scope you give the project.
Conditions and deadlines: AUVY lists the conditions and dates in permits and grid operator letters with the page they are on. Your people decide how to respond; AUVY gives no legal advice.
Subcontractors in one project: Installers and planners are invited into the project they work on, never into your workspace.
A person decides: No mail, notice or change request leaves 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

Can AUVY read permits and grid operator letters?

Yes, the documents and mails you give the project. It lists what they require and what in the project they affect, with the page as the source.

Does AUVY connect to our ERP or monitoring systems?

No. It reads the documents, exports and mails you give the project.

Can we use AUVY across many similar projects?

Yes. Each project is its own, and linked projects share approved work as context.

Where is our data stored?

Workspace and account data is stored in the EU (Helsinki). Customer data is not used for model training.

See it on one of your own projects.

Book a walkthrough Sign in

The grid operator moves the connection date. AUVY shows what moves with it.

A week on an energy project.

What comes in, and what AUVY does with it.