--- title: "AUVY for IT services: statement of work and go-live" description: "AUVY checks steering-committee decisions against the statement of work, drafts change requests with their sources and answers hypercare questions from the…" url: https://www.auvy.ai/use-cases/it-services lang: en site: AUVY brief: https://www.auvy.ai/llms.txt --- # Scope moves in the steering committee. AUVY checks it against the statement of work. In an implementation, the change request usually gets written after the work is done. AUVY checks each steering-committee decision against the statement of work, shows the milestone it puts at risk and drafts the change request with the line of the minutes and the clause attached, for the project manager to sign off. [← Use cases](https://www.auvy.ai/use-cases) For: 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, so the argument lands on the last invoice. Use cases ## What comes in, and what AUVY does with it. 1. 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 with its sources, for the customer to approve or decline. Reads Minutes item 4 · SoW v1.2 §5 · Plan M4 2. When ### Requirement workshops produce pages of notes. AUVY Pulls the requirements out with the passage each came from and marks the ones outside the agreed scope. You get Requirements you can trace, and scope changes caught where they start. Reads Workshop notes · SoW 3. When ### The customer asks where the project stands. AUVY Answers from the project's sources with what changed, what is at risk and what waits for whom, each line with its source. You get A status report for the project manager to review. Reads Mail · Minutes · Plan 4. When ### Hypercare questions arrive after go-live. AUVY Answers from the configuration documents and the decisions on record, with the source for each answer. You get Consistent answers, drafted for the team to send. Reads Design documents · Decisions · Mails 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 source No source: “The workshop date is still open.” **Offer v3.docx** Source 2 · section 4, lines 12 to 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. Meetings ## Steering committees, requirement workshops, the weekly status call. Meetings Before After Steering committee Changes and risks since the last meeting, change requests waiting and milestones at risk, with sources. Decisions logged against the statement of work, change requests drafted and the follow-up prepared. Requirement workshop Requirements already agreed and questions still open. New requirements traced to the notes, scope changes marked, tasks set. Weekly status call What moved this week and what needs the customer. Tasks with owners and dates, and the minutes filed with the project. Rules ## How AUVY fits the way your trade works. 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, so the last rollout's lessons carry over safely. Your ticket tool stays Keep Jira or whatever you use. AUVY reads the mail and files where the change actually arrived. At a glance Walkthrough 40 minutes on one of your own projects, free. Price €59 per person a month, billed yearly, with every project, team and bot included. Your data Stored on our own servers in Helsinki, never used to train AI, and deleted within 30 days after the contract ends. Contract Every order includes the data processing agreement under [Art. 28 GDPR](https://eur-lex.europa.eu/eli/reg/2016/679/oj) , German text binding. Checked 30 September 2026 Questions ### We already use Jira. Why AUVY? Keep Jira. It knows what someone typed in, while AUVY reads the mail, minutes and files where the change 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 their sources. A person accepts, edits or rejects them, and nothing is sent on its own. Also read - [Consultancies Consulting engagements change every week. AUVY keeps each one current. ](https://www.auvy.ai/use-cases/consultancies) - [System integrators & automation Revision D replaces revision C. AUVY shows what that means before commissioning. ](https://www.auvy.ai/use-cases/system-integrators) - [Meetings Most changes are agreed in a meeting. AUVY makes sure they leave the room. ](https://www.auvy.ai/use-cases/meetings) [All use cases →](https://www.auvy.ai/use-cases) ## See it on one of your own projects. [Book a walkthrough](https://www.auvy.ai/walkthrough) [Sign in](https://www.auvy.ai/os/)