Scope moves in the steering committee. AUVY checks it against the statement of work.

For IT service providers and implementation partners, AUVY checks steering-committee decisions against the statement of work. It reads customer mail, meeting minutes and project files, flags changes to scope and dates, and drafts the change request with the line of the minutes and the clause of the statement of work attached. The project manager signs off.

← Use casesFor: Managing directors, delivery leads, project managers, solution architects

IT services & implementation partners

A week in an implementation.

The steering committee agrees that the new CRM should also sync with the warehouse system from go-live.
The interface isn't in the statement of work, and the go-live date hasn't moved in the plan.
The change request is written after the work is done, and the scope argument lands on the last invoice.

Use cases

What comes in, and what AUVY does with it.

When
The steering committee agrees a new interface.
AUVY
Finds the decision in the minutes, checks it against the statement of work, and shows the milestone it puts at risk.
You get
A change request draft with the evidence, for the customer to approve or decline.
Reads Minutes item 4 · SoW v1.2 §5 · Plan M4
When
Requirement workshops produce pages of notes.
AUVY
Pulls requirements from the notes with the passage each came from, and marks the ones outside the agreed scope.
You get
Requirements you can trace, and scope changes caught at the source.
Reads Workshop notes · SoW
When
The customer asks where the project stands.
AUVY
Answers from the project's sources: what changed, what's at risk, what's waiting for whom, each line with its source.
You get
A status report ready for the project manager to review.
Reads Mail · Minutes · Plan
When
The cutover plan goes through its fifth version.
AUVY
Keeps every version and shows what changed and which mail or meeting caused it.
You get
Everyone works from the current version, and you can show why it changed.
Reads Cutover plan versions
When
Hypercare questions arrive after go-live.
AUVY
Answers from the configuration documents and decisions on record, with the source for each answer.
You get
Consistent answers, drafted for the team to send.
Reads Design documents · Decisions · Mails
When
Two projects for different customers use the same template.
AUVY
Links the projects so the approved work of one becomes context for the other; each customer's content stays in its own project.
You get
What you learned on the last rollout, reused without copying customer data around.
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

Steering committees, requirement workshops, the weekly status call.

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

MeetingsBeforeAfter

Steering committeeChanges and risks since the last meeting, change requests waiting for a decision, milestones at risk, with sources.Decisions logged against the statement of work, change requests drafted, the follow-up prepared for review.

Requirement workshopRequirements already agreed and questions still open.New requirements traced to the notes, scope changes marked, tasks set.

Weekly status callWhat moved this week and what needs the customer.Tasks with owners and dates; the minutes filed with the project.

How AUVY fits

How AUVY fits the way you have to work.

The statement of work as the baseline: Decisions and requests are checked against the statement of work you give the project, before the work is done.
Customer data stays in its project: Each customer is its own project. Linked projects share approved work, never raw customer content.
Customer approval by link: The customer approves or declines a change request from a link, without an account; the answer is recorded.
Your ticket tool stays: Keep Jira or whatever you use. AUVY reads the mail and files where the change actually arrived.

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

We already use Jira. Why AUVY?

Keep it. Jira knows what someone typed in. AUVY reads the mail, minutes and files where the change actually arrived and shows what the plan and the statement of work should now say.

Can AUVY read Teams meeting minutes?

Yes, the minutes, notes and transcripts you give the project, as files, mails or in the Teams and SharePoint places you connect.

Does AUVY write change requests on its own?

It drafts them with the evidence. A person accepts, edits or rejects them; nothing is sent on its own.

Is AUVY GDPR-compliant for customer projects?

Workspace data is stored in the EU, the AVV under Art. 28 GDPR is part of every order, and every subprocessor is listed in the trust center.

See it on one of your own projects.

Book a walkthrough Sign in

Scope moves in the steering committee. AUVY checks it against the statement of work.

A week in an implementation.

What comes in, and what AUVY does with it.

The steering committee agrees a new interface.

Requirement workshops produce pages of notes.

The customer asks where the project stands.

The cutover plan goes through its fifth version.

Hypercare questions arrive after go-live.

Two projects for different customers use the same template.