WRITTEN TO BE EXAMINED

Everything your firm wrote knowing a regulator might read it

Risk assessments, conflict checks, intake decisions, exception approvals. This material was written under the assumption that someone external might scrutinise it, which makes it far more rigorous than ordinary internal work.

Check your data Six questions, roughly two minutes.

Written under external scrutinyReasoning stated, not assumedScope agreed against your obligations

THE COMPLIANCE QUESTIONS

What risk functions ask first

Can we license compliance material at all?

That is your determination against your own obligations. We build scope around what you are free to license rather than asking you to stretch it.

These files name clients and individuals.

Identifying fields are stripped as part of preparing the data, before anything is shared onward, and excluded material is simply not in scope.

Would this need regulator notification?

A judgement for your own counsel. What we can say is that no equity or debt is created and the licence is bounded and defined.

What is the material actually used for?

It is anonymized, built into data sets, and supplied to AI labs. Use is bounded by the licence and we do not disclose which labs take what.

WHY THIS MATERIAL IS RIGOROUS

Four effects of writing for a hostile reader

Nothing is left implicit. An assessment that assumes shared context fails the moment an outsider reads it, so the reasoning is spelled out.
Alternatives are addressed. Good risk work states what else was considered and why it was not chosen.
Thresholds are explicit. Decisions reference a standard, which makes the judgement legible rather than intuitive.
Exceptions justify themselves. Anything approved against policy has to argue its own case in writing.

WHAT FIRMS HOLD

Four categories in a compliance archive

Every regulated or professional firm produces these continuously and files them without further thought.

Intake and conflicts

Decisions to take on or decline work, with the reasoning about why a conflict did or did not bite.

Risk assessments

Structured evaluation of what could go wrong and how likely it was, with mitigations proposed.

Exception approvals

Departures from standard policy, each required to explain itself in writing.

Reviews and attestations

Periodic examination of whether the firm did what it said it would, and what changed as a result.

SPEAK WITH A MANAGING PARTNER

The files written for scrutiny are the most rigorous you have

Six questions and a short conversation about where the line falls. Nothing you tell us leaves Polyshares.

Check your data