What Verivius actually does

When you log into Verivius you land on a single dashboard. From there everything is one or two clicks away. There is no multi-product suite, no module gallery, no separate applications you switch between. The whole platform is one workspace per service, organised around the rhythm of how a CQC-regulated service actually runs.

On the left there is a navigation rail. The top of the rail is the dashboard. Below that, the lifecycles you use every week: incidents, complaints, safeguarding concerns, risks, safety alerts, statutory notifications, governance meetings, training matrix, staff supervision, the assurance calendar, and the readiness review (which is the surface for Mock Inspection). Below those, the registers and settings. There are no nested menus four levels deep. If you cannot find something, it is one of the items in the left rail.

Verivius does not try to be your electronic patient record. It is not your clinical system. It does not store patient clinical detail. It is the layer above clinical practice that captures what your service does in governance terms: incidents and what you learned from them, complaints and how you responded, training compliance, governance decisions, the trail an inspector samples from.

The dashboard is organised into four zones, each answering a different question. The four zones are deliberate, not a grid of widgets. They reflect how a registered manager actually triages their day.

Small-band tenants see Zones 1, 2 and 4. Standard-band tenants see all four. The band is picked at signup based on staff size and operational shape; the platform adapts what you see based on the answer.

The product's thesis is one sentence: a service that does the work well and keeps an evidence trail an inspector can verify will pass an inspection cleanly. The evidence loop is the mechanism that makes the second half of that sentence happen as a side effect of the first.

The loop has four stages. Every record in Verivius moves through it, whether the record is an incident, a complaint, a meeting minute, a training certificate, or an assurance check.

1. Practice happens. A medication double check is missed. A patient complains about a follow-up call. A safeguarding concern surfaces. A nurse's BLS certificate is approaching renewal. These are the events of a normal working week.
2. Evidence captured as a side effect. The practitioner closest to the event opens the relevant record (an incident, a complaint, a training entry, an assurance check), fills it in, saves. The capture step is two minutes, not twenty. It is the same friction as a paper logbook, only the record is structured, linked, and immediately available to anyone else who needs it.
3. Continuous oversight surface. Captured records flow into the dashboard zones, the registers, the audit trail, and the monthly governance email. The registered manager sees the picture without having to ask for it. Themes emerge across lifecycles; the next governance meeting has its agenda already half-written by what the platform surfaces.
4. Inspection-ready by default. When an inspector asks to see "last quarter's significant events with closed action plans", the answer is one filter on the incidents register. When they ask "show me your decontamination audit log for the past six months", it is the assurance calendar. The work to be inspection-ready is the work you have already done.

This is what we mean by continuous governance. The traditional alternative is inspection prep: a six-week scramble before a known visit, during which paperwork gets retroactively tidied, policies get hastily reviewed, and the team spends evenings rebuilding minutes. Verivius replaces that with a loop that runs continuously and is ready when the visit lands, announced or not.

Each lifecycle is a structured record type with its own register, detail page, event stream, and reporting surface. They share a common shape: an open state, captured detail, a closure with documented learning, and an audit row for every change along the way.

Every write to every record in Verivius produces an audit row. Who edited, what they edited, when, and the before and after values. The trail is captured by a database trigger that runs on every change, so it is not something a developer or a user can switch off mid-write.

The owner-facing audit log lives at /audit-log within the workspace. You can filter by date range, by actor, by action type, and by lifecycle. Each entry expands to show the full before/after payload. When an inspector says "who closed this incident on the 12th?", the answer is in the audit log in seconds.

Verivius staff occasionally access customer data via break-glass support (for example, when diagnosing a production issue or honouring a customer support request). When that happens, the audit row carries a "[Verivius Support]" badge so the owner sees exactly when, what, and by whom. Transparency is part of the trust pitch and we treat it that way at the data layer, not just in the marketing copy.

On the first working day of each month, Verivius sends a monthly governance email to the owner and any additional recipients the owner has named. The email is the system looking at your service and telling you what it saw.

What goes in it: incidents opened and closed in the past month, complaints handled, safeguarding referrals, statutory notifications filed, training compliance, risk register movement, governance meeting attendance, assurance calendar completion, the top three themes across lifecycles. Plus a short narrative summary written by the system, not by us.

You can add other recipients in workspace settings. Each person confirms by clicking a link before they start receiving the email, and each one has their own unsubscribe link in every message.

The email is the proof-of-life signal that the platform does work on its own without prompting. The first time it lands in a new account is one of the platform's activation milestones.

Mock Inspection is a separate commercial engagement (£3,500 per location, eight to ten working days on site, written report, three-month follow-up). The product surface for it is the readiness review lifecycle described above. A Mock Inspection is a structured authoring of a readiness review by an ex-CQC inspector working as a Verivius consultant.

The workflow from your side:

1. Scoping. An initial call with Klaudiusz to agree the location, the dates, the focus areas (if any), and the scoping documents he needs in advance.
2. Fieldwork. Eight to ten working days on site or remote (your call) sampling records, interviewing the registered manager and key staff, walking the premises if on site, observing handover and other team-meeting touch points.
3. Drafting. The readiness review is authored within the platform. You see the draft as it is built, including evidence citations against your own records.
4. Factual correction. You have a week to flag any factual inaccuracies before the report is delivered. Findings are not negotiated; factual accuracy is.
5. Delivered. The final report, the action plan in the platform with assigned owners and due dates, and the three-month follow-up commitment.

A Mock Inspection produces a permanent record in your account. The findings live in the platform; the action plan lives in the platform; the follow-up at three months checks the action plan against current evidence. None of this is a static PDF that gets emailed and filed away.

Mock Inspection in full covers the commercial side: bands, refund policy, what changes if you are also a Verivius Design Partner.

What the platform looks like at three anchor points after you sign up. The shape evolves; the work compounds.

The other half of being clear about what we do is being clear about what we do not. Five negative commitments that propagate through the product as well as the brand.

• Verivius does not guarantee a CQC rating. No software does. We get the evidence trail in order; the rating depends on the underlying practice the trail describes. Any vendor promising otherwise is overselling.
• Verivius does not paraphrase regulation. When the platform surfaces a statutory wording, deadline, or duty, it reproduces the regulator's text verbatim with citation. Paraphrased regulatory wording is wrong wording.
• A Verivius consultant is not a CQC inspector. They may have been (Klaudiusz was, for thirteen years), but they are not now. The consultant's job is to help you read the evidence the way an inspector would.
• Verivius does not replace clinical judgment. No system decides whether a procedure is appropriate, writes a consent conversation, or makes a treatment call. The clinician owns those decisions; the software records the trail of them.
• Verivius does not sell to providers we cannot serve. If our discovery call reveals you are the wrong fit (an NHS trust, an EMR-shaped need, a compliance requirement we do not meet), we say so. Half of discovery calls should end with "Verivius is not what you need yet".

Read the full statement at About / What we will not do.