OVIOO AITalk about the work without losing the work.
Tasks with an owner and a date, requests that arrive with the job attached, cover when somebody is away, and one calendar for everything dated. Coordination that carries its context, so nobody starts by asking which job this is about.
- Chase certificates for Castellane7426912 days late
- Confirm delivery window with VantageFrom Adrián’s email742615Today
- Resend requirements list to VantageFrom Adrián’s email742615Today
- Quote for the spring programme742580Waiting on Vantage · 3 days
- Signed contract from Halden & Co742615Waiting on client · 1 day
- Final payment reminder to Halden & Co742615Fri 28 Aug
My work, sorted the way a day is.
Eight buckets with counts across the top, and every task carrying the message it came from and the job it belongs to.
Overdue, today, this week, waiting
Plus Later, Completed, All, and one bucket for what OVIOO proposed from the mail. Counts on every tab, so the shape of the day is visible before anything is opened.
Every task knows why it exists
“Where it stands” and “Linked to” sit on the task itself: the message that produced it, the job it belongs to, the person waiting on it.
Waiting is a state, not a failure
Work that sits with a supplier or a customer shows as waiting, with the date it left your hands — chaseable at a glance, and never mistaken for your team being late.
Requests are tasks other people own
Ask a colleague or a whole department for something with a due date. It lands in their list and stays visible in yours until it is answered.
Add a task by typing and pressing Enter. Give it a date and it appears in the calendar beside meetings, invitations, payments and records. “Take this on” moves a colleague’s task to you when they are away.
Where colleagues meet, on the job itself.
Three cards, each opening the full view: conversations, requests, handover.
Recent conversations
Internal chat on a reference or between colleagues — “what did the supplier say?” next to what the supplier said. Never a separate app; the thread stays with the job.
Requests
Ask a colleague or a department for something, with a due date: a document, a decision, a payment. The request sits in their My work and in the Calendar until it is answered; the answer is on the record.
Coverage & handovers
Mark someone away and name who covers. Their open tasks show “Take this on” to the cover; their mailboxes stay readable to whoever was granted them. Nothing waits on a person who is not there.
- MKMarta · Vacation21 Aug → 4 Sep
- COClara · Out Friday PM28 Aug
Marta is away. Daniel is covering 12 references until 4 Sep.
Can you check this before I reply? The dates changed again.
On it — the supplier confirmed the 12th this morning. Replying now.
- COClara → YouDue today
Check the Castellane proforma before I book the payment.
742615LaterDone - NBYou → NoraDone
Forward the specification changes to the site team.
One calendar. Every kind of date.
The Calendar shows seven kinds of thing side by side, each with its own filter: meetings, invitations, TODOs, requests, payments, documents and records. Switch between Everything, Mine and Company. Accept or decline an invitation from the mail and it lands here; set a date on a task and it lands here.
Deadlines remind once a day, per person, across tasks, requests and records. Payments remind their department, because a payable is owed by a desk, not a colleague.
- Mon 14MeetingsVantage — delivery window
- Tue 15PaymentsCastellane SA · €11,940 dueTODOsSend requirements list v4
- Wed 16RequestsClara → Daniel: delivery schedule
- Thu 17InvitationsHalden — kickoff callDocumentsQuotation #742615 expires
- Fri 18RecordsQuote Q-2027-014 valid until
Visibility for owners, without surveillance.
In the Business workspace, People → Team has four tabs. What a manager sees is the shape of the work, not the person’s screen: which references moved, how much mail was handled, what was created, and where work is piling up after a handover.
- People. Who is in the company, in which area, with which role and access level.
- Areas. Departments and teams as the places work and money are routed to — where a request or a payable lands.
- Away. Absences with cover, so the handover happens before the email does.
- Activity. References progressed, mail handled, documents created, by person and period. Business activity inside OVIOO; never screenshots, never keystrokes.
- DMDanielcovering Marta
- NBNora
- ERElena
- COClara
- Doing well: finance backlog cleared, 9 jobs closed.
- Needs support: Daniel carries Marta’s handover — consider redistributing 4 references.
- Potential blocker: 3 jobs waiting on one supplier for 5+ days.
Seats are people. The owner invites them.
No one wanders into OVIOO with a random account. The owner creates the organisation, invites colleagues, and decides which mailboxes, files and modules each one reaches.
- DMDaniel MoreauOperationsprojects@ · orders@Member
- NBNora BergOperationsprojects@ · orders@Member
- COClara OseiFinanceprojects@ · orders@Member
- MKMarta KellerOperationsprojects@ · orders@Member
- Invite a colleague — they set their own password, OVIOO never holds it.Invite
How work behaves here
Coordination that does not become a second inbox to reconcile with the first.
A request carries the job with it
“Can you check this quotation?” arrives with the reference, the customer, the supplier, the amount, the status and the file. One click opens the job itself. The person answering does not start by working out what is being asked about.
Waiting is a state, not a silence
Work sitting with somebody else shows as waiting, with the date it left. It is chaseable at a glance and never mistaken for your team being late — which is the difference between a list you trust and one you stop opening.
One list per person, sorted like a day
Overdue, today, this week, waiting on somebody else. Not a board somebody has to groom, not a project plan somebody has to maintain: the list is a by-product of the work rather than a second job.
Absence is planned for
Mark somebody away and name their cover. Open work offers itself to the cover, mailboxes stay readable by whoever was already granted them, and the handover happens before the next email does. No new access is created behind anyone’s back.
Checklists follow a job to the end
Each step names what has to happen, what counts as done and how long it may take, then watches the mail for the thing that closes it. A step that overruns is overdue against the job, not against a person.
What it will not do
No timesheets, no utilisation targets, no story points, no burndown, and no ranking of people against each other. It is not a project management tool and does not try to be one.
Fair questions
Neither, quite. A task here exists because something arrived — a message, a document, a date — and it keeps the link back to that thing. A task manager asks you to type work in; this one is a by-product of work already happening.
Probably, for the conversation that is genuinely conversation. What moves here is the part that should not have been in chat: a question about a specific job, with the job attached, so the answer is findable next month.
You can see the state of the work: what is open, what is overdue, what is stuck and on whom. You cannot see screens, keystrokes, idle time or anything a person did outside OVIOO, and that boundary is not configurable.
They stay on the job, because they were never only in that person’s list. Reassignment is a decision somebody makes, not a scramble to find out what was open.
See it around your own mailbox.
Connect the email you already have and watch the structure appear. Trial for the whole organisation.