Why this exists.
Everyone agrees assurance should be joined up. Nobody sells the software that makes it possible without forcing three teams onto one method. So we built it.
Get a walkthrough
Why it exists
Everyone agrees assurance should be joined up. Nobody sells the software that makes it possible without forcing three teams to work the same way.
The other route
Share the list, the plan and the actions. Leave the methods alone.
The usual answer is to put everyone on one methodology. It fails, every time, because a legal duty is not assessed the way an operational risk is, and the people who know that are the ones being asked to change.
So OneView shares only the parts that have to be shared — what is being assured, who is covering it, what was found, what is being done — and lets each team keep its own way of working behind that.
How we work
Three things we would rather be held to than described by.
We show the real thing
Every screen on this site is the working system with made-up data in it. Where something is a design rather than a build, we say so on the picture.
We publish what is unfinished
There is a page listing what works and what does not. You should never have to guess which half of a demonstration was real.
You deal with us directly
Demonstrations, security questions and awkward questions come to the director, not to a sales layer.
Come and break it.
Kago Matambo, Director, Gaborone.
info@oneassuranceview.com
+267 77 199 122
Get a walkthrough