Stratavue Assurance · pilots opening

Everything checked.
Every finding cited.
Every decision kept.

Give it your documents and the questions you have to answer. It reads all of them, shows the passage behind every finding, and leaves the deciding to a named person.

Ask about a pilotDesigned, not built yet — this page describes how it will work.
The shape

Two jobs have the same shape: read a large pile of documents against a set of questions, then show what you found and who decided. Both are done by hand, on a sample, by people whose time is the constraint.

How it works

Five stages. You start it, you decide, it does the reading.

1YouSet it up, onceYour documents and your checklist go in. Every paragraph is labelled so it can be quoted later.
2Something arrivesA subject turns upA new regulator publication, or the next client file due for review.
3StratavueIt does the readingFinds the likely places, reasons over each one, and drops anything it cannot quote.
4YouYou decideAccept, reject or amend, with a reason. Kept permanently, with your name on it.
5StratavueIt goes somewhereA change record in the pipeline you already use, or a roll-up for oversight.
Throughout: every run reports what it cost, and what the same run would have cost reading everything.
The screen you would live in

One claim at a time, with the evidence beside it

Never “is this map right?” Always “does this document implement this rule, as this sentence suggests?”

Rule 14 of 503 documents proposed · 17 policies linked to nothing · 9 rules unimplemented
The rule

A conduct rule about customers in vulnerable circumstances

“…take into account the characteristics of vulnerability…”

Your document

Vulnerable Customers Policy v3.2

Policies › ConductOwner, from metadata: Head of Conduct Risk
Why it thinks this implements it

“This policy sets out how we identify and support customers with characteristics of vulnerability…” — §1.2

YConfirmNNot this documentAA different documentSSkip for now

An example, not a real rule — no citation on this page has been checked against the Handbook.

Two ways it gets used

Regulatory impact

Change and compliance leads at building societies, insurers, wealth managers and specialist banks.

Hundreds of publications a year against a library nobody has read end to end. The tools that do this properly are priced for firms a hundred times your size.

A pilot gives you three recent publications mapped onto your own policies — each with the passage in the regulator’s text and the passage in yours, plus the rules nothing appears to implement.

File review

Heads of compliance services at adviser networks, consolidators and compliance-support providers.

A 2–10% sample tells you about the sample. Reviewer capacity sets the sample size rather than the risk.

A pilot runs your checklist across a batch of files, then a blind test: your reviewers assess a hundred as usual and we compare. The interesting number is which files the sample would never have reached.

What it is not
Not regulatory adviceIt does not say "compliant". It shows what is affected and the passage that says so; a named person decides what that means.
Not a horizon-scanning feedThere are good ones and this is not one. The work starts after the publication lands, on your documents.
Not a replacement for reviewersA first pass across everything, so judgement goes on the files that need it rather than on choosing which to open.
Not a way into restricted materialDesigned so that what your IT does not allow, the product cannot reach. A pilot runs on documents you hand over deliberately.

Tell us whether this is your problem

Including — usefully — if it is not. Say which of the two it is closer to, and roughly what you do about it today.

Ask about a pilot