Compliance consultants and outsourced MLROs
A compliance monitoring tool for consultants
You build compliance frameworks for licence applicants and run monitoring for firms that do not yet have a full team. Each client has its own spreadsheets, its own folders and its own history. Kompendra gives each of them the same structure.
What gets in your way
- Every client's monitoring plan is in a different workbook, in a different format.
- When an engagement ends, the history often leaves with you, or is lost.
- Licence applications need a documented compliance framework before the firm has any staff to run it.
The modules that matter most
Compendium
Start each new client from maintained requirements, not from last year's spreadsheet.
Monitoring
The same plan structure for every client, with reminders you do not have to track yourself.
Registers
Policies and controls mapped to requirements, with the coverage gaps visible.
Evidence
Evidence that stays with the client's records when your engagement ends.
Setting up a licence applicant in Kompendra
Day one. You set up the client’s entity and the licence it is applying for. You work through the compendium and mark each requirement applicable, not applicable with a reason, or under review.
The framework. You upload the draft policies and map them to requirements. Kompendra suggests mappings, quoting the passage that supports each one, and you accept or reject them. The coverage view shows what is still missing.
The plan. You build the first monitoring plan from the applicable requirements and the control library. Every test has an owner and a reviewer, even if both are you for now.
Handover. When the client hires its own Compliance Officer, the plan, the evidence and the full audit trail are already in the client’s own Kompendra. Nothing needs to be handed over, because nothing was kept elsewhere.
Each client firm has its own Kompendra with its own data. TODO(Miles): confirm how consultant access across several client firms works, and any partner or referral terms