The weekly status report, drafted from the sources.
Ask AUVY for the week's status and it drafts the report from the project's own mail, minutes and files: what changed since last week, what is at risk and what needs a decision, every line with its source. The project lead checks it, edits it and sends it.
← Use casesFor: Project leads, heads of delivery, owners, and the clients and steering committees who read the reports
Status reports
How status reports get written today.
- Every Friday, someone senior spends the afternoon gathering what happened from mails and files.
- The report says what its author remembered, and nobody can check where a line came from.
- By Monday the report is already out of date.
Use cases
What comes in, and what AUVY does with it.
- When
Friday's status report is due.
AUVYDrafts it from the week's mail, minutes and files: changes, risks and decisions due, each line with its source.
You getA report ready to check, edit and send.
Reads Mail · Minutes · Files
- When
The client questions a line in the report.
AUVYOpens the source behind it, at the passage, marked.
You getThe answer to the question in one click.
Reads The report's sources
- When
A line has no source.
AUVYNames it, so the project lead knows exactly what to verify.
You getA report where every unsupported sentence is visible before it goes out.
Reads The draft
- When
The steering committee wants a one-page summary.
AUVYCondenses the status into the decisions the committee has to take, with the evidence for each.
You getA one-pager for the committee, ready for review.
Reads Status · Change requests
- When
You want the same report every week.
AUVYTurns your report format into a repeatable workflow the team runs with review.
You getThe same structure every week, whoever writes it.
Reads Your template
- When
Someone asks what the status was a month ago.
AUVYShows the earlier version of the report and of the files behind it.
You getWhat was true then, and what has changed since.
Reads Report versions
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
Where status reports are read.
The report is ready before the meeting and picks up the decisions from the minutes after it.
How AUVY fits
How AUVY fits the way you have to work.
- Every line has a source
- Each statement links to the mail, minutes or file it came from, and lines without a source are named.
- A person sends it
- AUVY drafts; the project lead checks, edits and sends.
- The project, not the people
- Reports cover the state of the project, never how individual people work.
- History kept
- Every version of every report and every file behind it is kept.
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 write our weekly status report?
It drafts it from the project's mail, minutes and files, with a source for every line. A person checks and sends it.
Can we keep our own report format?
Yes. Turn your format into a repeatable workflow the team runs with review.
What if a line in the report is wrong?
Every line links to its source and lines without one are named, so errors are quick to find. Nothing goes out until someone accepts it.
Does the report rate team members?
No. AUVY has no per-person performance views and no employee scoring.
Also read
