Five of six are software.

A combined assurance programme needs six things in place. OneView is the system for five of them. The sixth is your people, and it gets easier once the other five stop fighting them.

Get a walkthrough

What a programme needs

The same six elements show up in every serious account of combined assurance. Here is what each one means in practice, and what the system does about it.

Element	What it means	What OneView does
Strategy	Assurance effort pointed at the risks the business actually cares about.	One register, rated and owned, that every team plans against.
Framework	Clear roles, responsibilities and accountabilities.	Roles and permissions enforced in the system — preparer, reviewer and approver cannot be the same person.
Methodology	Agreed ways to plan, do and report the work.	Each team keeps its own. What they produce still maps to the same record.
Plan	Top risks linked to the controls and the reviews that cover them.	One annual plan across every team, measured against coverage, with the gaps named.
Reporting	A clear read on how well risk is being managed.	Findings, ratings and actions captured as the work happens, so the pack is a review not a rebuild.
People	Assurance providers with the skills to work this way.	Not software. This one is yours — but the system stops being the reason it is hard.

The shared register in OneView: every assessable unit with its type, how critical it is, and who owns it. — The register. One list of everything that needs assuring — and the thing every other screen hangs off.

What the plan and the actions look like

Two of the screens a head of assurance actually lives in — coverage against the register, and everything still outstanding.

Assurance coverage

60% of the register · target 75%

Covered 6

Not covered 4

4 units with no assurance planned

Actions, every team

Action	Provider	Due
Vendor bank-detail callback verification	Risk management	68d overdue
Segregation of duties, payroll approval	Internal audit	14 Dec
Pre-processing approval of pay-rate changes	Internal audit	Closed

Your teams do not have to agree on a method. They only have to agree on what is being assured. OneView holds that, and lets the rest differ.

On an ordinary day

Most people only ever touch two screens: the work in front of them, and what is overdue.

An auditor

Opens their engagement, records what was tested and attaches the evidence. The rating follows from the results rather than from a dropdown.

A control owner

Sees what is assigned to them and what is due, and closes it with proof instead of an email saying it is done.

A head of assurance

Sees coverage, gaps and overdue actions across every team, without asking anyone to prepare anything first.

An engagement report in OneView, with its findings, their ratings and the report preview. — And the end of it: findings with their ratings, and the report they go into — built from what was already captured.

See it on your own register.

Forty-five minutes on the working system, and a straight answer on what is finished and what is not.