Back from leave, new on the project, next phase: nobody rebuilds where things stand.
You come back already ahead. After leave, on joining a project or when taking over the next phase, anyone can ask AUVY what changed, what was agreed and what is waiting for them, and get the answer from the project's own record, every line linked to its source.
← Use casesFor: Project leads, new team members, anyone taking over a project
Handovers
How handovers go today.
- Two weeks of leave means a morning of reading mail and still missing the one that mattered.
- A handover is a meeting where someone tries to remember everything.
- The next phase starts with questions nobody wrote the answers to.
Use cases
What comes in, and what AUVY does with it.
- When
Back from two weeks of leave.
AUVYShows what changed on each project while you were away, what needs you, and what was decided, each with its source.
You getYou pick up where the project stands today.
Reads The whole project
- When
A new colleague joins the project.
AUVYAnswers their questions from the project's record, with the document and version for each answer.
You getAnswers from the first day, each with its source.
Reads The whole project
- When
The project moves to the next phase or team.
AUVYLists agreements, open points, declined wishes and current versions.
You getA handover list anyone can check against the sources.
Reads The whole project
- When
A client's contact person changes.
AUVYShows the new person on the People map and what they need to know, from what's written.
You getContinuity on the client side too.
Reads Mail · Minutes
- When
A partner takes over part of the work.
AUVYInvites them into the one project, where they see what they need and nothing else.
You getA clean handover across company lines.
Reads The project
- When
The same kind of project starts again.
AUVYLinks it to the last one so the approved work becomes context for the new one.
You getWhat you learned last time, available from day 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.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
The handover meeting, shorter.
The record does the remembering; the meeting is for questions.
How AUVY fits
How AUVY fits the way you have to work.
- Access follows the project
- A newcomer sees the projects they're invited into, and nothing else.
- Answers with sources
- Every answer cites the document and version it read, and shows what it can't back with a source.
- History kept
- Every version is kept, so a newcomer can see what was true when.
- No one is scored
- Handovers are about the project, never about how a person worked.
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
How does AUVY help after holidays?
It shows what changed on each project while you were away, what needs you, and what was decided, each with its source.
Can a new team member ask AUVY about the project's history?
Yes. They ask in plain language and get answers from the project's own record, with the source for each line.
Does a newcomer see everything in the workspace?
No. They see the projects they are invited into. Personal notes stay personal.
Does AUVY help across similar projects?
Yes. Link two projects and the approved work of one becomes context for the other.
Also read
- MeetingsMost changes are agreed in a meeting. AUVY makes sure they leave the room.
- ConsultanciesConsulting engagements change every week. AUVY keeps each one current.
- IT services & implementation partnersScope moves in the steering committee. AUVY checks it against the statement of work.
Checked 29 September 2026 against what AUVY does today.